hellking

Just wanted to say that I am having the same problem. I tried the mission twice and it gets stuck right after CCRP instructions. I will try the fix.. Thanks.

Just to clarify, I am not doing a cold start. I am doing a hot runway start. Similar to other modules, you would expect the plane to be ready to take off with full flight control functionality in a runway hot start.

00Donkey's solution fixed it! Thank you.. Now I can enjoy the plane without having to hold the stick down and creating oscillations with every move I make.. At a minimum, this seems to be a problem with how runway starts are setup..

I feel like Viggen is the most FPS demanding module, right after MIG-21. Even in a clean mission, i see stuttering with the same graphical settings I am using for other modules. I wish developers offered an option to simplify textures and/or 3d model. Something like a "LOW - MID - HIGH" cockpit model option..

The module is not very Oculus friendly in terms of performance. MIG-21 was also not very friendly, but this one seems to be 10% or 20% less friendly (less frame rate on average). This small difference is a huge problem because MIG-21 was already at the limit of what can be tolerated in terms of stutter (if you also want to enjoy shadows). Would it be possible to add an advanced option to reduce the textures or 3D model one notch? Textures seem to be much more detailed than my eyes can see in the Rift... I really love the artwork, but cannot enjoy it when it is stuttering.. 3.2 GHz CPU 32 GB RAM 2 x GeForce GTX 980

Hmm.. I checked and re-bound them. Still not working.. If nobody else is having the issue, it must be related to my setup. Thank you for the help.

Thank you!

I made the same observation when videos were released, and after flying it, I still have the same opinion: sounds of this module are very sub-par at the moment (compared to other excellent features like textures, lighting, flight model, etc). Specific features that are sub-par: - Loopy afterburner sound - No road noise on runway - Very little wind noise in air (is it really supposed to be like this, even at high Mach?) - Button click sounds have no variation and sounds artificial. Sounds features that are very good in contrast: - Engine stall sounds at high AoA - Afterburner engagement sounds

Trim up and down functionality is not working when I assigned it to my HOTAS Warthog. Trim left and right (wing down) are working..

The load screen time seems to be double of any other module in DCS. Anybody else having this issue?

EDIT: I have Ge-Force 980, 32 GB RAM, 3.5 GHz CPU, Windows 10..

VR frame rate is not GPU bound. There was a detailed study on it in the forum somewhere.. I also did my own study and painfully found that out after my new expensive rig performed worse than my old.. My GPU utilization always hovers around 20-30% when I am playing DCS with Oculus Rift. For DCS + VR, CPU clock speed (single core kind) is the king.. Doesn't matter how many cores you have as long as it is more than 4.

I received my Touch today.. After my experience with leap-motion FSX, I thought there is no way this technology would make it in flight sims.. But Oculus Touch changed my mind.. Because Touch is heavy in the hand, it could mimick the weight of throttle and stick very well. I could easily think how Touch can be used as both the Throttle and Stick (you simply grab the Throttle and Stick in the cockpit to use them). There are not as many buttons on the Touch, but not too few either.. There are 8 buttons if I am not mistaken.. Not good for A-10, but should be minimally sufficient for most sims (for example missile trigger, gun trigger, Trim, lock, plus a few others).. The only thing that is missing from Touch is localization fingers exact position, which could allow implementation of virtual switches. I can see that this is only a few years into the future.. I would predict that Touch will be eventually implemented in DCS (with minimal success), and used widely once finger locations can be tracked precisely with next gen controllers (a few years later). EDIT: By the way, I just tried stowing (hanging) Touch at back of the hand using the wrist band for using the HOTAS, which could allow going back and forth between switches and stick.. it kind of works.. could be a intermediate solution..

I really like the lighting!! I wish all modules had something like this.. I have some comments about the sounds though: I don't hear any road noise during take-off. The aircraft seems to be shaking but no rumbling shaking noise etc.. It would be nice to have some.. I can also clearly hear the engine noise sound looping (noticeably repeating itself) every couple of seconds. It would be nice to use a longer sample or remove distinct parts of it.

I have the same issue but it is not unplayable, even in VR. I am wishing it is brought in par with other WWII planes though...

