User Details
- User Since
- Jan 24 2023, 6:39 PM (95 w, 2 d)
Wed, Nov 13
Wed, Nov 6
Sat, Nov 2
Thu, Oct 31
Version: Both current Stable and Exp (, 1.2.1.127)
Modded: No
Reproduction:
- Drag in Character_USSR_SR
- Find the entity labels in the EditableCharacterComponent under Visualization->UI Info.
- You can see that it has the ROLE_RIFLEMAN role, not ROLE_LEADER.
Oct 5 2024
Sep 24 2024
Sep 2 2024
Jul 18 2024
Even though I didn't see anything in the changelog, 1.2.0.92 appears to have resolved this issue.
Jul 15 2024
Jul 8 2024
Jul 5 2024
Jul 2 2024
Jul 1 2024
I looked into this issue, it appears that 1.2 broke the way terrain bounds are calculated.
Meaning when you create a new terrain or resave an existing world entity, the terrain bounds will break.
Reproduction is as simple as it sounds, just create a terrain larger than the default bounds (~3000m) and try to move the camera beyond it.
Jun 27 2024
Jun 22 2024
Jun 19 2024
Jun 11 2024
Jun 10 2024
Jun 5 2024
May 24 2024
This appears to be fixed.
May 16 2024
May 11 2024
May 7 2024
Apr 30 2024
Mar 31 2024
Mar 20 2024
Correction, this is only the case for the official worlds, not all read-only worlds - so likely just a part of your publishing process.
While it would still be useful to preserve these layers (both as reference material and for making derivative content), this is not actually a technical issue and can be closed.
Mar 15 2024
Mar 13 2024
Feb 28 2024
Feb 3 2024
Jan 30 2024
Jan 28 2024
Jan 26 2024
Thanks!
Do you know if this will be supported in the future, or not at all?
Jan 25 2024
With "potentially log the specified addonList" I just meant the message printed in GetGame().PlayGameConfig(), a function which calls RequestScenarioChangeTransition().
It's not actually relevant to the problem other than that it confirms I did not just accidentally give it the wrong input. Apart from that, nothing is logged either way.
But here's some detailed info on how to replicate the problem:
Jan 23 2024
Jan 21 2024
Dec 7 2023
Any updates on this?