MVAMS Error Message

[DorkfishFlokie]

Hi there,

Hopefully you can assist with a persistent issue I experience regarding the MD530 and its MVAMS.
Just noting: I have exactly the same issue with the 407, just decided to post it here for now, since I expect the same solution to both cases.

My issue is very close to the case here, which has been resolved, yet, with a couple of differences:

https://milviz.com/forum/viewtopic.php?f=107&t=9070

First - my MD530 is working just fine in my sole simulator FSX (SE). So does the 407 by the way, as explained above.

But whenever I want to use the MD530's MVAMS, resp. the 407's, I get the following error message.
MVAMS does start, but as soon as I select the MD530 or 407, the error message pops up:



I have administrator rights, tried it with virus scanner off and on (Norton), reinstalled several times, all to no avail.
MVAMS just won't work properly for my two MilViz copters.

Side fact: MVAMS has worked in the past and then just suddenly stopped to do so for the choppers - noteably with no change to the sim.

The funny thing: I also have the DHC-3 Otter and it works perfectly fine.

Since the other case posted above was resolved, should I go ahead and try the solutions stated therein?
Or are they somehow only applicable to P3D, since that is that other user's sim of choice?

Since I am unable to adjust any of the MVAMS settings, but would like to do so every now and then, I would very much appreciate your support in solving this issue.

Thanks for your response and effort already in advance.

Flo

[JonathanBleeker]

Did you install into multiple simulators or add any liveries recently?

[DorkfishFlokie]

Hi Jonathan,

I only have FSX (SE) installed and I have not added any liveries for either one of the choppers. Neither did I install any other repaints for different aircraft recently.

And I just can not wrap my head around the fact, that the Otter is working perfectly fine for no good reason. Seems like me FSX is kind of anti-chopper for some reason...

While it is nice, that I can still fly the MD530 and the 407, I really would like to be able to adjust the avionics, attachments, etc. - no clue why it suddenly stopped working. The only two changes to this PC recently really where a (dreaded) Win 10 update and I think there was a Steam update on FSX a little while back. No idea, if they could be the culprits with that kind of error.

[JonathanBleeker]

Regarding your admin rights, those aren't always the same as right clicking on the MVAMS, selecting properties->Compatibility and making sure Run this program as administrator is checked. Please verify that. Your Win10 update might have messed with it.

[DorkfishFlokie]

Unfortunately, that is not the issue, Jonathan. I had it set properly.

I really am not quite es cross with Win 10 as many people are. It does provide me with noticeably improved gaming performance and stability over older systems. The only thing I absolutely despise, are the constant updates. Aside from the fact, that the prior appreciated performance increase goes to hell, whenever an update uninvitedly sneaks in through the backdoor, every now and then they really mess stuff up.

Anyway, I have noticed something, while probing around for a while longer. While there is absolutely no way to get MVAMS running for the choppers while FSX is offline, once I actually start up FSX, if I pick either the 530 or 407, I can now suddenly access their MVAMS. Curiously this was not the case a couple of weeks back, when I tried the same. Maybe another in-between Win 10 update half-way-fixed things?!

Joke aside - at least now I have a workaround to get to my desired options. Yet, of course, this is no real fix. But maybe this information can provide a hint to the final solution? What do you think?

[JonathanBleeker]

Sounds like a file handle was not released for some odd reason. Will investigate.