slughead

You multiply, not add. The headset will provide the application with a resolution in pixels, i.e., the headset's native resolution multiplied by the headset PD. The application takes that and multiplies it by the application PD.

Oh right. I missed that.

I don't use QFVR/DFR. I use Virtual Desktop at Godlike and bump the render resolution further using PD in DCS, as I can't increase it further in Virtual Desktop. It doesn't matter where you do it as long as you give it due consideration. Does it? I thought it was fixed foveated rendering in the OpenXR Toolkit.

1.0 overall. 2 x 0.5 = 1.0

Hmm. That's an equivalent PD of 1.0 overall. What's the render resolution in your dcs.log file?

I use a Quest Pro which has eye tracking and edge-to-edge clarity. FFR would be a visual retrograde for me.

I have the same cpu/GPU as you. How hard have you pushed your PD/resolution?

If you have maximised the DCS options which loads up the CPU but your rig is good enough not to notice a drop in fps, running quad views over densely populated areas will affect performance as it pushes your cpu load even harder by drawing the image four times. This is why I don’t use quad views anymore.

I am aware that some fellow pilots are struggling to log onto the ED Forum to message me their orders. To remedy this, you can also email me at team.slughead @ outlook.com (remove the spaces around the @ symbol).

From the Virtual Desktop discord...

Important note about measuring your fingers. Hey fellow pilots! If you use an adjustable plastic ring gauge to measure your fingers, please do not measure the gauge with a ruler, as it will provide the wrong measurement. Please provide the number or letters on the indicator, e.g., US 12 (left index finger), US 13 (right index finger), Z (left index finger), or Z1 (right index finger) etc. Ideally, use metal ring gauges or visit a jeweller. It's rare for both left and right fingers to be the same ring size, so be sure to measure both.

Remember that Slugmouse doesn’t perform any hand tracking; it just emulates mouse or joystick button clicks. Your headset or Leap Motion Controller performs the hand tracking. So it’s really a function of your headset whether it can track hands in low light levels.

Hey Hadeda! You can do a couple of things to help with this. The first option is to use HTCC's hibernate mode to temporarily deactivate OpenXR hand tracking. To reactivate OpenXR hand tracking, hold one hand near the top of your field of view until you hear the beeps again. It takes a bit of practice. The other option I prefer is to reduce HTCC's wake and action field of view. By doing this, you can look straight ahead or away from your hand, reach for the mouse, and the normal mouse will take precedence. When you let go of the mouse and bring your hand back into HTCC's field of view the hands will take precedence. I have attached my htcc registry settings if you would like to try them. However, they are set for preferences and airframe which is usually fixed wing fighters with no overhead switches. For helos you may beed to change the settings to suit your needs. You may wish to backup your HTCC registry settings before installing mine. htcc.reg More details about the HTCC registry settings can be found here: Registry Settings | HTCC It's best to use the above methods to deactivate hand tracking and use the normal mouse for menus. For the comms menu, I map comms functions to the comms button on my Thrustmaster Viper HOTAS which gives me coms open, up down, exit, back etc. This is partly a limitation of the mouse implementation of DCS when using"Emulated touch screen or tablet" mode in HTCC. You could try the "Emulated Oculus Touch Controller" mode although Fred doesn't recommed that.

I'm glad you're up and running again. Perhaps you chose the wrong configuration when you installed Reshade. Maybe you should try uninstalling it and then installing it again, following my guide.

Personally, I think there needs to be work on the software side rather than developers relying on hardware to get them out of a hole. I don’t think that current CPUs are being utilised fully, but hey, I’m not the one with the source code so who am I to say. We’re still awaiting Vulcan. I can’t see how a 5090 is going to make things faster without improvement on the software/CPU side. I am more than happy to be wrong though.

I get the picture. Mine are all maxed out. Hence running QVFR over cities gives a drop on FPS whereas you may not notice.

What are your DCS settings? Lowering things like textures, civilian traffic, draw distance (can’t remember the exact name) is going to reduce the load on the CPU and give more headroom and potentially more fps.

£100 plus packing and shipping costs.

It has been considered. I have no plans to incorporate a strap into the design.

Yes. It has to draw everything 4 times instead of twice. So if you have a large number of objects, such as a city, the CPU is loaded harder. Give it a try over Dubai or Syria cities. If you already dial down the settings then you may not notice.

It can also give less fps over areas of a large number of objects such as cities. For me, I no longer use it for this reason.

@TFS is a helo pilot. I'm not sure if he flies the Apache, though.

Is there a fault with email notifications from the forum? I haven't received any in the last few days for comments or private messages. I have also been told by people trying to contact me via the forum that they are not receiving activation emails when trying to join the forum.

Current orders are shipping out on Tuesday morning! That's a one-day turnaround for one order and two days (I need a day off now and then) for another.