Shiny

Well looks like Oculus pushed v63 to the public so I believe I'm running into this issue on DCS 2.9.3.51704. On Nvidia driver 545.92. Attempted driver 546.33 from the above poster, but did not have any effect. Flat screen version of DCS loads, but not VR version.

Ok so it looks like I fixed my own problem. After 3 days and a suggestion on Facebook, I upgraded my BIOS and capped the GPU to PCIE 3.0 speeds instead of auto or gen 4 and now all the problems have gone away. I can now load high detail textures, high vis range and medium shadows on MP servers without issues. Who would have thunk?

Hello fellow pilots I recently upgraded from a 1070Ti to 3080 and now I've noticed that the Rift S "crashes" when I load into multiplayer servers like Hoggit or ThroughTheInferno. Symptoms: - Headset loses audio, either immediately upon loading into the server or after a while - Headset disconnects from Oculus. Light inside the headset turns orange and Oculus reports headset is no longer connected to the display port. The effect seems to be worse if textures are set higher than low, or if the Visib range is higher than low. There are no issues with single player missions, even with high textures or high visib range. Rest of the computer was unchanged from the upgrade. Running Ryzen 3600, 32GB RAM. Thanks! Shiny

I'm on a Rift S, same processor and RAM but on a 1070Ti. Yes, you're going to have to dial back the settings compared to a flat screen. For me, I much prefer the 1:1 movement of a VR headset. The other thing I do is run Oculus Tray Tool to raise my PD to 1.3 to 1.4. Try this guide and get some improvement in frames. I do not use the shader mod however: https://www.youtube.com/watch?v=ZyrAIhXFpv0

Ok, I reloaded DCS again, and this time when I logged in, the crosshairs showed up right away: - Air start viper - Click on Air to Ground mode - Left MFD to WPN (the mavericks are in VIS by default) - The crosshairs appeared without me touching anything I have no idea what changed, but it's working now. So I'm scratching my head. Thanks everyone though.

Hi Bignewy, Thanks for jumping in. So here's what I did: (OBS capture via Oculus mirror: https://drive.google.com/file/d/19te...ew?usp=sharing) - Air start with 6x AGM65-D, 3 on each wing - Set the Mavericks for VIS mode - In the WPN tab, I press TMS down short, and the 'Not SOI' appears and the FoV of the Maverick moves up. I do this a couple of times in the 35 second mark of the video and at around 52 seconds. Still I'm unable to see the proper symbology. - Then at around 55 seconds, I pretend that there is maverick symbology and put the center of the view over a transmission line and press TMS up short. This actually forces the maverick to lock and I am able to release it. - Rinse and repeat at 1:10 in the video - Both mavericks strike true Thanks, Shiny

I've tried both air and ground start. And with and without TPOD loaded. The result is the same.

Hello fellow pilots, Can anyone tell me what I'm doing wrong? I power up my mavericks but I don't get any crosshairs at all or FoV brackets. It's the same for AGM-65D or the H version.

Another alternative, is to use the left analog hat, as an analog trim. VKB allows you to add or subtract two analog axis together. So that's another way to add a trim. So this is a several step process. 1. Make the left analog hat a relative axis instead of an absolute axis. That means when you move the hat and release, the axis doesn't return to center. The left hat is axis 5 and 6. 2. Now, we're going to combine axis 5 and 6 values with axis 1 and 2 (your pitch and roll axis respectively). Here, I'm combining it with 50% of the effect of the analog hat. You can choose whatever value you want. Note: if the trim axis is being reversed, changed the Sign option from a '-' to a '+'. The first screenshot shows the results of steps 1 and 2 3. Finally, we're going to use the push button on the left analog hat to completely reset your trim to zero. The push button on the left analog hat is button 22, so click on it and change its function to reset the axis. See the third screenshot. Note, doing so means you lose button 22 for use with your games as an input. Note: all of these is in the VKB manual, section 3.5. https://vkbcontrollers.com/wp-content/uploads/2019/04/controller_2_11_En.pdf

