Carabassa

Have you closed the debug tool AFTER loading the game. The judder should disappear then.

You can close the de debug tool after DCS has loaded it will maintain the supersampling. If I don't close it I have judder.

Latest runtime and debug tool 1.4. FPS seem good, only tried alone without enemies for now. There is a little judder some times but asynchronous time wrap is doing well. I have yet to test other graphic configurations.

Received the CV1 last Thursday and it is a big improvement over the DK2. Everything in the cockpit is so crisp. You can even read the gauges and the HUD is more readable. Far horizon is also greatly improved. Setting override to 1.5 in debug tool makes a big difference. I only have to learn to fly any plane or heli properly .

This module is awesome. I am really enjoying it in the Oculus DK2. I crash almost every time I try to land but I will get better with more practice.

Thank you for the video.

Muchas gracias. Yo estoy poniéndome con este simulador ahora que empieza a ir mejor con la realidad virtual y ayer me compré este helicóptero junto con el mapa de nevada.

This would be awesome. I don't even know what functions have to bind to my X55. I am only playing this sim for some weeks. There is plenty of info about A10C, KA50 and other aircrafts but this had been just released yesterday and I am really lost.

So is it safe to update? Sent by mobile device sorry for the spelling.

So it is not only me?

F15 from FC3. Custom mission clear weather at 12 AM. Starting from random airport. Every else default. Thank you for your answer.

The one thing that shocked me most in the DK2 was how small a plane cockpit is. I have one question if anyone can help. I have configured all settings as recommended in the forum (shadows off and other stuff) and can fly alone without any judder, smooth as silk. But when I put some AI the judder appears. The CPU use is high but not 100% and de GPU use is around 50% or less, but the FPS drop below 75. Do you think my CPU can be a bottleneck or is any other configuration I can adjust? I am playing the 1.5 beta all with latest Oculus SDk 0.7 and Nvidia drivers. Thank you in advance.

Direct mode forces vsync no matter what is configured in the graphic card settings. It is absolutely fine to have 75 Hz.

It works :thumbup:. Thank You very, very, very much. I only have the base content and couldn't load any mission for the SU-25T. Only some instant action was working but most of the times crashed while loading and always with a crash on exit. Now it loads missions (not tried them all) and there is no crash on exit. Now I am ready for the next sale to b uy some juicy DLC's. With Windows 10 and non steam version of the simulator.

I always get 75 and sometimes 35 when my Nvidia GTX970 can't handle too much stress. That's in direct mode that forces VSYNC if I am not mistaken.

I think SweetFx is not going to work ever with direct mode (the way Oculus is working since SDK 0.7). The increased resolution of the consumer version sould be "enough" to play without it. The only thing that developers can do is to put some kind of image processing in the render code. For example Elite Dangerous lets you configure some supersampling resolutions but don't know if it will work once they introduce direct mode with SDK 0.7.

Yo como también estaba probando la beta por steam copié el fichero del training de ahí.