310 Redux won't save/load in ground scenario properly

[JNS]

Hi. I've tried everything I can think of, but I can't get the 310 Redux (or 310R) to save properly if saved in a ground position, such as at the beginning of a runway. I am running P3D v.3.2.3 and 310 Redux v3.180510 SP3.6. I start from the Prepar3D Scenario Setup screen and change vehicle to 310 Redux. I load the scenario with plane at the beginning of the runway with engines running (and BTW, the chocks and pitot covers are there, too). I remove the chocks and pitot covers and save as TEST 1. Next, I end the scenario (or exit and restart P3D), load TEST 1 from Scenario Setup screen and when the scenario loads the engines are stopped and the chocks and pitot covers are there again.

Now, if I do the same test and actually get the plane into the air prior to saving the scenario, then I end the scenario and reload it, everything is as it was with the plane in the air (engines running) exactly like I saved it.

I tried this with two default planes and I don't have this problem. I don't recall anything in the past happening like this either, but maybe I'm just missing something here.

Any help with this would really be appreciated.

Thanks,
Jeff Smith

[ThomasAH]

Can you verify if you have selected "Cold&Dark" in the MV-AMS? If yes, that's the purpose of this switch. If no, further investigation is needed.

[JNS]

Thanks for the reply. No, I do not have Cold and Dark selected. Sorry, I should have included that info before. That's part of the mystery. When I first choose the 310Redux and load it, the engines are running as expected. It's after removing the chocks and covers and saving that scenario and reloading it, the engines are stopped and chocks and covers have reappeared. I have edited my first post to try and clarify that more for future readers.

I'm beginning to wonder if this is related to the problem mentioned in the thread titled "Chocks still attached".

Jeff

[N4GIX]

Simple cause and effect at play. MVAMS and the C&D or RTF options ignore the "saved scenario" settings. The initialization routines we use are very complex and override the sim's default parameters.

[JNS]

Thanks for the reply(to both of my posts), Bill, but that still leaves the problem because I do not have C&D selected. Based on what you said, if I understand correctly, I am still confused. How can I save a scenario (where the plane is on the ground, engines running) and reload it with the engines still running? And again, there is the fact that saving the scenario after the plane gets in the air presents no problem when reloading the saved scenario. I'm not sure why it makes a difference whether the plane is on the ground or in the air when saving a scenario. Basically, I'm just trying to save a ready-for-takeoff (engines running) scenario at a certain airport, but can't seem to do it.

Thanks again.

Jeff

[fppilot]

And you are completely successful with other aircraft models? Strange. I have (3) saved 310 Redux flights in FSX, each at a different airport, and all work flawlessly. Wonder what else could be a play here.

[JNS]

Yes, fppilot,last night I tried with two default aircraft and when I reload the scenario everything is fine, engines running and ready for takeoff. I'm beginning to wonder if there is something going on between my version of P3D (v3.2.3) and this particular plane. It definitely is baffling to me. I hope I'm not missing something so simple that I end up looking like a fool (I've been at this for quite a few years). LOL I've tried to be very careful testing and retesting.

Thanks for your reply,
Jeff

[JonathanBleeker]

The setting in the AMS is persisting correct?

One question I would have then is if your P3D is set to run as admin. It might be prevented from reading the AMS file.

[JNS]

Thanks, Jonathan. Yes, every time I have looked at AMS the Cold and Dark box is unchecked. Also, I always run P3D as administrator. One other thing I just thought of is that (only sometimes) when I reload the scenario the props are still turning slowly and then stop. I've checked to make sure that my throttle and mix controls were set OK to keep engines running to eliminate the possibility that I had accidentally pulled the throttle to zero or mix was set too lean before loading. I have checked the controls calibration, but I will test again with that in mind just to make sure.

Jeff

[JNS]

OK, ladies and gentlemen. The plot thickens. After loading my saved scenario (Test 1) I happened to look up at my Add-Ons menu at the top of the screen and see 310R(not 310R Redux) and it says "Load: Cold and Dark" with no option to change it from there. MVAMS show Cold and Dark unchecked. Also, as I look at the instrument panel it's not really Cold and Dark. Avionics are on and all electronics such as battery, magnetos, etc. are on. Just the engines are not running. I remove the yoke to see switches, , hit the START switches for engines and they start. So, I thought maybe if I RESAVE now (after I started engines manually) under the same name (Test 1, overwriting the original Test 1) maybe this would work. I do this and then I End scenario and Load same scenario (Test 1). This time it works properly. Sooo, I Exit P3D, restart P3D, Load Test 1 from the Scenario Setup screen, and everything is fine (engines running). BUT, it's not consistent. Tried it all over as described above and saving as "Test 2" and it didn't work like the first time.

Soooo, I guess it kinda boils down to (1) Why does the Add-Ons menu show the 310R as "Load:Cold and Dark" while MVAMS shows Cold and Dark unchecked? AND (2) why won't things work correctly after my first attempt at saving the scenario immediately after creating it?

If all else fails, I can always just manually start the engines after loading the scenario, but I would like to get it working properly anyway, if possible.

Thanks very much for all your suggestions so far,
Jeff

[N4GIX]

Did you keep the original C310R installed? It sounds as though you are loading that version instead of the C310R Redux...

[JNS]

Thanks, Bill. Yes, I did keep it installed, but I'm definitely loading the Redux version in this situation. I had left it there because I figured it and the 310 Redux were two separate products and it wouldn't matter. But, I thought about this last night after I saw what was in my Add-Ons menu, so I uninstalled the original 310R version. But, it didn't seem to do any good. I think maybe now I will uninstall/install the Redux version just in case there was some interaction with the old version when I installed Redux.

Also, after having some inconsistencies in my testing last night and doing some internet research, I stumbled upon the fact that some people were definitely warning against loading the same aircraft on top of itself. At the time I was actually searching for the possibility of my version of P3D having some kind of quirk in saving/loading. And I have been ending a scenario and then reloading the same scenario in my tests....sometimes. Other times I was actually closing down P3D and restarting it before I loaded a saved scenario. But, now I'm wondering if that could be what's happening here. I'm sure I've done this in the past years, but maybe just got lucky. Milviz may have warned me of that possibility and I missed it. I'm going to do my tests again with this in mind.

BTW, thanks for making your planes easy to install and uninstall.

Thanks,
Jeff

[JNS]

Well, I'm happy to report that apparently the fact that I was "loading the aircraft on top of itself" was causing the problem. I tried Ending my test scenario, Loading the default scenario, Ending default scenario, and then Loading the test scenario and everything worked like it should. But, I still show the 310R "Load: Cold and Dark" indication in my Add-Ons menu while "Cold and Dark" is unchecked in MVAMS. Don't know what is going on there, but the rest is working. Should uninstalling/reinstalling 310R Redux take care of the Add-Ons menu issue? I really don't want to uninstall/reinstall Redux at this point if it won't take care of the Add-Ons matter. I can live with it.

Thanks VERY much to all who assisted in helping me with this.

Jeff

[JNS]

Bill, just noticed chocks and pitot covers are still there with engines running, so I guess I will re-install v. 3.180510 SP3.6 after uninstalling it first.....unless you have another idea. I'm running P3D v.3.2.3 .

Thanks,
Jeff

[doodlebug]

Officially only the latest version (v3.4) is supported