I don't have a solution in vJoy for you, but I know you can use the buttons on the joystick to basically create a trim. Which you can then combine with your pitch and roll axis, so essentially, the trimming is done in the joystick firmware itself. Here are some instructions: http://forum.vkb-sim.pro/viewtopic.php?t=3693

Yes, you can add a vJoy device and then play with a response curve. But you can do it via DCS or like Soko1 said, do it via direct FW change in the VKB stick itself.

Out of curiosity, why do you start with the balanced power option? I've had this problem forever, but it doesn't matter which device I have plugged in. Any one of these will prevent my screen from sleeping: - VKB gunfighter - Virpil CM2 throttle - T16000m throttle & pedals

You fly the AoA indexer and the ball (IFLOLS) until the back wheel touches the deck. Once the wheel contacts the deck, go burner and you either already caught the wire or you haven't. That or you completely overshoot or you get the wave-off lights, then immediately go burner.

I found that using Joystick Gremlin in conjunction gave me the most flexibility. Plus, being able to map to keyboard presses means I don't have to map every single DCS module since they share many common keyboard combinations. And for other games which exceed 32 buttons, then Joystick Gremlin is required:

Yeah, I had a nasty case of PIO when I first got the Viper because of the lack of reference with my own cockpit. So now I just stare at the tanker lights, use those as the large-ish adjustments. But I also use my peripheral vision to get a sense of the change in size or position of the engines on the tanker, to gauge whether or not I'm shifting position.

That's a cool mod. But after a couple of weeks of using it, I found that I don't actually want a physical momentary switch. So for example, I use my T4 as my refueling probe extend / retract. So the physical position of the switch tells me whether or not my fuel probe (or door) is extended (opened) and I don't have to glance at my cockpit but I can feel the position of the switch. In DCS, I don't want the joystick to keep pressing down the button. I know it'll work just fine on its own if you map the joystick button to fuel probe extend. But for other games, like Elite or Star Citizen, it won't recognize that many buttons and so I needed the joystick to press and release, so then it'll play well with joystick gremlin.

I think I know what the problem is with the Hornet elevation axis and it was explained in the hornet forums. The elevation axis there assumes you have to return the analog stick back to center position or else the elevation will keep changing. I have a spare analog stick on my VKB gunfighter for that. I'll think about it some more and see what I want to use it for. Generally I want to make my controls similar across the Hornet, Viper, Hog and Harrier since those are the 4 I fly interchangeably. So they all have to react a similar way or else I'm going to be super confused :)

I'm talking about the ring finger slider, not the flap one. The flap one I use as my nozzle position in the harrier.

I'm in VR and I'm struggling to find a use for this slider axis on the throttle. I've tried using it for antenna elevation but it's too fine of a control and there's too much lag for accurate control. What do you use it for?

I use mine as follows: - Left side encoder - TGP zoom in/out, push in for FoV/RAID. Also doubles for antenna elevation in something like the hornet. In the Harrier, I use it for the nozzle STO stop lever. In the Spitfire, it's my RPM lever. - Right side encoder - Could also be used for antenna elevation for the hornet. In my A10C, dial up to choose jammer mode, dial down to enable/disable jammer. The reason I do this is that the 5 way hat switch right there I also use as the CMS so all my countermeasures are right under my thumb on my A10C. - E1 encoder, push to activate NVG, rotate knob left and right for brightness - E2 encoder, I have mapped to Joystick Gremlin. When I'm in mode 2 or mode 3, (these are my approach/takeoff and ground startup mode) the push is for bringing up kneeboard and the dial flips pages for the kneeboard. - E2 encoder in mode 1, which is my combat mode, I use it for HMD brightness for the Viper and the Hornet.

