stefanwa

From their Discord. So maybe we should all give the new vectoring system another try! **Minor Patch 1.8.1.Experimental** ```🐞 Captain's Mistake * I forgot to flip a 0 to a 1 and almost all of the new Vectoring functionality was gated out of the last patch. Our testing process missed this because the resulting output was close enough analytically that it appeared to be working, even though it silently failed. Whoops! Sorry about that. * The Bad News: is that this entire time the new vectoring system was only half working (no wind compensation, too many vector instructions due to the refactored system never initializing correctly, etc) * The Good News: I swapped out that nasty 0 for the 1. All the new functionality is actually working now! The new vectoring system should now be fully operational. * As this is still WIP issues may still be present but the hope is now all the claims made in the previous patch notes will function. ✈️ Sequencing * Continued work on the sequencer based on user feedback. * Planes should be spaced better when arriving at airports (spacing based on min speeds/airframe/traffic conditions) 🛫 Traffic * Fixes to some traffic departure time issues * Further blocked traffic fixes - crossings and takeoffs * Better management of player pushing back into path of traffic Safe guard to slow traffic down if they taxi to close to aircraft in front ⚙️ Improvements * Map voices to tail number prefixes by country for GA / Bizjets (or any aircraft without a airline based callsign) * Further voice parsing fixes * Updated Airline and AIRAC data 🛬 Ops Updates KATL, GVAC, KMDW, VTSG, ESMT

Are you using this software? https://www.ddsconverter.com/ Thank you!

Try the Kodiak updater application in Windows installed with the Kodiak.

Maybe some „brains“ will also manage to get DLSS4 working on older cards like it was with FG on 30xx cards?!

How did you sort it? Have the same issue. Thanks

I got the 4070Ti Super recently and it works really well for me using a 2560x1440 monitor resolution and upscaling to 1.78x, DLSS and FG.

With DX12 and FG, is there an advantage using RTSS to limit the frames (60 Hz monitor here) over limiting using the NVCP? I do limit it with NVCP right now and Vsync in NVCP on. Thanks for suggestions!

Oh, so we are talking about the same thing! 😉 I am using the latest 0.7.3. I only copied the contents of FSR2FSR3_220.zip to the MSFS folder. Enabling fake NVIDA GPU (to play aorund with different settings) also works for me via the zip file or by setting it to "true" in the fsr2fsr3.config.toml file.

I think we are talking about 2 different mods. I was referring to the leaked FSR2FSR3 mod which also works for AMD cards mentioned earlier.

I think it works for me using 220 Version, simply copied the files to the XBoxGames MSFS/Content folder. It crashes when enabling FSR2(3) or changing FSR modes, but after restarting MSFS it seems to work. I get way more FPS using my RX5700 card, but image quality is decreased and some ghosting, which is expected.