wheelie

Correct 1.1.3 is the latest but it looks washed out, over saturated, over exposed and no matter what i do it just doesnt look right on my G2 so i rolled it back to the best version i've used so far which is 1.0.5. Also with regards to when DCS is updated, the install will move the modified files into a backup location so simply open the backup location and copy over the folders in that backup location and you're back in business in seconds without having to faff around with installations again. E.g. after the update on the 8th you should have a backup folder with the date created/updated. Now open the folder, in my case it was _backup.001 and copy the contents of the folder into the "DCS World OpenBeta" folder and choose Y to overwrite. Back in business immediately.

I have mine set like this and now use 1.0.5 of the OpenXR toolkit as the colours are far, far better. I also now have Saturation to Selective, RED @ 90, Green @100 and Blue @ 100.

Thats a good one and one I havent come across personally although the F14 and F16 do hit VR users the hardest especially in the cockpit. It reads like a refresh rate kinda glitch, i'd go to NVidia control panel, 3d settings and set VSYNC to Fast as this reduces tearing when moving your eyes across a scene, perhaps this would help.

I found the same issue, now when i save the mapping file i remove everything after the dot. E.g. F16_Stick.diff.lua I remove ".diff.lua" and it saves the file without creating another. A workaround for the moment.

I do find it wierd that we all have a different'ish experience even with comparable machines. What i have found is versions of drivers can make a difference, XMP memory settings, whats running in the background e.g. bloody MS defender, NVIDIA drivers (sometimes 5/10% diff), OpenXR companion version etc etc. While i doubt we will come to a concensus on this its great that we (mostly) seem to be going in the right direction with better FPS and better image quality.

Interesting corb the only time i've seen anything like that was when i was using NIS as the scaler and had an issue with reshade. I changed it to FSR and reinstalled reshade to get around it, it was also accompanied by a weird "scooby do" effect on the lenses. Do you have the openvr_mod.cfg file in your bin folder by any chance? If so change the line to: "useNIS": false, "renderScale": 0.77, "sharpness": 0/9, May be worth also changing "applyMIPBias": true, to false. Not sure why these would still play a part but if its there either change it or rename it so it's not used. I noticed that it also cleans up when you're looking away from the rotors. One other thought mate you don't have HAG on do you?

I've not actually as I am happy to lose a bit of FPS for more clarity and screeen eye candy, i'll give it a go though. Thankfully i don't have any issues at all with FPS now.

Try changing Vsync to fast in Nvidia CP 3d settings and leave it off in game.

Interesting I dont get the ghosting and dont use MR at all. Rotoblades are also no problem at all. I have VSYNC set to FAST in Nvidia CP 3d settings which helps with any tearing. I have PD @1.0 and OpenXR render scale at 100% and use the following settings. I also use the OpenXR runtime and NOT the steamVR runtime. i9 9900k all cores @5ghz EVGA 3090 FTW3 Ultra Gaming M.2 drives and 64GB corsair vengeance @3200 OCXR_WMR_ACC_v0.6.3 OpenXR toolkit Beta-3 v1.0.4 (newer version drops my FPS) I also use FSR instead of NIS as it's a far better image on my G2 rev2. Hope any of this helps.

It was already there as an option mate, i just changed it to custom. I think however it only shows when you change the menu, show expert settings to yes as below. Had similar tearing, try NVIDIA control panel, 3d settings and setting Vsync to Fast. Worked for me.

Indeed and I can appreciate that also mate, I just made a copy of the "bin" folder and stuck it on another drive, did my testing and when i want to use steamVR i copy the bin folder back.

I've recently started using this and am so far really impressed but found the colours completely washed out at the begining until i dug a little deaper and found the "Appearance Tab" changed Saturation from Global to Selective and changed the individual colour settings. Here's whats working for me at the moment. 90fps in Nevada with the Harrier at 10k and 55/60 over the strip at low level. Now i just need to get the OBS plugin to work...

Given the fixes in the recent update i can see why this would be on the back burner, hopefully they'll get around to it at some point as cinematics are proving a challenge now.

+1 unfortunately

Nice one mate ill check that out.

Hmm ive not had any success with this, so how are you transmitting the SPI over datalink? If I create a SPI from an overfly mark point and select transmit as on, on the right MFD and press transmit over VHF on my throttle all i see is the comms menu appear and no flash of the transmit icon on the MFD. Which keybind are you using to transmit from fighter to fighter?

I suspect its a different effect in VR David as its worked a treat for me and is replicatable outside of VR.

Thats what it is, i dropped my water setting from high to medium and it sprang back up so Caucuses F18 free flight upto 121fps (4k) and Syria free flight 89-103fps (4k). I suppose I could just keep it all maxed out but its important we know why the FPS drops potentially on each release so we can accomodate it, without this understanding 3 release/patches down the line it could be another 40/50fps down otherwise. At last knowing the cause so we can make an informed choice in the local settings. I'm pinning my hopes on better CPU redistributed instructions with vulcan and really wish they could take advantage of the Nvidia 30xx series cards but thats for the future I expect. @BIGNEWYCould you feed this back to the coders please chap? Many thanks. Big Thanks to @jpdesvals nicely done. Pyroscot. www.twitch.tv/pyroscot

Done that and no difference mate.

Well unfortunately its the same for me as well, 15-21fps drop and the only change on my end has been the update. System: i9-9900k @5ghz all cores, EVGA 3090 FTW3 Ultra Gaming 24gb, Corsair Vengeance 64gb RAM, dedicated M.2 drives for OS, Temp and Game. I play in 4k with everything pretty much maxed out and fly the same test before and after every patch. Something has definately affected us all with this patch and hopefully they can sort it. Pyroscot

Night Mission on Hoggit GAW hunting SAM's, seems a bit breezy

I think i've found out why, its being caused by the winwing panels I have attached, if I disconnect I can now use it in both stable and beta. So now need to figure out what is conflicting with the TDC slew on the warthog... Deep joy. Thanks for checking and advising chap, much appreciated.

Issue : Moving the TDC or simply manoeuvring render the radar beam stuck on attack radar Version: DCS 2.5.6.61527.3 Open Beta When in the Fa18 and select attack radar on ANY MFD, with MFD as SOI the TDC slew will not move on the MFD, the attack radar is frozen and will not respond. This happens in single player (not tested in MP) in specific missions I have created, training and free flight. The TDC slew works absolutely fine on the SA page in any MFD. Thrustmaster warthog HOTAS Windows 10 I tested the same action in the current working stable version of DCS without issue. The DIFF file for the HOTAS has been deleted, recreated and copied over from the current working stable version all the no avail. cause: I think i've found out why, its being caused by the winwing panels I have attached, if I disconnect I can now use it in both stable and beta. So now need to figure out what is conflicting with the TDC slew on the warthog... Winwing combat panel has a radar dial, this needs to be either standby or OPR for the TDC to work ... makes sense really. Sorted