October 4, 201411 yr Mike, sure did. Ever since 2.3 I have been getting OOM's... and I never had to deal with them in 2.2. Hard to believe this issue has now slipped under the radar after two releases. Same here. Never had an OOM since 2.3. I have to be very careful about the airports I fly to now.
June 28, 201510 yr Will increasing my RAM from 8GB to 16GB help with OOM errors running Win 64 and P3Dv2.5?
June 28, 201510 yr Will increasing my RAM from 8GB to 16GB help with OOM errors running Win 64 and P3Dv2.5? Unfortunetely it wont help in the slightest.
June 28, 201510 yr Moderator Will increasing my RAM from 8GB to 16GB help with OOM errors running Win 64 and P3Dv2.5? Nope - the "memory" you are out of is virtual memory (VAS) which has nothing to do with physical memory. Google VAS or virtual address space for more info. Vic RIG#1 - I9 14900K MSI Pro z790 RTX 5070Ti 40" 4K Monitor 3840x2160
June 29, 201510 yr Will increasing my RAM from 8GB to 16GB help with OOM errors running Win 64 and P3Dv2.5? Texture = 512 (or 1024) will resolve most out of memory errors if you have a lot of add-ons installed at a complex airport and dense scenery area. Also be aware that some AI Traffic products may assign "real aircraft" to AI aircraft, this can cause extreme memory usage especially if the AI aircraft comes into scope. Cheers, Rob.
June 29, 201510 yr Texture = 512 (or 1024) will resolve most out of memory errors if you have a lot of add-ons installed at a complex airport and dense scenery area. Also be aware that some AI Traffic products may assign "real aircraft" to AI aircraft, this can cause extreme memory usage especially if the AI aircraft comes into scope. Cheers, Rob. Hi Rob I am using MT6 . Does this software use "real aircraft ?" If so can it be disabled ? MT6 can take quit a hit on VAS even from 0-15% at for instance Toronto/London so i use the traffic manager as well, but 100-200mb is not un-usual. I do sometimes have an issue where traffic is loading the screen about every one minut or so. Its quiet irritating I will try TML=512 when doing longhauls with the PMDG777 . Traffic is better than textures on those long stints Michael Moe Michael Moe
June 29, 201510 yr Texture = 512 (or 1024) will resolve most out of memory errors if you have a lot of add-ons installed at a complex airport and dense scenery area. Also be aware that some AI Traffic products may assign "real aircraft" to AI aircraft, this can cause extreme memory usage especially if the AI aircraft comes into scope. Cheers, Rob. Thanks chaps. That's what i thought. After my meltdown last weekend i reinstalled 2.4, but I've have subsequently uninstalled it and reinstalled 2.5. I'm adding things slowly and have my sliders midway apart from mesh and scenery complexity which is about 75%. Im running the 40' Phillips 4K monitor at native resolution, I'm thinking of dropping that down to 1080p, which I'm reluctant to do but keen to see if that helps somewhat.(I'm going to hate the visual result) I'm still baffled that with my previous 2.4 installation I did not have 1 VAS error, running exactly the same addons and LESS conservatively than i have been the last two weeks. I could use Aerosoft EGLL, with MT6 @ 30%, the 777 with external views, GSX, - not a single issue. Nothing has subsequenty changed in my hardware setup. Baffling indeed... Is anyone using any special utilities to monitor VAS or is the standard windows utility okay?
June 29, 201510 yr I will try TML=512 when doing longhauls with the PMDG777 Hi Michael, If you have a VAS monitor running during your long haul flights and you start approaching destination and see that you are getting low on VAS (or hear the FSUIPC chime) you can quickly change the textures from whatever value you had (i.e. 4096, 2048, 1024) down to 512 and you will recover a good chunk of VAS that should be plenty to complete the flight. Does this software use "real aircraft ?" If so can it be disabled ? No, not by default ... well at least I don't think it does (pretty sure it doesn't). Is anyone using any special utilities to monitor VAS or is the standard windows utility okay? I use FSUIPC, but there are others. Cheers, Rob.
June 29, 201510 yr you can quickly change the textures from whatever value you had (i.e. 4096, 2048, 1024) down to 512 Rob, where would you do this? Is that just the standard P3D UI setting for textures? I currently have this set at 1024 as standard anyway.
June 29, 201510 yr Is that just the standard P3D UI setting for textures Yes standard setting via P3D menu system. Obviously it's not "optimal" but if you're doing a 7 hour flight and on approach to destination airport and you'd like to finish the flight switching to 512 textures will free up VAS and allow you to complete the flight (in most cases, not all). Only caveat is that you need to make sure you have 200MB or so available VAS before accessing the P3D menu system ... if you get too close to the VAS limit you might NOT be able to change the setting before you hit OoM. I like to keep a 300MB buffer (i.e. don't exceed 3.7GB VAS usage). Cheers, Rob. EDIT: another item you need to be very aware of is how close your destination airport is to a region border because if your close then a new region will get loaded and that can be another source of rapid memory consumption ... see here:
June 29, 201510 yr Somethings to consider with OOMs and P3DV2 (assume you mean V2): 1. Screen resolution (the more resolution the more the impact on VAS) 2. Texture sizes (1024, 2048, 4096) 3. Shadow/HDR settings 4. Scenery setting (I can't run the sliders all the way to the right) 5. 64bit Win7 or 32bit Win7? 6. GPU VRAM (I've used 3.8GB VRAM - the more GPU VRAM you have the better) 7. Clouds will increase VAS usage (especially 110mi distance, I usually set to 80mi) 8. 3rd party Aircraft will have a HUGE impact on VAS usage 9. 3rd party AI traffic products have a huge impact on VAS 10. 3rd party airports will vary A LOT on their impact on VAS 11. 3rd party scenery products like FTX Global/Vector will impact VAS 12. LM have acknowledge some memory leaks and will be fixing for 2.05 update due out this month (Jan) Rob Thank you Rob this information is very useful for me. If i ever encounter OOM again now i know where to look Yes standard setting via P3D menu system. Obviously it's not "optimal" but if you're doing a 7 hour flight and on approach to destination airport and you'd like to finish the flight switching to 512 textures will free up VAS and allow you to complete the flight (in most cases, not all). Only caveat is that you need to make sure you have 200MB or so available VAS before accessing the P3D menu system ... if you get too close to the VAS limit you might NOT be able to change the setting before you hit OoM. I like to keep a 300MB buffer (i.e. don't exceed 3.7GB VAS usage). Very useful tip , specially if you are running GSX. When ever i land at any airport i like to call GSX fallow me to guide me to the gate when I'm not familiar with the airport. Mr Leny CPU I7 8700K @ 5.0GHz , MOBO -Asus Maximus X Hero (WiFi AC),GPU - GTX1080 TI , RAM - CORSAIR Vengeance RGB 16GB DDR4 3600MHz SSD -Crucial MX500 1TB (P3D Install Only)OS- Samsung 960 EVO 500GB (Window 10 Pro 64)
June 29, 201510 yr On my setup I have unticked all default base scenery where I do not fly... I used the following link to identify the regions : https://msdn.microsoft.com/en-us/library/cc526966.aspx 5950x3d 5.4-5.7 GHz - Asus ROG 870 Crosshair Apex - GSkill Neo 2x 24 Gb 6000 mhz / cas 26 - MSI RTX 5090 Gaming Trio OC - 1x SSD M2 6000 2TB - 1x SSD M2 2800/1800 1Tb - Corsair 5400 case - Corsair 360 liquid cooling set - 3x 75’ TCL tv. 13600 6 cores @ 5.1 GHz / 8 cores @ 4.0 GHz (hypterthreading on) - Asus ROG Strix Gaming D - GSkill Trident 4x Gb 3200 MHz cas 15 - Asus TUF RTX 4080 16 Gb - 1x SSD M2 2800/1800 2TB - 2x Sata 600 SSD 500 Mb - Corsair D4000 Airflow case - NXT Krajen Z63 AIO liquide cooling - FOV : 200 degrees My flightsim vids : https://www.youtube.com/user/fswidesim/videos?shelf_id=0&sort=dd&view=0
June 29, 201510 yr Yes standard setting via P3D menu system. Obviously it's not "optimal" but if you're doing a 7 hour flight and on approach to destination airport and you'd like to finish the flight switching to 512 textures will free up VAS and allow you to complete the flight (in most cases, not all). Only caveat is that you need to make sure you have 200MB or so available VAS before accessing the P3D menu system ... if you get too close to the VAS limit you might NOT be able to change the setting before you hit OoM. I like to keep a 300MB buffer (i.e. don't exceed 3.7GB VAS usage). Cheers, Rob. EDIT: another item you need to be very aware of is how close your destination airport is to a region border because if your close then a new region will get loaded and that can be another source of rapid memory consumption ... see here: Thanks lots Rob.
July 1, 201510 yr Good evening, Maybe this could be of interest for some of you: http://www.orbxsystems.com/forum/topic/99769-my-oom-issued-drastically-reduced/ Cheers, Carsten Carsten U
July 1, 201510 yr Good evening, Maybe this could be of interest for some of you: http://www.orbxsystems.com/forum/topic/99769-my-oom-issued-drastically-reduced/ Cheers, Carsten Project Lasso affects Work Set Memory - Not 4GB Virtual Size - this is 32BIT Application Limitation. There is no way out of it. LM has to do some VAS cleaning up via their code, there is no other way. Project Lasso does completely different. I even posted in depth about this over here about Project Lasso http://forum.avsim.net/topic/470612-any-ideas-on-how-to-reduce-my-vas-usage-sli-users/?p=3257856 Forum Mods - it will be cool to make a sticky about Project Lasso - majority of people are interpreting the application use in a different manner. It trims Virtual Size of the Working Set Virtual Memory not Virtual Size How I Evaluate Third Party Sim Addon Developers Refined P3Dv5.0 HF2 Settings Part1 (has MaddogX) and older thread Part 2 (has PMDG 747)
Create an account or sign in to comment