Page MenuHomeFeedback Tracker

Custom ORBAT Markers Disappear on Mission Load
New, WishlistPublic

Description

Just as the summary states, custom ORBAT markers (stated in the description.ext) disappear on mission loads. The icons are present, but the information is not there when you click on them.

Details

Legacy ID
1717477358
Severity
None
Resolution
Open
Reproducibility
Always
Category
Visual-GUI
Steps To Reproduce

Add some custom ORBAT entries into your description.ext and place them in the editor via the ORBAT modules. You'll see that they work fine when you start the mission and during the mission. Now save the mission and load it. The information in the ORBAT screen has disappeared.

Event Timeline

Bohemia edited Steps To Reproduce. (Show Details)Oct 17 2014, 11:33 PM
Bohemia edited Additional Information. (Show Details)
Bohemia set Category to Visual-GUI.
Bohemia set Reproducibility to Always.
Bohemia set Severity to None.
Bohemia set Resolution to Open.
Bohemia set Legacy ID to 1717477358.May 7 2016, 7:38 PM
Bohemia added a subscriber: Bohemia.May 7 2016, 7:38 PM

Any update or news on this one? :)

Please assign this. I can't get my custom Orbats to show after loads :(

ORBAT markers are still disappearing on mission loads - does anybody know of a workaround?

ORBAT markers disappear on mission load when defined through the description ext. Not sure if similar happens through an fsm.

The modules appear on the map but they disappear when you click on them, really weird. Almost as though the description isn't getting read properly.

I wonder if a loadMission eventhandler could fix the issue somehow? Not sure how one would define the path again in the ORBAT module though...

Still not working for me. can they assign this one?

Ok, so I've actually succeeded in creating an ORBATcfg.FSM which works - however, the load mission bug is still failing. It seems it can't find the textures, whereas on the first time playing, it works fine. Apparently, it doesn't matter if you define the ORBAT in the description.ext or via an FSM, it's not being read in-game after a mission load.

I would suppose the reason BI's ORBAT works is because it's hardcoded? Eg. It's part of the game. Unless you defined your ORBAT as part of a mod I don't think it'll work on loading your mission. This really should be fixed - effectively, the ORBAT system isn't working for mission makers.

R_Marx added a subscriber: R_Marx.May 7 2016, 7:38 PM
R_Marx added a comment.Mar 4 2015, 5:54 PM

I have noticed this problem. Upvoted.

I agree. Unfortunately it seems, for now, ORBAT is out of commission. At least it is if you need to save the mission at some point!

Any chance of assigning? ORBAT's pretty broken.

Going to try this out on Dev branch tomorrow - you never know, may have already been fixed?

Ok - so it's still not working on Dev either.

Has anyone got this working yet? ORBAT and saved games = broken!

Any news on a fix for this? :) Or does anyone have any ideas for some sort of workaround?

Someone please assign this. please, please!

Going to attempt an addon with the ORBAT config in - should make a difference!