• There seems to be an uptick in Political comments in recent months. Those of us who are long time members of the site know that Political and Religious content has been banned for years. Nothing has changed. Please leave all political and religious comments out of the forums.

    If you recently joined the forums you were not presented with this restriction in the terms of service. This was due to a conversion error when we went from vBulletin to Xenforo. We have updated our terms of service to reflect these corrections.

    Please note any post refering to a politician will be considered political even if it is intended to be humor. Our experience is these topics have a way of dividing the forums and causing deep resentment among members. It is a poison to the community. We appreciate compliance with the rules.

    The Staff of SOH

  • Server side Maintenance is done. We still have an update to the forum software to run but that one will have to wait for a better time.

Milviz F4J crash in P3d

gray eagle

gray eagle

SOH-CM-2025
Anyone that has the Milviz F4J and installed it to P3D have it crash? I can install it to P3D V3.4 and see the liveries, but as soon as I choose one P3d goes belly up and that's pretty much our show.

There is some kind of a configuration program that installed to the desktop and I guess you configure the controls and other things. I really didn't mess with that part.

So, I have installed it twice and it crashes, twice.
 
gray eagle said:
Anyone that has the Milviz F4J and installed it to P3D have it crash? I can install it to P3D V3.4 and see the liveries, but as soon as I choose one P3d goes belly up and that's pretty much our show.

There is some kind of a configuration program that installed to the desktop and I guess you configure the controls and other things. I really didn't mess with that part.

So, I have installed it twice and it crashes, twice.
Click to expand...

They issued a patch yesterday for the latest version of P3D. You should have gotten an email with the download.
 
I ran the patch.. same issue.. crashes on load up..
i did notice.. unlike previous patches.. it doesn't give you the option to uninstall the previous build..
Anyway.. it's still broken in my machine
 
I may just may of discovered the problem. I did an event viewer to see what was going on in P3d when it crashed. It seems like a file named MV_F-4J_Sys.dll (in the gauges folder)
may be causing the problem- At least for me. I renamed the file with a different extension and then tried it and after a few times of getting it to work in P3d it seems to be more stable.
I did note that the nose gear will not swivel left/right in a turn. It stays locked up in a forward position but the plane will still steer left/right.

I've posted all this over at Milviz; waiting for a comment from anyone over there.
They did ask me to look in my Windows event viewer to see what was causing P3d to crash when I loaded one of their F4's.
For some reason, the gauge file MV_F-4J_Sys.dll came up in the error message, so I got the notion to just disable it and try, what could I lose as it caused P3d to crash anyway,

So, for now with that one gauge file nutralized it works.

Log Name: Application
Source: Application Error
Date: 3/31/2017 3:16:36 PM
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: ijdjr-PC
Description:
Faulting application name: Prepar3D.exe, version: 3.4.22.19868, time stamp: 0x588f7cbf
Faulting module name: MV_F-4J_Sys.dll, version: 1.4.0.8, time stamp: 0x5831d5de
Exception code: 0xc0000005
Fault offset: 0x0002c64f
Faulting process id: 0x19e4
Faulting application start time: 0x01d2aa5b668533fe
Faulting application path: P:\Program Files (x86)\Lockheed Martin\Prepar3D v3\Prepar3D.exe
Faulting module path: P:\Program Files (x86)\Lockheed Martin\Prepar3D v3\Gauges\MV_F-4J_Sys.dll <<<< I think this was the culprit.
Report Id: f079b480-164e-11e7-a478-6cf0497dce43
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Application Error" />
<EventID Qualifiers="0">1000</EventID>
<Level>2</Level>
<Task>100</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2017-03-31T20:16:36.000000000Z" />
<EventRecordID>242712</EventRecordID>
<Channel>Application</Channel>
<Computer>ijdjr-PC</Computer>
<Security />
 
"
There is some kind of a configuration program that installed to the desktop and I guess you configure the controls and other things. I really didn't mess with that part."
Pretty sure that's where you would configure the nose gear.
 
Penzoil3 said:
"
There is some kind of a configuration program that installed to the desktop and I guess you configure the controls and other things. I really didn't mess with that part."
Pretty sure that's where you would configure the nose gear.
Click to expand...

I know what you are talking about and I did look thru it, all it has was keyboard/joystick assignments for for flaps/speedbrakes etc. Didn't see anything related to steering control.

The planes turns but it's odd to see the nose gear not swivel left/right when making a turn.
 
It all works fine in P3D now that they issued and update that I think replaced a buggy file.

I got the nose gear steering to swivel, had to assign a combo key to make it work.

All's well that ends well. :untroubled:
 
henrystreet said:
They issued a patch yesterday for the latest version of P3D. You should have gotten an email with the download.
Click to expand...

I applied that patch and I think it replaced what must of been a buggy file that caused havoc with P3d (It would crash) and now, it seems to work just fine.
 
I have had the same CTD on the milviz phantom. On the F-4 support forum (not the general one, you have to provide Kat proof of purchase to be on the support one) they have said that there is a patch coming out that will fix the problem.
 
docjohnson said:
I have had the same CTD on the milviz phantom. On the F-4 support forum (not the general one, you have to provide Kat proof of purchase to be on the support one) they have said that there is a patch coming out that will fix the problem.
Click to expand...

I believe that patch was issued, I applied it and it and it seems to work. They issued it as an update.
 
Yes, it's probably not going to be an issue for much longer, with the end (or near the end) of the P3D V3 updates, but every time LM has updated P3D it has broken the Phantoms. It is extremely frustrating if you bought from a 3rd party vendor who doesn't update products on the server. Not really anyone's fault, Milviz don't break it, LM do, and LM are doing the right thing by improving P3D. It's just frustrating.

As a result I have not updated past P3D V3.4.9 and I'm not unhappy about that, it is a good, stable platform that looks and performs well.

Cheers,
 
I'm having the crash problem with the latest patch 1.17...

I've contacted MILVIZ and am awaiting forum access to figure out a solution. Funny that it only affects the J/S and not the E.
 
Not sure if your aware but the J for P3d will only work with the latest version of P3d. Found this out myself having similar situation.
 
Last time I had severe program crashes with an airplane, it wasn't exactly due to the airplane itself, but more to an outdated TacPack...
Now I'm in a "no-update" situation, because I'm still using P3Dv3.3.5.
I'm afraid to break down everything and not being able to go back if I trigger the updates for ASN, or TacPack, or the updated airplanes like the Phantoms... And since all is working fine at the moment (excepted the missing AASRAMs on Dino's Eurofighter...), I'm not updating anything at all.
 
You need to go on the milviz support forum, the updates that will fix the phantom are being discussed. Also the phantom when updated will only work with the latest p3d and tacpack version.
 
Milviz F4J crash in P3D

Chris Sykes said:
Not sure if your aware but the J for P3d will only work with the latest version of P3d. Found this out myself having similar situation.
Click to expand...

Hi,

I´m running the latest version of P3D (3.4.22.19868) and still crashes with [FONT=&quot]Fault Module ID : [/FONT]MV_F-4J_Sys.dll .
 
For information, it seems the F-4's have been updated again. I have received some notification emails from Milviz a few hours ago.
 
You must log in or register to reply here.
Back
Top