lemoen

run a repair, this stuff has been fixed.

Do you have DCS installed on an SSD? Either way, that sounds like something loading, try upping your pre-loading distance.

I have this problem in the Campaign too. Started at mission 4.

Blue WON! After some massive battles with hectic base defense from Red (Snowman, looking at you, well done!), Blue's bigger numbers where overwhelming in the end. Can we please have a reset?

Yeah... Something's wrong. Unless you are measuring on a multiplayer server. There bad things happens. On an empty mission over Las Vegas you should be getting plenty of frames with your setup. On lowest settings it certainly shouldn't be dropping below 45 ever.

You're running stuff at high with MSAA at 8x though right? Something is amiss with your game settings. A 1070 should be able to run DCS at 45fps easily enough. Most other games runs at 90fps with 2x supersample and the works. DCS is a bit of a killer.

The Mirage 2000 currently doesn't have compressor stalls unless you fly really high and the current flight model has a strange oscillation at high speed that rapidly results in your destruction :-)

Is there something we can do to help you guys analyze the performance? There was pretty bad warping last night when the server had just restarted. Also I was flying from kutaisi and had pretty terrible framerates over ambrolauri farp. Sent from my iPhone using Tapatalk

This looks really cool.

The AJS trim is pretty slow. You're supposed to set trim to 3º before you take off (if taking a X-Tank). It IS annoying when you air start with a neutral plane and the nose wants to dive. That should probably be fixed.

Low. Fast.

Use pixel density of 1.0 for maximum visibility. Your framerate will be better too. Setting this higher can cause the something that should display as 1 dark pixel to instead be displayed as 1 slightly darker pixel. Seriously. Set the PD higher if you want to be able to read the dials a bit easier but for seeing things far away leave it on 1

You guys are flying too high and too slow. Sent from my iPhone using Tapatalk

There's clearly something up with all kinds of spotting in DCS. Last night two of us couldn't tell whether the plane at the other end of Kutaisi runway was an F15 or an A10. I was in the oculus, the other player on a 1080p monitor. Even zoomed in I could only tell what it was when the plane was halfway down to the runway already. When one zooms in and out units appears and disappears too. This can't be correct either.They should be visible unzoomed as far as they would be zoomed in.

Rearming is super quick already, not sure we can complain too much here?

I have 2 sensors. I have a small hiccup now and then but not too much.

It looks like the afterburners take a different angle from the rest of the plane. The image could be stabilised somehow to make it look like there's no maneuvering. Re the afterburner, if you absolutely want to get out of there RIGHT NOW, the AB is probably the first thing you'd reach for too. How did you evade the last missile fired at you IRL?

The Saudis are not even claiming they didn't lose a plane. One of their F15s crashed, they admitted this. The reason, however, according to them is a 'technical glitch'. Engines blown to pieces probably counts as a technical glitch. This IR video looks real enough. Plane flying, you can see heat from the exchaust, then flares, some maneuvering, afterburner and a missile hit.

I asked the question about foveated rendering without eyetracking purely because the rift and vive's images are already out of focus away from the centre of the lenses. So applying some foveated rendering as if the user is just looking straight ahead may not have a big impact on visuals but it may well have a big impact on performance.

Yeah, I was thinking the center of the fov.

With 40+ people on this server just cannot hack it. Has it been hit with Spectre / Meltdown patches? We're currently playing at 5-10fps. Warping around 100s of meters. People having trouble logging in and the chat is minutes behind.

rctrl + numpad 1,2,3,4 sets between no warp 90fps, no warp 45, atw, asw on the rift.

The game will probably have to implement the foveated rendering calls. Unsure how this will play with Vulkan. I was wondering about foveated rendering WITHOUT eye tracking, considering that the image is out of focus towards the edges anyway. Maybe some performance could be gained.

+1 for Tirak's idea.

My HDMI cable got pulled out because the strain relief band became too large to hold down the hdmi cable on the side of the rift. I attached a zip-tie tightly to the cable on the headset. It has stayed put since.