Love the sound, but need headphones shortcut!
-
Unfortunately the MSFS in-build toggle-command for "headphone-simulation" on/off does not work since they implemented this feature. Even with SU15 the disfunctional toggle-shortcut was not fixed. You have to switch it on and off via the menu in MSFS. From what I`ve seen from P42 you also have to go into a menu (flow) to switch between states. I find this complicated too.
As I m a VR-only user, my solution on this (a more extended one):
I used the external software "VoiceAttack" and configured voice commands to control volumes. For example when spelling "sim volume down" the windows volume level of MSFS and also other programs like FSRealistic (which by the way is not affected by the MSFS headphone simulation) are set to 30%. The command "sim volume up" restores the volume level to 100 of both components. Did the same for different volume levels I wish and also for my music playing ( saying ..."music volume down" etc)
VoiceAttack is independent of MSFS and you can control many things with it. -
For an example of how it's done well (imo) look at the Lear35 from FSW - there it's on the tablet which is really not ideal but makes the a/c tolerable for long distance - really mutes the high freq whine from invertors? which is a vicious burrowing earworm
My personal pref would be to a). click on the headphone jack socket and just add a visual marker that it's engaged and b). an LVAR to enable binding via h/w.
Currently on both turbine and piston, but esp. piston I have to use my windows audio panel to attenuate the sim during climb and then put it back again before landing. Really breaks the immersion for me and sound is such a HUGE factor in my enjoyment of any a/c.
-
I really like how A2A did it in their Comanche, you have headphones for a bit of muffling and then a noise cancellation button to further down the noises. It's amazing how good that works
@Cristi I agree, that is a very handy clickspot.
It would be great to have something similar in the Duke and TBM. -
I have already implemented headphone cables and clickspot in all of my standalone aircraft, and you are able to adjust the amount of active noise cancellation by scrolling your mouse wheel on the clickspot (there is also a variable for cockpit builders). I apologize that it has taken this long for an update to the Dukes, but I thought MSFS 2024 compatibility would be a relatively easy task to be done soon after it was released. Alas, the goalpost is still receding with SU2, but I promise that I will have something for you soon.
-
I have already implemented headphone cables and clickspot in all of my standalone aircraft, and you are able to adjust the amount of active noise cancellation by scrolling your mouse wheel on the clickspot (there is also a variable for cockpit builders). I apologize that it has taken this long for an update to the Dukes, but I thought MSFS 2024 compatibility would be a relatively easy task to be done soon after it was released. Alas, the goalpost is still receding with SU2, but I promise that I will have something for you soon.
@Black-Square this implementation will be available in the next update or it's currently present?
-
The next update, along with MSFS 2024 compatibility.
-
I recently turned on the headphones simulation in 2020 through the menus, but I actually didn't like it (certainly in comparison with the Comanche's custom implementation). So while I am excited for the next Duke update, I'm cautiously interested to see whether the variable noise cancellation (great idea!) works quite as well or if I'll prefer it switched off.
I think I have become accustomed to the volume of the Duke in cruise now. It's when switching to the external view for screenshots that my ear drums are assaulted!
I know it's realistic, but it would nice if the internal/external volume could be better balanced for my own sake, and that of anyone in earshot! Not sure if it could be handled via the tablet, or if it's baked into the simulation (perhaps a .cfg file edit). Maybe another idea for the list.I know the 2020 Duke update won't launch before the 2024 update is ready, as that might cause chaos and frustration, but at this point I'm cursing 2024 for dragging general progress down for 2020 products
-
@Black-Square Did you find a solution to tune it with legacy mode, or will it be lock mode exclusive?
-
Any updates on this? I'd love to be able to have the headphone simulations on the Duke and TBM.
-
It will be in the next Duke update, which should be this week. I've added all the code to the TBM for a future time when I have the resources to build a custom sound package.
-
It will be in the next Duke update, which should be this week. I've added all the code to the TBM for a future time when I have the resources to build a custom sound package.
@Black-Square Question. Will you need to update the Duke flight model for 2024? The reason I ask is because it feels a little off in 2024, and I have two add-ons from 2020 that no longer feel good in 2024 (Avro RJ and iniBuilds A300). It makes me wonder if the changes in 2024 to how the flight model responds requires updating. It's a more stable, less prone to crosswind FDE. The Duke in 2024 feels a little more twitchy now. So I was thinking it might need a little tweaking is all
-
@Black-Square Question. Will you need to update the Duke flight model for 2024? The reason I ask is because it feels a little off in 2024, and I have two add-ons from 2020 that no longer feel good in 2024 (Avro RJ and iniBuilds A300). It makes me wonder if the changes in 2024 to how the flight model responds requires updating. It's a more stable, less prone to crosswind FDE. The Duke in 2024 feels a little more twitchy now. So I was thinking it might need a little tweaking is all
@Orlaam I agree that all aircraft I have experienced feel noticeably worse in 2024. I find them much less satisfying to fly in my pursuits as a real pilot. I have been hesitant to make adjustments, because there were no advertised differences to existing flight models in 2024, and I think the difference might lie only in control input responsiveness. I have decreased the sensitivities of my controls substantially compared to 2020, and that has helped. Although I don't like making changes at the last moment, I may find the safest variable to tweak on my 2024 updates in an attempt to alleviate this.