Just got my throttle and thought I'd share how I managed to reprogram switches T1 through T4 as momentary switches. In restrospect, it shouldn't have taken hours but I finally figured it out. Big shout out to HavocCompanyClan's YouTube channel. https://www.youtube.com/user/HavocCompanyClan What I wanted to do: Change switches T1 through T4 to be two position momentary switches like the T5 through T7 switches. By default T1 through T4 represents a single continuous button press if the switch is flipped up and that button is released when the switch is flipped down. Problem: Many games, like DCS, only require a single button press to flip a switch. So like turning on an APU, or something like master arm. Sometimes the module treats it as a toggle, so sending a continuous button press wouldn't work so well cause that will just keep flipping things back and forth. In addition, I wanted to use Joystick Gremlin to translate the button presses to keyboard presses. However, it turns out that Windows really doesn't like it if you hold down modifier buttons like Ctrl, Alt, Shift, and Windows Key, permanently. Cause well, they're modifiers and that can mess with your other button presses. Solution: Step 1: Change T1 and T4 to toggle a button. So when you flip a switch upwards, it actually presses a joystick button, and the releases it. By default, when T1 is flipped up, it presses down physical button 42 or logical button 34. So in your VPC software, double click on this button and instead change it to 'Toggle On' and check the box to add a delay: If you use the VPC joystick tester, you'll see that when you flip the T1 switch up, it will activate button 34 on and then button 34 turns off after ~100ms. Step 2: Make the switch flip down also toggle another button When T1 is flipped down, it triggers physical button 41. However, out of the box, the throttle doesn't trigger a logical button. So you need to add one to your list. The first free logical button out of the box is logical button 61. So set it up just like the screenshot above, but instead, logical button is 61 and physical button is 41. Now when you test it in the VPC joystick tester, you'll see also that when you flip T1 downwards, that button 61 will turn on and then turn off after ~100ms as well. Step 3: Rinse and repeat for the other T2 through T4 buttons if desired. Congrats, you can now map these buttons directly into DCS! Step 4: Setup Joystick Grelim (optional) Now, this step is completely optional, but if you want to remap the toggle to keyboard bindings, then you need this. The other thing I found is that Windows does not like 100ms of toggle at all if you use Ctrl, Alt, Windows Key, or Shift modifiers as a part of the keyboard remapping. That is just too short and I found that Windows thought those modifiers where stuck on, causing me endless frustration. The solution was to actually create a macro with delay between pressing the modifier, a series of keys and then releasing the modifier. Havoc has a great video here: But in short, you need to record a macro, with timings. So for example, I wanted button 34 to be represent Left Shift-A. Then it looks like below: Happy flying!

For basic flying skills, every lesson that is available in FSX is still applicable to DCS. Skills such as level & coordinated turns, slow flight, touch & go, climbs, descents, approaches, proper aircraft trimming, etc are all the same except everything happens at a higher speed so that means less room for error and everything happens faster. So take those FSX lessons and transpose them to your favorite jet in DCS. My next suggestion is start using the mission editor to create different scenarios such as adding weather and changing time of day. IFR lying is a lot of fun too. Inter-space this with some weapons training to keep things interesting. Besides, watching things go boom is one big reason for this game!

Howdy, I'm an aviation enthusiast but unfortunately having kids does restrict the available time slots for flying until late into the evenings on Pacific time. So I'm looking for a like minded squadron to fly with. At the moment, I'm flying both the F18 and AV-8B. Thanks in advance. Cheers, -Shiny

To reply to the OP, if you want to convert, there are two methods: 1. If you got the coordinates from the map view, simply press ALT-Y to change the mode until you get to the desired format. 2. Do a bit of math. Every minute is 60 seconds. So when you have 31.03 seconds, you take 31.03 divide by 60 and you get the minutes, which is 0.5172. So for your first example, in your UFC, you would first enter N 45 05, press enter. Then it would ask you for TTHOU, and you would enter 5172, then press enter.

I did some testing here between mk82 and mk83 and found the mk82 and its LG variant to be very inaccurate in auto release: https://forums.eagle.ru/showthread.php?t=246829