Number481

You make a good point about the FPS cap in graphics.lua... anyone with a 5800x or better should be setting that higher, especially if benching at 1080p. Or this track file needs to be made far more complex... Figured I'd give this a go on my new 7950x3d (w/ 4090) - High preset, various resolutions, all full-screen - Tacview installed but disabled Here's the full breakdown at 1080p null Here's a comparison at the three indicated resolutions. I'm a bit skeptical of the 4K test. My monitor is only 1440p, but the game should still be trying to render at 2160p.. the results are within the margin of error of being identical to the 1440p results however.... null And, if you're interested in how Tacview being enabled affects things... (I tested with it uninstalled and saw no difference from disabled)

Have you tried with safe mode enabled in OXRTK? This will force %100 default settings. Just to ensure that any potentially bad or corrupted settings aren't applied

Come over to the Varjo discord.. we'll get you sorted in a jiffy. The headset is everything you think it should be and the issues you have are easily sortable. https://discord.com/invite/Rk3CU6hTav

I was curious, too. This is actually straight from the Varjo SDK documentation. My pea-brain doesn't really understand all this, but I don't think they are implying you'd get better performance by submitting the quad view in a generic way (aka, how the native OpenXR implementation is currently doing it), rather, if you were implementing foveated rendering via the SDK.

Yeah, I'm %99 sure it will work if you play through without VA running. Vaicom does some wonky stuff internally to do its magic, and it ends up interfering with some mission script triggers. I had issues with this exact mission and a couple others from the campaign. I've also had it happen in some other campaigns too. Seems mostly to be on the "cut away" type triggers, including wingmen that should be kissing off in the pattern.

Somewhat random, but possibly related question... Are you by chance running VoiceAttack with Vaicom?

I have at least 10 tacview files on my drive of me failing, every single time to even come close to evading this f&58King Igla... So, I set up a quick mission with me and a single manpad to figure out what it would take to reliably decoy the missile. 20 Flares.. That's what it takes. Set up your CM to dump flares qty 10, repeat 2x, 1 second interval. That should get the SAM off your ass so you can, as Ekim so eloquently put it, JDAM the "..$ing guy.

Phew.. that was close.... Also.. holy $#!T.. now I need to upgrade my CPU

uhhh... 420... I need more coffee

Was also able to get a Gigabyte OC 4090 on NewEgg last week. Today is the day we find out how accurate the published specs for different GPUs are on TechPowerUp... The Strix 3090 is 319mm length, the Gigabyte OC 4090 comes in at 340mm... I have just about 22-23mm of space between my 3090 and my front fans/AIO. My case is big, but I have a massive Arctic Freezer 480mm 420mm radiator in the front.. I may be ordering a new case or a new 480mm 420mm AIO that isn't as thick as the Arctic Freezer..

There is a "VR preferences" file that is created in your save games folder that you need to delete in order to run the tool again. Unsure what the file name might be as I don't use the tool since I am running with OpenComposite/OpenXR which doesn't need the correction.

FYI, after many, many tests, I have been able to isolate the issue to Vaicom Pro (community version). If I have VoiceAttack running (even if I don't make any calls to it), Sting will not break. If I leave VoiceAttack shut down, Sting breaks without issue. Theres a new community version of Vaicom that was just released which has the following in the release notes: "- renamed timer to dev_timer in luas to avoid clashes with other mods" I'll give the new version a try and report back. It's unlikely that will resolve it, but worth a shot none the less.

Interesting, Thanks. I run a few pretty basic mods like custom auto start script and countermeasure setup and OpenComposite/OpenXR for VR as well as Vaicom/VoiceAttack, which I guess is technically a "mod". Will try pure vanilla and let you know what I find. Thanks

After joining up with Sting flight at WP2, and after Sting has been told by Strike to break for IP, they never actually break off. Just continue to follow around in a (wide) formation with Devil flight. Also, this is the only mission I recall where I didn't get a "joining up" call from the flight we are grouping with at a given waypoint. Not sure if thats just not in this mission or if it is a symptom. Also not sure if this is just the AI script trigger issue that many of the campaigns were facing (which I thought was fixed in the last OB update)

Just finished up mission 4. When RTB, on the overhead break pass, I got a call from tower clearing me to parking, then the "bravo zulu" message for mission success and then the onscreen "you can close the mission" prompt followed by the ending music track. I continued my landing as normal, parked and ended the mission and everything proceeded fine. Not sure what would have happened if I had quit while still in the pattern. Just thought I'd let you know.

no idea.. I wrote the post out on the virpil forum, on my phone. Copied/pasted from that to this forum, on my phone.

FWIW, I just finished lubing up my CM3 and it does make a world of difference and is well worth the effort. a couple of notes.. 1- the arm bolt is not, in fact, 14 spider legs as suggested in the tutorial :). It’s a 7/32”. Though I understand that will still be a one-off size for those who live in parts of the world where we don’t all have both metric and standard tools. 2 - if you loosen the 4 top bolts as well as the two large-ish pan head screwed on the top, then the top plate will be able to easily pull away from the cam assemblies and make removing the clutches super simple. 3 - less is more with the 767a. If you think there’s still some on there, try to wipe it off. I didn’t really have an issue with the sawtooth stiction when I was using the WarBrd grip w/200mm extension. The tiniest amount of tension on the clutches was sufficient to hold the stick in place in any position. The sawtooth was there, but barely noticeable. Then I upgraded to the Alpha Prime, which is probably twice as heavy as the WarBrd, requiring a bit more friction on the clutches which made the sawtooth a problem. It feels really good now. Though with that heavy ass grip, it requires a really tight clutch in order to not slowly fall over once you get too far away from center. But even with the clutch really tight, it has a good feel and I don’t notice the sawtooth issue. Now I have about 49.8g of nyogel that I don’t know what to do with. Haha.

Looks pretty sweet with the dampening. But I'm only a buyer if it can be de-sprung and has an adjustable clutch for helicopter use. (Really hoping for this capability)

nullI won't argue with your decision to stick with what works for you.. there is certainly something to be said for keeping it simple. It can become tiring constantly tweaking and tuning and forgetting to actually have fun. I will just say however, that you don't even need to use the OpenXR Toolkit. Simply using the OpenComposite DLL is enough to gain some level of performance over SteamVR. This is mostly due to removing a redundant piece of the pipeline (steamVR compositor).. these are two back to back tests, "Free Flight" instant action, Marianas, Huey.. similar FPS, but the smoothness provided by the (far) better %1 and %0.1 lows is noticeable. I'm not trying to change your mind, just stating that OpenXR Toolkit and all its possible tweaking/tuning aren't required to use OpenXR via OpenComposite.

Whether you adjust the setting above or below %100, it is doing the same thing. The initial implementation of the NIS scaler used a decreasing percentage to indicate "application rendering resolution over target display resolution" Then, at the request of users and to be more inline with how other games implement NIS/FSR, Matt also allowed values above %100, indicating "target display resolution over application rendering resolution" So, in effect, as said in the documentation, %50 is the same as %200, but they are referring to opposite relationships between target display and application resolutions. Stick with a direction that makes sense to you, and adjust it down (or up) from %100 until you find a spot that you are happy with both image quality and performance gain. (I am currently using FSR at %90) /m