Greyman

From the main page, select the settings (cog) and the Misc tab. Clear the Game Avionics checkbox and you should be good. I've just tried checking it and loading the aircraft and although the adjust settings dialogue appears to suggest that it is the F16_sim profile that is active, it is apparently using another one, presumably the easy profile. Clearing the checkbox made it all good again, so you should be OK

It is seriously built to last and is very stable, even if, like me, you get a bit excitable when you are flying. :) Also, I've attached a powered usb 4-port hub to mine, so that i only need to use one port on my PC. That makes it easier to switch in/out with a steering wheel setup. It also leaves a spare port, in case i ever also need to mount a keyboard.

I have a glass desk also and have a Wheelstand Pro stand that does the job perfectly, for my TM WH HOTAS and Crosswind pedals. It has also allowed me to very easily move my joystick over to the right for the F16. You can also get a smaller adaptor for the joystick. https://www.wheelstandpro.com/products/wheel-stand-pro/for-thrustmaster-hotas-warthog-saitek-x-55-x52-pro-x65

Maybe check that you haven't got any messages in the logs for your firewall/virus scanning software, to ensure that they aren't being "overly enthusiastic" about blocking stuff. Possibly not, but one worth taking of the list.

This issue, in VR at least, is caused by the simple fact that the HUD information does not scale up or down as you get closer or further away from it. It stays the same size and as the rest of the cockpit is scaled correctly, when you move closer to the HUD, the HUD information effectively has more space to be projected on and, conversely, when you move further back, there is less space and the HUD information effectively gets "cropped" at the bottom and top. I wonder if this is a result of the fact that the HUD information, particularly targeting brackets, has to perfectly align with objects in the real world, so it has been drawn on a distant plane, in the background, rather than in the foreground, like the rest of the cockpit graphics. Either way, the fact that it has been an issue for so long and that it has yet to be fixed, wouldn't fill me with that much optimism of it being fixed as part of the upcoming cockpit improvements. We can live in hope i suppose. Edit: Just been flying the F16 and the HUD information behaves in exactly the same way, but it has far more space and enough to not be cropped, even with the pilot back in their seat. Maybe the data projected on the A10c HUD is just being drawn too big?

They have different file names and their contents relate to different devices, so you should be good.

Is the TPOD fitted to your test aircraft and the right brake is holding better due to there being more weight on that side?

Are the pylons still there when you OK the changes or is it just the rearming dialogue that isn't displaying the change correctly? If this is a reproducible issue and a track can't possibly help, it would be a shame if the bug were to remain as result of an apparently odd insistence that a track be supplied. I'm guessing that ED will get to it eventually, but as you say, they might not see this as a show-stopper.

That sounds like a VoiceAttack error, so maybe go to the editor tab on the VP config window, press the FINISH button to copy the database to the clipboard and paste this into the VA profile. You need to make sure that the current content of the profile field are gone first though, with CTRL-a and delete.

I'll give the mission another try, with VA off and using just keyboard commands for the comms, and see if the track for that one is a more faithful reproduction.

It is an awesome tool, especially when you are using VR. I'd use the sticky VAICOM Pro thread, above this, in the future. The author pays regular visits and, in the meantime, I'm sure one of the long-time users will be able to help you out.

https://www.digitalcombatsimulator.com/en/files/3303798/?sphrase_id=19821145 might help Edit: miss out the "big" and you should be good and for JTAC, the first phrase is "checking in, playtime xx mins" where xx is 15, 30 and i think 45. I'm lazy so i don't tend to say the names before the purpose of the call. The cheat sheets should really help, especially as you can use them on your kneeboard. https://www.digitalcombatsimulator.com/en/files/3302815/?sphrase_id=19821145 for a slightly different format

I've just completed an albeit not perfect, AAR mission and landed safely at OMAM, but having saved the track and replayed it, the boom on the KC135 doesn't get deployed and my F16 then proceeds to crash into the tanker. I did save the track and can send it if needed, zipped as it's too big to be attached as is, but i can't see how it will help much when there is no other way of seeing the original flight. You will have to trust me that the actual mission ended in a safe landing and not as the track might have you believe. Edit: it looks like the boom might not have dropped because i was using VoiceAttack to set the radio frequency and handle the comms. Even though i wouldn't have expected that to cause the two aircraft to crash into each other, when they didn't in the actual flight, as my track is somewhat tainted by the earlier inconsistency it is probably going to be of even less use than i had initially stated.

make sure that VoiceAttack is running and that the VAICOM PRO profile is the active profile. Edit: you could also check that keyboard shortcuts haven't been disabled.

As a start, delete the export.lua file from your users/<your name>/Saved Games/<DCS folder name>/scripts folder and restart VA and DCS World. Also make sure that you are running VoiceAttack as Admin. Good luck

and does movement of the pedals register when you open the usb game controller dialogue in windows and show the properties for your rudder pedals? Also, tm controllers tend to require calibration with tm software, so if you have calibrated the rudder pedals with windows, then reset to default, perhaps ironically using the usb game controller, and then recalibrate using the TM software.

as there is another thread that suggests the aircraft pulls to the left, is there a chance that this might be something to do with the bit of the startup procedure that involves resetting the trim back to the centre, after one of the checks? if the trim isn't set perfectly to the neutral position, might this be causing the drift?

https://forums.eagle.ru/showthread.php?t=182299 is a good place to bookmark and there are a couple that you could try on the last page

It looks like it might be a display issue on the PTT tab, as for me, the TX1 button has unboldened text, VHF Radio AN/ARC-222, and it does appear to work when you press it. edit: i have just tried it again and both TX1 and TX2 allowed me to speak with ATC, on their respective VHF and UHF frequencies, so it is working.

no worries and i'd just change it to the other setting, as it sounds like it might have the eyes mixed up.

go to settings, then go to the special tab. select the F16 and you will see a couple of checkboxes, IIRC, one for AB detent and one for which eye the HMCS is displayed in.

Perhaps you should read the post again? He/she appears to be saying that images captured in VR may not appear the same as you might actually experience in VR. In which case, the two of you are saying exactly the same thing. edit: i guess you can speak for yourself. :)

...and be careful not to forget, as the default bindings for the WH has the flaps switch set to the master power switch.

it also, quite sensibly, appears to switch off when you are looking directly at the HUD. Having both on and overlapping would make the information on both difficult to read.

As per the title, is it possible to show the range and heading, that is included on the HSI, on the HUD. When TACAN is enabled on the HSI, the HUD continues to show directions to the selected steerpoint. If i've missed something, in the manual or a video, please point me in the right direction.