F22-Raptor-2006

stuck here too

This is still an issue 3 patches later, is someone even looking into it? I've even tried this in my autoexec.cfg in Saved Games/DCS/config/ net.use_new_fm = false Still doesn't work, will someone from ED reply?

Same problem, connection timeout since the last few patches. Attached logs. i7 4790k GTX-980ti 16gb ram DDR3 ASUS ROG Maximus VII Hero Windows 10 pro x64 dcs.txt

Hi, I've been trying out the F-86 both with and without a rift and it seems that I can't get any tooltip text to show when I mouse over any of the switches? I've also tried the MiG-15 and that works fine I get all the tooltips so I'm wondering if there is a bug here, or have I set something wrong?

It's cockpit based so it's not that bad. Also if you've had a lot of experience playing flight sims and if it's pretty second nature to you then the idea of moving in three dimensions shouldn't be an issue. I find from testing it on other people those that are most comfortable with flying or this concept of moving in all directions are the users that don't feel nausea.

I have a rift, no problems with judder on multiplayer servers with up to 30 people. Just lag from the server but that lag exists regardless of rift. Running GTX 980ti with i7 4790k @ 4.4ghz standard clock

Another thing about the mouse pointer which I'm using in 1.5 at the moment. It seems to be the case in all cockpits that where we I see the pointer rendered on the rift and I presume the same would happen on the vive is not the pointer actually is. In the sense that to click a switch I have to move the pointer to the side of the switch somewhere until it changes colour. Items near the center are fine but switches on the left side require me to move the cursor further left than the switch, and on the right hand side further right of the switch. Closing either eye doesn't seem to help so not sure if it's related to the distance at which the cursor is rendered or anything but it's a bit hit and miss trying to move the pointer over a switch that is offset from where you see it.

If you have enough ports to connect both, there should be no reason why you would have to disconnect one. However, I believe you would have a problem launching a game and deciding which one it would use and so probably you would need to unplug it. (Perhaps shortcut parameters can adjust this). If I launch DCS with the rift plugged in, it will automatically launch on the rift, you don't get a choice to use your monitor. So you wouldn't be able to choose which headset you want to view it on either I would expect.

I've never used a track ir but I have a rift and I can tell you that the camera tracks you pretty much up to the point where you're nearly perpendicular with it, it's surprising what kind of angle you can get it to track you at. This means you've got quite a wide and large space to use (effectively as if it's room scale, you could sit 2 meters away if you wanted to). You can sit in a reclining seat no problem, but your head still needs to be looking forwards to look forwards in the game (as in you can't lie on a bed with your head facing upwards and expect to be looking at the HUD in the game, your head orientation is reflected in the game based on the orientation of the headset). Depending where you decide to sit you just need to reset the camera to be centered on your position so you don't end up outside the aircraft for example.

That guide is great cheers!