slughead

I’d look/ask on the reshade discord server. You’ll get help directly from the developer.

I suggest you go to the reshade discord server for reshade support. https://discord.com/invite/PrwndfH

Works for me. What headset are you using?

You need to set a key to toggle it on and off on the reshade settings. It’s not set by default.

Hey, fellow pilots! I'm working on a version of the Slugmouse called the Slugpad. It's essentially the same product but will provide gamepad button presses instead of mouse clicks. This would allow the buttons to be mapped to virtually anything. For example, the device can be seen by the Open Kneeboard (which doesn't support mice), which you can use to switch pages and tabs. You could also map the gamepad buttons (DX input) to mouse clicks in DCS. It may not support fast repeat, i.e. when you hold down the up or down button, it may not repeat quicker to emulate mouse wheel scrolling. You can't have it all, I guess. So, if you want something to flip pages in Open Kneeboard or just ten extra buttons, Slugpad is for you!

Win11 is not the cause of your problem. I'd appreciate it if you could start a new topic/thread about your connection/performance issues as this discussion is straying off topic of performance gain through FOV adjustment.

Hey Tomcat! I have experienced the issues you describe, although they have nothing to do with changing the FOV or the render resolution. What you are experiencing is a high latency caused by either: Your graphics card isn't powerful enough for the HEVC/H.265 encoder. The HEVC encoder's bit rate is set too high. Let VD set it automatically. On the VD settings screen, hit the reset button. You are using a shared WiFi router. Ideally, you would have a dedicated router for your headset only, with no other WiFi devices using it, so that your headset has the maximum bandwidth available. Your router is not configured or capable of WiFi 6E. H.264 is less demanding than HEVC/H.265, which explains why you have fewer issues with that encoder with your graphics card. Additionally, locking half the frame rate doubles the frame time, giving your system more time to generate and send frames to the headset. If you solve your latency issues, you may not need to permanently run your headset in ASW/SSW. Other things to check: RAM set to XMP speed Your CPU is not thermal throttling and thus slowing down Your PCIe bus speed matches that of your graphics card - this can choke a system considerably

I have used QVFR. However, it can cause poor performance, especially when flying over cities with fast jets. Since DLSS was introduced, I no longer need to use QVFR. Now I have a clear image everywhere, whereas, with QVFR, there was always a split second where you looked that it would not be good until it caught up. But again, this post isn't about QVFR. It's about reducing the FOV to gain performance, as we used to do with the Meta Link, but using Virtual Desktop. QVFR doesn't allow you to reduce the FOV image size; it only allows you to adjust the resolution of the periphery and central region of the image. Here is the information about performance degradation with QVFR.

Check out this thread. Some of us have it working.

But there is no hand-tracking / gesture control in the Quest PCVR lobby. So, if you don't use your Quest controllers like me, VD is the better experience. Anyway, this isn't about the Quest PCVR lobby but a performance boost for those who use Virtual Desktop.

I recently switched from Meta Link to Virtual Desktop but haven't been entirely happy with the performance until now. My PC is no slouch of a machine: Intel i9-13900k @ 5GHz Asus Nvidia 4090 64GB RAM @ XMP setting NVMe drive for Windows NVMe drive for DCS Windows 11 Pro Quest Pro headset Meta Link and DCS Configuration: Meta Link x1.0 @ 72Hz. DCS PD 1.5 Most, if not all, settings in DCS are maxed out (the configuration can be seen in the attached screenshots). DLSS enabled. Performance Test: I judged performance by flying the instant action, Persian Gulf, ready on-ramp mission with an F-16. It's not a scientific test, but it was a rough guide to see if a patch or driver update had broken something. The goal of the test is to remain out of ASW. Take off, climb to 1200ft. Turn right to the coast, maintaining speed at 450-500kts. When the Burj Khalifa building is almost at my 3 o'clock, pull hard right towards it. Then, I took another hard right again as I passed the building. A well-performing system would make both turns and maintain 72 fps, staying out of ASW. On the switch to VD, my settings were: Godlike resoluton @ 72Hz. DCS settings are the same except for PD. Any PD over 1.0 would cause a drop to ASW with the above test flight on the hard turns. The image quality was identical/similar, but I was unhappy with the performance. I realised that with the Meta Link, I had been using Oculus Tool Tray and had set the FOV to 90%, as some of us found that this gave a performance boost without affecting image quality. Effectively, it reduced the image size that was drawn but just about within the FOV, which was limited by the frame of the lenses. Any more than 90%, and you could start to see the edge of the image as a black rectangle. When I turned off the 90% FOV in Meta Link, the performance was similar to Virtual Desktop. So, to get the performance in VD that I had with Meta Link, I started making some adjustments using the OpenXR Toolkit. OpenXR Toolkit has a FOV setting in the System tab. I set that to 90% but still had lower performance. Then, I looked at the render resolution in the dcs.log and found that it hadn't changed despite a reduced FOV. To change this, I adjusted the display resolution, which was also in the System tab of OpenXR Toolkit. I lowered it to match the resolution created with Meta Link at a FOV of 90% and PD of 1.5. For me, that was 2904x3041. With that change, the performance was back, and I am now fully converted to Virtual Desktop. Yes, Virtual Desktop is more expensive because it requires a dedicated gaming router. You can get cheap ones and expensive ones. Either appears to work. Be sure to pick one from the list of tested routers. Yes, the bit rate is lower with VD. However, that's not an issue if you use one of the newer, more efficient encoders. I am using the HEVC 10-bit encoder, and I can't see a difference compared to H.264 @ 500 Mbps. Yes, Meta Link can run up to 960Mbps (not without distorting the audio via the link). Some say they notice a difference, but I don't. For me, Virtual Desktop offers the peace of mind that Meta won't break DCS by changing their implementation of OpenXR on the Meta Link. It also allows you to see and interact with the Windows desktop, unlike Meta Link, where you have to peek under the headset to launch DCS. All in all, it is a better experience. To top it off, I am now wireless, which makes a huge difference. No more cable tethered to the PC! To maintain the charge of the headset, I use a power bank battery attached to a belt or in my pocket. Yes, there is a cable. I barely notice it. In summary, if you want to get the boost you had with 90% FOV using Meta Link: Find your DCS render resolution for your setup with Meta Link from the dcs.log file. If you are running DLSS, look for "DLSS successfully initialised". Mine is now: "DLSS successfully initialised, 1936x2032 -> 2904x3044". Set the FOV to 90% in OpenXR Toolkit. Adjust the "Display resolution (per eye)" in OpenXR ToolKit to match your old render resolution. Enjoy the performance boost. If you want a sharper image, you must sacrifice high CPU options such as shadows for higher resolution/increased PD.

I'm guessing the latest updates we were teased with back in February haven't been released. Is Barthek ok?

I've not seen anything official on this. I have seen that some analysts concluded that the headsets are sold at a loss, but nothing official from Meta. Anyway, matters not.

What makes you think they’re selling at a loss? They are the market leader by a long shot so they’re able to sell at a lower margin yet maintain their revenue target.

And that’s worth a grand / double the cost of the Quest 3?

LCD panels and fresnel lenses. The Quest 3 is better and significantly cheaper. I can't see this one being around for long.

Exactly. I have no intention of upgrading my VR headset (Quest Pro) until PC hardware or perhaps the software improves enough to run current VR headsets to the best of their capability. Anything with higher resolution is likely a waste at this time.

All orders have been shipped! Six this week are winging their way around the world! I think I'm going to get a free weekend! Enjoy your Slugmice, fellow pilots!

If I had the room, I would build a replica cockpit and use mixed reality to see and interact with the physical world and still fly in VR. The only problem with that is you’re tied to one airframe unless you have the space to have multiple cockpits.

The irony of this is that I fly in VR. So I never get to see the LEDs in action.

Correct as per the instructions in the first post of this thread.

If I were you, I'd use HTCC (hand-tracked cockpit clicking) by Fred Emmott. You can get it here (Home | HTCC (fredemmott.com) along with the instructions. Once you've done that and find that pinch clicking is not particularly reliable, go here (https://forum.dcs.world/topic/344857-slugmouse-a-mouse-button-emulator-for-hand-tracked-cockpit-clicking/) for a finger-mounted mouse button emulator that you use in conjunction with HTCC.

Hey Simba! This one works well and has a good range. I tested it out to 5 metres. It was plugged into the top of a PC. Plugging into the back of a PC may restrict range or connection reliability due to the amount of metal between the dongle and the Slugmouse. Tested with Windows 11. TP-Link Nano USB Bluetooth 5.0 Adapter for Multiple Devices, Long Range Bluetooth Dongle/Receiver for Windows 10/8.1/7, Plug and Play (UB5A) : Amazon.co.uk: Computers & Accessories All the best, Slughead

Any luck with this?

It will if you are using Virtual Desktop.