jalfrezi

Sorry, wrong campaign.

From your screenshots on the first page it definitely looks like it's your CPU that is the bottleneck, so I would look to drop Visibility to Medium/High and lower the Clutter/Grass setting <-- when I was carrying out testing I found this setting alone has a big hit on FPS even on the Tarawa - for no appreciable benefit other than some fake looking grass. I'd also ditch Process Lasso and re-enable HT, Windows 10 does a pretty good job of managing threads. You do seem to have a lot of things running in your screenshots - Chrome, Outlook, Office apps, etc - I'd close as much as you can before playing DCS, particularly web browsers as they're massive resource hogs, particularly RAM. In Nvidia control panel try turning on MFAA if you are using any anti-aliasing settings. EDIT: only change one or two settings as a time, then test DCS and see if it makes things better or worse, then move on to the next settings. Also, try and find a consistent DCS test scenario like a ramp start that has a lot of moving vehicles.

I went for this, it's not cheap but it's been working well for me, so far. Like the Monster Tech stuff there are plenty of options/accessories to customise it to how you would like it. EDIT: With the Next Level setup centre mount joystick extensions are limited to a maximum of 75-100mm in length due to the mounting point.

From further reading on Intel cores it looks like each physical core is split into two logical cores, so that two threads can be run at once. This suggests that running on 0, 2, 4, 6 will yield the same result as 1, 3, 5, 7, in that you are still running on four separate physical cores.

Is your processor showing as 8 or 16 cores? I'm surprised that running on the odd numbered cores showed no difference to the even numbered cores! Your results sort of confirm my own, in that Process Lasso didn't seem to make a noticeable difference to in-game performance.

If you're going to use CPU affinity then don't select odd numbered cores for the game, as these are the HT cores and only offer around 35% of the performance of the actual physical core (even numbered). I did try a similar approach myself for a while using Process Lasso, but found little to no improvement, so now just let Windows manage it, if you're still on Windows 7 it may offer an improvement.

I use an over the head headset which works fine, it's a little tight but providing the ear cups aren't too big you should be OK.

Nope, no helo on that mission just the truck, a helo would have made it more interesting. especially if it was a race against time to take it out!

I was getting this last night during my testing, once it happens even the menus are stuttering, as the GPU is being hammered. No idea why it happens, maybe the VRAM cache not clearing properly?

I spent yesterday evening tweaking my system as I was unhappy with the performance in certain situations, one in particular was tanking my FPS - a Tarawa night launch in the AV-8, it was dropping to as low as 15fps, by the end of the night I had managed to get this to around 30fps with 2xMSAA enabled. :) Frametimes at 90Hz are just too high even with motion reprojection as the GPU is still trying to hit 90fps, but failing dismally, and so it doubles up on frames to smooth things out. While this works well MSAA is still a complete no go as it's a frame rate killer at 90Hz, however without MSAA taxi lines and other objects are a jagged mess and while doubling up SS to 200% and enabling FXAA improves things quite a bit my 2080 Super is still struggling with frametimes at 90Hz. So, I dropped to 60Hz and sitting in the Hornet on the Stennis deck (daytime) I was hitting 55-60 fps with 2xMSAA enabled (also enabled MFAA in the Nvidia control panel, which improves the MSAA performance hit) and the jaggies are now greatly reduced. Other settings I reduced were: Water to medium Draw distance to medium (high has a big impact on fps) Clutter/grass to 0 (has a massive impact on fps even on the Tarawa - why?) Another big impact - up to 4ms frame time, is just turning on the MFDs and cockpit lighting in the AV-8 on the ground, I was pretty shocked at this but I guess there isn't much that can be done about it. Changing the cockpit res down to 512 saved about 1ms frametime. I just hope that the performance gains being touted for the new Nvidia cards are true, as we desperately need better performance in VR! NOTE:All of these tests were in a stationary aircraft (with the exceptions of the Tarawa at night), but there were still other aircraft moving around in the background.

I think it's a Reverb thing, my Reverb is also extremely bright in DCS but fine everywhere else.

Two snapviews to the rear - one left and one right are all that's needed. This can then be mapped to the left and right actions on a hat switch, like the VR Zoom modes. Come on ED, make it happen!

Just wanted to say thank you for a great campaign, really enjoyed it! My only observation, certainly not a criticism, is that some missions were a bit sparse - the mission with the crashed aircraft springs to mind, where you have to destroy a solitary truck (admittedly I missed with all four bombs and ended up taking it out with the gun!)

Have you tried fitting both springs on the rudder at the same time? It certainly made a difference on mine.

Sorry, no it's not OpenGL based I think it's DX11, I've been reading too much about XPlane! :pilotfly:

Yeah, I did see that on your graphs, not entirely sure why DCS on your monitor has a higher single core usage then when in VR, maybe there are already a few VR optimisations already in place - rendering each eye on a separate core perhaps? I'm pretty sure DCS does already run some processes/threads on other cores it's just the OpenGL graphics API is not particularly optimised for modern multi core CPUs, Vulkan should address this.

From what I've read on Vulkan it seems to suggest you'll only see a difference (maybe 10-15% FPS) if you're CPU bound by spreading the load more efficiently, if you're GPU bound then it will do little to improve your situation. The screenshots of the CPU load may not be related to the DCS.exe, I've noticed other VR related processes seem to suck up a lot of CPU such as the Steam VR Compositor.

In this instance he is actually right, Notepad++ is great for large scripts with its line numbering and colour coding but you don't NEED to use it, normal Notepad works just fine.

If you do make changes to the VR settings file just remember to restart the WMR portal as well as Steam VR for the changes to take effect.

I'm trying to get an Arduino FA-18 panel working that I purchased but I'm also having the same problem as Electriflier with the installation, the table isn't showing on the webpage and adding the suggested code to the Export.lua in Saved Games doesn't work either? Any suggestions? EDIT: Managed to get it working in the end, I had a couple of conflicts - one with DCS Flight Panels and the other was another Arduino based switch box.

Have you tried using FpsVR to see where your bottleneck is? It's available on the Steam store for around $4, it's an invaluable tool for seeing whether your framerate issues lie with the CPU or GPU.

They could have a waiting list with people paying a non-refundable deposit, at least then they could predict wait times. I guess you guys would be happy parting with a deposit and then being added to a waiting list? Has anyone tried contacting them to suggest this? At the end of the day people will be pissed whatever they do - as people don't like waiting once they've paid for something and don't like being unable to purchase something when they want it. Simple fact is they can't meet demand and unless they ramp up production the situation isn't going to change.

I guess there are reasons why they haven't scaled up their manufacturing to meet demand, maybe they just want to keep a steady flow of orders? In any case, if they allowed new orders even when they were out of stock we'd probably be looking at a 6-12 month waiting time, as opposed to a 6-12 week one - I don't think people would be happy with that scenario either, just look at the problems with Realteus, WinWing, etc....

Nice little PSU calculator - https://outervision.com/power-supply-calculator I used this when I specced up my new PC, I too ended up going a with an 850W PSU.

Some controllers seem to overlap it's not a VPC issue, I've had problems with my XBox One pad overlapping controls with my Warthog throttle and Logitech throttle quadrants. I'm not sure there's much you can do other than to disable the other devices when you don't need them. I use this tool and have created a batch file to disable and enable the devices as I need them - https://www.nirsoft.net/utils/usb_devices_view.html