Supmua

OK did some more testing, I guess persistency paid off. It turns out there was a problem with my NVIDIA driver and Image Scaling which didn't show on the control panel, so I guess it never worked properly. Had to download the Hotfix version, turned off HDR, and restored to default settings, before image scaling option would show up in the control panel. Next I tried the system wide NIS setting, but it crashed SteamVR right away, so had to disable this. Then I tried the FSR 2.0 with DCS, and found that it reduced my frametime to 8ms in the main menu which is pretty good (normally 10-11ms). Image quality is relatively meh even at 0.8 scaling, but tolerable at 0.9. FSR Sharpening is bad so I'm sticking with Reshade VR for this. With Reshade VR sharpening (CAS 1.0, Intensity 1.2), the quality is very close to my usual settings except the MFD texts aren't as crisp but still completely legible on the Hornet. This way I shaved off about 3ms in frametime during gameplay, which can be huge in VR depending on the situations. IQ still not as good as no-scaling + Rehade VR (might not even be noticeable on lower-res headsets compared to the VP2), but not bad either.

no idea, since I have trashed the whole thing since. The bottomline is I got 45 fps in the main menu instead of 90 fps due to 1 ms diff in frametime with the openvr_api.dll from FSR compared to the default one, tried swapping back and forth 3 times and results were the same so I decided to stop since there are better things to do.

It seems that per app SS is now the percentage of what you set globally. Could've sworn it was 1:1 in the past, so 100% per app means 140% if that's what the global SS is.

Any idea where this is located?

OK FSR actually increases my frametime by around 1 ms. With FSR my frametime even in the main menu is >11 ms which causes my headset to drop the framerate to 45 fps, without it my frametime is 10 which gives 90 fps. During actual gameplay the difference is between 0.5-1ms, with exact same SteamVR settings. Image quality is actually better without it, less muddy in the distant. it also seems to alter pixel rendering numbers in per app SS, Steam SS at 100% shows 3800x3800 pixels per screen which is crazy.

I’m still testing various combinations and the general idea is to use Reshade for sharpening and FSR purely for supersampling. Still trying to figure out the difference between per app setting at 100% Steam SS with low FSR number vs lower Steam SS with high FSR number—70% Steam SS on my setup is still over 3K x 3K per screen. The idea of having to run two graphics mods at the same time doesn’t sit too well with me though.

I've been testing this a bit both with NIS and without and the only meaningful filter that makes a difference for me remains Reshade VR using AMD CAS technology, none of this FSR stuff provide adequate image quality for my personal use. With Reshade VR, the texts on F/A-18's AMPCD on are very crisp and completely legible on the Vive Pro 2 and so are the distant ground details especially buildings and bridges. Without Reshade the AMPCD texts are a bit blurry and distant buildings and bridges really lack definition (with or without FSR). I'm going to try more various combinations of FSR with Reshade to see if it can shave off some frametime while retaining similar graphic fidelity, but I doubt I'll see anything groundbreaking at this point (I consider Reshade VR groundbreaking since it completely changes the way I look at DCS VR).

Since It was already posted in their own forum, I would like to show you what is coming.

VR is quite good now with high res headsets such as the Vive Pro 2 (and I’d imagine the Reverb G2 also). I do everything including mission editing in VR. With newer gen headsets from next year on things should be even better, the only catch is to have a top-end CPU and GPU to minimize bad experiences. I get much better framerate in DCS compared to MSFS so I can’t really complain.

It seems I’m the lucky one with no significant issues so far? I did have vertical scan line but this has been fixed since the past few firmware update. My problem with motion compensation causing gel-like artifacts has also been fixed. Fingers crossed. In Toms Hardware comparison review, they saw better fps from the VP2 compared to the Varjo Aero in most games but I’m probably going to sell this headset once I get the Aero.

The real F-16 stick requires crazy amount of force, more than 20 lbs for max input, something the home version of FSSB cannot cope with. They design it to operate at half of the force input of the real thing, with typical force setting around 4-5 lbs, max around 13 but not recommended as you will probably break it. Sometimes too much realism is no good. My RS F/A-18 grip, for example, has the 2nd trigger that has the same resistance as the real thing and is really hard to squeeze, and a lot of times I would lose half a sec to a second during a gun run trying to squeeze the darn thing. I’m used to it now but using it back to back with other grips still show a huge difference in the feel and operation, with others being much easier to operate.

