xsever

Yeah it was a pretty good deal. It was used mind you but in excellent condition. It was going to be either than or a 5060 Ti 16GB for $550 so I went for the 3090.

When I upgraded to MSFS2024, I realized that my 3070 with 8GB of VRAM was not going to cut it even at 1080p and low settings. I was running out of VRAM at the gate at Aerosoft Frankfurt. I ended up selling my 3070 for $210 and buying the 3090 for $480. That was an excellent upgrade for my use case.

I'm also using 566.36 with my 3090 running both MSFS2020 and 2024. This driver is known to be the most stable for 3000-series and older cards . The drivers that came after it, although they provided DLSS improvements for 4000-series and 5000-series cards, proved less stable for 3000-series and older cards. I tried many newer drivers that would eventually end in a sim crash and I would revert to 566.36 and it would deliver a stable and crash-free experience. Since I don't rely on DLSS and use TAA instead with 24 GB of VRAM available, 566.36 is ideal for me.

I found 2024's settings when it comes to frame rate cap and dynamic settings to be a huge improvement for medium hardware compare to 2020 where these features did not exist and you had to rely on an external frame limiter.

Ok thank you for replying and providing some insights. Will definitely contribute to this thread in the future. I had my third flight with the plane yesterday and I made sure not to go too fast through the FMC especially with SIDs and STARs and I didn't get any WASM crash. It was the same route as the route from the day before when the crash happened. I also wanted to know if the latest version 1.0.8 fixed the WILCO CPDLC message bug reported here: https://forum.inibuilds.com/topic/35823-cpdlc-wilco-not-working-on-the-hoppie-network-v107/

double posted for some reason. Please delete.

I cleared the wasm folder after updating to 1.0.8 and had my first flight with this version yesterday without any problem. During my second flight today, as I was programming the FMC to plan for the descent, I had my first ever wasm crash with this plane. Anyone else with the same problem?

Does the latest version 1.0.8 fix the WILCO CPDLC message bug?

Which FSR frame gen mod did you use with your 3090? Was it dlssg-to-fsr3 by Nukem9?

I have flown a couple of flights so far with the 3090 and here are my findings. After swapping the 3070 with the 3090, I switched from DLSS Performance and Secondary Scaling = 2.0 to TAA and Secondary Scaling = 1.0. I also increased texture resolution from Low to High and most settings are now at High or Medium. I am still optimizing with these as we speak to ensure I can benefit from the highest settings possible. Frame rates remain locked at 30 FPS using the sim's frame limiter, dynamic settings, and AutoFPS while lossless scaling enhances it and locks it at 60 FPS. Smooth sailing so far. In Aerosoft Frankfurt EDDF while on VATSIM with a ton of traffic, the FPS would drop below 30 in MSFS2020. Now in MSFS2024, that is never the case as the FPS remain locked and stable at 30 which is a testament to the optimizations of MSFS2024. Regarding VRAM usage, with Aerosoft EDDF while on VATSIM with a ton of traffic, the highest VRAM usage I saw with the iniBuilds A300 was 10.1-11 GB. During cruise, it's between 8 and 9 GB. In TaiModels Cairo HECA, VRAM usage at the gate is 8.5-8.8 GB. From these datapoints so far, 12 GB will definitely not cut it with these settings because the sim only sees 10.5 out of 12 GB. I still need to test with the iniBuilds A350 to see if it will encroach on 16 GB or not but so far, I am happy with the 3090 for $480 rather than paying $50 more to get the 5060 Ti which is weaker but newer. Regarding GPU usage at 1080p, the highest I've seen the 3090 is at 60% on the ground and it averages 40-50% in cruise. I hope these datapoints help inform others in their decision to upgrade their GPUs.

I pulled the 3070 out and plugged the 3090 in and literally had 15 mins to test things out before needing to go out. I loaded the 2024 version of the iniBuilds A300 Premium at gate A20 at EDDF and with DLSS Performance and low texture resolution, I was at 8.7 GB VRAM usage. When I switched to DLSS Balanced and medium texture resolution, it went up to 9.8 and I think I saw 10.1 briefly. As I'll have way more time tomorrow, I'll test with TAA and texture resolution and high and tweak the rest of the settings and see how it goes. I must admit it's funny how the 3090's usage does not exceed 50% at 1080p 😁. It's the most overkill ever if it weren't for the much-needed VRAM. I'll keep you all posted.

Well, I made up my mind after going through all these responses here and on Reddit and doing my own research. I went with an excellent condition 3090 for $480. I will report back here once I've had the chance to test it in my machine and see how well it works. The seller was kind enough to offer me a full refund if it doesn't work out and I want to return it. Fingers crossed. And yes you're right. I should be able to seel my 3070 for $230-250 which I find funny because I bought it 2 years ago for $200! Thank you for this additional insight and data point. I'm now sure more than ever that 12 GB was never going to cut it with MSFS 2024. I will report back and let you know how much VRAM 2024 is going to consume with my setup so you can then decide whether 16 GB will suffice or not.

