Cockpit lighting not working Phantom II J/S

[Hamilton]

Hello,

I tried a night flight with the F-4 and inside both cockpits no lights. I turned ON all switches and the brightest knob,try flood lights and even hit L on the keyboard but only exterior lights are working.

Well,I did the 5 itens (Run as Admn,UAC Off, A/V off,etc.,etc.) Reinstall the June 2010 dx runtimes and confirmed the MV_F4_NL.exe*32 in the processes tab.

Would you please give me any tip..

Thanks for any input,

Hamilton

[JonathanBleeker]

You running P3D or FSX?

[Hamilton]

You running P3D or FSX?

P3D 3.4.22.19868 and now swich back to P3D 3.3.5 . Win 7 x64.

[JonathanBleeker]

Is there an fsx.exe in your processes list in the task manager?

[Hamilton]

Is there an fsx.exe in your processes list in the task manager?

No,related to FSim, only P3d.exe, MV_F4_NL.exe*32 and EzDok.

[JonathanBleeker]

You aren't running the Estonia migration tool?

[Hamilton]

You aren't running the Estonia migration tool?

Sorry Jonathan, I DO have FSX.exe running,it´s the last of the list.Related to FSim: P3d.exe, MV_F4_NL.exe*32 , EzCA, Coualt, Aicarrier,FSX.exe and NO Estonia migration tool running. Sorry again!

[JonathanBleeker]

That's the problem. Your Estonia migration tool isn't fully disabled. It is putting an FSX.exe in the processes list and the lighting system thinks it has to link with FSX not P3D. That's why your lighting isn't working. Make sure the Estonia tool is fully disabled in your P3D's dll.xml.

[Hamilton]

That's the problem. Your Estonia migration tool isn't fully disabled. It is putting an FSX.exe in the processes list and the lighting system thinks it has to link with FSX not P3D. That's why your lighting isn't working. Make sure the Estonia tool is fully disabled in your P3D's dll.xml.

You´re the man Jonathan !! Disable Estonia migration tool and got full cockpit lights, Thank you !

Btw,do you think that Migration tool could also interfere and be the culprit that cause the crashes that I had with MV_F-4J_Sys.dll gauge ? I still didn´t test this...

[JonathanBleeker]

Nope. The Sys dll crash is due to version incompatibilities with P3D v3.4.22 that are fixed in the (Very soon) to be released update, as well as a problem with our hardware mapping system that sneaked in under the radar.

[Hamilton]

"The Sys dll crash is due to version incompatibilities with P3D v3.4.22"

Let me add P3D v3.4.22 and P3D 3.3.5 because I have the same MV_F-4J_Sys.dll crash in both P3D versions.

Thank again!