Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CBA Settings has greyed-out MISSION tab in 3DEN #865

Closed
freghar opened this issue Dec 31, 2017 · 3 comments · Fixed by #893
Closed

CBA Settings has greyed-out MISSION tab in 3DEN #865

freghar opened this issue Dec 31, 2017 · 3 comments · Fixed by #893
Assignees
Milestone

Comments

@freghar
Copy link

freghar commented Dec 31, 2017

Arma 3 Version: 1.80 (stable)
CBA Version: 3.5.0 (stable)

Mods:

- CBA_A3
- ACE3 v3.12.0

Description:

  • In some cases (which turns out to be most cases for me), the MISSION settings tab is greyed out, making me unable to set the mission settings - https://i.imgur.com/n33NQ5d.jpg .
  • Even though the screenshot shows extra mods used, I tested it with just CBA and ACE3 and then with CBA only, with new missions (both via the "New" button in 3den as well as loading the mission via arma3.exe cmdline), with existing missions, with a clean Arma 3 profile, with and without -world=empty -nosplash, after a mission preview, after MP preview, and so far I cannot get a reliable reproducer - I can edit the MISSION tab in ~10% of random cases, usually when loading an existing mission via arma3.exe cmdline.

Where did the issue occur?

  • Editor (Singleplayer) / Editor (Multiplayer)

RPT log file:

@freghar freghar changed the title CBA Settings has greyed-out MISSION tab in most cases CBA Settings has greyed-out MISSION tab in 3DEN Dec 31, 2017
@commy2
Copy link
Contributor

commy2 commented Dec 31, 2017

You have to save the mission first. Otherwise there is no mission.sqm to save the mission settings to.

@commy2 commy2 added the Question label Jan 2, 2018
@freghar
Copy link
Author

freghar commented Jan 5, 2018

Thanks, saving the mission under some name indeed seems to work, regardless of whether there are further modifications or not.

But why? As far as I can tell, CBA seems to be using

set3DENMissionAttributes [["Scenario", QGVAR(hash), _settingsHash]];

which should AFAIK just work regardless of whether there's a physical mission.sqm file or not - the attributes get saved to memory anyway.

For example:

  1. create a new mission, don't save it
  2. "Scenario" get3DENMissionAttribute "cba_settings_hash" returns ["#CBA_HASH#",[],[],any]
  3. do set3DENMissionAttributes [["Scenario", "cba_settings_hash", ["#CBA_HASH#", ["ace_advanced_ballistics_enabled"],[[true,true]],any]]];
  4. "Scenario" get3DENMissionAttribute "cba_settings_hash" returns what was set in previous step
  5. save the mission to "refresh" the CBA settings UI logic
  6. load the mission, open CBA settings UI, see ACE Advanced Ballistics enabled

The "simpler" single-attribute set3DENMissionAttribute should work the same (not tested).

@commy2
Copy link
Contributor

commy2 commented Feb 8, 2018

Will look into improving this behavior.

@commy2 commy2 added this to the 3.7 milestone Feb 8, 2018
@commy2 commy2 self-assigned this Feb 13, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants