Some things not saving?
Posted: Tue Sep 24, 2024 12:48 pm
Custom scenario - latest stable build (1328.18) with DB3000v505 database
(Can't seem to be able to post a .scen file on this forum -- only accepts images)
As I also mentioned in the feature poll thread, I've had a issue where, when I first started this scenario on Sep 7th 2024, a Burke-class and a Freedom LCS class were able to load small cargo type objects, and I, in fact, loaded them with containers to emulate crew supplies and mission supplies. Then, the other day, this functionality was changed to them only being able to load personnel size cargo, which means, not only they are not able to load containers with supplies (despite their enormous cargo holds) but they're also not able to interact with the containers already present onboard (transfer them to a helicopter, for example etc)
That was one of a few oddities I've noticed in the past few days, since I Sept 7th when I started the scenario. I was suprised to notice all these "bugs" (not sure if they are in fact bugs, or some error on my part, but they seem to be some kind of bug resulting from some update or hotfix I am not aware of during this time period)
The latest problem I've noticed is the incapacity for Custom Environment zones to retain their layer order. Again, up until a few days ago, this worked just fine, and the CEZs were saving and loading back to their correct layers. Now, I load up the scenario and the CEZs are all reset to layer 0. Map Display settings also dont get saved properly -- I work mainly with Topo map overlay, to get all the urbanization and google-like geography info that I need for general management. When I load up the scenario, now, it defaults to off, and I have to turn it back on, whereas, when I first started playing this scenario on Sep 7th, it was loading back just fine.
And so on, with a few other issues I've noticed but forgot, thinking they would be minor issues related to the scenario maybe being corrupted or something. So I created a whole new scenario and ported the stuff (using import units) and adding whatever I couldn't port back to the new scenario. A whole 24 hours of work, and nothing seem to have improved. I also noticed that, since I had starfted the Sept 7th scenario, the "weather affects aircraft sorties" started prompting a warning message about scenarios being built prior to this feature being introduced might present weird aircraft behavior. That was part of the reason for me wanting to reset the scenario, but I still get the warning message. I just hope this message is there regardless, and not because the sim still thinks the scenario was created prior to the feature introduction.
These things are such oddities that I can only associate to an obscure update that I didn't notice -- I know there has been a new publict beta, but I wasn't subscribed to the beta. As I said, I'm running the standard version. I did in fact try the beta, after seeing these issues, to see if, paradoxically, the beta would be more stable, but it wasn't, and, switching back to standard gave me enourmous Steam validation problems, to the point that it was systematically crashing trying to install back the standard version (I tried on two separate occasions, to make sure it wasn't a one-off error. In both occasions, I had to manually stop the download before it triggered a Steam freeze by immediately putting Steam in offline mode upon starting, then uninstalled CMO and installed it back from scratch. As I said, I tried this twice to make sure it was a recurring error and not a one-off)
My dumb hypothesis? The public beta release somehow also included some alterations to the standard version that made it behave weirdly. Of course, I know nothing of programming and the structure of the sim, so, this is only my random hypothesis, seeing as that's the only variable I can see during the time period since the stable scenario behavior and the current unstable behavior.
I hope we can figure this out
Thank you in advance for the help.
(Can't seem to be able to post a .scen file on this forum -- only accepts images)
As I also mentioned in the feature poll thread, I've had a issue where, when I first started this scenario on Sep 7th 2024, a Burke-class and a Freedom LCS class were able to load small cargo type objects, and I, in fact, loaded them with containers to emulate crew supplies and mission supplies. Then, the other day, this functionality was changed to them only being able to load personnel size cargo, which means, not only they are not able to load containers with supplies (despite their enormous cargo holds) but they're also not able to interact with the containers already present onboard (transfer them to a helicopter, for example etc)
That was one of a few oddities I've noticed in the past few days, since I Sept 7th when I started the scenario. I was suprised to notice all these "bugs" (not sure if they are in fact bugs, or some error on my part, but they seem to be some kind of bug resulting from some update or hotfix I am not aware of during this time period)
The latest problem I've noticed is the incapacity for Custom Environment zones to retain their layer order. Again, up until a few days ago, this worked just fine, and the CEZs were saving and loading back to their correct layers. Now, I load up the scenario and the CEZs are all reset to layer 0. Map Display settings also dont get saved properly -- I work mainly with Topo map overlay, to get all the urbanization and google-like geography info that I need for general management. When I load up the scenario, now, it defaults to off, and I have to turn it back on, whereas, when I first started playing this scenario on Sep 7th, it was loading back just fine.
And so on, with a few other issues I've noticed but forgot, thinking they would be minor issues related to the scenario maybe being corrupted or something. So I created a whole new scenario and ported the stuff (using import units) and adding whatever I couldn't port back to the new scenario. A whole 24 hours of work, and nothing seem to have improved. I also noticed that, since I had starfted the Sept 7th scenario, the "weather affects aircraft sorties" started prompting a warning message about scenarios being built prior to this feature being introduced might present weird aircraft behavior. That was part of the reason for me wanting to reset the scenario, but I still get the warning message. I just hope this message is there regardless, and not because the sim still thinks the scenario was created prior to the feature introduction.
These things are such oddities that I can only associate to an obscure update that I didn't notice -- I know there has been a new publict beta, but I wasn't subscribed to the beta. As I said, I'm running the standard version. I did in fact try the beta, after seeing these issues, to see if, paradoxically, the beta would be more stable, but it wasn't, and, switching back to standard gave me enourmous Steam validation problems, to the point that it was systematically crashing trying to install back the standard version (I tried on two separate occasions, to make sure it wasn't a one-off error. In both occasions, I had to manually stop the download before it triggered a Steam freeze by immediately putting Steam in offline mode upon starting, then uninstalled CMO and installed it back from scratch. As I said, I tried this twice to make sure it was a recurring error and not a one-off)
My dumb hypothesis? The public beta release somehow also included some alterations to the standard version that made it behave weirdly. Of course, I know nothing of programming and the structure of the sim, so, this is only my random hypothesis, seeing as that's the only variable I can see during the time period since the stable scenario behavior and the current unstable behavior.
I hope we can figure this out
Thank you in advance for the help.