F-86 Non TP Switches and Payload problem

[flyboy7798]

Nope, nothing out of the ordinary.

[JonathanBleeker]

I just thought of something. Go to your user\Documents\Prepar3D v4 files and send me the contenterrors log.

[flyboy7798]

I need to turn on the content error option, new install...will post soon.

[flyboy7798]

Here's a clean run...still same as before...

[JonathanBleeker]

Ok, I am going to need to ask you to go through all the aircraft cfgs listed and clear out the duplicate keys/sections. They are masking the F-86 errors.

I trust you know how to work through this since as I recall you work as a dev at SWS?

[flyboy7798]

Yes, but I found a crash dump for the run I sent you last night. It appears that the MV_F86_NL.exe is erroring out. Here's the windows crash dump data/windows debugger output.

Also, yes I'm a developer, and yes I'm working on a project with SWS. However, it seems to me that having me clear content errors is not something as a customer I should have to do whether I'm a developer or not (I'm not a fan of clearing out content errors that I didn't cause with my own work). Today I'm a customer with a problem getting your product to run in an environment that it's supposed to work in. Besides, I have plenty of work to do debugging my own aircraft systems. I'm going to remove all aircraft from the V4 install except the Sabre and rerun the test.

Let me know how you would like to proceed (short of sending me the .pdb file and I use the VS2015 debugger to catch the offending line of code or whatever the cause is, that is).

[JonathanBleeker]

Removing all aircraft is another option indeed.

Now that you mention it, are there any other errors in the Windows Event Viewer involving the F-86?

[flyboy7798]

Only the MV_F86_NL.exe, I was able to find out why the aircraft wouldn't start...I had some leftover gauges in a separate addons folder where I keep aircraft that I want to be available to both simulators (most of the V4 aircraft are installed directly into the V4 root)...for some reason, I had F-86 DLLs in that addons gauges directory. Once I removed them the start procedure worked, also the config and TP screens work. But the sim keeps crashing and its that DLL that seems to be the root cause. No warning, just a CTD, and the P3D4 window just vanishes. The Windows Debugger shows the same thing in this crash as it showed the last one I sent.

One thing that has changed lately is I'm using REX Skyforce (AS2016 + REX SF + PTA)...but that shouldn't affect the operation of the DLL?

[JonathanBleeker]

True it shouldn't.

Now regarding the NL exe, is this occurring with the TACPACK or the non TACPACK version or both?

[flyboy7798]

I believe it occurred with both in 4.1...

[JonathanBleeker]

This test is for non TP first. Unzip the LT.dll into your panel folder and the NL.exe in your texture folder, overwriting the existing files.

Let me know if it still crashes.

https://www.dropbox.com/s/3j3fyfzj7aab2 ... T.zip?dl=0

https://www.dropbox.com/s/5s08objtr6eha ... L.zip?dl=0

[flyboy7798]

That worked.

[JonathanBleeker]

Here are the files for the TACPACK version. Let me know if they work.

https://www.dropbox.com/s/m9oacf3dkda09 ... T.zip?dl=0

https://www.dropbox.com/s/wc871q2caidy5 ... L.zip?dl=0

[flyboy7798]

Just tested the guns...TP seems to be working normally. However, I didn't think to check the flaps, trim, etc., on the non-TP version. I just started it and took off...with the TP version, I noticed that I could not lower the flaps and when I was trying to trim out the plane for a strafing run, I noticed that the trim didn't work either...all other cockpit indications seem normal...

[JonathanBleeker]

And the cockpit lighting?