NoPro

Was it always like this? I just started noticing it since the day before yesterday. Is there any solution for it? Anyone knows if it’s software or hardware related? Cheers

maybe there is n option to map an axes for trim?! Haven’t checked that apart from rudder trim, therefore I have mapped an axes

I do have, yes BUT if I reverse the axes then all other aircraft are messed up as well. Anyway, as mentioned before, I just swapped the controls setup mapping in the Viper and everything is fine. I just wanted to know if it’s just me or if anybody else having this issue, so that we can address it to ED. Cheers

Sorry, my mistake....I pulled the hat switch back and the viper began to dive and according to controls setup pulling the hat switch down, the Viper should raise the nose. I’ve corrected my wording in my first post.

thanks for your reply. Fans are looking good and according to msi afterburner, the highest GPU temp was 61°C

:megalol:....no and the proof is, that it is working in all other aircrafts ;)

I'm having the same setup as you but the aircraft is behaving in the opposite way cheers

hahahaha dude, of course I've done that ;-). I just wanted to point out to ED that the mapping doesn't fit to the description in the controll settings.

Small update on this one: I switched off MSAA in DCS and I was flying for nearly an hour before it crashed again.

Hello everybody, the pitch trim input in the controll settings is inverted I think. I was setting up my device as with every other aircraft. Thereafter I went for a ride with the F16 and when I pulled my trim switch to nose up the Viper began to dive an vice versa. cheers

Thanks for your quick response. I was running steam VR stable before and had that crashes as well, so I tried the beta version

Hey Everyone, I just upgraded from a Rift S to a Reverb and I love the clarity BUT I'm getting a lot of CTD's, so this is getting frustrating if you have every attempt a different amount of time of playing before it crashes, sometimes 5minutes, sometimes more and also even less. So this is my mayday call and I'm hoping for any help. I was running the Rift S on pretty much high settings, so I thought that might be the issue and I lowered the DCS settings by pressing the VR button in DCS and in Steam VR I've set the SS to 100% but still no luck, it was crashing again. The crash itself is a freezing picture, followed by a CTD and steam VR is closing. Steam VR Beta is used. My specs are: Z390 Aorus Master Zotac GTX1080Ti i5 8600k @ 4.8GHz 32GB DDR4 RAM DCS is installed on a 1000GB Samsung 970 Evo Plus M.2 WMR settings: Visual Quality very high (Beta) Resolution is best resolution (4320x2160) Refresh rate set to 90Hz Cheers

Tomorrow’s patch?! Did I miss something?!

In steam VR or where to look/find this option?!

Hi Folks, so far I was using a Rift S and today I changed to the HP Reverb. Everything is fine so far except one small item which I’d like to address here and maybe you guys can help me out. When I start a flight, let’s say an instant mission, my loading screen is alternating between the DCS loading screen with the aircraft picture and the wmr Portal screen. As soon as loading is completed, everything is fine and works as should be. Any ideas or even a solution how to get rid of this small issue? Hope you understand what I’m referring to ;-) Thanks in advance Cheers

That has been done already several times as this is their procedure via email and also via the phone maintenance call

As I’m having the same issue and had also no joy with their maintenance via email and phone, I would also be interested if there’s any hint what to do Cheers

Hello everyone, I thought that I is about time to update the firmware of my VKB Gunfighter MCG Pro. So I downloaded the newest Vkb config, bootloader and Firmware 1.96F. I followed the instructions listed here https://vkbcontrollers.com/?faq=how-to-get-your-mcg-mcg-pro-to-work-with-your-gunfighter-mar-15-2018 After Flashing, everything looks normal to me apart that I have and had all the time a solid red stick light while according to the manual it’s supposed to be solid green. But everything shows the correct new firmware and the calibration thereafter is standard as usual and everything works as it should be. After I changed my brake lever axis to a button which these instructions http://forum.vkb-sim.pro/viewtopic.php?t=2868, the stick light starts flashing green but the everything seems to work normal. Any idea what’s wrong? I was using: Vkb dev v0.90.28 Njoy32 Firmware v 1.96.C Firmware MCG Pro v 1.96F Bootloader v 1.15

thanks! So as the rift s is a WMR Headset too, will there be also another app within the oculus software?

Hey guys, just one question as I’m May a bit confused regarding steam VR and steam itself. Right now I’m using a rift but I may change to a HP Reverb but here’s my uncertainty. The Reverb will use Steam VR, does this mean that I have to change my “normal” DCS to the steam DCS Version in order to use this VR headset or may I use it without steam DCS and steam VR is a separate program running in the background like the oculus home software. Hope I made myself clear and you understand what I mean?! Cheers

Thanks dude! Do you know if they’re working on it?

Okay, so we’l give it a try on a “neutral” server and check it.

We’re using the same mission, so same frequencies etc. Just read somewhere that there is a main issue with DCS which only allows the host to use the radio in MP aircrafts. This thread is a bit older, so I don’t know if it’s still an issue or has been fixed already. Anyone heard about this one?

As stated in my original post, the XMTR switch is set to the right position

No easy comms on and we’re both aware of the mic switches and their functions!