I currently have 32 GB. Should be enough no? I don't think I've seen my RAM usage exceed 16 to 20 GB.

Thank you for the insightful information. I assume you're run 4k so can you recall your VRAM usage with the 3090 and now with the 5090?

What resolution are you running, which planes do you fly, and what's the highest VRAM usage you've seen?

What resolution do you run and what's the max VRAM usage that you have seen with your 3090? I'm looking into upgrading my 3070 to 3090 and would love some insights. Thanks.

Thank for your valuable feedback and for confirming that 12GB will not be enough. Regarding DLSS, I currently use DLSS Swapper to stick with 310.4 which is the latest version compatible with 3000-series cards. As for frame gen, I find Lossless Scaling to be superior to native frame gen. I was even surprised to find people online saying that they prefer Lossless Scaling over native 5000 series frame gen. At what resolution do you run your 9070XT and what's the highest VRAM usage you've seen?

Hello gents, I'm currently running the PC specs in my signature below: 14400F, 32 GB DDR4 RAM, RTX3070 8GB, 3x 1080p 60Hz monitors with MSFS2020 and it's fine with all the airliners I fly using AutoFPS, Lossless Scaling, DLSS Performance and texture resolution set to medium. I lock the FPS at 30 or 35 and use Lossless Scaling to get 60 FPS. I never run out of VRAM. I tried MSFS 2024 with the PMDG 737 and texture resolution set to low and I was able to scrape by without exceeding VRAM usage. It was fine for my needs. When I tried the iniBuilds A300 at Aerosoft Frankfurt, VRAM was already at 9.5 GB at the gate and the sim wasn't playable and a crash occured afterwards. I'm looking to upgrade my GPU to one the below options and I'm wondering if 12 GB of VRAM will be enough for my setup and needs or do I need more like 16 or 24? RTX 3080 Ti 12GB VRAM for $435 RTX 3090 Ti 24 GB VRAM for $480 RTX 5060 Ti 16 GB VRAM for $535 $535 is the ultimate most I want to spend and I want a GPU that will be enough for all the airliners in MSFS2024 including the notorious VRAM eater the iniBuilds A350. What is your recommendation and why? Thank you in advance.

ummm, I thinkyou need a 5090 for 3 4k TVs.

You're a saviour! Thanks a lot for pointing that out. I didn't know despite reading the documentation. Now that it is working, I noticed now that after a couple of minutes of using the web fmc, the input of data through buttons becomes very lagging and delayed. If I refresh the page and the script re-executes, the lag is gone for a couple of minutes and then it's back. Would you happen to know why that is? I faced a tiny bit of lag with other web fmcs but nothing this major.

I tried so many things and nothing worked but 30 mins ago, I was able to resolve the issue and I think I did it by copying the global.js file that was in Documents\LorbyAxisAndOhs Files\WebPages and pasting it in Documents\LorbyAxisAndOhs Files\WebPages\a300 When I did that, the screen appeared and everything worked like a charm. I got this idea by analyzing the contents of the index.html file and seeing that it calls for the globa.js file so I placed it in the same directory and voila. Could that be it or am I imagining things here?

But the config.js file for the iFly 737 Max is structured the same as the A300.

I tested the iFly 737 web FMC and initially the same problem happened where the buttons worked but not the screen. I went into the Aircraft automated scripts and selected IFLY_737MAX_CDU (Repeating and One shot - Beginning) and added it and then the screen was displayed all of a sudden. Problem solved. Now I can't find a similar aircraft automated script for the A300. Am I missing it or what is actually happening here? Is this because I'm using MSFS2020?

I had some time to dig deeper into this with the hope of diagnosing the problem. I first assigned a button to "2 (>A:CAMERA STATE, Enum) 2 (>A:CAMERA VIEW TYPE AND INDEX:0, Enum) 22 (>A:CAMERA VIEW TYPE AND INDEX:1, Enum)"; and when I press it, I get a camera view that shows the CDU. Ok so that's good until here. I then used the mouse cursor position feature in AAO to get new x and y values that match my 1080p monitor and I then updated these values in the config.js file and saved it. I thought this would fix the problem but it didn't. I can still manually pop out the window fine, it is called WASMINSTRUMENT for sure, the buttons work, but not the screen. Is there a way we can modify the config.js code whereas it relies on a manual pop out of the window rather than popping it itself? I'm asking this because when I call the index.html file and the buttons work, the actual popping of the CDU window does not occur. Thanks.

Thank you for the response. The first thing I noticed in the code and I double-checked is the "WASMINSTRUMENT" and it matches 100%. I must clarify that I never use the pop-out manager to pop out the FMC. I only did that as a test to see if it's popping correctly. As you said, I am going to do some trial and error to figure out all these variables. I will revert back. The funny thing is that I've been doing all of this in MSFS2020. I launched MSFS2024 which is still relatively vanilla and tried this and I got the same result. The FMC screen remained black.