License problem

[JonathanBleeker]

When I meant remove references to it I meant not only comment out in the panel cfg but make sure there aren't any in any of your panel folders.

[Fowlie]

When I meant remove references to it I meant not only comment out in the panel cfg but make sure there aren't any in any of your panel folders.

I checked all the /panel folders and none of them contain any milviz_sound files.

Just to be clear, I'm checking in the \prepar3d\simobjects\rotorcraft\milviz_MD_530\panel.* (where panel includes all the panel.fr, panel.gns, etc.)

I don't know what else to try... Did it ever work?

Unfortunately it hasn't ever launched successfully.

[Fowlie]

So I've come across something that may provide new evidence. The updated milviz_sound.gau file I was sent originally might not be newer than the milviz_sound that was installed with the program.

I'm not coder so this might not even be a reasonable way to determine this, but this screenshot: https://drive.google.com/file/d/0BykmZF ... sp=sharing

Shows the date modified on the downloaded version (left) as slightly older than the file installed(on the right).

[N4GIX]

The one on the left is the correct version. The dates in Properties can be rather misleading since "Date created" does not indicate the actual date the gauge code was compiled, but rather the actual date the gauge was first installed in the folder! Note that the correct version shows 02/28/2017 which presumably is the day you placed the gauge file in the folder...

The "Date modified" on the other hand does show the actual date the gauge code was compiled! Here is a screen image of the Properties of the correct gauge version directly from my compiler's folder. Note the Date Modified is 12/4/2015 8:46 AM:

[Fowlie]

Okay, I've confirmed the milviz_sound.gau file in my /gauges folder is the correct version via the 'date modified'.

My current situation is that I have all of the panel.cfg files edited with the calls to the milviz_sound file commented out, as such from /panel.gns for example:

Code: Select all

//gauge00=Milviz_Sound!FBGS_XMLSound,  0,0,1,1,SimObjects\\Rotorcraft\\MILVIZ_MD_530\\MD530XML_Sounds#53
gauge01=MD530!boot_timer,  2,1,1,1
gauge02=MV_530_STF!STF,  0,0,1,1,0
gauge03=MD530!boot_gns,  1,1,1,1

It's still finding that error somewhere, through windows searches, and old fashioned manual searches I've determined there are no more milviz_sound files located anywhere within my /Prepar3d folder.

[Fowlie]

Then I am now officially baffled, since the error message is contained in that specific gauge module, and if you are still seeing it I sure don't know how!

[/quote]

So there are no other possibilities for a source of this error? It seems weird that I still received it after trying to straight up delete milviz_sound.gau file.

A md-500 came to our FBO today and made me want to fly this module pretty badly.

I appreciate everyone's help, but I'll probably resign myself to the $50 menu placeholder if there aren't any other ideas.

[JonathanBleeker]

Try doing a file search for that dll in all possible locations that your P3D uses?

[Fowlie]

No luck Searched my drives for anything with milviz in the name and only found the same suspect milviz_sound file.

In the interest of at least getting it running, I tried installing it for my FSX:SE install, and it seems to work as advertised. FSX did have a big obvious pop up window when it wanted permission to run milviz_sound.gau and a couple other .dll files that I don't recall off the top of my head. I don't know if that will help diagnose why it won't run in p3d v3 but I thought I'd share. I would much prefer to get it running in p3d if possible.

[N4GIX]

That's normal for FSX & FSX:SE. Any new gauge or .dll file that is "unsigned" will have to be manually approved once by the user when first loaded. That approval (or disapproval) is logged in the fsx.cfg file for future reference.

P3D has removed that silly scheme entirely.