|
sounds
Dec 23, 2020 17:44:04 GMT
Post by msparks on Dec 23, 2020 17:44:04 GMT
several sounds (like low and high rotor RPM) in VSL R44.snd use a != condition to stop. xplane fmod doesn't support this, so they dont had to disable the autoupdater to change them <
Great bird btw.
|
|
|
sounds
Feb 17, 2021 9:40:45 GMT
Post by msparks on Feb 17, 2021 9:40:45 GMT
OK, this might be something else, I keep getting a "something has corrupted the master sound banks you may need to install XP to correct this" hoping its just a corrupt file, I'll try reinstalling it?
Any other ideas?
|
|
|
sounds
Feb 22, 2021 5:22:40 GMT
Post by VSL-Admin on Feb 22, 2021 5:22:40 GMT
OK, this might be something else, I keep getting a "something has corrupted the master sound banks you may need to install XP to correct this" hoping its just a corrupt file, I'll try reinstalling it? Any other ideas? Hello there! Your report was tested thoroughly and was not confirmed. Would suggest to make sure that you are using the most updated version of the project. In addition, there are reports of sound banks issues in X-Plane 11, after updating to the 11.50 "block", so it may be related to preferences, or other addons conflicts. Trying this on a clean X-Plane install (even the demo) may confirm that. Let me know your findings!
|
|
|
sounds
Feb 23, 2021 2:12:04 GMT
Post by msparks on Feb 23, 2021 2:12:04 GMT
I think I had a corrupt .bank file, I re downloaded and extracted and I haven't seen it since.
Wonder if the != issue is a linux thing, because I would assume this wouldn't have happened otherwise, but I had to change
EVENT_END_COND sim/cockpit2/switches/instrument_brightness_ratio[10] != 0.5 to EVENT_END_COND sim/cockpit2/switches/instrument_brightness_ratio[10] < 0.5
and EVENT_END_COND sim/cockpit2/switches/instrument_brightness_ratio[10] != 1 to EVENT_END_COND sim/cockpit2/switches/instrument_brightness_ratio[10] < 1
Otherwise when the low/high rpm horns sounded they would never stop.
|
|
|
sounds
Feb 23, 2021 7:15:20 GMT
Post by VSL-Admin on Feb 23, 2021 7:15:20 GMT
I think I had a corrupt .bank file, I re downloaded and extracted and I haven't seen it since. Wonder if the != issue is a linux thing, because I would assume this wouldn't have happened otherwise, but I had to change EVENT_END_COND sim/cockpit2/switches/instrument_brightness_ratio[10] != 0.5 to EVENT_END_COND sim/cockpit2/switches/instrument_brightness_ratio[10] < 0.5 and EVENT_END_COND sim/cockpit2/switches/instrument_brightness_ratio[10] != 1 to EVENT_END_COND sim/cockpit2/switches/instrument_brightness_ratio[10] < 1 Otherwise when the low/high rpm horns sounded they would never stop. Hi there! Main VSKYLABS development rigs are Linux (Ubuntu)...and this was never observed... I just read a reply at the .org of a guy with a sound bank issues, he found out that it was caused by SteamVR. So he closed it, and when launched X-Plane, he enabled VR from X-Plane and let X-Plane to launch it. Then all of the sound issues were over. I don't know if this is your case, but sharing his findings anyways...
|
|
|
sounds
Feb 23, 2021 16:57:51 GMT
Post by msparks on Feb 23, 2021 16:57:51 GMT
I think I had a corrupt .bank file, I re downloaded and extracted and I haven't seen it since. Wonder if the != issue is a linux thing, because I would assume this wouldn't have happened otherwise, but I had to change EVENT_END_COND sim/cockpit2/switches/instrument_brightness_ratio[10] != 0.5 to EVENT_END_COND sim/cockpit2/switches/instrument_brightness_ratio[10] < 0.5 and EVENT_END_COND sim/cockpit2/switches/instrument_brightness_ratio[10] != 1 to EVENT_END_COND sim/cockpit2/switches/instrument_brightness_ratio[10] < 1 Otherwise when the low/high rpm horns sounded they would never stop. he found out that it was caused by SteamVR. Thanks, yeah, this could be it, it wasn't 100% of the time every flight (and it could have been related to whatever corruption was causing the "corrupt sound banks"), if I find out any more or get a reliable way to recreate it I'll let you know (flying her a lot atm)
|
|
|
sounds
May 23, 2021 14:52:59 GMT
Post by msparks on May 23, 2021 14:52:59 GMT
After a lot of faf and A+B testing, I _think_ I've tracked it down to one or both of these two: BEGIN_SOUND_ATTACHMENT EVENT_NAME /rotorblades-ext #VEH_XYZ 0 0 0 PARAM_DREF_IDX 0 #EVENT_ALLOWED_FOR_AI EVENT_START_COND sim/flightmodel2/engines/prop_rotation_speed_rad_sec[0] > 5 EVENT_END_COND sim/flightmodel2/engines/prop_rotation_speed_rad_sec[0] < 5 END_SOUND_ATTACHMENT BEGIN_SOUND_ATTACHMENT EVENT_NAME /rotorblades-woosh-int #VEH_XYZ 0 0 0 PARAM_DREF_IDX 0 #EVENT_ALLOWED_FOR_AI EVENT_START_COND sim/flightmodel2/engines/prop_rotation_speed_rad_sec[0] > 5 EVENT_END_COND sim/flightmodel2/engines/prop_rotation_speed_rad_sec[0] < 5 END_SOUND_ATTACHMENT ____ Yes, SteamVR definately "helps it on its way" - the != vs < was a total red herring. Here's a video of what happens when the sound system crashes (e.g. low rotor sound never stops - but its just general fmod crazy with sounds starting and never stopping): youtu.be/YHuo9npYpssDeleting the above two events seems to stop it happening. The errors coming up in the log are: 0:00:35.962 E/FMOD: /jenkins/design-triggered/source_code/app/X-Plane-f/../../engine/sound/soun_fmod.cpp(144): FMOD error 31 - An invalid parameter was passed to this function. 0:00:36.007 I/TEX: Target scale moved to 8.000000 0:00:36.007 E/FMOD: /jenkins/design-triggered/source_code/app/X-Plane-f/../../engine/sound/soun_fmod.cpp(144): FMOD error 28 - An error occurred that wasn't supposed to. Contact support. 0:00:36.036 E/FMOD: /jenkins/design-triggered/source_code/app/X-Plane-f/../../engine/sound/soun_fmod.cpp(144): FMOD error 28 - An error occurred that wasn't supposed to. Contact support.
|
|
|
sounds
May 23, 2021 16:40:09 GMT
Post by VSL-Admin on May 23, 2021 16:40:09 GMT
After a lot of faf and A+B testing, I _think_ I've tracked it down to one or both of these two: BEGIN_SOUND_ATTACHMENT EVENT_NAME /rotorblades-ext #VEH_XYZ 0 0 0 PARAM_DREF_IDX 0 #EVENT_ALLOWED_FOR_AI EVENT_START_COND sim/flightmodel2/engines/prop_rotation_speed_rad_sec[0] > 5 EVENT_END_COND sim/flightmodel2/engines/prop_rotation_speed_rad_sec[0] < 5 END_SOUND_ATTACHMENT BEGIN_SOUND_ATTACHMENT EVENT_NAME /rotorblades-woosh-int #VEH_XYZ 0 0 0 PARAM_DREF_IDX 0 #EVENT_ALLOWED_FOR_AI EVENT_START_COND sim/flightmodel2/engines/prop_rotation_speed_rad_sec[0] > 5 EVENT_END_COND sim/flightmodel2/engines/prop_rotation_speed_rad_sec[0] < 5 END_SOUND_ATTACHMENT ____ Yes, SteamVR definately "helps it on its way" - the != vs < was a total red herring. Here's a video of what happens when the sound system crashes (e.g. low rotor sound never stops - but its just general fmod crazy with sounds starting and never stopping): youtu.be/YHuo9npYpssDeleting the above two events seems to stop it happening. The errors coming up in the log are: 0:00:35.962 E/FMOD: /jenkins/design-triggered/source_code/app/X-Plane-f/../../engine/sound/soun_fmod.cpp(144): FMOD error 31 - An invalid parameter was passed to this function. 0:00:36.007 I/TEX: Target scale moved to 8.000000 0:00:36.007 E/FMOD: /jenkins/design-triggered/source_code/app/X-Plane-f/../../engine/sound/soun_fmod.cpp(144): FMOD error 28 - An error occurred that wasn't supposed to. Contact support. 0:00:36.036 E/FMOD: /jenkins/design-triggered/source_code/app/X-Plane-f/../../engine/sound/soun_fmod.cpp(144): FMOD error 28 - An error occurred that wasn't supposed to. Contact support. Hi there! For sure, you are experiencing a local issue, as this is not a confirmed issue. I highly recommend you to re-download the most updated version of the project from your store account. It seemed to resolve other user long-going same issue. Let me know your status.
|
|
|
sounds
May 23, 2021 18:28:46 GMT
Post by msparks on May 23, 2021 18:28:46 GMT
After a lot of faf and A+B testing, I _think_ I've tracked it down to one or both of these two: BEGIN_SOUND_ATTACHMENT EVENT_NAME /rotorblades-ext #VEH_XYZ 0 0 0 PARAM_DREF_IDX 0 #EVENT_ALLOWED_FOR_AI EVENT_START_COND sim/flightmodel2/engines/prop_rotation_speed_rad_sec[0] > 5 EVENT_END_COND sim/flightmodel2/engines/prop_rotation_speed_rad_sec[0] < 5 END_SOUND_ATTACHMENT BEGIN_SOUND_ATTACHMENT EVENT_NAME /rotorblades-woosh-int #VEH_XYZ 0 0 0 PARAM_DREF_IDX 0 #EVENT_ALLOWED_FOR_AI EVENT_START_COND sim/flightmodel2/engines/prop_rotation_speed_rad_sec[0] > 5 EVENT_END_COND sim/flightmodel2/engines/prop_rotation_speed_rad_sec[0] < 5 END_SOUND_ATTACHMENT ____ Yes, SteamVR definately "helps it on its way" - the != vs < was a total red herring. Here's a video of what happens when the sound system crashes (e.g. low rotor sound never stops - but its just general fmod crazy with sounds starting and never stopping): youtu.be/YHuo9npYpssDeleting the above two events seems to stop it happening. The errors coming up in the log are: 0:00:35.962 E/FMOD: /jenkins/design-triggered/source_code/app/X-Plane-f/../../engine/sound/soun_fmod.cpp(144): FMOD error 31 - An invalid parameter was passed to this function. 0:00:36.007 I/TEX: Target scale moved to 8.000000 0:00:36.007 E/FMOD: /jenkins/design-triggered/source_code/app/X-Plane-f/../../engine/sound/soun_fmod.cpp(144): FMOD error 28 - An error occurred that wasn't supposed to. Contact support. 0:00:36.036 E/FMOD: /jenkins/design-triggered/source_code/app/X-Plane-f/../../engine/sound/soun_fmod.cpp(144): FMOD error 28 - An error occurred that wasn't supposed to. Contact support. Hi there! For sure, you are experiencing a local issue, as this is not a confirmed issue. I highly recommend you to re-download the most updated version of the project from your store account. It seemed to resolve other user long-going same issue. Let me know your status. Hi, I redownloaded, tested both not updated and updated versions from the one that comes from the store. Before I started cutting out fmod events (this is the only aircraft I'm seeing this on). I can recreate this now every time by Starting steam VR Starting the R44 enabling VR triggering the Low RPM horn (doesn't do it) exiting VR restarting X-Plane starting the R44, triggering the low RPM horn (the video above - does it, at which point it will do it every time xplane is started) With those two events cut out I cannot recreate it at all. I've seen this from day one (Linux, VR) other sounds that manifest include the skids scraping on the ground, high RPM horn, and engine sound when the engine is off, this is why I first thought it was the != not cancelling them, but its not that, something with one or both of those two is doing that " An invalid parameter was passed to this function." at which point any started sounds will not stop (and then trying to reload the aircraft once that error is in the log causes that "error in master sound banks" CTD) I wonder if its the commented VEH_XYZ, and I have no idea what PARAM_DREF_IDX does.
|
|
|
sounds
May 23, 2021 19:38:22 GMT
Post by msparks on May 23, 2021 19:38:22 GMT
Here's a full recreate with the auto updater running freshly downloaded from the .org. Its either of the those events, both need removing to stop it doing this, swapping the guid for another sound is also enough to prevent it, uncommenting VEH_XYZ and/or commenting PARAM_DREF_IDX in both is not enough. youtu.be/I2qHM6iV8L8
|
|
|
sounds
May 23, 2021 19:56:51 GMT
via mobile
Post by VSL-Admin on May 23, 2021 19:56:51 GMT
Here's a full recreate with the auto updater running freshly downloaded from the .org. Its either of the those events, both need removing to stop it doing this, swapping the guid for another sound is also enough to prevent it, uncommenting VEH_XYZ and/or commenting PARAM_DREF_IDX in both is not enough. youtu.be/I2qHM6iV8L8Hi. As said, you are experiencing a local issue or conflict with a plugin or other reason. Please send in the log.txt file, to be found in the main X-Plane directory. You can upload it here or send via email. It may provide some clues to your issues, and will assist me in finding a solution to your situation. Thanks!
|
|
|
sounds
May 23, 2021 21:54:15 GMT
Post by msparks on May 23, 2021 21:54:15 GMT
Here's a full recreate with the auto updater running freshly downloaded from the .org. Its either of the those events, both need removing to stop it doing this, swapping the guid for another sound is also enough to prevent it, uncommenting VEH_XYZ and/or commenting PARAM_DREF_IDX in both is not enough. youtu.be/I2qHM6iV8L8Hi. As said, you are experiencing a local issue or conflict with a plugin or other reason. Please send in the log.txt file, to be found in the main X-Plane directory. You can upload it here or send via email. It may provide some clues to your issues, and will assist me in finding a solution to your situation. Thanks! Does it with no plugins Attachments:Log.txt (161.95 KB)
|
|
|
sounds
May 23, 2021 22:05:08 GMT
Post by VSL-Admin on May 23, 2021 22:05:08 GMT
OK! It seems that you have some kind of an FMOD error...
Please try this procedure, exactly as specified:
1) Launch X-Plane. Make sure that you are NOT in VR mode. 2) Load the default C-172 aircraft. 3) Reload the default C-172 aircraft. 4) quit X-Plane. 5) Install a fresh copy of the R44, after deleting the old one. 6) Launch X-Plane and make sure that you are NOT in VR mode. 7) Load the R44.
Let me know your status. This process will help me to rule out some probable causes. We will resolve it sooner or later...
|
|
|
sounds
May 23, 2021 22:39:25 GMT
Post by msparks on May 23, 2021 22:39:25 GMT
OK! It seems that you have some kind of an FMOD error... Please try this procedure, exactly as specified: 1) Launch X-Plane. Make sure that you are NOT in VR mode. 2) Load the default C-172 aircraft. 3) Reload the default C-172 aircraft. 4) quit X-Plane. 5) Install a fresh copy of the R44, after deleting the old one. 6) Launch X-Plane and make sure that you are NOT in VR mode. 7) Load the R44. Let me know your status. This process will help me to rule out some probable causes. We will resolve it sooner or later... please re read the thread, and watch the recreate video. This is NOT happening 100% of the time under normal circumstances, the recreate i posted more or less has to be exactly that for it to occur with consistency, as an example, it didn't do it starting on the runway after removing my plugins, had to start from grass - not sure if thats related. Otherwise its fairly random, I've logged may 80 hours in her since december, in VR, The only time I really noticed it was when the engine noise kept running after I turned the engine off, and one or two flights ruined by the low rpm horn practicing auto rotates. This morning i found that way of reliably recreating it and removed fmod events in blocks, eventually getting to the two i posted that when removed it stops happening, when added back it happens. This of course doesn't mean its not something else, and not having those just makes it even less likely. So i can tell you exactly what will happen at 7, 9 times out of 10 it will be fine (as it was the first start in the last video), I do that often with the 744 - i am "that" mSparks. I added to your list 8) start VR 9) exit VR 10) exit xplane 11) start xplane 12) the log/video you just got If i repeat those steps with those two events I mentioned deleted/commented, it stops doing it, if either are not commented it does it (at 12) I'd say you're triggering an xplane bug, with something either defined against those events, or corrupt in the master.bank. might be worth calling in Daniela, she helped with something fairly similar in the 744 fmod.
|
|