ppokit

Hi, I had the same problem with re-installing an older version of VB. VB leaves behind a few files when you un-install it that upsets the roll backed version of VB. These have to be manually removed before installing an older version of VB. I used an app called "Everything" as recommended by an Aero user on Discord to find them and it worked well.

It's worth it. The vertical FOV reduction is soon gotten used to. Everything else is superior. Varjo Foveated Rendering is a game changer (literally).

Hi all. Sometime ago I asked this question to @f4l0 in the SimShaker Discord: Hi there, was wondering if there are any plans to add an effect for the Mirage F1 compressor stall? @f4l0 replied: Sounds interesting. But I need to find a way to "extract" the data for the compressor stall... I was wondering if @fausete (and/or the Aerges team) were able to help? The SimShaker profile for the Mirage F1 is fantastic, but having the seat shake itself to pieces during compressor stalls would be the icing on the cake. Thanks!

Hello Aerges. What a fantastic module the F1 is. Could I suggest that more axes are able to be bound where appropriate in the controller setup? For example the volume controls for radios & missile tones would really benefit from being able to be bound to a controller axis, likewise some of the radar controls. I'm sure there are others too. Thanks!

Yes same here. Crested a ridge at low altitude and yaw oscillations went bonkers!

(ouch)

That’s what I was thinking, but the system as modelled seems highly selective by only activating when a missile is launched and not activating when a rocket is fired. Current WIP limitation or modelled feature?

Perhaps @Chizh has some thoughts on whether the MWS should differentiate between missile launches & rocket launches?

Yes reason I posted was my wingman was firing Vihkers and the MWS activated, but when he starting firing S80 rockets there was no indication of launches

Currently very much enjoying the BS3. Its a great module and a good improvement on the BS2. Quick question regarding the missile warning system. Should the MWS alert the pilot to nearby rocket launches as well as missiles? Do the rocket motors in both missiles & rockets emit the same UV/IR signature? Thanks!

2. Yes but not needed. The standard spacer is fine for using glasses. 3. Not likely. The FOV mod face gasket sits the Reverb’s lenses very close to your face/eyes so there is very little room for glasses.

6. Correct. No hand tracking. 7. No. I set mine up with a mouse. I only use it for DCS so no controllers aren’t an issue. 8. Only if you want to use controllers . 9. It comes with a PSU as part of the cable. 10. Yes. 11. Maybe. The v1 gasket works fine with glasses. I have ordered prescription VR lenses so hopefully will be able to use a v2/wider FOV gasket when the lenses arrive.

I recently went from a Quest 2 to a refurbished G2 v1. Big improvement in visuals. 1. V2 has better cable, closer fitting facial gasket (improves FOV) & better tracking of controllers. 2. Yes, but I have latest BIOS on an MSI B550 board with a SATA powered PCIe USB card. So far no issues with v1 cable. Haven't dared try it directly on the 550's built in USBs (scared!). 3. Probably will have a broken cable clip at rear of headset (not really that important). V1 will have the reduced FOV so maybe consider purchasing a V2 gasket from eBay etc. Note, V2 gasket is not for spectacle wearers - it sets the lenses too close to the eyes to be able to wear glasses at the same time. 4. No problems with my V1 so far. Cable (& headset in general) definitely do not have same build quality as Quest 2, but still perfectly usable. 5. I've looked and I think you may have to phone HP. Seems to be very limited supply of V2 cables. Good luck!

I can tell you going from a 5600X to a 5800X3D made a significant impact to frame rates. Yes the 5600X when boosting clocked faster in GHz than the X3D, but that huge cache in the X3D is what is making all the difference in DCS. If you do go for it, ensure you have a good cooling solution (they run hot) and don't expect to do any overclocking (they are mostly locked). Expensive....but good!

With you on this one. I was commenting to my co KA-50 flyer that all the she needs is a FLIR & an RWR to be nearly perfect. Perhaps the cynic in me tells me it won't ever happen as it may impact Apache sales. I'd like to think not and that it would encourage further KA-50 sales and even up the red vs blue force levels.

Yes hard to be sure settings are applied at start up. I just check HWiNFO for tiny reduction in VID and of course run a stress test and temperature should be a little lower

Try this if you're looking to reduce the 5800X3D temperatures by a few degrees: How-to-undervolt-AMD-RYZEN-5800X3D-Guide-with-PBO2-Tuner/README.md at main · PrimeO7/How-to-undervolt-AMD-RYZEN-5800X3D-Guide-with-PBO2-Tuner · GitHub Works quite well

BIOS for the GPU. Its an MSI gaming X trio 6800XT. Had black/green screen/crash issues from day 1. MSI acknowledged problem and sent a new BIOS https://forum-en.msi.com/index.php?threads/rx6800xt-gaming-x-trio-black-screen-random-signal-loss.357186/ For this MSI card ONLY. Probably not linked to your issue unless you have the same card and not updated. On occasion I get problems with the Q2 misinterpreting my spectacles moving slightly when combined with fast head movements as the headset being taken off so the screen shuts down momentarily. Always happens when you really want the screen to go blank on you.

Before MSI released a new BIOS for my 6800XT I got black screens all the time (not VR or DCS related). Since then the only visual issues I experience are when ASW is used. AMD cards don't play nice with it.

Maybe look at your .yml file, make adjustments with the hotkeys while counting how many times you press each hotkey and manually inputting that into the .yml file? Or in my case lots of trial & error by manually editing the .yml file after every adjustment.

According to the help text this is not possible with hotkeys, so you'll have to save your changes manually by editing the vrperfkit.yml file with Notepad++ (not Windows notepad)

Hi, not the exact change you're planning but can report real noticeable improvements going from R5 3600 to R5 5600X. Couldn't tell you frametime differences as I didn't measure them with the old CPU, but certainly can notice in game, especially MP. Full specs: R5 5600X (PBO2 curve enabled, no OC-too many crashes), AIO 240mm cooler, 6800XT, MSI Pro B550A, 32GB RAM, NVMe etc....

In the oculus debug tool. You can also adjust SS, sharpening, ASW etc with it. It comes bundled with the oculus software.

Yep ASW doesn't play nice with AMD cards. I usually turn mine off altogether. A big performance boost for me was the FOV modifier. Currently set at 0.75, 0.85 and big improvement in FPS. Still get drops in frames, but its still quite smooth even at ~30FPS. R5 5600x, 6800XT, 32GB DDR, SSD, Quest 2.......etc.etc.

I use FSR at 0.82, sharpness 0, radius 0.6. Currently using the Quest link built-in sharpness & VR clear water shaders. [Resolution in the Oculus app is max. Currently using 80Hz, set at 45 forced via the OTT. Encode resolution is a major factor on number of pixels displayed. I have it set it maxed out at 4064. Be warned, if you use this encode resolution IT WILL NOT work for 72Hz. Make sure you turn it back down if you want to use 72Hz or it will appear as though your Quest 2 link/PCVR capability is bricked. Important DCS settings are currently 2xMSAA, terrain shadows off, PD 1.2. Am going to try increasing PD and turning off MSAA, but I think the jaggies & shimmers will be too unbearable. PC: R5 5600X, 6800XT, 32GB RAM, SSDs etc etc]