Post by transportfan2014 on Jun 24, 2020 5:59:55 GMT
Hello, Having recently tried the Mercure, while it functioned normally, an issue that happens to me whenever I reload a previously saved flight involving the Mercure (when the plane is in mid flight), whereby the plane went into cold and dark status as soon as I loaded the saved session. Did all I could think of, but I could do nothing other than watch the plane plunge to the ground. Any insight would help, thanks.
Post by aerofoto - HJG Admin on Jun 24, 2020 8:06:19 GMT
She short answer to this is ....
The MERCURE represents some "pretty complex FS engineering" .... and although FS will generally load some instrument settings from any previous (not saved) flight after a normal shutdown, restart, and later return to FS .... a lot of the MERCURE's engineering likely won't work in the case of attempted "saved flights".
Solution: Don't use the MERCURE as part of any "aaved flight scenario".
Post by transportfan2014 on Jun 24, 2020 15:11:23 GMT
I am an FSX user, btw.
Regarding the remote possibility of the sim crashing, it does happen, but only when I use the right mouse button very frequently (usually to switch from cockpit to outside view and vice versa, and to engage the mouse yoke option for steering). To prevent this from happening I only use the yoke until just after I retract the landing gear, then I pause the sim, and from this point on I only fiddle around the AP panel until the plane is close to touchdown.
I have no idea what causes the sim to crash occassionally, but it tends to happen whenever I click my right mouse button/upper menu bar too frequently. Which is why I tend to save my flights as well. To prevent my simulator from crashing, I try to minimise the number of times I switch between 2D panel/VC panel/exterior views.
As I rarely use keyboard commands to switch views during one session, I have no idea if switching views without using the menu bar causes the sim to crash, though.
Post by aerofoto - HJG Admin on Jun 24, 2020 19:32:47 GMT
There's nothing wrong with the MERCURE simulation/s (not suggesting anyone's implying there is ) .... and that's in regard to either its FS2004 and FSX version/s.
This simulation's been available here since 2017 .... and since that time new features have been developed and added to it and which have only further improved it .... the last of which were applied during December 2018 and as is stated within the manuaI compiled for it.
I once again repeat .... "The MERCURE simulation is composed of some fairly complex engineering/programming and as such saved flight scenarios ARE NOT recommended".
Saved flight scenarios are not recommended for some simulations .... simply because such can result in data retrieval/processing problems in regard to some features represented within certain panels (this once applied to the HJG B707 panels too .... and may still apply).
The MERCURE simulations are intended to be used for any flight/s within any FS session. They can be paused without problems .... but .... not necessarily saved without "potentially" inducing problems. Apart from this minor limitation there's no known issues associated with these simulations .... at least none that are determined to be in need of fixes.
As I've stated within my MERCURE manual .... the MERCURE's a stand-alone product/simulation and can only be used "as-is"/as supplied. It's panel/gauges and sound pack "CANNOT" be swapped/exchanged for other alternatives or the simulation simply "WILL NOT" function .... so .... don't ever try to import other options should one ever feel the least bit adventurous/tempted to try'n do so.
Mario's produced "a very advanced simulation" .... to the extent its really considered for use by "advanced FS users" only (not suggesting, in the least, that you're not, but, people do need to be aware of this right from the very start ).
The best way to try'n avoid any issues is simply .... "don't attempt to do what we advise shouldn't be done"