GhastlyTT

Yes, you can. I do it so friends can connect to me and I believe it helps spread some utilization across cores. Make sure you have adequate RAM. 32GB works for me.

VR recenter is in the UI layer options and is not the same as the "5" option you're using.

No need to be sorry. I'm the one that is incapable of explaining it. A simple internet search agrees that CPU workload does not increase when you increase resolution. https://lmgtfy.com/?q=how+does+resolution+affect+cpu no further discussion needed. I'm wrong and all is good.

It's not expected. Not in the sense that i was trying to convey. Everyone got hung up that I mentioned Steam Supersampling in the first post. Play something else at low resolution. Anything else. Decrease all details so that your CPU is the bottleneck. Now, increase your resolution. CPU doesn't slow down generating handing the frame to draw to the GPU until the GPU can no longer keep up. Now GPU is maxed out and CPU can't work because it's waiting for GPU to request info. DCS doesn't work the way I expected. CPU is doing something behind the scenes, whether it's intentional or not I do not know, that is HIGHLY affected by resolution. The higher the resolution, the harder it is for the CPU to generate the scene for the GPU to then render. BOTH CPU and GPU get hammered by higher resolution which is not the status quo. 2 gentleman explained to me that I don't understand and DCS is unique so I'll accept that until I'm smarter on the topic and agree or disagree. In the meantime, if you're in VR, reducing PD reduces load on CPU thus generating more frames for our starved GPUs. You don't lose detail. You only lose clarity. Everything will still be there. The scene is the same. Find a compromise and benefit. edit to add: I started this because every guide i found says to leave PD at 1.0 . There's real world benefit to high resolution HMD owners by reducing PD, especially in the current state of the OB.

Very insightful. Thank you both.

Thanks!

Does the CPU verify what's written to the screen? Or does it just present the next thing to write to the screen when the GPU is able? Sent from my SM-N970U1 using Tapatalk

Not really a trick. I'm on standalone. SteamVR is only used because it's part of WMR.

Can you point me in the right direction? I love learning. This is unique to DCS in the handful of titles I've tried.

I'm not assuming that. I'm pointing out that the task performed by the CPU at .5 and at 1.0 pixel density (or even 1080p and 4k) is the same. The scene is decided and set. It doesn't decide how many pixels it's drawn across. That's the GPUs job.

Just because you can't see it at a reduced resolution doesn't mean it's not part of the task presented to the GPU. Text in the cockpit is a blurry mess at .5 PD but it's still the same texture file. DCS isn't unique.

An analogy: 1. Teacher (CPU) tells student (GPU) to write a 2 page paper 2. Teacher (CPU) tells student (GPU) to write a 9 page paper In both instances, the teacher's workload is constant: tell student to write paper. Only the student has to do more work. Telling the student to write a smaller or bigger paper doesn't change the load on the teacher. The CPU requests the GPU to draw a picture the same way regardless of resolution. PD should not affect CPU workload if the GPU is not bottlenecking the CPU. CPU should stay constant as the idea of the frame doesn't change, yet in DCS, this is happening. .5 or 1.0, the idea of the picture is the same. Yet, at .5, CPU generates that idea faster. It shouldn't. Something is off. Maybe ED will see this and understand.

This isn't an RTS. From a CPU standpoint, increasing resolution doesn't add detail, objects, extra things going on in the presented picture. Reducing resolution doesn't reduce detail, objects, or things on screen. Pixel Density is resolution. Supersampling isn't part of the discussion. PD should not impact the CPU workload. Regardless of PD/resolution, CPU should send the same frame to the GPU for rendering. This is the case for every other title. Something is off. Leave Steam Supersampling at native resolution. Reduce PD and you'll see the CPU present frames faster to the GPU. Do not confuse this with GPU frame rate. The point I'm trying to make visible here is that PD below 1.0 can remove a CPU bottleneck if you're willing to sacrifice the sharpness of your picture.

Ok, Let me break it down some more. Supersampling is irrelevant here. Game (CPU) interprets your place in time and space. Then, based on your settings it inserts detail and objects. Once it does this, it hands the frame and textures off to the renderer (GPU). On a reverb pro screen, with Pixel Density set to 1.0, the renderer says, "how many pixels do I fill? 9 million? OMG" and goes to work. It's hard on the GPU. The scene should not change based on resolution for the CPU. It's the same "picture" until it's handed off to the GPU for rendering. So why does a lower pixel density reduce workload on the CPU when it's the GPU that gets the relief?

Thank you. Yes. That was the point I was trying to make.

Glad my findings are helpful. It really doesn't make any sense. Maybe ED will investigate. It sucks losing a little crispness to the lower PD but if you're familiar with the cockpit beforehand even .7 is not so bad. Of note, I'm on a Ryzen 2600 at 4ghz, a 2080Super, and 32GB of RAM at 2933mhz. Cheers.

From my findings experimenting with my Reverb today... Try dropping your PD and watch your game become smoother. If you can settle on a smaller than 1.0 PD, you'll have a smoother VR experience. Crank SteamVR SS up a bit to compensate. In other titles when you increase pixel density you tax the GPU, not the CPU. The problem with increasing resolution is never how many frames can the CPU send to the GPU. It's can my GPU handle the increased pixel load? In DCS on OB, I can run max settings at .5 PD on my reverb pro... it's blocky and shimmery, even at 500% SS, but it's smooth. Every .1 towards 1.0 PD affects the CPU negatively until it becomes the bottleneck. Why is this happening? Draw demand isn't on the CPU and texture files aren't fluid in size. Strange. Anyways. I settled on .8 PD and have a smooth experience at 300% steam SS with medium settings and 2x msaa.

If anyone has a green spring they'd like to trade for cash that doesn't cost $30 usd to ship, please PM me.

Is there a way for the user to change the comm switch mapping for the Warthog? The manual says the advanced configuration guide has instructions, but then the guide says only the Cougar can be remapped. For instance, I've always used Comm Up as UHF and Comm Down and VHF in the F16. In the profile, it's Forward and Aft. Can i change this to preference? Thanks!

Warthog stick and throttle, TrackIR, 3x MFDs, SRS and Vaicom Pro

Mr Hollywood, if you get the time, would you do a video tutorial on the new SRS integration and how you envisioned it functioning and being utilized? Thanks!

Hello Mr. Fries! In addition to the hot mic causing issue above on the A10C, switching to the A-10C via the script will complete, but the MFDs will still switch profiles. LMFD gain will cycle like such for me instead of opening kneeboard: "Done. DCS A-10C Warthog Init Complete! DCS A-10C MFD Defaults (0,0): A-10C Warthog Config Complete! Combined Arms Config AWACS Mode Config DCS Standard (DX) Config Su-33 Flanker D for DCS Su-25A/T Frogfoot for DCS Combined Arms Config"

Are you using the new VSPX speech processing? That would explain why you didn't recognize the keyword collections and why it's not telling you anything is missing. Page 18 of the manual: "In the keywords editor, you will not get feedback on your VA profile with the TEST button (this may follow in a later plugin update). When in doubt if your VA profile is up-to-date, follow the FINISH steps (see page 37). "

Thank you for this! I have a small issue. Hopefully someone can advise. I've adjusted SRS and my Vaicom Pro mappings as per the manual. When i'm in the A10C, using the gunpac switch activates my comms, specifically tx2 and tx5. Sometimes temporarily. Other times they get stuck hotmic'd. Is this a known issue or something on my end? Thanks again!

Necro post, but this was my experience passing this mission today on open beta. Had to resort to guns after 1st sidewinder for the next SU25.