I have also found 109 very effective in a dogfight, but you still need to maintain a good balance in a turn otherwise it punishes you with a spin and it is very difficult to recover the advantage. In Spit, I can turn twice faster and don't go into any spin. If I act greedy and turn it even faster it goes into the spin, but I can recover from 2-3 spins one after another without loosing advantage. It feels like there is no way to fail a dogfight in Spit.

Anybody else is also finding the roll rate and rudder sensitivity too high? When I am in a dogfight with FW190, I can out turn without any effort. Spit ends up being a little bit slower than FW190 but I can very easily cut into it's turn with almost double the turn rate. It is also possible to make very high G turns even at slow speeds.. If the real Spit was like this then FW190 or Me-109 are no opponent to it.. If you happened to make a change in the rudder pedal position it makes a springy motion that goes back and forth for too long.. Feels a bit too exaggerated... EDIT: Just realized that I mixed up roll-rate and turn-rate above.. What I meant was turn rate, not roll rate...

I have this problem too... Cannot move mouse cursor if the comm menu is closed. The only way to work with the cockpit is to keep the comm menu open. Hope this is fixed before Spitfire and Viggen are released.

After playing with ASW with different settings I found that it works wonders if your original frame rate is above 45. If you are below 45, it causes frame burst effects every second. In the latter case, I find the artifact worse than ATW because I got to learn how to deal with predictable and steady ATW artifact after months of playing, while periodic and unpredictable ASW artifacts messes with my brain.. I guess it could be learnt to deal with as well given enough time.

Anybody else having wobbling effects with ASW on? The frame update rate seems to go up to 45 as it should in heavy graphics (Vegas for example), but frames update in bursts and they are not uniform. So objects don't flow smoothly, they wobble.. I don't mind the standard ASW effects such as ghosts etc. but wobbling makes it even with how it was before.. I tried updating my graphics card drivers but it didn't help.. I also tried to turn on/off VSYNC and fullscreen. I also maximized/minimized DCS window to no effect. Any experiences?

I really enjoy the M2000 sounds, especially after the start up. During the start up it is not programmed to what is going on in the cockpit, so it sounds like pre-recorded and out of place. After ED programs it properly it will be the best.

Same problem here with Saitek rudder... Too sensitive. Even a tiny touch on NS makes a very hard turn. When you try to correct it you end up overcorrecting and enter an oscillation. There is no way this is how it works in reality. This was the only obvious bug that I discovered, otherwise excellent module!

I have the trim problem as well. Try air refueling with no trim :lol:. With DCS 2.0 I was able to fix the problem by turning the feedback off in options. In 1.5.4 it does not fix it.. I have a G25 connected (not used in DCS, mainly for racing games).

I am having the same problem... It was working fine when I had 1.5.3 v7. Then I installed 1.5.4 and had the black screen problem. Oculus was still successfully being detected at that time. While trying to solve the black screen problem, DCS suddenly stopped detecting the Rift... Log shows this: 00001.599 ERROR VISUALIZER: unable to init OpenVR runtime: Hmd Not Found (108) The strange thing is 2.0 Open Alpha is still detecting the Rift. All other games are also detecting Rift.. So Oculus Rift is not the problem. I have tried: 1) Copying over options.lua and adding the VR text (gets rid of the settings crash, but Oculus still cannot be detected) 2) Uninstalling and reinstalling DCS Open Beta (tried this twice) 3) Unplug/plug the HMD, switch to a different USB 4) Repair (tried this 3 times) 5) Update to old version 1.5.3 6) Deleting DCS Open Beta folders (both in My Games and Program Files) None of these worked.. Even the version which worked before, is not working.. It is unbelievable.. I have to stick with 2.0 Open Alpha and hope that 1.5 is going to come back.... Sigh...

Adding the VR text in options solved the black screen problem. But DCS does not open in VR mode anymore. VR mode is enabled in the options... After launching the application, I keep seeing Oculus Home. DCS opens in my monitor like it cannot see the Rift.. B.T.W. I tried deleting my options.lua from saved games folder. I was expecting DCS to create a new default one, but it never happened... I had to go fetch one from DCS installation directory and copy it over.. I don't know if I did the right thing. I think I will revert back to 1.5.3 until these issues are resolved.. Looking forward to the nice updates in 1.5.4!