uri_ba

It's a stupid request I know, but I got jumped by it, when I mounted my Leap motion on my VR HMD. apparently TIR sensor picks up the IR cameras in the Leap and goes crazy. it keeps locking on 90 deg roll, 180 deg yaw. and the game position changes between the TIR reported position and the HMD position. if it is simpler, just priorities HMD tracking data. if present, just disregard TIR data. Cheers.

Yeah, it took me a few minutes to figure it out :) Thanks!

I'll just put this here.. :)

Thanks for this :) I'm having hard time figuring out why I can't get proper FPS on 2.1 (significantly less the I get on 1.5.x). after going over your findings, I starting to think that my i7-2600K is bottlenecking my 1080 seeing under 30FPS in 2.1.0 and 45+ in 1.5.6 (i'm running in VR) anyone has suggestions? or should I start putting money aside for the 8700K?

can you try and correlate FPS drops to the presence of airports in your FOV? (at any distance)

Happens to me too with TIR4.

For me it happens regardless of aircraft on the ramp. But you guys actually conferming my suspicion it's a LOD switching problem. I wasn't sure if it's buildings or static objects :) Thanks guys... ED folks, can we haz a more aggressive LOD distance switching in VR (at least)?

I'm Flying with a Vive and I've noticed that I get very bad stutters every time I have an airport in view. I've initially thought it has something to do with VRAM but it seems that something in the Airport is Sucking up Triangles... Up to say 4M tris, which is enough for low level flight above an Urban area in 1.5.4 I have no performance issues what so ever. whenever I have an airfield in sight, empty or not. Tris count goes up to ~13M and FPS drops to about 15-25fps. not a problem in most cases.. big issue in VR. I couldn't pinpoint the building, but it seems to be something in the Aprons. Can someone confirm? is it just me? Thanks, Uri Spec: GTX1080 I7-2600K@4.2Ghz (HT off). P.S. if someone can edit the thread subject, that'll be great... -- Update -- Turning shadows from "Flats" to "Off" seems to have reduced the tris count from 16M to 6M. which is more manageable by the GFX card. I've been testing using the M2K "takeoff" mission, sitting on the RWY and look left.

OK, seemed to be something local I still need to figure out. looks like letting the GFX card rest for 24H (night then work) had "fixed it". it's probably something that has to do with thermals on the card (which I can't understand - as it's under the limit all the time). I'll keep digging into it. 10x anyways.

Hi guys, OB was solid till the last weekend's patch. Ever since I've been getting flickers as FrameRate bounce up and down while not adhering to the 90/45/30 fps limits. I've been seeing 45 to 60 FPS quite a bit which cause screen flickers and a not so freindly experience. I've not seen it in any other VR game, so I'm wondering if that is just me Thanks, Uri P.S. same applies to 2.0.3 (where it also flickers in the UI)

In theory it's actually this way already. you have a mirror of the left eye onto your main display. I actually use it quite a lot for menu work, just lay they headset on a table, recenter it and work off the screen.

I guess not then.... Thanks.

Try freeing up some GPU memory by lowering texture quality and lowering AA. To See if that helps. If you constantly need to load and unload textures it might be the spikes.

FC3 has no clickable cockpit... so no ToolTips.

Hi guys, Currently in VR mode DCS mirrors the left eye on the main deisplay. very useful for "spectators" (i.e me watching someone else so I can help them not crash). Howerver I wanted to do a little experiment with 3D video. I was wondering if there is a secret debugging console setting that will allow both eyes to be displayed togeater. I'm fully aware that is the a Bad Idea, and it will tank performance. But as I've said. Experiment. Thanks, Uri

I have to agree with them. The added value of the KW-908 to my VR experience was very noticeable. I've pretty much wrote everything I could about it in my blog https://pits.108vfs.org/uriba/kw-908-forcefeedback-seat/

you'll need to overclock the GTX970 to get to a proper frame rate. the problem is that unlike normal screens, where you can drop down to 20fps from time to time and it will be OK, with VR you must stick above 45FPS for as much time as you can. and while dropping to 30 is acceptable, you want to make sure it is kept to the minimum, and you don't drop below that. you can use the DSR feature on the Nvidia driver to push up your resolution to 4k (which will be closer to the render target you will need for a VR HMD). play around with the settings, to get the framerate and you'll get the rough estimate on what to expect visual quality wise. I'm using an OC'd 2600K and OC'd 970. it's not perfect, and I'm running 45-30 fps, (optimal will be 90fps). But it's reasonable, and the immersion is great. but the instruments are very very hard to read. (don't forget that the resolution needs to cover 100 degrees FOV)

no problem here, I actually envy you on that performance (I can only get 45-30 fps on my rig - GTSX970 w/2600K@4.2) VR headsets use Vsync like frame capping to prevent nausea induced by wrongly timed frames. so even if your system can display 80fps, you will still be cut down to 45. as long as you are above 45fps at all times the game feels OK (you can see that, but it's tolerable). Going down to 30 will cause you disorientation. you can try disabling HT on the CPU and see if that helps a bit. games do not utilize multicore processors as efficiently because they only use 1-3 threads, when one of them is the "heavy lifter" the the others are small. in my case, I believe that disabling HT gives me ~15%, but it could be just an illusion :) 0 risk, worth the try.

actually for me FPS in the air is much better then on the ground, try running an Instant action, just to check. I have a 970 with much lower OC then what you get there. and I can maintain 45 for most of the flight (A-10,M2K and P51), but when I go to land, things get messy usually (as well as when I start dodging buildings in towns).

In addition to that, there is a small effect, in which if both rockets have the same drag, the lighter one will deccelerate a bit faster then the heavy rocket. Due to the fact that the higher mass has more inertia (I.e you need more force to slow it down) - another effect of the higher energy in the heavier rocket.

But you pay for this over sampling. You need to render X times more pixels, if you have 1080SLI go for it, you might be able to boost up to 2.0 while maintaining high FPS. However, most systems will need to sacrifice to use it. But it's making the pit usable vs higher graphics. Some systems can't trade, a stock 970 will not be able to use MUltisample at all (at least not on the vive)

I'm testing low alt over town most of the time (p51 "free flight over poti") this give me a rough benchmark. Going back to land is the real problem, with fps initially dropping to 20 in the flare. With playing with the tree and gras radius I have it back to 45, which is good enough (even with 1.5 multiplier). I do have AA at x2 and MSAA off, shadows on flat only. However, I did decide to "bite the bullet" and turn on HDR, just because starting into the sun without it breaks too much of the immersion (same as no shadows at all). I've yet to to test 2.0.2

Thanks, I'll have a look, based on this, I can try and push the memory a bit more. I run +175mhz clock, +150mhz on me, no very voltage. And I'm not throttling due to TDP or Temp, (it just crashes if I try to boost it up a bit more). Boost clock is stable around 1500mhz

what settings are you on? I can barely get 45fps on my 970 while in flight, not to mention the massive performance impact setting the multiplier has on my system. in practice you double the resolution you render then scale it down to the screen. 2.0 makes the P51 pit very readble, I can actually read the compass. but I can barely scrape off 30pfs with everything on low. I had settled, on 1.5 with lowered quality (compared to 1.0) just to maintain a decent framerate (i.e 45 most of the time).

I only get the vive "load env" when the game loads (going from UI to 3D). once in the pit I don't get it anymore.