Glide
-
Posts
1198 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Posts posted by Glide
-
-
Is there something up with the clouds? The lighting on the clouds changes every couple of seconds. I had my mission starting at 05:50. Clouds were set to Light Scattered 2. Default date.
-
1
-
-
Sorry, I can't recall which GPU you have, but if you are on Nvidia, try setting Negative LOD Bias to Clamp in the control panel.
-
This is a good video explaining what impacts the CPU in game. Some multiplayer servers have a lot going on which impacts the ability of the CPU to keep up. I think you are good with your 11gen. It's not you, it's the server.
-
1
-
-
I spend a lot of time chasing Ace-level Mig-29's around in the sim, so that's my reference. On paper, the Mig is the better fighter, and that's my experience as well. I can out turn them for a short while, but I can't catch them until they make a mistake (Ace level doesn't seem to make mistakes) or they run low on fuel and head for the nearest airbase or faceplant. It would be a lot more fun if the Viper could keep up to them, but I think the numbers are pretty close.
-
1
-
-
These are mine for the 3080Ti, i7 11gen. There's two ways to go, MR or non-MR. Motion Reprojection is not perfect yet, but I am sure you will want to try it.
Set the headset to maximum quality and highest resolution in WMR. I run mine at 60hz because I've been using 60hz monitors for years, and I don't notice any flicker. The nice thing about 60hz is you can maintain 60fps, whereas maintaining 90fps in a dogfight or multiplayer is still out of reach. My game settings below work for both MR and non-MR.
non-MR settings:
Set OpenXR tools to 100% custom resolution, MR disabled, Prefer Frame Rate over Latency.
No settings from Nvidia Control Panel are required.
In OpenXR toolkit, if you want to see 60fps, add 75-80% scaling, either NIS or FSR. Without this I get more than 30fps (the bare minimum) but less than 60fps. You can add some Sharpening if you like, but that's all that's really required from OXRTK.
MR settings:
Set OpenXR tools to 50% custom resolution, MR enabled with best frame rate, Prefer Frame Rate over Latency.
No NCP settings required.
In OpenXR toolkit, you don't need any scaling because you took the load off the graphics pipeline with the 50% OXR resolution. You may want to add sharpening to your taste.
With MR, it's critical you don't fall below the FPS target or you will get lots of screen artifacts. I get a solid 60fps in a busy dogfight with these settings.
-
2
-
-
Try these:
G2 60hz, best visual quality, highest resolution
OpenXR Tools, custom resolution 50%, Motion Reprojection enabled best frame rate, Prefer Frame Rate over Latency
Game settings: MSAA off, Anisotropic Filtering off, Visibility Range Low
OpenXR toolkit, nothing but a little NIS Sharpening, say 25%.
Nothing in Nvidia control panel.
I get a solid 60fps with this, and it is very smooth.
I hope this helps.
-
It turns out the answer was there all along. If you go Dogfight Mode, TMS up twice to get HMD boresight mode (the egg), TMS up breaks the lock and returns to HMD boresight mode (the egg) with radar emitting. So, if you lock up a Blue force jet by mistake, just TMS up to break lock, put the egg on a Redfor jet, and you get a lock. One click.
-
Unfortunately, you can't see the fuel flow or the RPM indicator, so you can't know what the pilot is doing with the throttle.
-
1
-
-
I did not mean to imply it was incorrect. I just wanted a few less clicks during a busy dogfight.
-
I see. It's not so much "TMS reject". It's more like "TMS return to default" to break the lock, and the system goes back to default state of non-radiating. If you imagine it like a state diagram, I thought there would be a way to just return to the previous state of "radiating but not locked". "TMS reject" is the fictional command. You are not "rejecting" ; you are "resetting". Thanks for the detailed feedback.
-
You can identify the bad stick by removing one, testing, and then swaping the one tested for the other (2 stick method). However, you replace them in pairs, so if you have 4 sticks read the mobo manual for which slots go together, then test two at a time until you find the bad pair. If you only have two sticks it doesn't really matter which one is bad because you will have to order a new pair. You can run the computer with just one stick until the new pair arrives. I'm not sure if 3 sticks work though. (read the mobo manual to be sure) If you have 4 sticks, find the bad pair, order a new pair, and run with two sticks until the memory arrives.
BTW, I had RGB memory (with the LEDs), and I went to non-RGB memory. I can't say if the LEDs where a factor in the memory failure, but the non-LED type works just fine.
-
Have you tested your memory with something like Memtest86+? I had bad memory on my machine for who knows how long. The computer will run fine until it tries to access the bad location, and it may just be luck that the other sims haven't hit that location.
-
Training for the big show.
-
Currently, if you wish to reject a locked target you press TMS down. This rejects the target and puts the ACM mode in vertical scan mode. This requires another action to put the ACM mode back into boresight mode. It would be ideal if you could reject a locked target and stay in boresight mode. The hat switch is 5-way, so TMS could be mapped to fore, aft, port, starboard, and down. For those without a 5-way switch, they could map a key to TMS reject.
-
6 hours ago, SKIPPY 7-7 said:
Had a AI Mig-21 dominate the rate fight in my F-16.
They will win every time. Don't be fooled.
-
I still see the wobble on the leading edges of the wings of the TF-51D, depending on what kind of textures are behind the wings.
-
11 minutes ago, minimi66 said:
Can't think what else it could be?
You will always have the ground stutter with those settings. Trust me. I didn't test clouds, since I turn them off. Vis Range LOW, AF off, AA, off, terrain shadows OFF. The issue is in the graphics pipeline.
-
1 minute ago, DirtyMike0330 said:
Your suggestions are worthless
Whatever. Try just the game settings then. Vis Range = Low, Terrain shadows off, AA off, AF off.
-
19 minutes ago, minimi66 said:
Please can you fully explain your experience with OpenXR including the tool kit etc
I assume you have DCS set up to launch with OpenXR using the shortcut parameters. I have my G2 set up for maximum quality, and see below for WMR settings. OpenXR Toolkit should be at defaults for this exercise, but you can use the excellent FPS counter on Advanced. Your NCP settings for DCS should be restored to defaults. As for the Quest Pro, try to match my setup if you can. The resolution is already lower than my G2 at 50%. Set your game settings just like the screenshot, and hop into the TF51D on the Caucasus map. Report results.
-
1 hour ago, DirtyMike0330 said:
That thread is a snake-oil filled mess and mostly you responding to yourself.
And thanks to your trolling, the OP won't even try them. So, I guess we'll never know.
-
Try my settings here:
Basically, 50% OpenXR custom resolution, no Motion Reprojection, no NCP settings, no OpenXR Toolkit settings, and the game settings I have posted in that link. They may not be the best looking settings, but you will know if you can achieve 90fps with perfectly smooth ground motion. They look just fine to me.
-
On 4/7/2023 at 1:41 PM, edmuss said:
Rotor wobble will be gone soon
Still there in this patch.
-
Yes, the settings I show are not the best looking, but you can use them to demonstrate to yourself that your system can achieve perfectly smooth 90fps with the G2. The rest is up to ED to optimize the new graphics pipeline.
-
You should try my settings here:
Recommended settings for Reverb G2 v2
in Virtual Reality
Posted · Edited by Glide
Assuming you have OpenXR Toolkit installed, you can add sharpness with NIS, FSR or CAS. You can leave the size at 100% and just adjust Sharpening to taste.
Another approach is to set OpenXR Custom Resolution back to 100%, and set the Size in OpenXR Toolkit to 50% to help stay above 60fps. NIS and FSR will render at 50%, then scale up to 100%. I'm not too sure how Continuous Adaptive Sharpening (CAS) works, but you can experiment with it.
Personally, I prefer the non-MR approach because if MR works it's great, but if the frame rate drops below 60 it's really ugly. If the FPS fluctuates with the non-MR approach, you don't get any screen artifacts.
Try adding MSAA x2 and Anisotropic Filtering x16 to see if your system can handle it. This will sharpen it up and reduce the aliasing.