nojwod

From the moment I first installed it I have had no problems other than a few teething issues. If you're trying to use the legacy rather than the modern flight model it won't work. Using the manual that is available at the Orbx Direct site and in the aircraft folder is mandatory to learn the unique features of this plane. It's very powerful for its weight and very slippery so you can't fly it like a Cessna or Piper. All tests so far on the flight model have shown that it's within 2-5% of published figures across the board. If you are having trouble with the trim then it's probably realistic, it's a pilot's hands-on plane first and foremost.

Just an interesting observation, I've been making a helicopter tour video of a walking track which involves recording the MSFS flight over the trail, which twists and turns. The best chopper for the task is the nimble Guimbal but when I used the Asobo one to follow the flightplan on the map, the route did not appear. No idea why that particular chopper somehow prevents the flightplan legs from appearing on the VFR map but it does. Luckily the freeware Guimbal is still available at flightsim.to so I downloaded it and although its flight model is slightly harder to manage than the Asobo one, at least I can follow the intricate flight plan using the map. I need the flightplan because in many areas the trail is invisible under the trees and it's the only way to know I'm overhaed of it.

If it's just the once in a flight then my advice is to ignore it! Occasionally I have the same thing, it's almost certainly sim related not the Reverb.

And setting the 2D window to a small size until it stabilises can also help

I have the Reverb G2 and I can assure you the foveated rendering is supported and works.

Not a single one of the shots in that link show anything like my screenshot, one shows some faint multiple lines, yes, but the rest are either that single horizon marker, or some sort of colour banding it looks like. Anyway like I said it's fixed so it's time this was put to bed.

I use it for the colour and the foveated rendering, amongst other things. Wouldn't do without it. There's a ton of information about all of the advantages at a site where people go for lots of information, much more than we can fit into a reply such as this.

Google it?

No it's a completely different bug. That horizon line has always been there and is easily ignored. These lines, multiple obvious lines, can't be ignored. Or did you not even see my screenshot?

Problem soled I was running 1.2 something of the Open XR Toolkit Companion but updating to 1.3 solved it. Issue closed but someone else might have the same issue so I'll leave this post up.

Here is the screenshot. These lines didn't appear in the first flight I loaded, but when I went back into the Main Menu and generated a second flight the lines appeared in VR. Switching to 2D didn't change anything, they are still there.

Are you sure you don't mean the generic single line that sits on the horizon level? I'm talking about multiple lines right across the distant scenery. ever seen before. I'd better get a screenshot so you know what I'm talking about.

Since SU12 when I set up a flight and switch to VR, I get multiple lines across the mountains in the scenery. I'm still trying to test to see if it's associated with the OpenXR Toolkit Companion but first indications are that it doesn't make any difference. I'm also not sure if it is only on a change of flight, I didn't notice it on my fisrst flight but the second flight from the main Menu I did, but I also changed location. After they appear, if I go to 2D monitor, they are still there. Anyone else seeing this?

That's a Steam VR WMR window, I only have the MS one. Plus, it's not the window that is showing the VR view, which is the MSFS window that sits on the desktop along with the WMR window, and which is the one that needs to be kept as small as possible.

Can you post a screenshot I don't have anything resembling a pause button either in WMR or the MSFS preview window

I have no idea on fps I never look at the counter I just note if it's smooth or it's jerky.

Exactly as I said in the original post it depends on your setup.

Well it makes a big difference for me.

I don't see any option to turn the preview off. Can you elaborate?

The following tips are from my experience, they should be important for all users but I guess it depends on each users' setup. I'm using the HP Reverb 2 and an11700K cpu and 3060ti card. Anyway, here goes: 1. Reduce the 2D window that sits on your desktop to the minimum size when entering VR. If I leave mine even half screen I see a drop in frame rates/performance. 2. Do not have any other programs running if you have a browser window or mail open, close it down. MSFS often runs the CPU close to it's limit, and even a few stray instructions form another app can tip it into a bottleneck situation, that like a traffic jam on a freeway, can take a long time to clear. 3. Use DLSS, and the open XR toolkit, and have foveated rendering set to the most aggressive setting you can tolerate. 4. If flying in dense scenery like major cities, reducing the resolution in the Open XR to say 95% can make quite a difference to performance without too much of a hit to the visuals. It depends of course on how loaded the system is, but works for me.

I make sure my desktop MSFS window is minimum size and I think it helps because my display is 4K and some resources must be used to display such a large window. If I don't make the desktop window as small as possible, when I exit VR, framerates tank to just a few per second or less.

Using the XR Toolkit I set my brightness down and my saturation up and mostly I'm happy with what I see now.

It's normal MSFS. It's to keep frame rates as high as possible. Nothing that you can do about it unfortunately.

For me FSUIPC is compulsory in MSFS. So many different sensitivities in the different aircraft, the Asobo one are way too sensitive, while the Orbx Optica is like a lead balloon without upping the sensitivity. But each to their own, only get it if you agree that there is a range of sensitivities in the different aircraft. Oh, and of course with the quadrant for throttles etc , I can set up the 747 for 4 engine control easy peasy.

You can also edit the line nearby that says parking type, often filled in as "RAMP", not sure if it's just blank between the " '' or a value like 0, I'm sure you can work it out.