SGT Coyle

I would say that you have an install issue. It might be helpful to uninstall all and delete drivers. And maybe contact Thrustmaster support and describe your issue to them.

Are you running TARGET as Admin? Try running the software install and choosing repair. It helped me with a snickity issue.

Same here. VR red range numbers nearly invisible.

It's not that there's a need for TARGET. It's the persistent presence of a controller that should not be present. I fond what might be the culprit though. My TARGET GUI software got corrupted and was hinkying up my Editor process. A quick repair sorted me. In my Saved Games > Open Beta> Config> Input Folder I only saw modules that I may have edited the controls in settings. Can it be that the duplicate is hiding in the settings of a module FlyingTaco hasn't edited yet? Maybe try deleting the config folder from Saved Games. That was always the standby procedure.

Pretty much have the same issue. Thrustmaster TARGET combines stick and throttle into "Thrustmaster Virtual Game Controller (root)". For some reason windows still shows "Joystick-HOTAS Warthog" That should not be showing up. Posted in the Thrustmaster section of Input/Ouput Forum. Here

Just noticed recently that TARGET is removing the Joystick from Joy.cpl. It is allowing it to exist as a separate controller alongside the "Thrusmaster Virtual Game Controller (root)" controller. DCS is picking up the Joystick and assigning default keys and buttons to it. Went through the config folder in Saved Games and removed all files for the Joystick and left the Virtual Controller in tact, but the game still shows "Joystick-Thrustmaster HOTAS" as an option for every module. Any thoughts? Quick repair of the TARGET GUI.exe sorted out my SE. Now all works fine.

Same issue. Right throttle lever is loosening and I don't see an apparent way to tighten. Hope someone has been here before and is willing to share.

There is no fusing select for BDU-33. It's a simple impact charge on the nose. The whole point is to give the pilot a visual reference of impact. I don't disagree that the smoke time is too long, but I think your better off playing with the chimney slider in settings. I think it reduces all smoke produced in game, be it duration or intensity.

Mission still broke

Looking at at Trickers video, It doesn't seem that any attempts at evasion are necessary.

OK, thanks. Look forward to getting past Mission #1. I'm having cob webb issues.

I just started playing DCS again after a bit of a break. So having to learn the CDU again ( to be honest never was very good at it. To many numbers going by). You have a "Press Space Bar to Receive Coordinates" in mission one, but then they linger a bit on screen and disappear. Then you can F10-Other => F1-Repeat Coordinates. They don't last very long, and got to be a bit frustrating when I wasn't able to ask for second repeat. The F10 option wasn't available. My biggest issue is entering numbers in while someone (the voice over ) is talking. I would argue that since you are already utilizing the "Press space bar to continue" message to receive use it to acknowledge and move on. I've been having DCS issues and have crashed the game twice at the same spot in Mission #1. I don't think it's anything to do with the mission. I think it;s Voice Attack / VIACOM Dictation.

Can we get a "Space bar to continue" delay on messages passing coordinates please? I play VR and trying to write things down is a pain. For those that don't like it, hit space bar to continue.

In OB, UI Layer Page, Frame rate counter - Service info RCtrl + Pause must be overwriting Toggle Console in individual Module controls. Reproduce: Start any mission and use RCtrl + Pause to see frame rate. Adjust Toggle Console to anything else and open console You'll see that Toggle Console has no effect.

performance stats

Thanks for the guide speed-of-heat. Working through some of that. Good stuff. On another note. Any reason I can't get the console to show in VR? I get the controls indicator, but no console. There's no # define MASKSIZE in the replace _HMD.hlsl. I've tried the mask setting in the DCS VR Settings, but that has no effect that I can see.

I was having trouble with micro stutters and seeing clear cockpit text. I've reset my DCS settings (System and VR) and am slowly increasing them and testing on the Caucasus Free Flight Instant action mission. I don't have any other mods installed. I have to admit. I have no idea what any of these settings really do, but I followed this DCS: Nvidia Control Panel — Debunking the NVCP pretty closely, and it helped some issues I was having. My specs: AMD Ryzen 9 3950X 16-Core Processor 4.28 GHz RAM 32gig GPU Custom water cooled ASUS RTX 2080Ti Turbo DCS installed on SAMSUNG 970 EVO SSD 1TB - M.2 NVMe MB ASUS Crosshair VIII Hero Oculus Rift S

Thanks for the reply. Directing OvGME to root directory instead of Saved Games, was quite literally the last attempt before your post. Got it working, but I don't see or feel much of a difference. I'm gonna play with settings and see what happens.

C:\Users\.........\Saved Games\DCS.openbeta\bazar\DCS VR Shaders mod for 2.7.6 (Clear Water) Hotfix\bazar\shaders Can someone help me with the correct folder path in OvGME to get shaders to work?

Anyone got a video showing the VR goggle view where the clouds don't make the game completely unplayable? Haven't play since the 2,7 cloud update because they're so bad. Jumped back on today and there has been no improvement. AMD Ryzen 3950 32 gig RAM RTX 2080TI Oculus Rift s

Recently ran into this. My Toggle_Console mapping isn't working. I don't recall changing it, but when I checked it was assigned to LALT + ` , but that's not working. RCTL = PAUSE works and I understand it is hard coded in the game by default, but not in my game. Screenshot attached. Seems weird.

What is FSR?

That means you have your Throttle mapped to your rudder in game. Just clear the throttle mapping and reassign to the throttle in game.

Different controllers are going to have the same axis's. Pedals with toe brakes are going to have JOY_X, Y, and Z. Standard Joysticks are going to have JOY_X and Y, and if there's a throttle slider, it probably be a JOY_SLIDER. The important thing is to not have more than one controller axis (Pedal, Stick, or Throttle) assigned to a single game axis.

F16 module mission "On the Range", JTAC provides MGRS coordinates not LatLong.