nojwod

Yay! In the latest WU in FS24 (and FS20) some nonk placed trees all over the lawns at Canberra's Parliament House. Completely ruined what was a faithful model of Australia's equivalent of the Houses of Parliament in London. Anyway I asked Bijan if he could take a look and praise be, in the update V$ released today it's fixed. Thankyou Mr Bijan from all Aussie simmers.

I believe that you need two full computers each capable of driving VR, and then there are packages that can link them apparently.

Depends on your settings. My initial start with the Oasis was only 60-70% of the res I was used to in WMR but after reading everything I could and adjusting settings it's as good as it ever was in WMR. The tip about setting the resolution to 150% is the most important.

It sounds to me that you do complain about something that you are allowing to dominate your experience rather than dealing with it. It's all in how you approach the problem, if you tell yourself you're not going to enjoy it because of the field of view then that's exactly what will happen. If however you go in with a positive attitude and accept the limitations of VR and concentrate on the positives you can enjoy it like thousands already do around the world.

I tried the Quest 3 and the image was horrible compared to the Reverb G2. No matter what I did the ground detail was lucky to be half of the sweet spot in the G2. This was using the data cable. There's a reason the G2 uses the Display Port on the video card, it delivers a far better image. The Quest 3 visuals in the headset itself in loaded games and the virtual room were excellent but the MSFS visuals were not up to scratch. I tried wi fi as well as the cable and neither was a patch on the G2, So I sold the Q3 and bought two second hand G2 headsets and with the Oasis driver I couldn't be happier under $1000.

Yes I did. But a quarter of a second out of my flight preparation to bump that slider isn't considered a huge impost on my flight sim experience.

That was incorrect. Didn't make any difference. Unfortunately. But I did discover that when I went into the NVidia app and used that to optimise settings for FS24 and FS20, all the hesitations and jumping around ceased and performance is silky smooth. And to be honest it still looks great in the VR goggles. I had no idea that high graphics settings could cause the VR to play up, I assumed that if the CPU and the GPU in the box were OK with settings then the goggles would just receive the images and display them. So all I need to do now is jump into settings and raise the optimised settings bit by bit until I notice display problems then back off a bit. Oh, and that purple 45 degree line across the left eye? Fixed by moving the ipd slider a fraction.

Aliexpress is something that changes all the time, you'll have to check what's available. I discovered another issue, and I think I might have a solution. The image would jump around a bit, as though there were connection issues. So I've got tried changing usb ports etc. Sometimes it was better sometimes not. I was thinking that FS24 was more likely to cause the problem. But now I'm thinking it's the large monitor directly in front of me affecting the headset cameras, which expects to be seeing a static view. So, I just tried the headset with the WMR window minimised and it seems to have come good. I've now found a large piece of cardboard to put in front of the monitor while flying in VR, fingers crossed that it will work.

But luckily it was fixable. I started Steam VR as usual and thought my headset was dying. There was a 45 degree line across the left eye, and artifacts appearing in the corners. Luckily I've got a spare headset so I plugged it in, same problem! So that confirmed that it was software not hardware. A pc restart didn't help. word not allowed! Then I tried starting the session with the Oasis driver icon on the desktop, and for some unknown reason, success! So I've now turned off the pc and hopefully when I restart it'll all be back to normal. If not probably just a full reinstall of the Oasis driver will be next. By the way, my spare headset died but it was the cable. A new cable costs more than a second hand headset, but then I found on Aliexpress a cable for $US70 approx, which works perfectly. So I now have a working headset and a complete spare, which should see me through until 4K headsets come in at sub $1000...

There are controls in the sim that dictate how nosewheel steering works, and I know sometimes I have inadvertently activated lock steering or decreased steering. If you Google steering controls in MSFS you should get a list of what you can lookout for.

Certainly in FS20 the smallest possible window provides better performance. The resolution is irrelevant. In FS24 I find that the windowed size has less effect but I still keep it as small as possible. Another thing that can result in lower fps for no reason is other applications running. A few times I had poor performance that I tracked to having my browser open, as soon as I closed it fps went back to normal.

Compared to MSFS, VR in FS24 is word not allowed. Constant lags, pauses, and momentary screen to black. Even in low density scenery. Terrible. And even on average settings, almost every startup gives the warning that the GPU resources are exceeded. My 4070 has 12GB so it shouldn't be overloaded with normal settings. Luckily I still have MSFS installed and ready, I'm only going into FS24 for testing. So much for all the reports of how good SU4 is for VR, including the VR Flightsim Guy, for me it's a disaster.

