DX10 Fixer Issue

[Caribflyer]

Well, I'm not entirely sure that its the DX10 causing this issue, but everytime I load an airport from FSDT, I am only seeing the gates and just as the rest of the terminal buildings are being loaded, FSX SE freezes up. It is still running and I can hear the engine sound of the aircraft but everything is frozen. If I load up at any other airport it works just fine. Any tips on how I can fix this?

Also, when I finally close down FSX from the Task Manager, I also get a message saying that Coualt has stopped working.

[virtuali]

Well, I'm not entirely sure that its the DX10 causing this issue, but everytime I load an airport from FSDT, I am only seeing the gates and just as the rest of the terminal buildings are being loaded, FSX SE freezes up.

That doesn't look like a video driver issue so, it's unlikely it's related to the DX10 fixer. Of course, it should be fairly easy to confirm this, by switching to DX9 as a test.

It is still running and I can hear the engine sound of the aircraft but everything is frozen. If I load up at any other airport it works just fine. Any tips on how I can fix this?

It might be a sound drivers issue.

Try to enable logging in the Troubleshooting section of the GSX - Settings menu, restart the sim, and after closing it down, check the %APPDATA%\Virtuali\Couatl.LOG and see if there are any errors there.

Also, when I finally close down FSX from the Task Manager, I also get a message saying that Coualt has stopped working

This is normal. By closing FSX abruptly, Couatl won't get a proper notification from it that is going to close, so it won't have a chance to clean up all its own internal memory and stuff. It's just a consequence of the freeze and the forced termination.

[Caribflyer]

I uninstalled DX10 Fixer and the problems seems to have stopped. However, I did notice that now GSX causes the same issue. When I tried to select a gate after landing, FSX SE froze up but as was the case before, the sound was still playing and in the Task Manager FSX SE was still running as normal (no "not responsive" messages)

Here is what my err log showed

couatl v3.1 (build 3532)
panic log started on Fri Aug 19 20:04:43 2016

problem raised by engine or unspecified addon
Application aborted because of C++ exception: <unknown error>
{'Airport': 'KLAX', 'User Pos': (33.93583320927437, -118.41915959541463, 39.5395 m, 1.13552 m, 82.96758696638487)}


I am also using the new FSLabs A320 so I am not sure if there is any new conflict.

[virtuali]

Application aborted because of C++ exception: <unknown error>

This error should basically never happen, and it looks as if there's a conflict between system libraries.

I am also using the new FSLabs A320 so I am not sure if there is any new conflict.

I haven't tried the latest version, but we were in touch with several beta testers for the FSLabs A320, and we made several changes to GSX to support it, following their suggestions, so I must assume there shouldn't be any conflicts with it, but of course, I cannot be sure without trying the final version.

[Caribflyer]

Thanks I will do some testing and also contact FSlabs. By the way, I sent you a PM on another matter.

[Caribflyer]

Here is the content of my log file

Python 2.7.6 Stackless 3.1b3 060516 (default, Feb 19 2015, 15:56:51) [MSC v.1800 32 bit (Intel)] wxPython 3.0.2.0
couatl v3.1 (build 3536)
log started on Sun Aug 28 10:41:19 2016

connecting to SimConnect...
connected to SimConnect
connected to bglmanx
Running in mode: FSX (bglmanx setting)
Loading addons
Loading addon common
Added Menu Item "Couatl settings" (id 67)
Addon common loaded
Loading addon LiveUpdate
Added Menu Item "Couatl Live Update" (id 69)
Added Menu SubItem "Disable Addon" (parentId 69, id 70)
Addon LiveUpdate loaded
requesting AddOn list to bglmanx
Added Menu SubItem "Restart Couatl" (parentId 67, id 71)
Added Menu SubItem "Restart Couatl and rebuild airport cache" (parentId 67, id 72)
Added Menu SubItem "Key Mappings..." (parentId 67, id 73)
Added Menu SubItem "Show YouControl™ Menu        Ctrl+F12" (parentId 67, id 77)
Current locale is English_United States.1252
Initializing audio...
Available devices:
  Generic Software on Speakers (Realtek High Definition Audio) (47656e6572696320536f667477617265206f6e20537065616b65727320285265616c74656b204869676820446566696e6974696f6e20417564696f29)
Created OpenAL device: Generic Software on Speakers (Realtek High Definition Audio)

Device info:
   Major version: 1
   Minor version: 1
   Frequency: 44100
   Refresh: 40
   Sync: 0
   Mono sources: 255
   Stereo sources: 1
   Extensions: ALC_ENUMERATE_ALL_EXT ALC_ENUMERATION_EXT ALC_EXT_CAPTURE ALC_EXT_EFX

Context info:
   Vendor: Creative Labs Inc.
   Version: 1.1
   Renderer: Software
   Extensions: EAX EAX2.0 EAX3.0 EAX4.0 EAX5.0 EAX3.0EMULATED EAX4.0EMULATED AL_EXT_OFFSET AL_EXT_LINEAR_DISTANCE AL_EXT_EXPONENT_DISTANCE

Using EFX 1.0 extension, with 1 auxiliary send(s)
Using EAX reverb
Added Menu SubItem "Check Live Update" (parentId 69, id 81)
Slew mode False
Connection with FSX lost (has it crashed?)
disconnected from SimConnect.

[virtuali]

Your log now doesn't show any error on our side. Except that Couatl detected that FSX crashed. So, it's seems now that FSX is crashing for some reason (unrelated to us), and of course we can only report it.

[Caribflyer]

Thanks, I guess I will have to try figuring out the cause since it must be something else.

[Caribflyer]

Here is a new reports from Event Viewer. I am not sure if this says anything or if this is just as a result of ending the FSX process in the Task Manager after it froze up.

couatl.exe
   3.1.0.3536
   57bf02a2
   ntdll.dll
   10.0.14393.82
   57a557a3
   c0000374
   000d9841
   12d4
   01d204cfb5cc40cd
   C:\Program Files (x86)\Steam\steamapps\common\FSX\fsdreamteam\couatl\couatl.exe
   C:\WINDOWS\SYSTEM32\ntdll.dll
   e219d612-0ab0-462a-86e0-39cec8b625d1
    

[virtuali]

Here is a new reports from Event Viewer. I am not sure if this says anything or if this is just as a result of ending the FSX process in the Task Manager after it froze up.

If you still don't have any problems in the Couatl.LOG file, it means it's FSX that caused Couatl to crash, not vice-versa. In that case, it's just to be expected you would see errors related to Couatl in the Event Viewer, since no program responds well to being closed abruptly, especially with FSX, when external programs needs to receive a message from the host application (FSX) in order to know they are supposed to exit, something that FSX cannot send anymore, if it has crashed itself.

[Caribflyer]

I finally figured out what the problem was. It seemed that it was actually a hardware issue. Since installing the FSL A320, I assigned the Steering Set feature of the FSUIPC to my yoke stick and it seems like my FSX didn't like it very much. After changing this feature I no longer have any freeze up of FSX. Perhaps the process of louding scenery and constant hardware inputs was too much for FSX. I also updated my graphics card so this could have also been a factor but the definite change came from changing my joystick settings so that inputs are not constantly being sent to FSX for a variety of tasks (steering, and aileron control all in one..)