FSDreamTeam forum
Products Support => GSX Support FSX/P3D => Topic started by: crauds on September 23, 2015, 09:48:21 pm
-
I just posted a topic but for some reason it is not appearing. After the upgrade, Coatl disables the audio device and so I have no sound for any GSX functions. FSX sound still works fine. I will try to post this thread again. If it is a duplicate and the initial one eventually reappears, then my apologies. I am uploading the FSX.cfg file showing my audio device and the coatl.log file showing the disabling of audio device. There is no err log created for this.
-
After the upgrade, Coatl disables the audio device and so I have no sound for any GSX functions. FSX sound still works fine.
Nothing in the update (although it not very clear what do you mean "after the update") could have any effect on audio. Nothing has changed in the way GSX handles audio since it was released.
I am uploading the FSX.cfg file showing my audio device and the coatl.log file showing the disabling of audio device. There is no err log created for this.
It's normal there's no error log for this problem, since it's not a GSX problem.
The Couatl.LOG shows your audio device has failed to initialize, so GSX has reverted to not using any audio device, because it cannot use a faulty device, and it will likely crash if it tried to.
GSX has used OpenAL audio since it has been released, and nothing has changed in any of the updates. If your audio device fails to initialize, there's nothing GSX can do, other than reporting it.
The first thing to try, is restarting Windows, and re-selecting the audio device in GSX.
If that doesn't work, then it's a problem of your audio drivers, that have an issue with OpenAL, possibly related to a recent update of the drivers, or an update of your OS.
-
Hi Umberto!
My audio device initializes fine and is fully operational in all programs including FSX. All other sounds work fine is FSX using my default sound device. From my config file you can see the code for my devices but Coatl is not seeing them apparently. The device certainly has not "crashed"!
You recommend "... re-selecting the audio device in GSX."
How do I re-select the device in GSX?
-
Hi Umberto!
I reinstalled v3.0 and this time it found my audio device. Thanks. The install gave me an error loading vehicles and stated that it was reinstalling default, whatever that means! I will give it a test run.
-
My audio device initializes fine and is fully operational in all programs including FSX. All other sounds work fine is FSX using my default sound device.
This doesn't mean anything.
As I've said, GSX uses the OpenAL standard audio library. GSX doesn't try to talk with your Audio device directly, it will talk with your audio driver implementation of OpenAL so, what has failed to initialize is *that* one.
Your audio device might work in DirectSound (which is what FSX uses), but that doesn't automatically ensure it will work in OpenAL. It's the SAME as your video driver: fact it might work in DirectX (so ALL DirectX games will work), doesn't guarantee it will work in OpenGL too, so all your OpenGL games will have problems.
The device certainly has not "crashed"!
But it surely has reported to GSX that it has failed to reply to an OpenAL initialization request, so GSX doesn't have any other choice than not using it, because it's not possible to make subsequent OpenAL calls if the initialization failed.
How do I re-select the device in GSX?
After a Windows restart, go into the GSX sound settings page, and select the audio device.
I said after a Windows restart, because it might be just a temporary problem with the OpenALL .DLLs installed in your system.
-
Please note my results already posted in reply #3. BTW, I have Vista 64 SP1 and I don't find a GSX sound settings nor an OpenAl folder. But irrelevant since reinstalling v3.0 solved the audio issue, but I now have a new problem: If I select "restart" cuatl from the dropdown menu while in FSX I get a coatl APPCRASH to desktop and occasionally a runtime error message. But even though the message states that coatl has stopped (crashed), when I return to FSX, it still appears as a menu entry iand seems to be operational. This is all strange.
Also, is there an updated manual explaining your new features? I did a complete re-install but still only have the manual for 1.95.
-
I don't find a GSX sound settings
Yes, you have a GSX sound settings page. It's a tab of the GSX - Settings menu.
nor an OpenAl folder
You are not supposed to have an OpenAL folder, you have an openal32.dll file in the Windows\System32 folder.
If I select "restart" cuatl from the dropdown menu while in FSX I get a coatl APPCRASH to desktop and occasionally a runtime error message. But even though the message states that coatl has stopped (crashed), when I return to FSX, it still appears as a menu entry iand seems to be operational. This is all strange.
It looks like you had two copies of Couatl running, most likely because you restarted FSX too quickly after closing it down. A Windows restart would surely fix this.
Also, is there an updated manual explaining your new features? I did a complete re-install but still only have the manual for 1.95
The manual labeled as 1.9.5 contains all new GSX features, even those added later, except for the Traffic cones, which surely won't need explanations, at least not until we'll update the editor to allow you to customize them too.
-
Hi,
something is up, because I have similiar problem...
since I installed the newest version of Addon Manager and Vehicle Update I also have problem with GSX sounds.
First FSX' run after install the newest Addon Manager and Vehicle Update I get Couatl Error - unfortunatelly I didn't do screenshot. After close error message, FSX run normally, but without GSX in Addons menu.
I opened Settings dialog and saw that no audio device is set and there aren't any audio devices on the list to choose - it's strange.
So I ticked "Restart Couatl and repeat audio diagnostics checks" checkbox and after Couatl restart had an error like this:
(http://www.fotoszok.pl/out.php/t2517213_gsxerr01.jpg) (http://www.fotoszok.pl/show.php/2517213_gsxerr01.jpg.html)
I shut down FSX then fire it up again and next Couatl error appeared while FSX was starting - unfortunatelly don't have screenshot.
I closed this error message, FSX opened normally, but without GSX in Addons menu.
So I shut down FSX and run again - no Couatl error. But when I load the flight, next two errors appeared (one by one):
(http://www.fotoszok.pl/out.php/t2517212_gsxerr02.jpg) (http://www.fotoszok.pl/show.php/2517212_gsxerr02.jpg.html)
(http://www.fotoszok.pl/out.php/t2517211_gsxerr03.jpg) (http://www.fotoszok.pl/show.php/2517211_gsxerr03.jpg.html)
Then, the flight loaded normally, but without GSX of course.
Something is wrong that I don't see any audio device in Settings dialog but I don't know if all these errors are related with it.
What can I do to recognize a reason of problems and why there is no sound?
Ps. In log file I found following entry:
Initializing audio...
Detected failed previous attempt to enumerate audio devices: disabling audio
Lucas
-
Hi,
...anyone have similiar problems with sound? What should I do to see audio device in GSX settings?
Lucas
-
I get the same thing. It happens when Couatl crashes, which happens randomly only within the first couple minutes after loading. On restart of FSX (I use FSXSE) There is no sound in GSX. What needs to be done then is go into GSX Sound settings You'll see in the drop down box has no devices. The "Restart Couatl and Repeat Audio Diagnostic Checks" check box will be active. Click on it and click ok. Couatl will then restart. Go back to GSX Sound settings and you'll see that check box is no longer clickable. Your sound devices should now appear in the drop down list. Select the one you are using, and click ok. You should now have sound back in GSX. Note when Couatl crashes again, you'll have to repeat this procedure.
-
Note when Couatl crashes again, you'll have to repeat this procedure
Exactly... Couatl crashed in my machine. But I didn't try repeat this procedure again. However it is not final sulotion...I think :)
-
First, be sure you use the CURRENT version of Couatl.exe, which can be obtained by installing any FSDT product or the Stand-Alone Addon Manager. No, the Live Update that can update without exiting from FSX, cannot update Couatl.exe.
Also, check if you still have Couatl.exe running in the Task Manager after a crash, because it's possible that sound might not re-initialize if there's an old instance of the exe still running.
And, of course, whenever you have a crash, report it here and indicated precisely if it was a real abrupt crash (with a Windows error code), or just message from Couatl that opened a normal FSX window asking if you want to restart it.
-
Hi Umberto,
a few screenshots with errors I pasted a few posts above. Of course, if it will happen again, I'll paste them again.
I installed Standalone Manager downloaded from GSX site, not the Live Update - after that, issues are present...
Thanks for reply,
Best,
Lucas
-
a few screenshots with errors I pasted a few posts above.
But it was from the previous version.
I installed Standalone Manager downloaded from GSX site, not the Live Update - after that, issues are present...
Which issues ? You said you'll post a new screenshot "if it will happen again" so, has it happened again, or are you now referring to the audio problem ?
And, see my previous reply about checking if Couatl.exe is still running. If it happens again, try to RESTART WINDOWS after a crash, and see if the audio device comes back.
-
First, be sure you use the CURRENT version of Couatl.exe, which can be obtained by installing any FSDT product or the Stand-Alone Addon Manager. No, the Live Update that can update without exiting from FSX, cannot update Couatl.exe.
Also, check if you still have Couatl.exe running in the Task Manager after a crash, because it's possible that sound might not re-initialize if there's an old instance of the exe still running.
And, of course, whenever you have a crash, report it here and indicated precisely if it was a real abrupt crash (with a Windows error code), or just message from Couatl that opened a normal FSX window asking if you want to restart it.
Thanks Umberto! Yes the crashes I'm talking about are Windows crashes not an Couatl error message. I also think your right that 2 instances of Couatl is running at the time, since I get 2 separate windows error messages one right after the other. The problem though, is this can happen right after a fresh reboot, where FSX wasn't running prior, so it appears in some circumstances Couatl is spawning a second instance on it's own. I'll take a screen shot the next time it happens. I also reinstalled GSX completely yesterday to try and remedy a different issue after the latest live update (which I'll report in another thread, I just have to pull together the screens showing the issue first.) and Couatl has crashed the same way afterwards yesterday. So I know I had the latest version installed.
-
it appears in some circumstances Couatl is spawning a second instance on it's own.
Couatl surely doesn't spawn any second instances on its own. Restarting FSX too quickly (without allowing to close all running processes, which includes Couatl.exe ) might cause this.
Have you seen a prompt to restart Coautl ? That would be the only case when Couatl will shut down itself and launch again, so perhaps the process doesn't work if it crashed at the same time.
-
Ok, I installed the newest Standalone Addon Manager 3.0.0.8 and checked "Restart Couatl and repeat audio diagnostics checks" - then, without errors, audio devices appeared on the list - sounds work. Thanks.
-
Hi,
unfortunatelly errors still exists... ok, from the beginning:
I installed Standalone Addon Manager 3.0.0.8. (and as I mentioned above - sound works)
Load the flight (NGX, at Freeware UK2000 EGLL, stand 192).
Request catering, choose operator and error:
(http://www.fotoszok.pl/out.php/t2530674_error1.jpg) (http://www.fotoszok.pl/show.php/2530674_error1.jpg.html)
(LOG atteched)
After press YES, another message:
(http://www.fotoszok.pl/out.php/t2530675_error2.jpg) (http://www.fotoszok.pl/show.php/2530675_error2.jpg.html)
After press YES, I requested catering again, and:
"Program Couatl Scripting Engine for FSX/ESP stop working"
Nazwa zdarzenia problemu: APPCRASH
Nazwa aplikacji: couatl.exe
Wersja aplikacji: 3.0.0.3185
Sygnatura czasowa aplikacji: 560525a4
Nazwa modułu z błędem: ntdll.dll
Wersja modułu z błędem: 6.0.6002.19454
Sygnatura czasowa modułu z błędem: 55ae6da5
Kod wyjątku: c0000005
Przesunięcie wyjątku: 0002a828
Wersja systemu operacyjnego: 6.0.6002.2.2.0.768.3
Identyfikator ustawień regionalnych: 1045
Dodatkowe informacje 1: fd00
Dodatkowe informacje 2: ea6f5fe8924aaa756324d57f87834160
Dodatkowe informacje 3: fd00
Dodatkowe informacje 4: ea6f5fe8924aaa756324d57f87834160
FSX still running, but there was not "GSX" in Addon menu.
After re-run FSX -> no audio device again. So I have to check option "Restart Couatl and repeat audio diagnostic".
GSX found audio devices, so I choose my audio device, press OK and... error again:
Nazwa zdarzenia problemu: APPCRASH
Nazwa aplikacji: couatl.exe
Wersja aplikacji: 3.0.0.3185
Sygnatura czasowa aplikacji: 560525a4
Nazwa modułu z błędem: oleaut32.dll
Wersja modułu z błędem: 6.0.6002.19243
Sygnatura czasowa modułu z błędem: 5475359a
Kod wyjątku: c0000005
Przesunięcie wyjątku: 0000452d
Wersja systemu operacyjnego: 6.0.6002.2.2.0.768.3
Identyfikator ustawień regionalnych: 1045
Dodatkowe informacje 1: fd00
Dodatkowe informacje 2: ea6f5fe8924aaa756324d57f87834160
Dodatkowe informacje 3: fd00
Dodatkowe informacje 4: ea6f5fe8924aaa756324d57f87834160
I pressed "Close Program" ..and second error:
Nazwa zdarzenia problemu: APPCRASH
Nazwa aplikacji: couatl.exe
Wersja aplikacji: 3.0.0.3185
Sygnatura czasowa aplikacji: 560525a4
Nazwa modułu z błędem: MSVCR120.dll
Wersja modułu z błędem: 12.0.21005.1
Sygnatura czasowa modułu z błędem: 524f7ce6
Kod wyjątku: c0000005
Przesunięcie wyjątku: 00011b0d
Wersja systemu operacyjnego: 6.0.6002.2.2.0.768.3
Identyfikator ustawień regionalnych: 1045
Dodatkowe informacje 1: f5cb
Dodatkowe informacje 2: 93d5d08571260f9300aeb2c6e94d930b
Dodatkowe informacje 3: 00ab
Dodatkowe informacje 4: 33141845f746de4a6eb1d7304cd7f7a0
After a few these cycles, finally I can choose my audio device again and there is a sound, but above errors can appear suddenly and problems start again... :(
EDIT: few minutes ago I had next error when choosing time of day in Free Flight menu:
Podpis problemu:
Nazwa zdarzenia problemu: BEX
Nazwa aplikacji: couatl.exe
Wersja aplikacji: 3.0.0.3185
Sygnatura czasowa aplikacji: 560525a4
Nazwa modułu z błędem: couatl.exe
Wersja modułu z błędem: 3.0.0.3185
Sygnatura czasowa modułu z błędem: 560525a4
Przesunięcie wyjątku: 002fa6a8
Kod wyjątku: c0000005
Dane wyjątku: 00000008
Wersja systemu operacyjnego: 6.0.6002.2.2.0.768.3
Identyfikator ustawień regionalnych: 1045
Dodatkowe informacje 1: 4d49
Dodatkowe informacje 2: 204ba7f044b2b66f0a57923eae5d0e1b
Dodatkowe informacje 3: 739f
Dodatkowe informacje 4: a1497cecf31066ee9cc68f844a5a62dc
-
Umberto,
do you think that install from full installer should help?
-
do you think that install from full installer should help?
Since the problem is not GSX, but some kind of issue with your sound drivers, I don't think it would make any difference but, you can always try.
Reinstall after restarting Windows, and turn off antivirus AND firewall (yes, even the default ones), to be sure you get all the latest version of all files.
-
Umberto,
but on earlier GSX versions there was no sound issues and Couatl errors I mentioned above... so how is it possible that this is the sound driver issue? I don't understand it...
-
but on earlier GSX versions there was no sound issues and Couatl errors I mentioned above... so how is it possible that this is the sound driver issue? I don't understand it...
Nothing in the handing of sound has changed in GSX since it has been released. It used OpenAL back then, and it still uses OpenAL today. But of course, it's possible your sound drivers might have been updated in the meantime
You haven't said what's the result of this:
Reinstall after restarting Windows, and turn off antivirus AND firewall (yes, even the default ones), to be sure you get all the latest version of all files.
-
Hi Umberto,
I did what you suggested... and after reinstall from full installer I get an error when FSX startup:
---------------------------
couatl.exe - not found component
---------------------------
Application run failed because not found python25.dll. Reinstall can resolve problem.
After pressing OK, another error:
Program Couatl Scripting Engine for FSX/ESP stop working.
Nazwa zdarzenia problemu: APPCRASH
Nazwa aplikacji: couatl.exe
Wersja aplikacji: 2.0.0.2378
Sygnatura czasowa aplikacji: 54bec650
Nazwa modułu z błędem: python25.dll
Wersja modułu z błędem: 6.0.6002.19454
Sygnatura czasowa modułu z błędem: 55ae6da5
Kod wyjątku: c0000135
Przesunięcie wyjątku: 0006f40f
Wersja systemu operacyjnego: 6.0.6002.2.2.0.768.3
Identyfikator ustawień regionalnych: 1045
Dodatkowe informacje 1: 9d13
Dodatkowe informacje 2: 1abee00edb3fc1158f9ad6f44f0f6be8
Dodatkowe informacje 3: 9d13
Dodatkowe informacje 4: 1abee00edb3fc1158f9ad6f44f0f6be8
However, FSX works after press "Close Program"
So, I completely uninstalled GSX in Control Panel (including uninstall Addon Manager and Couatl Engine)...
Restart Windows...
Reinstall GSX from the newest full installer...
FSX startup normally... but GSX was still without sound (<no audio devices>)
So I did Rescan audio devices, it found devices, so I set my speakers system... and still don't hear machines sounds BUT only in external view (?!) - However I hear "beep", when green top bar with communicate appears.
When I switch back to VC, I hear all (quieter of course because I'm in VC :) ) ... or when I switch to - for example - "wing view" and move camera (I have EZCA) near to the bus, baggage car or any other machine, I hear all sounds.
Is it normal?
Lucas
-
Hi Umberto,
I did what you suggested... and after reinstall from full installer I get an error when FSX startup:
Nazwa zdarzenia problemu: APPCRASH
Nazwa aplikacji: couatl.exe
Wersja aplikacji: 2.0.0.2378
Sygnatura czasowa aplikacji: 54bec650
Nazwa modułu z błędem: python25.dll
You have not installed the current GSX version, but a very old one. Or, you installed another FSDT product using an old installer, after GSX. There's an identical thread here:
http://www.fsdreamteam.com/forum/index.php/topic,7628.0.html
And I can only repeat and confirm, it can only happen if you install an older installer.
-
Umberto,
please... I downloaded full installer from GSX website yestarday, to be sure I have the newest version.
Unless on website is older version...however, I doubt.
-
please... I downloaded full installer from GSX website yestarday, to be sure I have the newest version. Unless on website is older version...however, I doubt.
You might have downloaded it, but you might have installed something else. The installer on the website is the latest version, and it doesn't contain Couatl 2 so, it's not possible you would get it by mistake by running it.
As I've said, the other thread I linked, indicates some solutions, like uninstalling and being sure no old files are still there.
But of course, it assumes you ARE installing using the 1.9.0.12 installer, which is the only installer we have online now.
-
You might have downloaded it, but you might have installed something else.
What exactly? I don't undarstand...
Anyway... as I mentioned, GSX Couatl doesn't show errors (for now) ... in my last post I asked about sounds in external view. Should I hear them in external view?
-
What exactly? I don't undarstand...
It's possible you are not installing what you just downloaded. Maybe the new download ended up in a different folder, and you are still launching an old installer from another download location.
Anyway... as I mentioned, GSX Couatl doesn't show errors (for now) ... in my last post I asked about sounds in external view. Should I hear them in external view?
Ok, so I guess you finally have the right version. Yes, you should hear some sounds (vehicles) in the external view. And if GSX said there's no audio device, it means your audio card doesn't support OpenAL, or there's a problem with the drivers.
Have you tried what I asked before ? Restart Windows, start FSX and try to select the audio device in GSX.
-
It's possible you are not installing what you just downloaded. Maybe the new download ended up in a different folder, and you are still launching an old installer from another download location.
Rather impossible. When download from your website was completed I opened folder straight from web browser with this downloaded file. But ok... I'll try check what GSX version I have currently installed.
it means your audio card doesn't support OpenAL
If I recall corectly you mentioned in another thread (or even this thread) that GSX was based on OpenAL from the beginning, but I never get these kind of problems before - so I believe it's impossible that my card does not support OpenAL.
Have you tried what I asked before ? Restart Windows, start FSX and try to select the audio device in GSX.
Not exactly, because sometimes only after restart FSX (restarting Windows was not necessary), GSX founded audio devices (of course I had to check "Rescan for audio devices" firsrtly) and then I could set proper audio device and sound worked well... BUT...after a few re-run FSX later, Couatl error appeared again. It was randomly.
Umberto, let's see what will happen ... as I mentioned, after yesterday's full reinstall of GSX, and after two or three FSX runs, there wasn't Couatl Error...but I'll keep an eye on it...
In the maintime, I'll check what GSX (and Couatl) version actually I have and report here.
-
Umberto, I checked Couatl version:
(http://www.fotoszok.pl/out.php/t2537733_couatlprop.jpg) (http://www.fotoszok.pl/show.php/2537733_couatlprop.jpg.html)
So, I hope, that Couatl errors finally gone... now I have to find the reason, that I don't hear car's engines sounds in external view...
-
Umberto, I checked Couatl version:
That's the correct one, finally.
If I recall corectly you mentioned in another thread (or even this thread) that GSX was based on OpenAL from the beginning, but I never get these kind of problems before - so I believe it's impossible that my card does not support OpenAL
I also said that is, instead, possible that a driver update might have issues with OpenAL. It's not as if this is just a GSX issue: if you Google for OpenAL issue, you'll find thousands of messages related to other games that use OpenAL that might stop working, maybe after a driver update.
GSX founded audio devices (of course I had to check "Rescan for audio devices" firsrtly) and then I could set proper audio device and sound worked well... BUT...after a few re-run FSX later, Couatl error appeared again. It was randomly.
Nothing is "random". There surely is a reason, for example if you restart FSX too quickly, not allowing Couatl (and all other running processes) to close correctly, and this will likely cause issue on the next run.
That's why I said to check after a Windows restart. I guess it *always* work after a restart ?
When you quit from FSX, pay attention with the Task Manager if Couatl.exe closes automatically.
-
I tought that problems are gone...unfortunatelly not.
Today I had Couatl error message again when I was choosing airport in main FSX menu. The error was:
Program Couatl Scripting Engine for FSX/ESP stop working.
Nazwa zdarzenia problemu: APPCRASH
Nazwa aplikacji: couatl.exe
Wersja aplikacji: 3.0.0.3187
Sygnatura czasowa aplikacji: 56128a59
Nazwa modułu z błędem: ntdll.dll
Wersja modułu z błędem: 6.0.6002.19503
Sygnatura czasowa modułu z błędem: 5606c25a
Kod wyjątku: c0000005
Przesunięcie wyjątku: 00061129
Wersja systemu operacyjnego: 6.0.6002.2.2.0.768.3
Identyfikator ustawień regionalnych: 1045
Dodatkowe informacje 1: fd00
Dodatkowe informacje 2: ea6f5fe8924aaa756324d57f87834160
Dodatkowe informacje 3: fd00
Dodatkowe informacje 4: ea6f5fe8924aaa756324d57f87834160
When I pressed "Close program", there was next Couatl error:
Program Couatl Scripting Engine for FSX/ESP stop working.
Nazwa zdarzenia problemu: APPCRASH
Nazwa aplikacji: couatl.exe
Wersja aplikacji: 3.0.0.3187
Sygnatura czasowa aplikacji: 56128a59
Nazwa modułu z błędem: MSVCR120.dll
Wersja modułu z błędem: 12.0.21005.1
Sygnatura czasowa modułu z błędem: 524f7ce6
Kod wyjątku: c0000005
Przesunięcie wyjątku: 00010e20
Wersja systemu operacyjnego: 6.0.6002.2.2.0.768.3
Identyfikator ustawień regionalnych: 1045
Dodatkowe informacje 1: 0e48
Dodatkowe informacje 2: 7fe478a5a1021b43aada3d50d999fd5b
Dodatkowe informacje 3: 284c
Dodatkowe informacje 4: 8b7ab5e437ad4cc64febe836afc565a1
I have no idea what is wrong. I have never have problems with GSX before like these :(
You also said
I also said that is, instead, possible that a driver update might have issues with OpenAL. It's not as if this is just a GSX issue: if you Google for OpenAL issue, you'll find thousands of messages related to other games that use OpenAL that might stop working, maybe after a driver update.
I didn't update audio driver.
EDIT.
After above situation, I restart FSX, set audio - all works. But after next run of FSX (today) error again in the same time (when choosing airport):
Nazwa zdarzenia problemu: APPCRASH
Nazwa aplikacji: couatl.exe
Wersja aplikacji: 3.0.0.3187
Sygnatura czasowa aplikacji: 56128a59
Nazwa modułu z błędem: kernel32.dll
Wersja modułu z błędem: 6.0.6002.19381
Sygnatura czasowa modułu z błędem: 554d42e0
Kod wyjątku: c0000005
Przesunięcie wyjątku: 0004d3cc
Wersja systemu operacyjnego: 6.0.6002.2.2.0.768.3
Identyfikator ustawień regionalnych: 1045
Dodatkowe informacje 1: fd00
Dodatkowe informacje 2: ea6f5fe8924aaa756324d57f87834160
Dodatkowe informacje 3: fd00
Dodatkowe informacje 4: ea6f5fe8924aaa756324d57f87834160
Look, that every error is related with another .dll file. What is going on?
-
Ok, I updated audio driver to the newest version (Realtek HD Audio v2.79) - will see...
-
Hello Umberto,
so...yesterday I had Couatl error again. It appeared after the flight, while GSX deboarding:
I opened GSX options and Airport position configure to check pushback settings for this gate. It was set only on one direction, so I set it to "both" and after Apply, error appeared:
Nazwa zdarzenia problemu: APPCRASH
Nazwa aplikacji: couatl.exe
Wersja aplikacji: 3.0.0.3187
Sygnatura czasowa aplikacji: 56128a59
Nazwa modułu z błędem: python27.dll
Wersja modułu z błędem: 0.0.0.0
Sygnatura czasowa modułu z błędem: 54e5f9b4
Kod wyjątku: c0000005
Przesunięcie wyjątku: 001267dc
Wersja systemu operacyjnego: 6.0.6002.2.2.0.768.3
Identyfikator ustawień regionalnych: 1045
Dodatkowe informacje 1: fd00
Dodatkowe informacje 2: ea6f5fe8924aaa756324d57f87834160
Dodatkowe informacje 3: fd00
Dodatkowe informacje 4: ea6f5fe8924aaa756324d57f87834160
Of course FSX was still running.
The difference is that I have all GSX sounds after restart FSX (in GSX Settings I saw my audio device; it was no need to Rescan Audio devices).
-
Ok, I updated audio driver to the newest version (Realtek HD Audio v2.79) - will see...
As I've said in another thread, I just rebuilt a new PC from scratch, with Windows 10 freshly installed. Using the Windows 10 audio drivers that came with the mainboard ( ASUS, with Realtek audio chipset ), NORMAL WINDOWS AUDIO randomly disappeared. I'm not referring to GSX or FSX. I'm referring to the normal, standard, sounds that Windows makes.
Searching online, it seems Realtek is blaming Microsoft, and Microsoft is blaming Realtek...
However, when I uninstalled the audio drivers that came with the mainboard, and replaced them with the generic ones that comes with Windows for the Realtek chipset, all my problems with audio disappeared.
I'm not suggesting this might be the same thing that affects Couatl, but it's something you might want to try.
-
Ok, I can try what you suggest.
In the meantime I had a little bit different Couatl error:
Nazwa zdarzenia problemu: BEX
Nazwa aplikacji: couatl.exe
Wersja aplikacji: 3.0.0.3187
Sygnatura czasowa aplikacji: 56128a59
Nazwa modułu z błędem: couatl.exe
Wersja modułu z błędem: 3.0.0.3187
Sygnatura czasowa modułu z błędem: 56128a59
Przesunięcie wyjątku: 003176be
Kod wyjątku: c0000005
Dane wyjątku: 00000008
Wersja systemu operacyjnego: 6.0.6002.2.2.0.768.3
Identyfikator ustawień regionalnych: 1045
Dodatkowe informacje 1: b80a
Dodatkowe informacje 2: f52b7790ad863725610c4526356ab152
Dodatkowe informacje 3: a554
Dodatkowe informacje 4: 55364b150664a7a2aff4541773cc929e
It appeared after choosing airport in Free Flight menu.
Maybe it tells you something...
-
In the meantime I had a little bit different Couatl error:[/quote]
Maybe it tells you something...
It doesn't tell anything, other that nobody else reported it. Perhaps you have one of your custom configuration files corrupted or simply made wrong.
Try to remove the following folder:
%APPDATA%\Virtuali
And reinstall GSX. This will result in removing all the settings you changed, including aircraft and airport customizations so, you might want to backup them first.
-
Ok Umberto,
all my problems are not related with sound driver - I deinstalled Realtek audio driver and startup FSX with generic audio driver installed by Windows. Same error like above.
I don't know what is wrong. Everything started when I installed Couatl 3.0...
Try to remove the following folder:
%APPDATA%\Virtuali
And reinstall GSX.
Ok, I can do that...we will see.
I think it doesn't matter what I will do first: delete \Virtuali folder or uninstall GSX?
-
all my problems are not related with sound driver - I deinstalled Realtek audio driver and startup FSX with generic audio driver installed by Windows. Same error like above.
SOME of your errors you posted here ARE surely caused by the audio driver. Some are not.
I think it doesn't matter what I will do first: delete \Virtuali folder or uninstall GSX?
I told you to remove the folder AND reinstall GSX, in that specific order, because you MUST remove the folder first AND THEN reinstall GSX.
-
I told you to remove the folder AND reinstall GSX, in that specific order, because you MUST remove the folder first AND THEN reinstall GSX.
You didn't wrote in previous post that it has a matter...I just want to be sure. Thanks.
-
Umberto,
I did what you suggest:
Try to remove the following folder: %APPDATA%\Virtuali
And reinstall GSX.
I downloaded the last version (full installer) from your site.
First FSX run after reinstall ... and Couatl error.
Now, using GSX is great lottery. I'm disappointed. GSX worked great...until Couatl 3.0 I think. Now, it's nearly unusable for me.
-
I downloaded the last version (full installer) from your site. First FSX run after reinstall ... and Couatl error.
What error ?
Now, using GSX is great lottery. I'm disappointed. GSX worked great...until Couatl 3.0 I think. Now, it's nearly unusable for me
If you are referring to the audio errors, you are the only one with this error. The only other user that had issues with audio, fixed them by updating the audio driver, of course:
http://www.fsdreamteam.com/forum/index.php/topic,12718.msg96119.html#msg96119
-
I also updated audio driver, but no results.
Error was the same as before: "Program Couatl Scripting Engine for FSX/ESP stop working." It only reffered to another .dll.
I don't know if all this situation is related with audio driver, because sometimes, after restart FSX, GSX' sounds work, sometimes not.
-
I don't know if all this situation is related with audio driver, because sometimes, after restart FSX, GSX' sounds work, sometimes not.
You clearly have an audio driver problem. Exactly as in the thread linked before, the user was also puzzled why sometimes it worked, sometimes not:
http://www.fsdreamteam.com/forum/index.php/topic,12718.msg96064.html#msg96064
How can Couatl and audio fail twice then work perfectly all in one session without a reboot or reinstall or anything
-
Umberto,
does the following error is related with sound driver:
Nazwa zdarzenia problemu: APPCRASH
Nazwa aplikacji: couatl.exe
Wersja aplikacji: 3.0.0.3187
Sygnatura czasowa aplikacji: 56128a59
Nazwa modułu z błędem: StackHash_378e
Wersja modułu z błędem: 0.0.0.0
Sygnatura czasowa modułu z błędem: 00000000
Kod wyjątku: 00000000
Przesunięcie wyjątku: 00000000
Wersja systemu operacyjnego: 6.0.6002.2.2.0.768.3
Identyfikator ustawień regionalnych: 1045
Dodatkowe informacje 1: 378e
Dodatkowe informacje 2: 9cb57cf9db8e077c0c60205279fd5eff
Dodatkowe informacje 3: 753c
Dodatkowe informacje 4: b9ccea9dc15dae8045271a15f72be1a9
-
does the following error is related with sound driver:
A driver could cause errors in any place in Windows, because it's the only kind of software that has complete access to it.
If the problem was related in any way to our software, SOMEONE ELSE would have reported it. Instead, it's just you now, with random error messages that keeps appearing out of nothing.
I'm sorry, but it's clear the problem is something in your system that is CAUSING Couatl to crash, not the other way around. Couatl is the victim here...
-
"Now, using GSX is great lottery. I'm disappointed. GSX worked great...until Couatl 3.0 I think. Now, it's nearly unusable for me"
If you are referring to the audio errors, you are the only one with this error. The only other user that had issues with audio, fixed them by updating the audio driver, of course: http://www.fsdreamteam.com/forum/index.php/topic,12718.msg96119.html#msg96119
No, he’s not the only one. I have the same problem and it started from updating Couatl. I’ve installed latest audio driver but it didn’t fix anything.
It seems that something is wrong between Realtek audio drivers and Couatl 3.0.
-
Hi Izomag,
I leave this issue and didn't use GSX.
Now, I have fresh Windows 10 install and FSX:SE. Didn't install any external (separately downloaded) Realtek audio drivers (so, I use stock Windows drivers).
GSX works... for now...
Regards,
-
Now, I have fresh Windows 10 install and FSX:SE. Didn't install any external (separately downloaded) Realtek audio drivers (so, I use stock Windows drivers).
GSX works... for now...
That seems to confirm what I said in a previous reply:
http://www.fsdreamteam.com/forum/index.php/topic,12536.msg96105.html#msg96105
-
Umberto,
but I reinstalled all system and simulator. Do you mean that is the only solution? Hope not...
Anyway, before reinstall system I didn't resolve it... even by uninstalling Realtek audio driver and using generic one.
-
but I reinstalled all system and simulator. Do you mean that is the only solution? Hope not...
I'm not sure I understand you: you say it's working now. If this worked for you, than it means in YOUR case, a reinstall was needed.
Anyway, before reinstall system I didn't resolve it... even by uninstalling Realtek audio driver and using generic one.
That's likely because the sound driver uninstaller didn't uninstall anything, but left some conflicting file behind. Again, nothing to do with GSX, which was just affected by a problem in your audio driver installation.
-
Hi Izomag,
I leave this issue and didn't use GSX.
Now, I have fresh Windows 10 install and FSX:SE. Didn't install any external (separately downloaded) Realtek audio drivers (so, I use stock Windows drivers).
GSX works... for now...
Regards,
No way, I’m not going to reinstall the whole operating system because of conflict in one FSX addon :D
But thanks for sharing, luko!
Just a couple of months ago, GSX worked great on my PC and with my audio drivers. Now, the PC and the drivers are the same, it’s Couatl that changed. And I belive that faulty drivers should affect more than only one application.
Perhaps there is a downgrade to the previous version of the GSX?
-
No way, I’m not going to reinstall the whole operating system because of conflict in one FSX addon
Nobody said you *must* reinstall your OS. You should do that only if you are unable to fix the problem caused by your audio drivers in another way.
Just a couple of months ago, GSX worked great on my PC and with my audio drivers. Now, the PC and the drivers are the same, it’s Couatl that changed.
Your audio drivers must have changed or ANOTHER file in your system has AFFECT THEM. Nothing in Couatl has changed in relationship to audio since it was released.
And I belive that faulty drivers should affect more than only one application.
If will affect ONLY games/apps that use the OpenAL library, which is something that works (or not) ONLY if your audio drivers correctly supports it.
If you don't have any other game/app using Open-AL, you won't notice any problem with audio. That's why you can be easily mislead thinking it must be a Couatl/GSX problem, when it's not.
This is CLEARLY proven by luko report. Under your reasoning, if it was a problem that "Couatl has changed", it should NOT work after an OS reinstall, shouldn't it ?
Since the Couatl luko was using *before* reinstalling the OS is the same, if he fixed his problem by reinstalling the OS, it's should be fairly obvious that what caused the problem was something in his previous OS installation, not Couatl, since he's installing the same version which didn't work on his old OS install.
Perhaps there is a downgrade to the previous version of the GSX?
You cannot downgrade GSX, unless you have an old version and install it with the network disconnected. But I doubt this will fix anything.
-
Thank you for your response.
Reinstalling the Standalone Addon Manager (version 3.0.0.10 downloaded from Fsdreamteam website) seems to help somehow. Couatl is still unstable, but at least the GSX is usable now. Autodiagnostic checks for audio often are needed, but Couatl doesn’t crash completely everytime during restart anymore (altough sometimes it still happens).
I found that allowing Couatl to update via Live Update within FSX, will cause Couatl to crash permanently and the only rescue from that situation will be reinstalling the Standalone Addon Manager again. In fact, doing anything with Live Update (even trying to disable it) immediately causes Couatl to crash. But as long as I keep my hands away from Live Update, GSX seems to work.
I don't belive this issue is really solved, but complete reinstall the Standalone Addon Manager and keeping away from Couatl Live Update helped a little in my case.
...without reinstalling the whole operating system ;)
-
Reinstalling the Standalone Addon Manager (version 3.0.0.10 downloaded from Fsdreamteam website) seems to help somehow
The Stand-Alone Addon Manager doesn't have ANY interaction with ANY of the audio in your PC so no, it's impossible that installing it would make *any* difference to anything related to audio.
Couatl is still unstable, but at least the GSX is usable now. Autodiagnostic checks for audio often are needed, but Couatl doesn’t crash completely everytime during restart anymore (altough sometimes it still happens).
If the audio diagnostic checks sometimes fails, that's a clear proof OpenAL support in your audio drivers is buggy. And there's not much else we can do about it, other than *having* that diagnostic to point you out of a problem with your audio.
If the audio diagnostic, we can at least not use audio and have GSX runs silently, but with no crashes. But, if the audio drivers is bugged, and initializes correct, but it then won't work when used, Couatl will surely crash when audio is called. The diagnostic is not a complete test of each and every function: it's just a test if the audio *initializes* correctly, but we wouldn't know for sure it won't ever crash when USED. In order to do that, we should make a complete audio diagnostic that would call each and every OpenAL function, and if some of it would fail, it WILL probably crash while doing the test!
If we could be able to test each and every audio function in your drivers, and doing that without crashing, that would be an impressive feat by itself, more than the whole GSX product, and might be a worthwhile product to sell as a stand-alone audio troubleshooting utility.
I found that allowing Couatl to update via Live Update within FSX, will cause Couatl to crash permanently and the only rescue from that situation will be reinstalling the Standalone Addon Manager again. In fact, doing anything with Live Update (even trying to disable it) immediately causes Couatl to crash. But as long as I keep my hands away from Live Update, GSX seems to work.
The Live Update downloads exactly the same files as the Stand-Alone Addon Manager, with the exception that the Stand-Alone Addon Manager downloads also the latest Couatl.exe (if you don't have it already), and the latest version of the Addon Manager (bglmanx.dll, if you don't have it already) so, the problem doesn't have anything to do with Live Update but, instead, it's just seems to be a generic issue of restarting Couatl, which is done automatically by the Live Update when it's done.
You'll probably have the same issue if you restart Couatl manually from the menu, and this can ALSO be caused by a problem with audio drivers, since if they are initialized and fail, there might cause problems during a restart.
I don't belive this issue is really solved, but complete reinstall the Standalone Addon Manager and keeping away from Couatl Live Update helped a little in my case.
Since the issue doesn't have much to do with Couatl of the Addon Manager, it's to be expected it won't be "really solved" by reinstalling any of them. In order to "really solve it", you must act on your audio drivers, because they are the REAL problem.