By the time they’re done fixing your VP2 you might already be using the Aero

I like ACASIS hubs (check Amazon), they’re well built (aluminum enclosure) and reliable. Sabrent and Anker are also good brands.

Disable TARGET and see if the problem persists?

I’ll be following this also, mainly because of the micro OLED screen and portability, though not having high hope about their software, tracking or support. Imagine if Valve, Meta, Samsung or even HP pushes out a headset with similar panel it’d be game over for these guys…and there is a good chance that we will see more OLED VR headsets in the near future too.

It's kind of strange that they didn't want to test the cable. I wonder how they would know if there's defect with the cable (happened with quite a few G2 headsets). So if they don't find anything wrong with the headset at their HQ are they going to ship it back with a new cable?

Let me review the manual and get back to you via PM. I haven’t had to do this in awhile but the flashing left LED usually means it is searching for a pairing device (i.e. your PC).

It could still be BT issue. Try connecting the grip to your FSSB and update firmware from there.

They did think about the dual throttle, but then it won’t be the F-35 replica that they want and it would also drive up the cost, not to mention significant deviation from the pro version. People who actually utilize dual throttle typically do it during acrobatics, BFM or AAR—hence the throttle split option is there for them. For simpler dual throttle operation during startup or shutdown, you can just set up the side switch for that purpose. There are specific settings that will bring the throttle to IDLE or OFF positions. There are also 8 memory slots if you want to bypass that and bind them directly in DCS so your imagination is the limit. The throttle weight around 9 lbs (4 Kg), heavy for its slim profile but this is optimal for stability during use especially without mounting. They tried lighter casing but it became wobbly and unstable.

I shifted the unit a bit so the plate would stick out to the side. But you can see the rough size of it, next to the Winwing.

Hopefully it’s just the cable. I’m still very impressed with the image quality at 3090x3090 pixels setting (~65% SteamVR SS) that I’m getting on my headset (except the peripheral glare), really can’t go back to the Index now. It’s hard to imagine that the Aero is supposed to give much better image quality than this. Demo’ed it to one of my friends recently and he was blown away (Index user).

The leaked benchmarks aren’t super impressive. Intel basically caught up to AMD, slight advantage in gaming performance at the expense of significantly more power usage. Waiting to see DCS benchmarks. Those DDR5 RAM will sure cost $$$ if you want low latency I decided to wait a bit, probably going to end up with the 12700K as I don’t really need the i9 for flightsims or gaming plus it will be easier to cool. That Asus mobo also is incompatible with Noctua cooler, so I’m gonna return it.

Very cool in deed, both in hardware and software. I think the F-35 grip will probably be coming in early 2022. They typically would focus on one product at a time, and right now the throttle is the main focus. The F-35 grip is very interesting also and is def on my wishlist (as I’m a big F-35 fan). Currently the RS F-16 is my go to grip due to the most amount of buttons avail, but it looks like the F-35 grip will top this. Would also love to see an actual F-35 module for DCS but will probably have to settle for the MSFS version for now.

Sorry to hear, mine is still fine with typical daily use. Have you tried to reinstall the software and recheck? (Vive Console and SteamVR, as well as NVIDIA GPU driver). Another thing you can do is run fpsVR and see if it shows any sign of CPU or GPU frametime problem during the problem. Or just plug in the Index and see if there is similar issue (Will have to repair the controllers).

I don't have the exact dimensions but the mounting holes for screws are in the exact same locations as the TMW throttle (similar to the FSSB R3L which can share the mounting plate with the TMW stick base). The length of the throttle base is the same as Winwing's throttle as I place them side to side in my current setup. I'm currently using Monstertech's TMW mounting plate and it fits well. Of course the throttle itself is longer than the plate so you will either need a longer profile (the 14 cm one) if you plan to utilize screws. Right now I just use 3M doublesided mounting tape without screws with the TMW mounting plate and it will not move at all as it's already quite heavy.