New user-various problems

[Gullwing 91]

First, it's a great aircraft and I'm please to have it, but I'm having some problems. Here's a summary-sorry but it's 6 years since I last used FSX and I'm very rusty about the technicalities.

1. When I installed the Turbo Otter all seemed to go OK but I got an error message about not being able to find DLL.xml. I found DLL.xml in what looks like it's default location on my C drive (FSX is on F). There was something in the error message about a manual update but I couldn't figure how to do that.

2. When I used the Turbo Otter in a flight and left the flight, FSX crashed and re-started. I got the following message in event viewer:

"Faulting application name: fsx.exe, version: 10.0.61637.0, time stamp: 0x46fadb14
Faulting module name: TurboOtterSystems.DLL, version: 1.0.0.0, time stamp: 0x5b523927
Exception code: 0xc0000005
Fault offset: 0x000017f1
Faulting process ID: 0x2a14
Faulting application start time: 0x01d48bbc04b42a12
Faulting application path: F:\Microsoft Games\Microsoft Flight Simulator X\fsx.exe
Faulting module path: F:\Microsoft Games\Microsoft Flight Simulator X\SimObjects\Airplanes\DHC-3 Turbine Otter Milviz\panel\TurboOtterSystems.DLL
Report ID: 295e288d-3fd2-4257-b752-ed9d848a26dc
Faulting package full name:
Faulting package-relative application ID:"

The re-start changed my settings. It deleted my default flight (I was back to the microlight).

3. Some of the animations are not working. The power lever/throttle is stuck in reverse and won't move, the rudder pedals won't move, nor is rudder movement visible externally. However these only missing visual effects: the aircraft responds properly to control inputs.

4. When it first appears, the aircraft appears half buried in the runway. That is rectified if I press "pause" twice.

5. As of today I am getting visual corruption-at first the aircraft is not visible (I can see its shadow), then bits of it gradually start to appear. However, thereafter the sky goes completely black.


My response to your support page questionnaire is as follows:
Does your system meet the sim's requirements? YES
Did you temporarily disable your anti-virus program during the download process? YES
Before installing did you disable UAC. (User Account Control)? YES
Did you install, and are you running the sim as an admin? YES
Before running the sim did you make sure the FSX/P3D directory is off limits to any AV scanning? YES
Does your system have the required distributables? YES
Is your video card DX11 compatible? YES
If applicable, did you disable any FSX to P3D migration tools (like Estonia) before running the sim? YES
Are you using an aircraft other than a Milviz one as your default aircraft? NO (using default Cessna)
Have you installed in the root sim directory? YES
Do you have the appropriate SimConnect libraries installed? YES
Aircraft: DHC-3T Turbo Otter
Sim platform: FSX + Acceleration
Operating system: Win10
Version: 1.180919
Unique ticket identifier: 75665FEC-D696-E248-814D-B7A88DCE606F

System
OS Name Microsoft Windows 10 Pro
Version 10.0.17134 Build 17134
Processor Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz, 3401 Mhz,
Installed Physical Memory (RAM) 16.0 GB
GPU: Nvidia Geforce GTX 660 2 Gb
Controller Thrustmaster: T16000M used with the TARGET program. I have also tested without TARGET and with a Logitech Extreme 3D and saw no difference.

FSX info
FSX Gold (Acceleration installed)
SDK installed YES
SimConnect installed YES
FSUIPC installed YES (free version)

Addon scenery
Maldives X
Tongass Fjords X
PNG Bush Flying

Addon aircraft
Aerosoft Beaver X
Aerosoft Dornier 27
Aerosoft Wilga
Lionheart Creations Quest Kodiak
Flight One ATR

Testing has been done by loading the Turbo Otter over a default flight at Seattle using the stock Cessna. I have also tried running it directly from free flight, no apparent difference. Hope you can help and that I have given you enough to go on, many thanks. Having browsed the forum a little now I see someone had a problem with tools.xml which looks at bit like mine.

[Taguilo]

Hi,

Please read this:

https://milviz.com/forum/viewtopic.php?f=157&t=8528

Thanks!

Tomas

[Gullwing 91]

Thanks for that Tomas, but all I am getting on that link is "You are not authorised to read this forum.".

[Taguilo]

Oops, sorry.

Edit your DLL.XML file and add:

<Launch.Addon>
<Name>XMLTools</Name>
<Disabled>False</Disabled>
<ManualLoad>False</ManualLoad>
<Path>XMLTools.dll</Path>
<DllStartName>module_init</DllStartName>
<DllStopName>module_deinit</DllStopName>
</Launch.Addon>

To be sure, do a search for DLL.XML in your machine and see if you have more than one for FSX. If so, add the code from above to all of them.

Also check that XMLTools.dll is present in your FSX main folder

Thanks!

Tomas

[Gullwing 91]

Major progress! The aircraft is now working as it should, but is still re-booting FSX when I quit the flight with messages like this:

"Faulting application name: fsx.exe, version: 10.0.61637.0, time stamp: 0x46fadb14
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0xfffffc96
Faulting process ID: 0xac8
Faulting application start time: 0x01d48c96b59442bd
Faulting application path: F:\Microsoft Games\Microsoft Flight Simulator X\fsx.exe
Faulting module path: unknown
Report ID: b7e67823-f1be-4645-8a26-df6aa3734efc
Faulting package full name:
Faulting package-relative application ID: "

But at least now it's not changing my settings and my default flight is surviving. Is a fresh install the way to go now? Thanks for your help.

[Taguilo]

Honestly i don't know what could be causing the reboot.
Are you using the WX radar?
If so, try deselecting i from MVASM config


Thanks!

Tomas

[Gullwing 91]

No not using that. Is it worth considering a complete reinstall of FSX? Can't face it at the moment, but will do it as a last resort.

Edit: More progress to report, I think I'm getting somewhere. I uninstalled then reinstalled the Otter module. I again got the message about dll.xml but this time knew what it meant. The aircraft started by working fine and when I quit, no re-start of FSX! However, when I ran it again there was more graphics corruption, e.g. external model not showing and some weird combos of images and when I quit the flight, I got a message about my computer being out of memory. Checked the resources used and saw my video memory was at 14% and my RAM at 33% used. So did some more research and it may be that there is not enough virtual memory on my system to run your module. The suggestions are: reset swapfile, update video drivers and use something called the 4Gb patch which allows FSX to use more virtual memory. My drivers (Nvidia 388.13) do need updating.

I'm spelling all this out in case its of use to a newb with the same problems or someone like me who has forgotten all this stuff. Please feel free to comment if I'm going up the wrong path. Will report back on progress.

[Gullwing 91]

Please excuse double post but I seem to have cracked all the problems. Crashes of FSX were caused by lack of virtual memory. Graphics corruption has been sorted out now by tweaking my fsx.cfg file. Will post full details if anyone wants me to. Now to do some flying.