Redlinebuzz

Apologies for being stupid, I have no idea what VR Runtime I am using, all I know is that when I start DCS the Oculus app starts, I go to the OcukusDebugTool, Force ASW Off then ON, and everything is honkey dorey, But when I do this in the Multi Threading version my framerate locks to 40 (Rift S) as it does in the non MT version, but looking at the scenery it's a mess. I have looked through the various release notes to see if this is listed as a known issue but couldn't find anything, thankfully the non MT version still works magnificently, am I alone and do I need to look into these different runtimes or should I just wait for a fix? Any help appreciated, I did search before asking.

So I'm not alone with the huge performance hit with rain in VR? Everything else in 2.8 is fantastic, performance is much improved, the rain looks beautiful, but it kills my frame rate.

Yeah, he said it twice as well, surely not a slip of the tongue.

I find that if I don't move my head, the clouds don't bounce, if that helps !

This is a request for rivers beyond say 50 miles not to be rendered in VR. I was totally in awe of the Syria map with the new clouds, words can't really describe how awesome it looks. But one thing is kind off ruining the whole experience, mostly at low level, rivers at huge distances are causing some pretty immersion breaking jaggies. It would be really nice if there was a distance at which rivers don't get rendered, I don't really need to see a small river at 50 miles create a huge disturbance in the force ! Anyway, great work from Eagle Dynamics on 2.7, really a game changing update, thank you.

Yes, same here, all my clouds are having a party !

Sorry, have no idea how to accurately describe this. But can't get TACVIEW to record, their troubleshooting indicates a module may have broken something. So I tried doing a clean install in a different location on the same disc and get this error. "03888.568 STATUS: C:\Program Files\Eagle Dynamics\CLEAN_INSTALL\DCS World OpenBeta\_downloads\CoreMods/WWII Units/SpitfireLFMkIX/Liveries/SpitfireLFMkIXCW/USSR pilot Lt. Col. V. A. Matsiyevitch, 26th GvIAP/SpitfireIX_USSR_Matsiyevitch_26th_GvIAP.dds.downloading.6e5f1ccbd3afce42: (3) The system cannot find the path specified." Any help greatly appreciated. Thanks EDIT: Found the problem, folder structure, thanks !

Thanks anyway.

Could this be used with a profile that was created using the GUI ? Thanks.

Yay! The fw190 seat is now in the middle! Happy days.

Just tried the f16 landing quick mission in 2.5.6 and the airfield hangers don’t appear until very close to the, then they appear in one eye until you get closer when they pop into both eyes, anyone else ?

May have been a combination of new NVIDIA drivers as well, went back to non beta Oculus and older GPU drivers and everything went back to normal ! That'll teach me to update drivers !

Just a heads up, the new Oculus Beta software will probably destroy DCS with huge 1-2 second pauses every 30 seconds or so.

LOD texture ? Been searching for ages but cannot find an answer, I managed to figure out how to skin the F14 but for the lige of me cannot figure out how to do the LOD file, so it keeps jumping back to a different skin at distance, is it even possible ? Because I don't see an LOD file in the paintkit, thanks in advance.

What happens if you don’t ! Well I can confirm, that if you don’t follow the new procedure of confirming coordinates, you end up all kinds of lost ! Tried an inflight alignment but the sim crashed before I could see if it worked.

Elite Dangerous rebuilds it's shaders every time there's a driver update, or you can force it to do it every time the game starts, can't be that hard to implement ?

Just noticed this after being away for a while and buying the F16 to get back into the swing of things, also tree shadows are working great for me !

Just started having this problem after the most recent update.

This has been a problem in Xplane 11 for ages, to fix it you need to open up the Oculus Debug Tool, launch DCS, then in the Oculus Debug Tool you need to force disable ASW, and then Force enable it, switch back to DCS and all should be well.

I have a sneaky suspicion that the Pixel Density in 2.1 is not working, I see no difference between 1, 1.5 and 2 I only noticed it because I couldn't read the gazelle gushes anymore, setting it to 1.5 in Oculus Debug works fine though. As for stutter, if I have any shadows at all enabled and look of the right window I get horrible stutter, so I don't look out the side window much !

Has anyone noticed that the pixel density in game doesn't work anymore ? I have had to use the Oculus debug tool to set it up. Also when you look out the right window does anyone else get stutter with shadows enabled?

For me it's the shadows, any shadow is a real killer, the other settings don't affect much, but as soon as even flat shadows is turned on the stutter starts, only on Normandy though, Nevada is fine, strange...

Yep, what they all said, once you try it there is no going back, the only people I've seen talking negatively are people that don't have one !

Does disabling the automatic app updates stop the Oculus from updating its own software or is that not just 3rd party apps ?

Any more news on this, I want to buy the new campaign for the A10c but not until I can see the HUD.....