Installer Steam
log på
|
sprog
简体中文 (forenklet kinesisk)
繁體中文 (traditionelt kinesisk)
日本語 (japansk)
한국어 (koreansk)
ไทย (thai)
Български (bulgarsk)
Čeština (tjekkisk)
Deutsch (tysk)
English (engelsk)
Español – España (spansk – Spanien)
Español – Latinoamérica (spansk – Latinamerika)
Ελληνικά (græsk)
Français (fransk)
Italiano (italiensk)
Bahasa indonesia (indonesisk)
Magyar (ungarsk)
Nederlands (hollandsk)
Norsk
Polski (polsk)
Português (portugisisk – Portugal)
Português – Brasil (portugisisk – Brasilien)
Română (rumænsk)
Русский (russisk)
Suomi (finsk)
Svenska (svensk)
Türkçe (tyrkisk)
Tiếng Việt (Vietnamesisk)
Українська (ukrainsk)
Rapporter et oversættelsesproblem
Thanks for keeping the mod updated, cheers.
Edit 2: nvm, ignore if you read the other edit, the bug persists. I didnt realize I was testing it with another mod.
Technically this shouldn't be possible to be caused by my mod. There's no code to begin with to change anything render-related, no layer changes (yet) and only a very few changes to some graphicClass/shaderType related things in a very few mods to fix their inherent 'bugs' with wrong or missing masks. And nothing of that should even be related to pawn-rendering while in bed.
Thing is, the way my patches are working - even if another mod would somehow break mine, that would just mean that the changes (mostly stats) aren't applied and the armor just keeps its vanilla stats & behaviour. There's also no interconnection between features, so one patch breaking wouldn't cause weird behaviour of another one - at least at the moment there shouldn't be any such interconnection.
Long story short; I fail to come up with a good idea what would cause that behaviour.
I'm gonna fire my test-setup here right now to see if I'm missing something stupid, but if it's related to my patches, it clearly has to be a conflict between mine and another mod. Make sure to drop a full Hugslog though - ideally from directly after a pawn went to bed and the glitch happens - I'm really curious what could result in that behaviour.
[img]https://imgur.com/FYSDjs1.jpg[/img]
[img]https://imgur.com/ftgvmZ3.jpg[/img]
Thank you for your time.
Again, sorry for wasting your time, but I'm grateful of your help. Sometimes modding this game is a pain
Did you find out which mod specifically is causing it? I'm curious and it might help if maybe someone shows up with the same issue in troubleshoots.
Yes, it was this one:
https://gtm.steamproxy.vip/sharedfiles/filedetails/?id=2990606008
I informed the author and he was aware of the bug, so all good on that end.
Your answer made me realize I was looking in the wrong place, so it was useful regardless. The thing is, I didn't even know I had this mod activated, which caused me to believe it was yours doing it.
Looking at the mod now, it was pretty obvious.
Cheers mate, thanks for being so collaborative.