One further comment here, to do with the supposed misaligned centre markings: A lot of factors can influence how the sim details are portrayed to the user. Even different video cards, and drivers can display information differently from one user to the next. Resolution selection and other sim options can also have an effect. As the various LODs used to display scenery change, often the details change position, mostly only by a fraction but sometimes quite a lot. I've even seen cases where I've noted a wavy centreline on one approach, reported it, and then next time I flew the same scenery it was dead straight. So, that's why I say, if you sweat the small stuff then you're making a rod for your own back, and instead of enjoying the sim experience by noting all the incredible reality of the sim, you allow yourself to be affected by details that in the big scheme of things matter very little. Here endeth the sermon.

I wonder how many of the complainers here have done any scenery development. An update is not just a few clicks and 5 minutes work. More often than not attempts to fix problems especially minor ones lead to unintended changes and a supposedly quick project takes days. So, the principle by which I sim of 'suspension of disbelief' which involves looking the other way or ignoring minor defects allows me to enjoy scenery knowing the developer has probably better things to do than correct minor faults.

I will try the VR trick and see if it works for me. Cheers

No thanks for the suggestion but I've been through that step and many others. It's not to the level of a sim uninstalling problem because I can access any of the aircraft by searching, rather it's an annoying problem that didn't exist before and has never existed in MSFS.

I have the Premium Deluxe version which has around 100 aircraft included in the sim, and I have around 30 in my Community folder, a total of around 130 aircraft that should show up in the Aircraft Selection list in Free Flight. But I am only able to see around 100, one time I counted 104, another time I counted 98. The alphabetical list stops around P, so aircraft like the Textron C152 just don't appear. If I use the Search function I can get the missing aircraft to appear (one at a time) but that's not really good when I'm scrolling through looking for an aircraft that catches my eye for a particular flight. So... I'm wondering if any of the community who have the Premium Deluxe edition and several add on aircraft in the Community folder could check to see if they are able to see all aircraft or just a limited number like me? And anyone who understands the MSFS 2024 files structures etc might be able to suggest if trhere are any caches, indexes I can clear to see if the problem lies in my setup?

Steam VR drivers to be released 29 August according to the VR Flight Sim Guy: How good is this? I've been using the old W11 version and praying they weren't going to update me by force, now it sounds like it will be all good.

Open XR Toolkit companion has a range of colour, contrast and saturation settings, as well as three 'sunglasses' settings for when the scenery is washed out. I have mine configured so the look of the scenery is very similar to my monitor.

I use a small program called incontrol.exe. Seems to be working fine, my G2 in W11 continues to run well.

Flew both in VR last night worked perfectly for me. One of them has a small tear in the rh wing fabric which is fair enough but it shows the ground underneath rather than the bottom skin. Other than that no issues that I could see, performance was excellent. Oh except for the viewpoint which is a little annoying but just a few seconds to correct.

I don't even get that file in my folder. I didn't even have the DA40NG folder until I just loaded a flight with the plane and it created a very minimal folder. As with all the new streaming planes and scenery you'll get some control but only the minimum. I have allocated the number pad keys to the translate cockpit views which makes moving the pilot view extremely quick and not a problem at the loading of the flight. / = down 8 = fwd 5 = up 4 = left 6 = right 2 = back I seem to remember that a couple of the bindings were in a different section of the controls menus so a bit tricky to find. Or maybe that was a couple of the slew bindings which I also have allocated to the number pad keys I forget.

I've been trying to work out why I don't like the look of the landscapes in FS24, they're washed out colourwise and generally don't feel as immersive as MSFS. But I think it's possible because in order to generate the fps in FS24, the ground in kept at a lower resolution than MSFS, until you get close and then it generates a lot of detail in your limited view radius. But... and this is the big but, all the trees and buildings sitting on the blurry ground are displayed as crisp detailed textures. The mismatch is obvious in areas of grassy fields between small forest areas, as you pass over at 500-2000'. And when you add in the washed out colours, and in my corner of the world downunder, it just doesn't cut the mustard. In 2D FS24 manages to generate lots of detail in the countryside and it looks quite balanced, but who wants to fly in 2D?

I just checked the DA50 cameras.cfg and I found the PilotVR section. But I have no idea if it can be saved. And of course there's no way to save the view in the streamed aircraft I'm assuming.

Hey contributors... no one cares if you are going to uninstall it or request a refund. Just do it and let these forums be for those who are prepared to make the effort to get millions and millions of lines of code work together, by being patient, flexible and avoiding the need to be dogmatic.