Steam telepítése
belépés
|
nyelv
简体中文 (egyszerűsített kínai)
繁體中文 (hagyományos kínai)
日本語 (japán)
한국어 (koreai)
ไทย (thai)
Български (bolgár)
Čeština (cseh)
Dansk (dán)
Deutsch (német)
English (angol)
Español - España (spanyolországi spanyol)
Español - Latinoamérica (latin-amerikai spanyol)
Ελληνικά (görög)
Français (francia)
Italiano (olasz)
Bahasa Indonesia (indonéz)
Nederlands (holland)
Norsk (norvég)
Polski (lengyel)
Português (portugáliai portugál)
Português - Brasil (brazíliai portugál)
Română (román)
Русский (orosz)
Suomi (finn)
Svenska (svéd)
Türkçe (török)
Tiếng Việt (vietnámi)
Українська (ukrán)
Fordítási probléma jelentése











I spent at least 3 hours trying various configurations. At least it made me optimize the code somewhat :D.
I think what happened with Uncle, is that he caught my mods mid-update on workshop, and I will not know better until he comes back with more information.
- 1.5 or 1.6
- What mods are enabled
- What errors do you see if you enable DevMode and press Console
I just tested and it seems to work fine on my end:
1) RimTek DigiPal-equipped pawn: https://i.imgur.com/JgzRsZr.png
2) Hurt by shooting: https://i.imgur.com/9VqfwIb.png
3) No errors: https://i.imgur.com/vGGOEsR.png
Just in case, if it's Workshop weirdness, try to unsub and resub to the mods, and relaunch your game.
The only idea I have is that maybe the fact that I updated Core and underlying mods synced with your activity on PC and workshop messed it up for you locally.