Supmua

The Aero is now $300 off during Thanksgiving sales.

I asked RS a very similar question, and the simple answer is that they still won’t behave the exact same because the internal hardware is different and is tuned differently. If you ever set the current R3L to very low force numbers it can behave erratically and might not even center correctly.

The Analytics window needs to be left open on windows desktop or minimized, I’m not sure why they decide to bury this feature in a hard to find location instead of making it a toggle switch like Vsync. Vsync mode will shift frames between 30/45/90, so it’s not ideal if you have significant framerate fluctuations because stuttering also occurs when framerate is not constant (when we have HMDs that can support variable refresh rate in the future, this type of stuttering will be eliminated). I think framerate limit option on OXRTK can also get the job done and that setting will stick. Also note that VB frame lock doesn’t play nice with MSFS (at least on my setup), it will instead half the framerate that you are supposed to be getting. And perhaps this is why it gets hidden because it doesn’t work well with some games.

It’s really 3 mm difference in max displacement vs the old one…

The only thing new as far as I know is the change in force-displacement graph’s slope with the new hardware.

No, ET foveation is MSFS only for now. With the latest update foveation option generates small but intermittent GPU frametime spikes with DCS on my setup so I stop using it, this doesn’t happen with MSFS.

Displacement is the distance that something moves, in this case the distance the stick travels when a certain amount of force is applied. With the MKII, less force is needed to produce similar amount of displacement.

There is only one distortion correction profile with version 3.7, so you can no longer pick and choose. In order to use foveation, you need to install OpenXR Toolkit. Enable foveation and select fixed or eye tracking.

Board upgrade takes just a few mins. 8 screws total, you’ll need 2 different screwdrivers (T20 M4 torx for the inner screws and M4 hex for the outer ones, no need to touch the Phillips screws). Align the white arrow on the board with the USB port.

Right now 8.5 pitch, 6.5 roll (not exact as I’m not home but around that ballpark). But I’m still tweaking. If you look at the graphs you can see that it’s more responsive to the older one so there’ll be an adjustment period. There’ll be people who’ll want to push harder or the other way around. Also remember the force limit of the FSSB is 13 lbs by design, push harder and you may break it. There’s a Pro version that is 1:1 to the real thing but costs 10x more and needs a lot of force to operate.

Mini USB. The release for now will be upgraded board only. A simple direct board swap. I’m enjoying this one so far, it is quite responsive when you need to make a sharp turn without feeling like breaking your arm or the joystick connection in the process. It is especially better with faster pace games like Star Wars Squadron, MechWarrior 5, etc.

This is the reason why existing owners may want to upgrade. Subjectively, it feels much more responsive pulling high G’s, making tight turns, etc. with the F-16C. You have better control in low force input scenarios also making it easier to hold steady the force input at say 20% vs the old one (Helicopters control is tighter with this one also). Regarding helicopter control, the built in software trimming option works really well. Without trimming it’s still harder to hold the input vs my regular stick with long extension though since my arm gets tired out after awhile. Objectively, see the attached graphs. I have no idea regarding the the upgrade details or release date, I’m only testing the product.

Switch to OpenVR and run fpsVR, check CPU and GPU FT graphs see which is causing the stuttering?

Latest driver. Just did around 45 min of Apache flying, pretty much one of the most taxing aircrafts right now and it's pretty smooth with framelock at 45. It must be some background process causing your stuttering. I'm also running Asus Tweak III in the background since I overclock the heck out of my 4090, no issue.

Very smooth in my case, and I looked both left and right and all around during takeoff. The frametime graph also confirmed this, smooth without spikes.

hmm let me try this. Don't mind flying more since I'm testing this new joystick base anyway lol.

Right CTRL-Pause. I think these represent GPU FT not 100% since there're 3 of em.

Well I was flying at 90 fps so I didn't really see any lag. Even with the spikes at that fps I could barely tell. Let me try more intensive missions. OK microstutters, slightly worse than OpenVR actually. But smooth once you force 45 fps lock via Analytics Window in VB.

Ok, I have isolated the OpenXR stuttering problem. It appears to be from OXRTK, will inform mbucchia about this. Due to very high framerate, I barely noticed any stuttering at all but GPU FT graphs revealed everything (those intermittent spikes). null And the image below is OpenXR without OXRTK. No GPU FT spikes. Noted the dropped fps, this is due to running at full resolution without OXRTK res override, so it's 4100 horizonal pixels vs 3200. OpenVR mode doesn't have this problem either, pretty smooth GPU FT graph similar to the bottom picture. EDIT: Had a brief chat and got some pointers from mbucchia. If you have stuttering with OXRTK, try enabling the Safe Mode from Companion App then reset the settings with CTRL+F1+F2+F3--this fixed my GPU FT spikes. It might be the foveated rendering setting in my case, turned that back on and the spikes came back.

I haven’t tried OXR yet, been using OpenVR since the update and didn’t notice any new change. Will try OpenXR later today.

I think the fps drop depends on which performance bracket you were originally on. For people using motion smoothing or fps lock, if you already have good fps cushion, 2ms of GPU frametime drop will not affect the overall fps as fps lock happens. But if you were right at the edge say 46-47 fps, a drop into high 30s or low 40s can hurt, and the same goes for people who were in the 30s before (for 90Hz headsets). For the people who play mostly in CPU bound scenarios (crowded MP servers), a slight increase in GPU frametime will not result in fps drop either because CPU is already taking a bigger hit. However, if you do a direct measurement of the frametimes for both CPU and GPU, you will see a slight GPU frametime increase with the new beta.

Seems fine to me, and I've been flying a lot testing the new FSSB R3L MKII.

Still testing but some more info. The new R3L MKII offers more realistic control in low force input scenarios which is more suitable for simulation. Real F-16 stick: 26 lbs of force for full input with 1/2 inch of stick displacement. Can be rough for typical simmers if you play for hours. R3L: 13 lbs max input with 1/4 inch of stick displacement. R3L MKII: reduces the force sensitivity further by 4 lbs while retaining realistic movements, so aircraft control feels more responsive without breaking your arm. The force sensitivity remains adjustable via software. Upgrade path for now. Old/existing housing with new board for Christmas.

Teaser. The board is very well built, solid quality.

Can’t help you with IL2. MSFS is mostly plug and play and Varjo discord is probably the best place to hang out for this. In general, high preset is good enough, TAA for sharpest image or DLSS quality if you want 15-20 extra fps. OpenXR Toolkit is highly recommended for foveated rendering options, resolution override (I use 3368x2880), and postprocessing to correct over exposure in VR, etc.