Greyman

Maybe it is for no other reason than ED promising said discount when the Hornet first came out???? Of course, percentages don't mean much until we know the absolute price of the Supercarrier module, so it might not make much difference either way.

They could just make the non-Hornet owners' pre-release discount 30% and the Hornet owners' pre-release discount x% higher. That way, they don't force Hornet owners to wait and remain good to their promised discount. After release, they could just up the price to either full or retain an x% discount for a little longer, so as not to upset the peeps that don't want to buy the pre-release. I know that is effectively "stacking", but the alternative is likely to test ED's "anti-pitch fork defences" :)

...but it still makes it look like the promised discount for Hornet owners will, in real terms, not be delivered, as non-Hornet owners will be able to buy the module for exactly the same price. Why would a Hornet owner wait until after early-access to buy it, just to get the same discount?

the double binds you need to remove will be in the axis commands, where it sounds like one of your throttle axis commands has the pedals assigned as well as your throttle lever and possibly one of your joystick axes as well. each of your command axes should normally only have one controller axis assigned to it, so clear any that you don't need.

maybe check that you have the desired default output device set in the windows tray. there are some VoiceAttack audio options that you might want to play with, but i think that it just uses the windows device by default.

maybe check for noise on your roll axis and insert/increase deadzone to cancel out any unwanted input that might be there. the properties of your joystick in the windows usb game controller dialogue should show up any such unwanted movements. oh and you might also want to check that you don't have any of those duplicate axis mappings, your rudder pedals or a twist axis for example, that might cause the aircraft to think that you want it to roll. Merry Christmas

Ah, it works for me now also. Must've been finger trouble and a bit of age-induced memory issues and the lack of a 'special for joystick' category, as for my other aircraft. I'm guessing the 3-way mappings are probably hard-wired in for the A10C.

+1 I just lowered my seat a couple of notches and the HUD is just about fully visible. I do hope that the improvements haven't come at the expense of the monitor pilots, but this really is a massive improvement to a VR pilot's experience.

Were the special bindings, for things like the flaps switch, ones that we had to add or were they included as standard in the original A10C? They don't appear to be there anymore and I just thought it worth asking, just in case ED have accidentally missed adding them, before I add them back myself. It would certainly be better to have them as standard, especially with the TM WH being designed specifically as a replica of the A10's HOTAS.

I always delete export.lua after every DCS update, as that is likely to solve at least some, if not most, of these types of issues. The file will be in your /Users/<username>/<DCS folder>/Scripts folder

I always use "Arco Select", "Shell Select", as appropriate, and then don't bother with the name before any subsequent commands to that tanker. I've done it on a mission with 3 tankers and topped up at all of them and this method worked for me.

Maybe take a look at the "2 mins install fix" video, linked on the OP of this thread. Without more detail on what you are seeing, it's tough to know for sure, but I'm guessing that your solution will probably be included.

The Tornado, to give the Viggen some competition at very low level.

LOL, intermittent issues are by far the most annoying, but there is usually an explanation for it. :) Windows sound devices appear to allow programs to take exclusive control of them, so you might want to try changing those, in the advanced tab, for the device you want to use. Another app might have taken possession of your headset, last night without you knowing it and then let it go again, when you tried it subsequently. worth a try

Maybe get them to watch a few Grim Reapers' videos. Those guys seem to have lots of fun. :)

That's what I'll be doing and I will post here when I have. I think it will probably be clearer, but whether it convinces me to buy one, or a rift s instead, remains to be seen.

It'll be interesting to see how it performs

https://www.amazon.co.uk/dp/B01E9W8KYC/ref=cm_sw_r_cp_tai_4fZ0DbY3YS1QQ Was linked on the official Oculus blog. The 6ft one.

My son has a Quest and has just ordered the Oculus recommended cable, from Amazon, so hopefully tomorrow i will be able to compare the performance of that with my now ageing Rift CV1.

@TWC_Alamo - sorry but i'm just running the bog-standard DCS and VoiceAttack on the same PC, as i have no need to make it that complicated. :) I'm sure that Hollywood will be able to help you out though. @williehayesjr - your speakers are probably set as your windows default output/communications device, so try changing to your headset as the default when you are using VAICOM. There is possibly a more elegant way to enforce the use of your headset, but as this works, i've not bothered to look for it.

I thought it worth mentioning, as just opening those ports on the firewall of just one of your PCs might still leave network comms, in one direction or the other, blocked, when traffic in the other direction might get through. I'm sure that Hollywood will be able to solve it for you.

have you opened up the firewall on both PCs to the specified ports?

On the main menu page, check out the module manager button, for signs that a new module is ready for download/install. Of course, you also need to have purchased the F16.

Good to hear

make sure that you are using the same profile in the module that you have edited. the F18 has two profiles, one for sim mode and one for game mode, the latter of which is selected by having game mode (in gameplay settings) and/or game avionics (in misc settings) my guess is that you have one of those set. edit: the other thing you might check is that there aren't multiple mappings for each of your axes. by default, DCS will normally set an axis from each of your controllers (throttles, stick, rudder pedals) against each of a new aircraft's control axes. in other words, your rudder pedals might affect the throttle or an axis on your stick might affect the yaw. to solve this one, if you haven't already, just remove all of the unwanted axis mappings.