Hello
I’m trying to fly freely over Tokyo with Pimax8kx and shoot. I want to use FSLTL.
(I can’t list the video for some reason, but you can follow the link from my profile)
It has 5800x3D (x3D is omitted below) and 32GB of memory.
After the 3080ti and 1080TI, we introduced the 4090 with high hopes, but not as much as we expected.
As of 4090, it’s a financial situation that has already lost one Concorde,
I’m considering installing either the 7800 or 7950.
This problem is maximally annoying.
Currently, the memory usage reaches a maximum of about 29GB, but it is often short-term and stable at 25GB or less for the time being.
Regarding memory, keep the capacity at 32, increase the speed, or reverse the problem selection.
What do you think?
The 4090 is a disappointment so far, and there are still videos from the 1080TI. Filming with the 3080Ti is much older than that of a helicopter.
However, since I learned how to shoot while displaying the values of rdrCPU, appGPU, and FPS in real time with Openxrtoolkit, I will try to release videos at 4090, which is disappointing.
If you are using up that much memory, 64GB is the way to go. 7800x3d has great results, if money is an issue. Get a 7800x3d. But you do need more memory. 64GB Ram
thank you
I flew under various conditions and collected data.
(Fortunately, rain clouds came and passed us on the way. I think it was a good test.)
Memory is the third green graph from the bottom.
It is stable around 20GB.
Do I still need 64GB?
If you make it 64GB, will you be able to use it more advantageously?
And here is a graph of load data from Openxrtoolkit for the same flight.
This software is for VR, but it leaves a data log with numerical values.
(5800x3d+4090)
In general, it clearly reflects the load of flight conditions. (I checked it against the video recorded at the same time)
The load of data reading is large immediately after takeoff, the load is low at high altitude and low speed such as landing, and high speed movement at medium and low altitude is severe, especially low altitude flight at supersonic speed is the worst and appears as a spike.
You can also see the load of foobar (music playback software), but I think you can find something interesting about the load that FSLTL brings.
There is certainly an increase in load on the GPU, but you can see that there is an extremely drastic increase/decrease in that of the CPU.
I hear AMD is affected by memory speed, is it better to choose 32GB of 5600 instead of 32GB of 6000?
I think both should be good choices.
So maybe it’s a stupid question on my part.
I don’t really understand it, so if I’m only using 20GB, I think I have plenty of memory left.
I forgot to write
When the value of APPCPU (red line) is high, the audio also has severe noise.
ATC can even become a slow talker.
My 5800x3D seems to be the limit for this load.
My FlightSimulator.exe uses around the same - Between 28-30gb of RAM when flying.
AIGTC occupies another 3gb & Pilot2ATC another 2gb… it adds up! Hence whey I went from 32gb to 64gb
I am learning from this thread.
I also set the ultra setting to the outside of the field of view, but I feel that the stutter when I turn around and the place where I passed a few minutes ago is redrawn again.
I have a question and would appreciate it if you could answer it.
As a countermeasure to this problem, if a large amount of memory is loaded,
1,msfs and Windows will use the memory effectively without permission. (I also read information by Mr. Baracus250 that it starts creating a page file when it exceeds 16GB.)
Is my understanding correct?
2, Move rolling cache to RAM disk
(I have a rolling cache deployed in NVME, but setting it up was a lot of work to enclose the map.
The RAM disk disappears when the power is turned off.
Does it mean that if only the settings are left in MSFS, they will be automatically expanded after each boot?
If the effect of rolling cache is the biggest factor for huge RAM, it worries me.
I’m worried if it fits my personal situation.
In addition to the MSFS map, I have introduced a huge metropolitan area MOD data for Tokyo. Would this fall within the scope of the RAM disk functionality? )
There is a way to set up the ramdisk to run automatically after reboots. I don’t run it this way. I just recreate a file on the ramdisk named cache after a reboot. Then msfs always sees it. But, then msfs will default the cache size to 8GB, I usually run 16. So something else needs to be changed each run. I find it to be a lot smoother when panning.
thank you.
If this happens, there is no choice but to fly the Concorde.
After all, the 7950x3D and b650proRS have already been shipped to my house.
I searched for a 64GB, 6000, and hynix chip, but I could only find a 5600 cl30 one in Japan.
I’m still looking, but 5600, yeah, I think I’ll go around here.
Is this a little weak?
However, I don’t have as much budget as you do, and Japan seems to be becoming a country that many manufacturers don’t care about.
In addition, I will read this carefully and would like to have some kind of report.
I’ve finally had a chance to start tinkering, and man, I’ve been getting some serious undervolts going. I’m only about 40% of the way, got the first 7 cores stable, but could definitely fine tune them a bit more. Core 0 is at -60, core 1 is at -57, core 2 is at -52 and the trend keeps on going. Still have to finish with 6 & 7, but the highest I’ve got set right now is -45. I may have won the lottery…or it’s the RAM. Either way, I’m seriously impressed.
I have been mixing in MSFS benches as well just to make sure there aren’t any stability issues where it counts. I’ve noticed that the further down the list I go, performance (FPS) increases become more marginal, however, where dips used to be, they are far less frequent. My two test scenarios are both in the PMDG 737. One at RJAA and the other at KJFK. TLOD at 300, the rest at ultra, and both have addon scenery. This has also been without AI traffic. KJFK is the hardest to run, but I’m delighted that where before I was getting dips on the takeoff roll down to 55 (with FG) I now see no lower than 64. Really looking forward to tuning the RAM when the under volting is done, since it’ll help out with the lows.
The most interesting thing about this has been seeing just how stable it’s been with such a huge undervolt. I could definitely run cores 0-3 at -60, but kept them higher just for increased stability. I have had zero BSODs and only one failure to load windows throughout the entire process so far. I like warm fuzzy feelings, and there appears to be plenty of margin.
Average CPU temp has ranged from 61-70, with it settling around 57 while in the sim.
I also tried a PBO limit of -150. While I do see a slight benefit, I’ve opted to get rid of it. The reason is because I noticed that cores still dipped to 4080Mhz. Even though with it in auto, I see some cores drop to the 3’s, my overall frame rate is higher. While a higher frame rate doesn’t mean much if there is a bunch of stuttering, I’m seeing a fairly consistent frame time. I may have to retest with a higher TLOD. If I could get the cores to boost to 5.1 and stay there, it may be a different story, but I’m hoping a RAM OC will help with the lows. I just find it strange that the cores would still dip with such a large temp margin. You think if i ran +5 or 10 over the severe undervolt that it’d have a bit more juice to maintain 5.1? The only thing to worry about then is temps…. But those have been fine, and boosting to 5250Mhz has had no issues. I dunno. It’s been fun this far!
I have the ramdisk set up as fully transparent, hands off, I really don’t like a bunch of manual steps before I can even start the sim. I turn the computer on and click on the MSFS icon and I’m ready to go. All of the extra programs etc are automatically started.
I like to save the repetitive button clicking until I’m in the cockpit following checklists.
Using Imdisk it’s super easy to automate.
1…Create a directory on disk, I called it “Cache”. Configure Imdisk to initialise from this directory.
2. Set Imdisk to start at boot, also enable AWE physical memory otherwise Windows might start swapping your cache out to the paging file which would be terrible. 16600MB is a good size for the ramdisk if you want a 16GB cache.
2. Start MSFS and create the 16GB cache on the ramdisk using the general setting>data screen as usual, but do not start any flights.
3. Exit MSFS and then copy the cache file it created from the ramdisk to the directory you created earlier.
4. Now when you reboot you can check the ramdisk restarts with the empty cache file in it. On my system it takes about 5 seconds for the 16GB cache file to copy to ramdisk so it should be there by the time you look.
5. Load MSFS and check it still has the 16GB cache configured. All ready to go!
You can set Imdisk to save the cache out back to disk to preserve its contents over reboot. I deliberately chose not to do that, I like the cache starting clean every time, probably reduces risk of bad data leading to repeated CTD if there was some kind of bug. Also it means I can’t forget to reset the cache every time there’s an update, since it’s always reset.
My experience with Ramdisk FWIW (although after reading your setup there I think I will change to try it that way).
I have only been using a few days but also have it repopulate the RAM on boot up, but I was using a snapshot of the RC after a flight (fist flight) by using the “Synchronise Now” button to write that ram state to an Image, which ImDisk then uses to restore the Ramdisk on Window boot up.
It was all good but last night suddenly I had terrible performance in PG cities with serious stutters and lurching frames, especially when flying low. Nailed it down to the RC needing to be deleted/recreated. That solved it. So does seem like if the contents on the RC are somehow different to what it THINKS is there from previous session shut down (maybe there is some kind off index file it stores somewhere else that points to different ‘parts’ of the RC for different geo-locations??) then it get’s all in a mess.
My only question is:
I thought what was loaded into ram is an IMAGE, not an actual file?
Either way, I will try and adjust my setup to load contents of folder – containing the empty .ccc file, which actually IS still shown as 16gb (in bytes) when you create it fresh. I suppose it’s ‘reserved storage’ with no actual data? And I will remove that TEMP file.
An image in this context is just a regular file that stores the contents of a disk, ie. has the on disk format. You can copy it around and do what you like with it.
It’s not empty, it’s got lots of zeros in it I expect. And probably some metadata too but I haven’t looked.
I think it’s stored as the full 16GB on SSD so it’s a little bit of a waste, but compared to the install size of MSFS it’s peanuts. I don’t know if windows even supports sparse files.
Yes the AWE setting is on one of the tabs in Imdisk.
