quote:

ORIGINAL: KnightHawk75

So basically if you create and or re-save a scenario in the newer builds, the problem should not happen, the check box for both should be enabled by default, and should be properly saved.

But to correct an existing scene, I believe one must load the scenario, enable the checkboxes where needed\desired and re-save. So other than scenarios the developers themselves publish I'm not sure how they could universally fix it (without also erroneously overriding what might be a scene authors actual choice to have disabled changing it - rare but it happens).

quote:


local sides = VP_GetSides()
for k,v in ipairs (sides) do
local side=VP_GetSide({side=v.name})
ScenEdit_SetDoctrine({side=v.name}, {weapon_control_status_land_player_editable=1})
print ('>>> '..side.name..' Side Doctrine Fixed...')
for each,mission in ipairs (side.missions) do
ScenEdit_SetDoctrine({side=v.name, mission=mission.name}, {weapon_control_status_land_player_editable=1})
print ('... '..mission.name..' Mission Doctrine Fixed...')
end
print (side.name..' Doctrine Fixes Completed <<<')
end

quote:

ORIGINAL: apache85

Hey ronmexico111,

For context, there was a bug that marked WCS-Land as non-player editable. Because of the way scenario files work, this affected any file saved with an affected version--a pretty big deal.

We've corrected the issue that caused this, and as part of support for official scenarios we have included fixed versions with the latest update.

Unfortunately any save file created with an affected version will retain this problem until (with a post-fix version of the game) the file is opened, the options changed and the file is re-saved.

To make this easier for players with a large amount of personal scenarios, I've written a small Lua script to automate the process. If you have lots and lots of scenarios to apply this to, please let me know and I'll help you to apply it as a batch.

quote:


local sides = VP_GetSides()
for k,v in ipairs (sides) do
local side=VP_GetSide({side=v.name})
ScenEdit_SetDoctrine({side=v.name}, {weapon_control_status_land_player_editable=1})
print ('>>> '..side.name..' Side Doctrine Fixed...')
for each,mission in ipairs (side.missions) do
ScenEdit_SetDoctrine({side=v.name, mission=mission.name}, {weapon_control_status_land_player_editable=1})
print ('... '..mission.name..' Mission Doctrine Fixed...')
end
print (side.name..' Doctrine Fixes Completed <<<')
end

quote:

ORIGINAL: KnightHawk75

So basically if you create and or re-save a scenario in the newer builds, the problem should not happen, the check box for both should be enabled by default, and should be properly saved.

But to correct an existing scene, I believe one must load the scenario, enable the checkboxes where needed\desired and re-save. So other than scenarios the developers themselves publish I'm not sure how they could universally fix it (without also erroneously overriding what might be a scene authors actual choice to have disabled changing it - rare but it happens).

quote:

ORIGINAL: apache85

The fixed files are available for download here.

Important Note: These files work fine in C:MO, simply follow the instructions in the readme.txt file. However for C:MANO the briefings for these files are not readable--which is why we've held off applying them as an official update. We're working on fixing that and the files will be out in an official update as soon as possible.

These files should be considered beta versions with the standard disclaimers; I recommend backing up your current Scenarios folder before extracting the .scen files from the linked archives.

quote:

ORIGINAL: ronmexico111

Thank you for that. Please note though that there still is an issue with the BVR engagement behavior (is still locked) and also the tutorial folder still uses the CMANO file structure so at least in CMO those files need to be copied into their correct folders.

quote:

ORIGINAL: apache85

Try again with the new files at the same link; these should work for CMO and CMANO respectively. Let us know if there's any further issues.