Is there a simvar for headphone simulation? It would be cool if we could have
a settable simvar for this.
Yea, this would be cool. Regards, Raul
I upvote this.
This is a great idea!
Hello @SWS-AlexVletsas
@Simbol @Flysimware
@tiberiu11 Unfortunately, Headphone simulation
being a parameter in the option menu, we will not allow third party to
manipulate it programmaticaly. Best regards, Yohan
@Yoanito You can have a cfg setting to override
and disable the one from the menu options. This is like how we disable the
auto rudder. Then have a secondary headphone system or another variable tied
to the same system that is not tied to the menu options and now devs can
control this new system from the aircraft. This way users can have a more
realistic experience as they can plug in their headset into a jack and the
sound changes. So we could have both if well thought out as I just explained.
Hello @Flysimware I’m not quite sure to
understand what you mean by “cfg setting” ? Can you explain what this cfg is
supposed to be and how it can modify the auto rudder ? Best regards Yohan
@Yoanito if 3rd party devs are not allowed to manipulate the setting there are
other options to make it workable. 1. At least provide a read-only SimVar to
3rd party devs that shows if the headphone simulation in the options menu is
enabled/disabled. 2. Introduce a method by which 3rd party devs can override
the headphone simulation mode in the options menu. Ideally this would be a
SimVar but alternatively something like @Flysimware suggested an override
switch in one of the *.cfg files (e.g. aircraft.cfg).
Hello @Flysimware@SimAcoustics Thanks for your replies, I forwarded them to
the dev team and it will be discussed. Best regards, Yohan
The flight_model.cfg allows us to override some menu settings such as: 1)
Centre of gravity slider 2) Force flight model to use legacy 3) Force flight
model to modern I don’t know if the architecture allows that to happen with
headphone simulation, but if it can be added as a property to systems.cfg it
would be great. override_headphone_sim=0 or 1 Then having a RW simvar like
(A:HEADPHONE SIMULATION, Bool) would allow us to do certain things that take a
lot of work and are error-prone currently.
@Yoanito The point of having an override cfg setting (from the aircrafts
systems.cfg) for the headphone menu option is so it can get around the
limitation you @Yoanito mentioned earlier. So this way you can offer us a
variable as @SWS-AlexVletsas described. So when we force the menu to be off
or null from the cfg setting we can now have FULL control of the
headphones system using (A:HEADPHONE SIMULATION, Bool) that is readable and
writable.