Asenna Steam
kirjaudu sisään
|
kieli
简体中文 (yksinkertaistettu kiina)
繁體中文 (perinteinen kiina)
日本語 (japani)
한국어 (korea)
ไทย (thai)
български (bulgaria)
Čeština (tšekki)
Dansk (tanska)
Deutsch (saksa)
English (englanti)
Español – España (espanja – Espanja)
Español – Latinoamérica (espanja – Lat. Am.)
Ελληνικά (kreikka)
Français (ranska)
Italiano (italia)
Bahasa Indonesia (indonesia)
Magyar (unkari)
Nederlands (hollanti)
Norsk (norja)
Polski (puola)
Português (portugali – Portugali)
Português – Brasil (portugali – Brasilia)
Română (romania)
Русский (venäjä)
Svenska (ruotsi)
Türkçe (turkki)
Tiếng Việt (vietnam)
Українська (ukraina)
Ilmoita käännösongelmasta
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.