Interior Lights

[farman]

Yes, they do. Actually, at the present moment I've installed only the F-4, since the P-38 is for v 2.5. But I tested it for a while and it worked properly. In teh p-38 the issue was at the opposite; interior ok, exterior not working.
Attached the TM while loadiong the F-4. In this case the MV_F-4E_NL.exe has started.
Attached some image:

[pipeorgan]

I can confirm that I also do not have MV_NL.exe in task manager process list.

Regards John

[farman]

Hi,
just a brief summary of my actions:
I had the same issue with the Phantoms interior lights (except the new British version, properly working). All has been fixed after
1) Given all the Permissions as full administrator to the .exe files, the MV_F4_NL etc.. In the end, to all the possibile and imaginable files
2) Start P3D v3 as Administrator (as default choice) - and I think this was the correct, final move.
I was expected that similar actions might fix the same interior lights issue faced with the new T-38, even having installed the last version, the "MV_T-38A_v3.151218". Unfortunately I went on with the same problem. I was told to check the SimConnect.msi installetions; so I re-installed them lokking at EACH of the "lib" folders from the Redist/Interface/ESPv1>FSX-RTM>FSX-RTM-JPN>FSX-SP1>FSX-SP1-RUS>FSX-SP2-XPACK/SimConnect.msi. All this to no avail; attached the SimConnect files from my Programs.Only in one case I was warned that a SimConnect.msi was older then the ones already installed.
When opening the T-38, from the Task manager no MV_NL.exe working.
Hope having written all the parametra in order to try to fix this issue.
Thanks for any further help,
Fulvio

[hodge001]

Hi
I had the same issue with the interior lighting and tracked my issue down to the fact that my DLL.xml file had the Migration Tool add-on listed in it and as soon as I removed that I had interior lights,
it loads the Migration Tools MigTool.dll on start-up which seems to not play well with the MV_NL.exe, so the entry you need to remove is as follows..

<Launch.Addon>
<Name>Migration Tool Plugin</Name>
<Path>MigTool.dll</Path>
<DllStartName>module_init</DllStartName>
<DllStopName>module_deinit</DllStopName>
</Launch.Addon>

I hope it helps in your case as it did here.
Jim Hodkinson

[farman]

Hi,
thanks for the useful suggestion. I'll try it. But I never let Migration Tool enabled, when flying. Fine; will follow a feedback.
Fulvio

[hodge001]

Hi

The migration tool does not have to be active or running, it is the actual MigTool.dll file loading that was causing my lighting issue.

I hope it works out OK.

Jim Hodkinson

[farman]

Hi,
please, perhaps I missed something or didn't understand well:
1-P3D launched
2-Add-on Manager open on the Processe" page. Attached images of ALL the processes working: I can't see the one you wrote about.
Thanks for any further help. But I think I'll un-install the Migration Tool until I'll have to use it. So, problem should be solved at its root.

[hodge001]

Hi

You may not see it as a running application it is just the fact that the entry is in the DLL.xml file that caused my lighting issue, and once I removed it the Talons interior lighting worked OK.

Jim Hodkinson

[farman]

Hi Jim,
thanks again for your quick answer. I was told about the Mgration Tool in the very beginning, when I had problems with the Phantoms interior lights. Right now I even uninstalled the Migration Tool - even if I enable it ONLY when installing some FSX add-on (Aerosoft airports etc.). After that I immediately disable it, knowing its dangereousness in P3D v3(v 3.1 (my actual platform).
Unfortunately to no avail. I solved the Phantom problem giving all tghe permission to the .exe files and giving an Administrator default start to P3D. All worked fine, since then. But obviously there's something else affecting the proper functionality of this lights. Who know where to dig to find out this damn bug; or, at least, I'm not so professional in terms of processes to know where to look at.
Thanks for your help, it'ps very kind of you,
Fulvio

[hodge001]

Hi

Sorry to hear that it did not work at your end, it must be just one of those things for it to be the issue I had but not yours, still it was worth a try.

Good luck with finding a fix, but I am sure the MV team will get you up and running.

Take care.

Jim Hodkinson

[farman]

Hi Jim,
thanks again.
Fulvio

[farman]

Hi,
I made just a small test, stating at the least some things:
1-Migration Tool must be disabled.
2-P3D must be started by default as Administrator (as a lot of .exe files in W7 64b, BTW).
2-The MV_NL.exe (or MV_f4_NL) must be running in the Task Manager.
3-These two .exe files must have ALL the permissions available set to ON in the Security page.
Said that, choosing the T-38, no MV_NL.exe file is running in the Task Manager, differently from the that of all the Phantoms.
Fulvio

[hodge001]

Hi

Out of curiosity did you check the DLL.xml file for the Migration Tool dll entry, I ask as even when something is uninstalled it can leave traces of its file and their entries.

Jim Hodkinson

[farman]

Hi Jim,
ehm.. and where can I find this file?
BTW, with Migration Tool installed but not enabled, even the Phantoms lights didn't work. Uninstalling it, lights reappeared. Further, on the T-38 the MV_NL.exe doesn't appear in the Task Manager, while the MV-F4_NL.exe yes.
Jim, it's very kind of you to help me. You can't understand how much angry Iam to myself in not sorting out of this damned issue. I did it in so many cases, but this time it seems as it was a curse.
Fulvio

[hodge001]

Hi

There are actually two of them in different locations, the main one is in the following directory folder….

C:\Users\YourName\AppData\Roaming\Lockheed Martin\Prepar3D v3

And a second version which you may as well check is in the following location…

C:\ProgramData\Lockheed Martin\Prepar3D v3

The file you are looking for in both locations is named DLL.xml, which you open with notepad or a similar program, not word,
word pad or internet explorer though as they tend mess with the formatting of the file.

If you don’t see a file or files that look like the one you need then you may have to turn on “Show Hidden Files and Folders” in windows,
you can do this by clicking on any folder and from the top menu select Organise>Folder and search options, which will open a pop-up window
named Folder Options, this has three tabs along the top and the one we need is named View, now when you click on that you will get a
new panel with a window named Advanced settings, and the sixth entry down the list is Hidden files and folders, which has two settings one
being "Dont show hidden files folders or drives", which is the windows default setting, and the second one being "Show hidden files folders or drives",
you will probably need to put a check mark against this one and then click the Apply button to be able to see some of the files needed like the
DLL.xml file we are looking for.

I hope you can follow my attempt at guiding you to the file as I have been known to go off track at times.

Good luck.

Jim Hodkinson

P.S.
By the way I know exactly how you feel at the present time, as they say “I have been there done that and got the T-Shirt”