64GB was the high lod minimum ram spec from when I used to do it pre SU5 (I flew everywhere in a minimum tlod 7.00). I bought a second gskill samsung b-die kit just to do that, and bring me to 64gb.
Not yet. Worried it killing the SSD (expensive 4tb 7100mb/s one!) or at least severely shortening itās life.
I think I would like to get some proper EXPO ram (2 x 32) and allocate some of that as a ramdisk, and auto-assign the cache to that. Sounds like optimal solution, but I am still not sure if safe to try and push my CPU and board to extremes due to the āAMD Fire Fiascoā and last time I checked that RAM I wanted (GSkill Neo) that is exactly on the QVL list was not in stock. And the price is a bit eye-watering. Running Kingston Fury Silver now but took 2 sticks out (I paid for 64gb on this build, but running only 2 x 16 now to be stable at 6000).
Also I just know that a week after I buy more ram, a new revision will come out that is better 
And OK, H145 - booking it now. Hey, maybe we could get a free one if we synchronise an accident. You go first then Iāll fall off a roof when they are nearly overhead to the hospital. You jump out over the sea (donāt worry itās soft!) and wave goodbye to the pilot! Sounds like a plan?
YES!!! This, this is what Iām doing. I have the gskill 2x32 cas30 6000 kit, they are really good. Board to expo no probs and that kit has very high compatibility, I donāt know that it wonāt run on any board @DensestSnail693 has also been doing doing this a long time with ram disk.
Alright I will scoot around and see if stock has returned yet!
I may have to 
the ram i got initailly was XMP and not EXPO and didnāt have the best compatibility, so i got 32 GB at 5600 for the mean timeā¦been putting it off, but i guess itās time to upgrade to 64. In that case, should be able to put a few more gigs of space on the RamDisk for the rolling cache.
I think back in the day that meant something but modern TVās and monitors are well used to upscaling/downscaling so damage is unlikely. You get the option to test and if thereās a problem you would normally get a not supported message ā¦ However you are right, if still under warranty and something (even unrelated) goes wrong there could be a flag showing you had used a higher than spec res at some time and this could possibly void it.
Thinking about it, thereās no reason to suggest lowering LOD could help a struggling gpu (the cause of most CTDs), if anything it just increases the imbalance with the cpu or rather it increases fps thus making the gpu work faster.
Heck yes!!! It does work really darn good
Not sure that wonāt increase latency when flushing. As I mentioned earlier I would rather have 4GB than the default 8 but that doesnāt stick after a reboot (maybe it does if you load an image but I prefer my RC to be clean and fresh)
You do understand how this CPU works correct? That if MSFS is not in focus your performance will drastically drop? Also if you use head tracking you need to understand the relationship between your head trackerās resolution and your monitorās refresh rate and lock frames to an exact multiple that you can maintainā¦otherwise it will appear to be a stutterfest.
trueā¦unless youāre using gsync
Yes sure, I understand the theory, but what I see in practice doesnāt quite match up to what I think sometimes, or to some of the things you wrote there or that I gather from other posts.
My system can manage (and my target for now is) 50fps, plus FG to make 100 in DX12. But when I set my screen to 100Hz, it was nowhere near as smooth as it is at 120 or 144Hz. I am on 120 now and that seems the best. Maybe itās because the adaptive refresh of the screen (? itās Freesync, not Gsync) works better with some headroom so it can go a little over, but ramp down better to match frames? All I know is with 100Hz and 100fps cap in NVCP there was a lot of tearing which totally went away with 120Hz. Now itās just the terrain stutters etc that are too often but please see the bold paragraph below coz I have a theory why.
The game is in focus, of course. And I see that as soon as another window is then it drops, yes. Actually even if I bring FSRealistic to the front on the same screen, that has 120 count (max refresh of my screen) in the corner of itās window while FS then has 60.
I donāt think I have control over that? Itās Tobii 5, and there are barely any settings at all that I can see. What do you mean by this? Itās just moving the camera freely so as long as frame-synch is working I donāt see what input resolution has to do with it? Not being awkward here, but I really donāt know - or know where I can even change this.
Also as there are so many people here that know everything, it would be REALLY helpful if I could get an answer to a question I posted in a couple of places that still nobody has answered. Does it mean no-one knows?
Itās in this very thread here:
And originally asked here: (4090 + DLAA + Frame Generation = WOW - #354 by Baracus250)
I think this would totally solve my issues. I just need FS to only deliver 50fps, not 60 or more.
At the end of the day I am after either 60fps in DX11 or 50 in DX12 with FG. I find 50 with no FG is not comfortable when looking around with the head tracker, unless of course there is some other settings or combination I missed that can smooth that out. It was same with the TrackIR I was using until a few days ago (I āupgradedā to Tobii 
)
There are too many threads on this topic so itās all a bit fragmented really hehe
I donāt think GPU was struggling though - it rarely gets into the 90%'s, it was struggling to draw in different PG LoDās so lowering that did help. Anyway I think the actual CTD was unrelated as it happened again now in a non-PG area (but in the H145, which is quite heavy on calculations) and when I alt-tabbed out to the browser. I think it was the latest .net update I was asked to install by Win11 today PLUS the new HFS software (Haptic Seat) version crashing. I have gone back to the old version and letās see!
So what res would you suggest? - bearing in mind this is not 16:9 or 16:10 screen. Itās 21:9 apparently.
What is the refresh rate of your monitor set to? Thatās the first question. You want to lock your frames to an exact multiple of your refresh rate.
So if you are running at 120Hz refresh rate on your monitor in DX11 you would set Vsync to on in the sim and lock your frames to an exact multiple of the fresh rate that you can maintain. The options available to you in sim would be the refresh rate 120FPS, 1/2 refresh rate 60FPS or 1/3 refresh rate 40FPS. The lower in FPS you go the less fluid your head tracking and sim will be but a locked 40FPS is pretty ā ā ā ā smooth and leaves headroom for MSFS.
DX12 gets a bit different because Vsync in sim does not work. More than likely you will also be using FG. You must lock frames via the Nvidia control panel. To do so you must turn Vsync on in Nvidia control panel, and set you max frame rate in the Nvidia control panel. When setting max frame rate in the Nvidia control ensure it is set to an exact multiple of refresh rate. Again if your monitor is 120hz you will want to set your frame rate to a direct multiple of 120. That will be either 120, 60, or 40. The caveat here is that your in game (MSFS) framerate is going to be exactly 1/2 of your target locked framerate in the NVCP and FG will effectively double that framerate. So if you set you target frame rate to 120Hz in the NVCP in DX12 you will want to make sure you can maintain a locked 60FPS in MSFS. If you cannot maintain a locked 60FPS in MSFS, then you would set your target in NVCP to 60FPS and so on.
If you are not maintaining near an exact multiple of refresh rate and you are using head tracking panning views is not going to appear smooth.
A 240HZ monitor can help you gain a little better performance because you can get more creative playing with multiples because you can now set 80FPS as a target.
Is this an nVidia thing? Because Iāve got an AMD gpu and I use DX12 and Vsync on at 100% for 60 FPS on a 60Hz display.
I do not own an AMD GPU and have no idea if Vsync works in game. My guess is, if Vsync does not work in game for Nvidia on DX12, it does not work for AMD in DX12. Is your FPS locking at 60FPS?
Yes and it locks at 30 if I set it to 50%, as expected.
Again that is the theory, and I spent hours trying every combination of everything in DX11 and DX12. So, as I cannot guarantee 60fps (in New York for example) but it can do 50, then by those rules setting 100fps cap in NVCP and 100Hz screen should be correct. But I am telling you, that it was way better with 120Hz screen. Donāt know why, but it is for me.
Why doesnāt DX12 allow vsync in game? Do you think it will come when itās out of Beta?
My theory is, that even with FG on, the CPU is still working as hard as it can (because you canāt limit it in MSFS) and any extra frames are just being dumped internally by the 4080 to show the capped limit. I think this because if I run DX11 with 50 limit, it is so so much more consistent. No hitching, no pauses. If I try to push 60 in DX11 or leave it uncapped then it behaves like it does now in DX12, so I am certain that ābehind the scenesā the limit of what the game engine is REQUIRED to output is NOT being respected simply by having FG on and a cap outside of the sim.
I would stick with DX11 but it is just so much more fluid and āsnappyā with 100 than 50 for the kind of flying I do that I find it hard to accept āonlyā 50 now I have seen the power of FG (I donāt notice any artefacts so that really does not bother me).
With nvcp I lock 40fps @120hz and no vsync, gsync. This is true.
One other point - I donāt know, but I thought the screen refresh was VARIABLE (like, per screen redraw it can offset or change the timing)ā¦ so it can go UP TO the max refresh but can adapt down as needed. Pretty sure that is what Freesync does, no? So I could still set 80 target and 120Hz screen (although itās not exact half) can still match that, as itās less than the max available.
Your theory is wrong. In DX12 if you set your max framerate to 120FPS with FG, MSFS will limit your max frames to 60FPS if you can maintain it. So in MSFS itself your FPS will be 60 or less and with FG enabled your resulting frames will be double of that in sim (120fps or less).
Also if your are trying to use freesync or gsync, disable and set as above and see what you get. I use neither and am locked at 120 with FG and the sim is butter smooth. If my in game frames drop to near 50ā¦stutters. Itās a balancing act.
Maybe struggling was the wrong description, more like running away with itself although you donāt mention the OC / Overheating notice so maybe thatās not it.
As for that bespoke resolution, my screen is a comparitively old, comparitively large 32" 16:9 native 1920x1080 which showed up every filtering glitch even when using TAA and rendscaling. However I added 50% resolution in both directions giving a slightly blurry 2880x1620 and then used Nvidiaās Image Scaling (NIS) to make it nice and crisp again. An important point is that the DLSS quality setting actually renders this at my native 1080p and end results are very similar to DLSS + DLAA at native, this was not an option or was unbeknown to me when I first used my method so now I feel thereās little to be gained by using it instead of ā¦ Therefore for warranty flagging reasons such as you highlight
I am no longer advocating my method so itās at your own risk.
Although it really shouldnāt be a problem (and saying that Iāve never actually tried on an ultrawide).