KLR Rico

I'd think it'd be nice for things like dogfighting where there are advantages and disadvantages to VR, but everyone would be on common ground.

I'd love to see a server dedicated to VR users! For chat, the friends I usually fly with switched to Discord, but I have no objections to using TS.

I did some testing last weekend to find that "Image quality vs frame rate" sweet spot. I recorded a track, and then played it back at different pixel densities while recording performance information with MSI afterburner. I found that I can maintain 90 FPS pretty well right up through a density setting of 1.6. The real limit is somewhere between 1.6 and 2.0, but that gap is bigger than it seems because the GPU load is exponential to the density setting. I'll probably test again to narrow down where the sweet spot is hiding in there, but there are probably lots of situations where I'd hit a GPU limit even at 1.6 (like dusk/dawn, in weather, etc). It's also worth noting that there are points here where frame rate takes a hit regardless of the graphics settings, these were mainly the parts where I was diving in on targets and the simulation was CPU bottlenecked. It's also kind of strange that there are lag spikes that were only felt at 1.0 and 2.0, I'm not sure what caused those.

Perhaps record a track and watch it in Tacview to see how many G's it's pulling.

I already have a couple thousand dollars in hardware that is used for DCS almost exclusively. I'd pay stupid amounts of money to have a new engine that could take advantage of it.

I also have labels on HOTAS. That, along with the option to zoom and increasing pixel density has solved pretty much all my concerns with spotting.

I've been having this problem with 1.5.4 also. FFB will die randomly, and I have to exit DCS and unplug/replug the controller to get it to come back. The controller is still recognized and the axes work, just no forces. I tried skipping my USB hub and going straight to the computer, and messing with power settings, but I couldn't get it to stop disconnecting.

^ You win.

I jumped into 1.5.4 after a couple weeks ago after about a month without playing and I thought the sounds were really good, but I thought it was just from not playing. Glad to know I wasn't just imagining it. :D

For the most part, the framerate in DCS is is CPU limited. Having more GPU power won't increase frame rate, but you can make your limited frames look really good! I didn't gain any FPS switching from 970 to 1080, but I can now run some post-processing and a 2.0 pixel density with the same frame rate as before, which was more than worth the cost of the card.

If you OC'd the CPU well past 5 GHz on LN2 you probably could get consistent 90 FPS in single player. :D

That's incredible... it's hard to appreciate numbers on such large scales, but this certainly helps visualize it. It's crazy to think that each tick mark is an entire thousand human lives cut short.

1080 isn't slow, just that DCS is completely CPU bottlenecked. Yeah, CPUs haven't improved much in the last few years, pretty disappointing there. Use the 1080's excess power to crank up the settings that load the GPU but not the CPU; pixel density, HDR, AA, filtering, etc.

Uh... sit down and *then* put on the HMD? :huh:

It's been brought up before (a lot), and the answer is generally "Easier said than done", and it's not gonna happen.

Hold RCtrl + RShift, then use the keypad to move around (I think * and - are the forward/aft adjustments). I usually look over my shoulder and use the headrest to gauge where I should be. When you get it where you want, use RAlt + KP0 to save the view position.

I have a 970 that I put in my wife's work computer, I'll see if I can steal it back for some testing. I didn't do any scientific testing at all when I did the swap, but when I first put in the 1080 I was a bit disappointed I didn't see any significant FPS increase in DCS at all. Then I cranked up the pixel density to 2.0 and suffered basically no FPS hit for a MUCH better image quality, which was worth the upgrade price itself.

I want to start testing different settings to see if I can squeeze out some extra performance, but I've been having too much fun flying as-is. Here's a historgram style chart of my framerate during an A-10C instant action mission, including a NOE flight back to base. Textures: High/High Civ. Traffic: Low Water: Med Vis. Range: Med Heat Blur: Off Shadows: Med Cockpit Disp: 512 MSAA: Off HDR: On DoF: Off Lens Effects: Off Clutter: 1000 Tree Vis: 10K Preload: 100K Anisotropic Filtering: 4x Flat Terrain Shadows: On Pixel Density: 2.0

Are you on this week's 1.5.4? Last week's had a problem with saving view positions, but it's fixed now.

Use the keypad view adjustments (RCtrl + RShift along with the keypad) to get it where you like, and then RAlt + KP0 to save the setting. I found I had to adjust the positioning a little in pretty much all the A/C to make it feel right.

The Rift feels like a 2nd gen device with 2.0x pixel density, it's magical.

They're both pretty good, but I understand the Rift has the slight edge for DCS and the like. If you have the $ (sounds like you do), get both. :D With those PC specs, you could probably run both at the same time in VM and do some multiplayer with a friend in the same room. :joystick:

Just couldn't let the thread die in peace, eh?

You'd keep it full forward (3000 RPM) to get maximum power for takeoff and dogfights. Maximum continuous is 2700 RPM and 46" Hg manifold pressure, and cruise setting is 2400 RPM at 36".

No