Captain Slow

Thanks, good to know. That is pretty much the same machine I have (9900k and 3090). The biggest contributor to slowdowns, by far looking at just frame times, seems to be the category "Simulation". Is there any explanation somewhere what the different frame time categories include more in detail? "Simulation" normally sits around 5 ms, but when the slowdowns start it jumps to above 10 ms every few frames, probably even quite a bit more. Thus usually happens when flying closer to the ground and near cities. (example numbers taken from simple instant action testing)

I realize it is unlikely anyone will 90 in all circumstances, however I want to make sure I have understood the implementations of g2 reprojection correctly (as my first post) and am curious about the stuttering without it.

So I finally got both the 3090 and Reverb G2, but unfortunately my machine isn't able to produce 90 fps in dcs in *all* situations. So, Ive been trying to understand reprojection, and the conclusion and experience I'm currently seeing is: * If I enable reprojection, due to limitations in WMR + SteamVR, it will go to 45 fps (but still feels kind of like 90 fps) when the game starts rendering below 90 fps. Many times I dont even realize reprojection kicks in , but somtimes I do (wild rolling causes certain hud elements to show some ghosting artifacts) * If I dont enable reprojection, head rotation will still have reprojection, but pretty much everything else (head translation, aircraft movement, aircraft rotation..) will move at game framerate, for example 70fps - and for some reason it causes some super wild stutters (not a framerate issue, but rather just plain old stuttering), pretty much making the game feel unplayable. Have I understood my options correctly? And also that there might be a better reprojection option coming in the future for us Reverb G2 users, which is basically option 2 without the stuttering? For now I am sticking with reprojection enabled, because the second option/mega stuttering is just unbearable for me I don't really understand why option 2 starts stuttering so madly below 90 :/. Normal desktop games with regular vsync on an triple buffering does introduce some stuttering when slightly below target fps, but nowhere near this also, different question: Is there ANY way to disable the desktop mirroring of DCS VR view?

same issue here. 100% reproducibility. target box/diamond is just straight ahead regardless of where target is - and the angle off indication is locked at 4 degrees :)

LTWS TDC-over information does not move with contact if turning I wish to inform you that this report is valid again, now that LTWS has officially been added: https://forums.eagle.ru/showthread.php?t=233537 symbology is obviously a little different, but the principle is exactly the same. You can basically have your tdc on the left side of the display while the target you are supposedly keeping the tdc over is on the right :)

SA page and RDR page both introduce very significant performance hits for me as well. Basically 2-3 ms of frame time added by just those pages combined. The more contacts, the more impact. They dont seem very well optimized.

yup - having the same issue. The function has been removed I suppose ? (or was never supposed to be introduced yet).

pointing the nose means giving the opponent a better shot. I would avoid it if possible, so very much looking forward to being able to point the radar instead of my nose :). mini-raster? you mean when you tell it to try to lock the first best target which comes into the highlight volume? I need something with more control in a multi target environment.

FYI: The IDLE problem was solved for me by disabling the game's built in fps limiter. It can be found in <DCS_HOME>/Config/graphics.lua line 350

My situation has improved significantly by disabling the game's own fps limiter. You can edit it in <DCS_HOME>/Config/graphics.lua line 350. I just set it to 10 000 :). Before that I had some rather crazy issues where my GPU actually decided to go into "idle" power profile. If you fly the F18, also check so that you havent run into this issue I fought against for a few days: https://forums.eagle.ru/showthread.php?t=233582 NOTE : The solution in the thread is actually wrong. .net had nothing to do with it. I dont know what the solution is yet, but after reinstalling windows and removing the fps limiter it seems to work better.

I'm 90% certain we will get HAFUs on radar screen (because there are TODOs in the lua code about it ;) ), even if we might not be able to link radar tdc with sa tdc.

Yeah, given the answer by Anonymous User I think we are still waiting for it to be implemented. Re-engaging after being on the defensive right now is quite dangerous and slow. Need to be able to reposition scan center.

My 2080ti does the same quite often, and I have yet to figure out what is the cause. I have verified with gpu-z that indeed it sometimes goes to idle in DCS! No idea why. I thought I was the only one... But apparently I am not, and this isn't a single user case. My system is 9900k, 32 GB ram, Palit 2080ti gamingpro OC. What about you? This is on a fresh windows installation! (yesterday) with zero usb input devices attached except mouse and keyboard Setting the card to "prefer max perf" has absolutely no effect on the issue. Screenshots attached Flapping idle/full perf in game Idle in menus: Idle looking at sky:

Reproducible: 100% Date: 2018-03-03 1940 Z Sim version: 2.5.4.28090 Open Beta Mission: Any with air target (Track recorded in F18 instant action aim120 training mission) Steps to reproduce: 1. Angle your radar to scan the targets 2. Look on SA page 3. Position TDC around contacts Problems: * TDC should be drawn on top of contacts, so we can read altitude and mach number - right now it is the opposite * same issue with SA page RWR info * Draw order among contacts order is reversed (prio 1 should prob be drawn topmost/last - right now it is the opposite) Track: attached. Screenshot: attached. Desired solution: * TDC should be drawn on top of/after contacts * TDC should be drawn on top of/after SA page's rwr symbols * draw order among contacts should favor highest prio drawOrder.trk