wakevortex Posted July 3, 2022 Report Share Posted July 3, 2022 I have recently been getting the x plane log filling up with FMOD errors when flying the current update of the challenger -like below ,but many more 0:04:07.079 E/FMOD: C:/jenkins/design-triggered/source_code/app/X-Plane-f/../../engine/sound/soun_fmod.cpp(144): FMOD error 2 - Error trying to allocate a channel. 0:04:07.100 E/FMOD: C:/jenkins/design-triggered/source_code/app/X-Plane-f/../../engine/sound/soun_fmod.cpp(144): FMOD error 2 - Error trying to allocate a channel. 0:04:07.116 E/FMOD: C:/jenkins/design-triggered/source_code/app/X-Plane-f/../../engine/sound/soun_fmod.cpp(144): FMOD error 2 - Error trying to allocate a channel. 0:04:07.131 E/FMOD: C:/jenkins/design-triggered/source_code/app/X-Plane-f/../../engine/sound/soun_fmod.cpp(144): FMOD error 2 - Error trying to allocate a channel. 0:04:07.146 E/FMOD: C:/jenkins/design-triggered/source_code/app/X-Plane-f/../../engine/sound/soun_fmod.cpp(144): FMOD error 2 - Error trying to allocate a channel. 0:04:07.160 E/FMOD: C:/jenkins/design-triggered/source_code/app/X-Plane-f/../../engine/sound/soun_fmod.cpp(144): FMOD error 2 - Error trying to allocate a channel. 0:04:07.175 E/FMOD: C:/jenkins/design-triggered/source_code/app/X-Plane-f/../../engine/sound/soun_fmod.cpp(144): FMOD error 2 - Error trying to allocate a channel. 0:04:07.191 E/FMOD: C:/jenkins/design-triggered/source_code/app/X-Plane-f/../../engine/sound/soun_fmod.cpp(144): FMOD error 2 - Error trying to allocate a channel. 0:04:07.207 E/FMOD: C:/jenkins/design-triggered/source_code/app/X-Plane-f/../../engine/sound/soun_fmod.cpp(144): FMOD error 2 - Error trying to allocate a channel. 0:04:07.223 E/FMOD: C:/jenkins/design-triggered/source_code/app/X-Plane-f/../../engine/sound/soun_fmod.cpp(144): FMOD error 2 - Error trying to allocate a channel. 0:04:07.237 E/FMOD: C:/jenkins/design-triggered/source_code/app/X-Plane-f/../../engine/sound/soun_fmod.cpp(144): FMOD error 2 - Error trying to allocate a channel. 0:04:07.252 E/FMOD: C:/jenkins/design-triggered/source_code/app/X-Plane-f/../../engine/sound/soun_fmod.cpp(144): FMOD error 2 - Error trying to allocate a channel. 0:04:07.267 E/FMOD: C:/jenkins/design-triggered/source_code/app/X-Plane-f/../../engine/sound/soun_fmod.cpp(144): FMOD error 2 - Error trying to allocate a channel. 0:04:07.282 E/FMOD: C:/jenkins/design-triggered/source_code/app/X-Plane-f/../../engine/sound/soun_fmod.cpp(144): FMOD error 2 - Error trying to allocate a channel. 0:04:07.297 E/FMOD: C:/jenkins/design-triggered/source_code/app/X-Plane-f/../../engine/sound/soun_fmod.cpp(144): FMOD error 2 - Error trying to allocate a channel. 0:04:07.311 E/FMOD: C:/jenkins/design-triggered/source_code/app/X-Plane-f/../../engine/sound/soun_fmod.cpp(144): FMOD error 2 - Error trying to allocate a channel. 0:04:07.326 E/FMOD: C:/jenkins/design-triggered/source_code/app/X-Plane-f/../../engine/sound/soun_fmod.cpp(144): FMOD error 2 - Error trying to allocate a channel. 0:04:07.340 E/FMOD: C:/jenkins/design-triggered/source_code/app/X-Plane-f/../../engine/sound/soun_fmod.cpp(144): FMOD error 2 - Error trying to allocate a channel. 0:04:07.355 E/FMOD: C:/jenkins/design-triggered/source_code/app/X-Plane-f/../../engine/sound/soun_fmod.cpp(144): FMOD error 2 - Error trying to allocate a channel. 0:04:07.369 E/FMOD: C:/jenkins/design-triggered/source_code/app/X-Plane-f/../../engine/sound/soun_fmod.cpp(144): FMOD error 2 - Error trying to allocate a channel Is this connected to the challenger or is it coming from something else? Its only there when the C650 is loaded... any help appreciated Bill P Quote Link to comment Share on other sites More sharing options...
Cam Posted July 3, 2022 Report Share Posted July 3, 2022 1 hour ago, wakevortex said: I have recently been getting the x plane log filling up with FMOD errors when flying the current update of the challenger -like below ,but many more 0:04:07.079 E/FMOD: C:/jenkins/design-triggered/source_code/app/X-Plane-f/../../engine/sound/soun_fmod.cpp(144): FMOD error 2 - Error trying to allocate a channel. 0:04:07.100 E/FMOD: C:/jenkins/design-triggered/source_code/app/X-Plane-f/../../engine/sound/soun_fmod.cpp(144): FMOD error 2 - Error trying to allocate a channel. 0:04:07.116 E/FMOD: C:/jenkins/design-triggered/source_code/app/X-Plane-f/../../engine/sound/soun_fmod.cpp(144): FMOD error 2 - Error trying to allocate a channel. 0:04:07.131 E/FMOD: C:/jenkins/design-triggered/source_code/app/X-Plane-f/../../engine/sound/soun_fmod.cpp(144): FMOD error 2 - Error trying to allocate a channel. 0:04:07.146 E/FMOD: C:/jenkins/design-triggered/source_code/app/X-Plane-f/../../engine/sound/soun_fmod.cpp(144): FMOD error 2 - Error trying to allocate a channel. 0:04:07.160 E/FMOD: C:/jenkins/design-triggered/source_code/app/X-Plane-f/../../engine/sound/soun_fmod.cpp(144): FMOD error 2 - Error trying to allocate a channel. 0:04:07.175 E/FMOD: C:/jenkins/design-triggered/source_code/app/X-Plane-f/../../engine/sound/soun_fmod.cpp(144): FMOD error 2 - Error trying to allocate a channel. 0:04:07.191 E/FMOD: C:/jenkins/design-triggered/source_code/app/X-Plane-f/../../engine/sound/soun_fmod.cpp(144): FMOD error 2 - Error trying to allocate a channel. 0:04:07.207 E/FMOD: C:/jenkins/design-triggered/source_code/app/X-Plane-f/../../engine/sound/soun_fmod.cpp(144): FMOD error 2 - Error trying to allocate a channel. 0:04:07.223 E/FMOD: C:/jenkins/design-triggered/source_code/app/X-Plane-f/../../engine/sound/soun_fmod.cpp(144): FMOD error 2 - Error trying to allocate a channel. 0:04:07.237 E/FMOD: C:/jenkins/design-triggered/source_code/app/X-Plane-f/../../engine/sound/soun_fmod.cpp(144): FMOD error 2 - Error trying to allocate a channel. 0:04:07.252 E/FMOD: C:/jenkins/design-triggered/source_code/app/X-Plane-f/../../engine/sound/soun_fmod.cpp(144): FMOD error 2 - Error trying to allocate a channel. 0:04:07.267 E/FMOD: C:/jenkins/design-triggered/source_code/app/X-Plane-f/../../engine/sound/soun_fmod.cpp(144): FMOD error 2 - Error trying to allocate a channel. 0:04:07.282 E/FMOD: C:/jenkins/design-triggered/source_code/app/X-Plane-f/../../engine/sound/soun_fmod.cpp(144): FMOD error 2 - Error trying to allocate a channel. 0:04:07.297 E/FMOD: C:/jenkins/design-triggered/source_code/app/X-Plane-f/../../engine/sound/soun_fmod.cpp(144): FMOD error 2 - Error trying to allocate a channel. 0:04:07.311 E/FMOD: C:/jenkins/design-triggered/source_code/app/X-Plane-f/../../engine/sound/soun_fmod.cpp(144): FMOD error 2 - Error trying to allocate a channel. 0:04:07.326 E/FMOD: C:/jenkins/design-triggered/source_code/app/X-Plane-f/../../engine/sound/soun_fmod.cpp(144): FMOD error 2 - Error trying to allocate a channel. 0:04:07.340 E/FMOD: C:/jenkins/design-triggered/source_code/app/X-Plane-f/../../engine/sound/soun_fmod.cpp(144): FMOD error 2 - Error trying to allocate a channel. 0:04:07.355 E/FMOD: C:/jenkins/design-triggered/source_code/app/X-Plane-f/../../engine/sound/soun_fmod.cpp(144): FMOD error 2 - Error trying to allocate a channel. 0:04:07.369 E/FMOD: C:/jenkins/design-triggered/source_code/app/X-Plane-f/../../engine/sound/soun_fmod.cpp(144): FMOD error 2 - Error trying to allocate a channel Is this connected to the challenger or is it coming from something else? Its only there when the C650 is loaded... any help appreciated Bill P I have also had these errors on a CL650 crash. Quote Link to comment Share on other sites More sharing options...
wakevortex Posted July 3, 2022 Author Report Share Posted July 3, 2022 1 hour ago, Cam said: I have also had these errors on a CL650 crash. Aircraft seems fine..no crash, just noticed these in the log... Quote Link to comment Share on other sites More sharing options...
Pils Posted July 3, 2022 Report Share Posted July 3, 2022 26 minutes ago, wakevortex said: Aircraft seems fine..no crash, just noticed these in the log... These are from a bug in X-Plane that can’t be avoided, you can ignore them. Quote Link to comment Share on other sites More sharing options...
Scorpio47 Posted July 27, 2022 Report Share Posted July 27, 2022 (edited) On 7/3/2022 at 3:05 PM, Pils said: These are from a bug in X-Plane that can’t be avoided, you can ignore them. Hi Pils, I am not so sure about that, as other aircraft use FMOD too and do NOT lead to this long list of "Error(s) trying to allocate a channel". That seems to indicate that it IS perhaps a problem specific to the Challenger.... OK, nothing bad happens I guess, but nevertheless XP crashes when asked to quit and wants to send a report to Microsoft (who could not care less...). As you can see from the message above, there seems to be a faulty path starting with "C:/jenkins/design-triggered/source......." that provokes those messages. Perhaps this can be corrected in the file "Master Bank.bank" which is the biggest in the fmod directory and probably holds that information which is clearly wrong. I would assume that no user has a directory on his C: drive with that name, haha. Thanks for looking into this annoying error messages which are unique to the Challenger. If that helps to exclude our beloved plane, even better. The question then is where this path information comes from..... Kind regards Jürgen P.S. I found fmod also in the Carenado Turbo Commander 690B and the Phenom 300 by Aerobask and most likely some other planes. They do not generate that error.... Edited July 27, 2022 by Scorpio47 P.S. added Quote Link to comment Share on other sites More sharing options...
Ben Russell Posted July 27, 2022 Report Share Posted July 27, 2022 https://www.jenkins.io/ The path is likely part of the Laminar research xplane build process. Given the deep complexity of the product I'm sure the issue would be solved if it could be or it actually mattered. The crash on exit could be caused by many things. Quote Link to comment Share on other sites More sharing options...
Pils Posted July 27, 2022 Report Share Posted July 27, 2022 (edited) 2 hours ago, Scorpio47 said: other aircraft use FMOD too and do NOT lead to this long list of "Error(s) trying to allocate a channel". That seems to indicate that it IS perhaps a problem specific to the Challenger.... Other aircraft don’t have as many audio samples and as complex a soundstage as the Challenger. It’s really pushing X-Plane 11 to its limit. The developer has been in direct contact with Laminar on this issue. Maybe they will address it in 12. 2 hours ago, Scorpio47 said: As you can see from the message above, there seems to be a faulty path starting with "C:/jenkins/design-triggered/source......." that provokes those messages. As Ben surmises, these paths are baked into the error messages as part of the executable by Laminar’s build (compilation) pipeline. They are nothing to do your local system and can be ignored. Edited July 27, 2022 by Pils Quote Link to comment Share on other sites More sharing options...
Scorpio47 Posted July 27, 2022 Report Share Posted July 27, 2022 Thank you both Pils and Ben, that will most probably be the situation then. My idea was simply triggered by that strange path and I assumed that it came from the sounds database built into the plane. Your explanation makes perfect sense and we can all only hope that Laminar will take care of the issue in the next version. Until then I´ll just ignore the errors and live with the CdT at the end of each session. No harm done Thanks again for your expert input and for teaching us something (again)! Cheers Jürgen 1 Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.