Skip to content
View in the app

A better way to browse. Learn more.

The AVSIM Community

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

At last, starting to get somewhere with MSFS2024 in VR

Featured Replies

  • Author

OK - I will skip the tortuous route of what SU1 had done to my folders (basically, it had added a full extra tree of 'Community; MSFS2020 Official; MSFS2024 Official folders into my original Community Folder). 

I downloaded a fresh copy from BATC of their BATC VR Toolbar directly into the new Community Folder location and, hey presto, I now could see the BATC box in the MSFS2024 Toolbar.

And, OK, so I need to now copy my other Community file addons into that new location too...

...nah!  This is MSFS2024 and that would be too logical.  I copied a scenery file, went to the new Community file and tried to paste the file in..

"YOUR ORGANISATION DOES NOT ALLOW YOU TO PLACE THIS FILE HERE!"

Hang on...I am my Organisation!!   I checked the file security and access rights and yes - I was administrator with all rights of access and amendment.

I tried a number of times.  

In the end - and, to be honest, getting fed up with the ridiculously long tree of folders we have to go through every time we need to get to the default Community folder and check the results - I remembered that the Community folder can be anywhere.  Including a different drive to where the sim is sitting on.  So instead of a tree of C:Users/AppData/Local Cache/Packages/ruewiorjionfjkLimitless/Local/ Packages/Community/Community (see above why there are two Community folders) or whatever, I created an alternative file structure on my spare SSD drive of

E: Microsoft2024 Community/

I told MSFS2024 that was where the Community File needed to be and it obliged by creating for me the three folders of Community; MSFS2020 Official; MSFS2024 Official in that location.

I went into my original Community Folder and recopied the scenery addon and clicked Paste on my new E: Microsoft2024 Community/Community folder

"YOUR ORGANISATION DOES NOT ALLOW YOU TO PLACE THIS FILE HERE!"

AAAAAAAAAAAAAAAAGGGGGGGGGGGGGHHHHHHHHHHHHHHHHHHH!!!!!!!!!!!!

After 30 minutes of shouting words that I believe were used back in Anglo-Saxon times at loud volume around the house, in the garden and in the street, I deleted the MSFS2024-created Community folder, created a new folder in the same location and named it 'Community'.  Pasted the addon into that and ran the sim.  And it worked.  

 

My understanding from lots of internet searches  is that Windows doesn't cope well with very long file structures and this can cause this error message.  And clearly, a file nest of 9 levels is getting to its limit in this instance.

Yes - quite!

My humble advice is to create a Community folder in your own preferred location with a short file structure.  Easier to get to and you will retain access to your own folder and your own add-ons.

That's the rant and 'if you can't find your addons post the SU1 update, look here' advice over.  Next post, I'll move onto the better bits... 🙂 

 

Edited by AJZip

Ryzen 7 9800x3D @5.2GHz; ASUS X670-P Motherboard; nVidia 4080 (factory o/c); 32G 5600MHz DDR5 SDRAM; Pimax Crystal Light VR Headset; Quest 3 VR Headset

  • Replies 73
  • Views 13.6k
  • Created
  • Last Reply

Top Posters In This Topic

Most Popular Posts

  • You were both quite correct to press home the DLSS point @HiFlyer and @odourboy I've taken my Crystal Light; my processor, my graphics card and my RAM to levels they've definitely never been befo

  • Just a short postscript for those who understand or are interested in such things. As explained above, I needed to make a few adjustments to my previous MSFS2020 settings in one or two shared are

  • And so, finally, a complete back-to-back flight of MSFS2024 and MSFS2020 - Same Simbrief Flightplan  - Same time of day (8:30 - 10:00 am) - Same AutoFPS settings used in both - Sam

  • Author

So to the better bits.  

First of all, the results - and then in further posts I will outline the broad way I've been working in terms of what I've tweaked and where.  It won't help anyone for me to detail actual settings (although happy to if anyone has specific queries) as everyone's system is different.  But it may be of interest which bit of my hardware / software chain is being used for what.

PC Specs are below in my signature.  My tests have been with the Pimax Crystal Light.  Additionally I have a bit of help from OpenXR Toolkit for render enhancement only and have been running a number of the aircraft below using BeyondATC in VR, with live airtraffic on, albeit at a low aircraft coms density setting.  

Results so far:

Jet Airliners / Jet Fighters / Twin Prop GA

So far, I've done flights in:

Just Flight Hawk T1

Fenix A320

Asobo Boeing 737Max

Just Flight Avro RJ 

Asobo/Ini A310

Black Square B60 Duke

CJ Sims Typhoon

Asobo Diamond Aircraft DA62

India Fox Tomcat F-14

 

My results with all of the above:

Positives

- Sharp external scenery up to and including the horizon.  Sharper than MSFS2020 running with the same settings and addons

- Smooth.  No stalls or major judders in normal operation - this is about the same as MSFS2020 of, say 6 months ago, but lately MSFS2020 has been 'unexpectedly and unexplainably juddery quite often'...hmmph!!.  Very smooth scenery movement looking down from the cockpit to the front; teeny micro-judder when looking down through the side window.

- Sharp internal cockpit - airliner glass screens to dials to panel text.  As an example, I was able to read all of the Fenix co-pilot's dials, screens and button text from my normal seated position on the other side

Negatives

- Same old washed out, over-exposed, milky glass external view from inside the cockpit.  It is ridiculous.  You click to external view and all is absolutely fine, click back to the pilot's seat and the outside view is, frankly, rubbish.  Shocking for day one, quite bewildering 6 months in and after a major update.

- The DLSS4 airline altitude ribbon (I'll talk about TAA/DLSS when I go through my broad settings and add-ons regime) is still bonkers, but at least you can now read the thousands and hundreds even though you still can't read the tens and units until you level out.

- My TLOD is lower than I would run in MSFS2020 and, with performance issues restricting the scenery pre-cache level I can use, city buildings and similar objects morph quite a lot

 

But, overall, much better than my previous attempts.  In my next post (prob tomorrow) I'll cover the 'where I'm tweaking what' while I try to get the optimum mix of tweaks for my own particular system and hardware. 

 

 

 

Edited by AJZip

Ryzen 7 9800x3D @5.2GHz; ASUS X670-P Motherboard; nVidia 4080 (factory o/c); 32G 5600MHz DDR5 SDRAM; Pimax Crystal Light VR Headset; Quest 3 VR Headset

  • Author

Oh...note I haven't included single prop aircraft.  There's a reason for that...and a different set of results I'll reveal tomorrow.

 

Ryzen 7 9800x3D @5.2GHz; ASUS X670-P Motherboard; nVidia 4080 (factory o/c); 32G 5600MHz DDR5 SDRAM; Pimax Crystal Light VR Headset; Quest 3 VR Headset

  • Author

I'll add the MaddogX to the list of aircraft I've now tried which has recently been released for MSFS2024.  This was a surprise as I have never thought of it as being particularly VR optimised.  Anyway, all controls and script sharp and fully readable, even the co-pilot's side info panel from the pilot's sitting position.  Flight, again, smooth with no stutters or micro-judders and externals as good as the other airliners flown.

So - what am I using and in what way

1.  DLSS4  - the original 310.1.0.0 driver and not the amended 310.2.1 version.

- Tweaked as documented elsewhere to use the 'latest' version (probably K)

- I am using DLSS /Quality.  With the help of the additional tweaks below, for the first time since I tried experimenting, DLSS is giving me clear scenery and decent

***Computer glitched and posted by itself.  I'll restart the post***

 

Edited by AJZip

Ryzen 7 9800x3D @5.2GHz; ASUS X670-P Motherboard; nVidia 4080 (factory o/c); 32G 5600MHz DDR5 SDRAM; Pimax Crystal Light VR Headset; Quest 3 VR Headset

  • Author

I'll add the MaddogX to the list of aircraft I've now tried which has recently been released for MSFS2024.  This was a surprise as I have never thought of it as being particularly VR optimised.  Anyway, all controls and script sharp and fully readable, even the co-pilot's side info panel from the pilot's sitting position.  Flight, again, smooth with no stutters or micro-judders and externals as good as the other airliners flown.

So - what am I using and in what way

1.  DLSS4  - the original 310.1.0.0 driver and not the amended 310.2.1 version.

- Tweaked as documented elsewhere to use the 'latest' version (probably K)

- I am using DLSS /Quality.  With the help of the additional tweaks below, for the first time since I tried experimenting, DLSS is giving me clear scenery, glass panels, steam gauges and cockpit info text and decent FPS all at the same time!  VERY few visual aberrations at the moment - but this is jets, airliners & twin props.  Single prop aircraft are a disaster with the DLSS4 (any settings) AND even TAA pretty unusable on my system.  The prop effect is having a massive and impact on the visuals...and with a single prop that is pretty much your complete viewpoint.  The TAA result surprises me - I'm actually considering using the DLSS Swapper each time I use a single prop...but still experimenting.  

- On my system/setup, I found the newer driver (310.2.1) less smooth

2.  Pimax Play

- Relatively modest with render at 0.9x native for the Crystal Light.  I am finding on my system that using OpenXR Toolkit (for ONLY the resolution boost) to raise the resolution values beyond 100% native gives me the visual result without the performance impact that pushing the Pimax Play setting beyond 1.0x often results in.

3.  OpenXR Toolkit

- I'm not using any of the facilities other than increasing the resolution per eye .  Next time I'm on, I'll check what numbers I've settled at and post here -  ***Display Resolution 3541x4190 per eye ***

4.  MSFS AutoFPS

- Such a splendid tool.  I had to download the very latest version for it to run in 2024 but this sorted the occasional stutters... 

 

So, to summarise, I'm using

DLSS4 - for the FPS

Pimax Play at medium-high - for the basic VR start point

OXRTK - for the render boost

MSFS AutoFPS - for smoothing it all out to a sharp, smooth, stutter-free experience inside and out

 

And yes, I'm old enough and wise enough to know - this is MSFS after all - that all these good results might be different tomorrow

Edited by AJZip

Ryzen 7 9800x3D @5.2GHz; ASUS X670-P Motherboard; nVidia 4080 (factory o/c); 32G 5600MHz DDR5 SDRAM; Pimax Crystal Light VR Headset; Quest 3 VR Headset

  • Author

The OpenXRToolkit Display Resolution I am using is 3541x4190 per eye

Ryzen 7 9800x3D @5.2GHz; ASUS X670-P Motherboard; nVidia 4080 (factory o/c); 32G 5600MHz DDR5 SDRAM; Pimax Crystal Light VR Headset; Quest 3 VR Headset

Thanks for outlining this AJ..

I reset all my settings in VR and was struggling again as always use TAA ... but have come to realize that its just not possible if you want decent FPS... lowering the resolution so much defeats the purpose of such a headset..

I tried your settings and am happy with them

We can only wait and see what SU2 will do for VR folks!

i9 13900KF @ 5.5Ghz | MoBo MSI PRO Z690-A WiFi | Corsair Vengeance Black RGB RS 64gb DDR4 3200MHz | MSI GeForce RTX 5090 Vanguard SOC 32GB | MP33 Pro 1TB M.2-2280 NVME SSD for OS | Samsung 870 QVO 2.5" 4TB SSD SATA2 | Samsung 990 PRO 2TB | Corsair RM1000X 2021 1300W 80 Plus Gold PSU | Antec Dark Fleet DF700 Flux Gaming Case | Win 11 home | Samsung 65" 4K TV | G512 Keyboard | Razer Basilisk V2 Mouse | WinCtrl URSA MINOR 32 Throttle Metal / 32 PAC Metal  | WinCtrl Ursa Minor Sidestick |Velocity One Rudder | MiniCockpit FCU and EFIS | WinCtrl MCDU | Stream Deck XL | Tobii Eye Tracker | Pimax Crystal Light |

Doug 

  • Author
47 minutes ago, vonduck said:

Thanks for outlining this AJ..

I reset all my settings in VR and was struggling again as always use TAA ... but have come to realize that its just not possible if you want decent FPS... lowering the resolution so much defeats the purpose of such a headset..

I tried your settings and am happy with them

We can only wait and see what SU2 will do for VR folks!

I'm pleased that you also found that this broad strategy seems, at the moment, to give some benefits.

No doubt the approach will need to change as the sim develops but this is, just at the moment, giving me the best results, inside and out, of any VR flight simming I've done to date for all except single prop aircraft.

That said, either it doesn't suit MSFS2020 or MSFS2020 is degrading all by itself.  Just because I'm paranoid doesn't mean they're not out to get me. 😁

Ryzen 7 9800x3D @5.2GHz; ASUS X670-P Motherboard; nVidia 4080 (factory o/c); 32G 5600MHz DDR5 SDRAM; Pimax Crystal Light VR Headset; Quest 3 VR Headset

  • 2 weeks later...
  • Author

So - a couple of weeks later, is the position holding?

Actually...and I'll say this very quietly just in case it encourages someone in 'you-know-where' to put a spanner in the works and take us back to square one...

For most types of aircraft, since SU1 was implemented, MSFS2024 in VR is presently consistently visually BETTER on my system and with my settings than MSFS2020

And not just a bit.  I'll qualify the statement shortly - and also come back to single prop aircraft - but at the moment for the airliners, fighter jets and twin props:

- the cockpit text, numbers, glass displays, knobs, switches are sharper over a wider FOV than in the same aircraft in 2020

-  the scenery is also sharper.  And while the detail drops off as I look further towards the horizon, the view is sharp up to and including the horizon

- most aircraft are smooth flying with little or no stuttering or juddering.  Just like MSFS2020 used to be...

 

Clearly, there are still all the usual annoyances:

- yes, the outside view from inside the cockpit is still massively overexposed and milky compared with the same view from the external viewpoint.

- yes, the altitude ribbon is still a solid green line where there should be the 10's and units when you are climbing or sinking.

- yes, the sim still randomly changes some of your custom settings for seemingly no better reason than, 'because I can'.

 

But, visually, MSFS2024 is actually significantly better for me at the moment, both in terms of sharpness through the Pimax Crystal Light and the smoothness.

Some of that is absolute - DLSS4 made a big difference.  But also some of it, I am sure, is relative.  For me (and a few other folks I multiplayer with) MSFS2020 has become less sharp (especially some internal gauges/instruments but also, I am sure, runways and scenery when looking towards the horizon) and MUCH more stuttery.

I'm more than happy to post screen shots of my present settings and the addons I use if they of any interest to anyone, although, as we all know, everyone's system is different and there are multiple ways of achieving a similar result.

 

And my final hope...that SU2 doesn't wreck it all once it's released into the mainstream.     

Ryzen 7 9800x3D @5.2GHz; ASUS X670-P Motherboard; nVidia 4080 (factory o/c); 32G 5600MHz DDR5 SDRAM; Pimax Crystal Light VR Headset; Quest 3 VR Headset

After SU2, I'm finally starting to feel like msfs2024 was worth the money for VR.

Between virtual desktop and meta link (using quest 3), I'm now getting the best results with meta link cable, like with most of the other games.

I've set the headset to 90hz and 1.0x , using  server:asw.clock30  to lock ASW reprojection to 30hz, DLSS Quality & preset F or K, oxrtoolkit for Turbo-On and upping the res to roughly 3300 x 3500 via oxrtoolkit.  It's now mostly butter smooth all over JFK airport even with 400 LOD. Reducing the brightness or exposure and reducing contrast using OXRTK now seems to make a small but noticeable improvement to the over exposed skies

im using 4090 and 5800x3d

 

if you want to use a batch file to lock asw to 30hz, copy the following into a text file and change extension to .bat         Then run it just before you start the game or start flying

 

echo server:asw.clock30 > “TEMP.txt”

echo exit >> “TEMP.txt”

call “C:\Program Files\Oculus\Support\oculus-diagnostics\OculusDebugToolCLI.exe” -f “%~dp0\TEMP.txt”

del “TEMP.txt”

Edited by dogmanbird

  • Author

Clearly MS think there might have been implied criticism of them somewhere in the thread  - Microsoft Edge has blocked me from posting comments, topics or replies on this forum 😄

I've switched to Firefox...

Edited by AJZip2

Ryzen 7 9800x3D @5.2GHz; ASUS X670-P Motherboard; nVidia 4080 (factory o/c); 32G 5600MHz DDR5 SDRAM; Pimax Crystal Light VR Headset; Quest 3 VR Headset

  • Author
23 hours ago, AJZip2 said:

I'll qualify the statement shortly - and also come back to single prop aircraft

So - single prop aircraft.  Well, while DLSS4 seems to be working very well for me with the other types, with NO obvious visual aberrations, nevertheless for single props it is an entirely different matter.

The visual aberrations of, and around, the propeller disk of the single prop aircraft I've tried are dreadful.  Pretty much unusable dreadful.  The whole area jiggles and morphs around all of the time.  That is, interestingly, except for the splendid A2A Comanche.  While this model does seem to take a greater toll on performance than even, say, the Fenix A320, nevertheless there are no visual aberrations whatsoever - around the prop disc or anywhere else.

It's an odd one but presumably it is related to how most devs (Asobo and 3rd Party) get the prop disc effect.  I can only assume that A2A do it a slightly different way.

Edited by AJZip2

Ryzen 7 9800x3D @5.2GHz; ASUS X670-P Motherboard; nVidia 4080 (factory o/c); 32G 5600MHz DDR5 SDRAM; Pimax Crystal Light VR Headset; Quest 3 VR Headset

Su2 appears to have improved things being rendered differently / missing in one eye than the other, nearby graphic pop-ups, modest fps improvement and improved exposure a bit 👍

This is the most I've enjoyed it to date

Edited by dogmanbird

chrome also seems to be broken with avsim at the moment

Create an account or sign in to comment

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.