Gasman3874

I have a warthog Hotass and always have usher it to full throttle for takeoff. Is there something else you have to do in 2.9 to get into burner in the catapult?

Since the 2.9 upgrade, the shooter is not responding to my salute or launch requests. I have rebound the command several times but it has not fixed this. Is anyone else having this issue?

Need some help from fellow HP Reverb G2 Owners. I just installed my new HP REVERB G2 yesterday. I am upgrading from an Oculus Rift CV1. I had numerous issues finding the right USB and Display port combos to make this work (over 4 hours of experimenting). I finally got WMR to work and after deleting the old Oculus software, was able to get VR to come up in DCS. However, Of all my planes (F18, F15, F16, F14, Huey, Spitfire, P51, P47), the only plane that will fully render is the F15 which is an old model. All the others will only partially render in game. Frame of fuselage but no cockpit instrumentation or canopy. Does anyone have any recomendations on how to fix this. I have rebooted numerous times with the same issue persisting. BTW, I have used the latest recommendations on VR settings to configure, WMR, SteamWMR, DCS, and my Nividia Control panel. Any help is greatly appreciated.

Just a quick update if anyone with a V3 NLR Motion platform ran into the same issue I did. I contacted NLR (Next Level Racing) support and they worked with me to analyze the files. The were very helpful and found the issue in their software, updated it to correct the situation, and got me back up and running. I have been very impressed with NLR Support. They are very responsive and effective in supporting the V3. DCS is awesome with Motion. Highly recommend the V3 for who ever might be considering the plunge.

I have a v3 and once I loaded the new 2.75 software update last week, the motion stopped working for DCS. IT still works in XPlane 11, so I know it's not my motion platform. Has anyone else run into this issue. Does anyone have any recommendations on how to fix this?

Thanks, I will try that

I had issues with being able to select the next nav/steer point during the second Red Flag 16-2 mission. I even attempted to rebind my Hotas buttons and tried the key board commands and none of this worked. Basically was stuck on Steerpoint 0. Did anyone else experience this issue on the second Red Flag mission? If not, can anyone guess what I may have been missing?

I agree....Your mission overview was very helpful in showing how to prep and execute the mission. I have now accessed the Briefing Docs and will start my campaign shortly. Out of curiosity, do you find TACVIEW easy to use? Which version do you use? This looks like it could give great feedback for all kinds of Training.

I have been using the ProUSBPanel (Flight Panel) for several months with absolutely no issues. I have successfully created profiles for DCS F-15, P51 and A10C again that work perfectly. Unfortuneately, when I went to load it to show some friends on Thursday evening, I got several configuration error messages in a row (1093 configuration system failed to initialize, 1017 configuration system failed to initialize, 2043 configuration system failed to initialize) and then it would not load the switchpanel or multi-panel templatetab. All I could see was the top level menu. I am running Win 8.1 and have run PROUSB Flight Panel on DCS 1.2, DCS 1.5, and DCS 2.0 in the past with no issues as stated above. I have attempted to delete the PROUSB.EXE file and reload a fresh copy but with no improvement to the situation identified above. I am attaching the Error Log and my F1-5 Profile below. Any support on how to resolve this is much appreciated as I have come to completely rely on this fantastic software to run my DCS aircraft. Thanks in advance for your assistance EDIT: I was able to resolve the problem by completely deleting the original folder and all files in it and reloading the flight panel files to a new directory. Not sure what corrupted the original program file....but this fixed it. Flightpanels_error_log.txt F15_Saitek_DCS_Profile.txt

Thanks Hollywood. I got AutoHotkey working and was able to fly. Will verify .cmd file extension is on fetch data......This is a fantastic profile!!!!

Hollywood, I am having the same file not recognized issues as quoted above. I also cant get AutoHotkey to work. I have a warthog and have eliminated Num0-Num6 keybindings from the control settings. The VA profile works by manually pressing Num0 on keypad, but will not recognize throttle mic switch activation with AutoHotkey running. Really looking forward to your profile, but so far is no joy. Any help on resolving "Unable to get value from URI - Could not find file 'C:\Program Files (x86)\VoiceAttack\Apps\VAICOM\Tools\TEMP\mission.lua'." and getting AutoHotkey functioning is appreciated.