Drazkul Posted April 6, 2019 Share Posted April 6, 2019 Hi, Since SP1 has launched after a short while during a flight X-plane pops up a box saying that its running out of memory and scenery loading has been disabled. It never used to do this before SP1 and I could fly for as long/far as I wanted. At first I thought that it could it could of be a corrupt installation when I first installed the SP1 update so I did a complete re-install of both X-plane and all my ORBX scenery packs. Sadly I've had building work in my house since SP1 has been released so I hadn't had a chance to test it till today. I did two flights taking off from Coventry airport and heading towards Birmingham. The first one ended up with X-plane giving me the memory error before I'd fully cleared Coventry. I then dialed back my graphics settings to the ones recommended in this forum by John (previously I would run with the sliders completely on the right except for reflections and had shadows on scenery and draw parked planes off - though the last two are still off). On my 2nd flight it lasted a little longer but still got the memory error before I made it too Birmingham. My only other none X-plane scenery I have is a San Francisco ortho and overlay. My PC specs: I5 6600 1070 8GB RAM 16GB RAM WIN 10 I run X-plane 11 in 1910x1080 and in fullscreen mode. Link to comment Share on other sites More sharing options...
sunjunkiesi Posted April 8, 2019 Share Posted April 8, 2019 There is a problem that orbx have recognised with sp1 that may be related to this. So far there's no indication of how quickly they can resolve it so it may be best to, as I have, uninstall tegbs for now until the fix is made live. Link to comment Share on other sites More sharing options...
Drazkul Posted April 8, 2019 Author Share Posted April 8, 2019 Ahh cool, Its definitely something in TE GB south thats causing the issue as I did a flight from Inverness towards Manchester and it ran fine. Link to comment Share on other sites More sharing options...
Nick Cooper Posted April 8, 2019 Share Posted April 8, 2019 Hello, I see no one else complaining of running out of RAM, I do see sunjunkiesi complaining that in VR, the frame rate is too low. Perhaps you might try reducing the X Plane 11 settings a little. If you leave the world objects at maximum, you will see virtually no difference. Also, please ensure that you have a Windows paging file active. Link to comment Share on other sites More sharing options...
oldboy43 Posted April 8, 2019 Share Posted April 8, 2019 I think 16 GB of RAM is very small for X-Plane 11. Look at my screenshot. At the start of the 27 London City is total RAM consumption of 17.5 GB from 32 GB in PC. Sincerely Karoly Link to comment Share on other sites More sharing options...
Nick Cooper Posted April 8, 2019 Share Posted April 8, 2019 This is why a working swap file will be required. Link to comment Share on other sites More sharing options...
Drazkul Posted April 8, 2019 Author Share Posted April 8, 2019 I'll double check the paging file tomorrow but it was one of the first things I looked at when I first started to have the issue after the initial download of SP1. I'll also try dropping the sliders another notch down again tomorrow if I get enough time to fly in X-plane (my wife is off work tomorrow so gaming time will be limited) - I'll keep world objects on maximum as you suggested. Link to comment Share on other sites More sharing options...
Drazkul Posted April 12, 2019 Author Share Posted April 12, 2019 So I managed to get a bit of flight time and I took a look at my page file and adjusted it which seems to have stopped the out of memory errors - though now after 20 mins or so flying i'll now get a random program freeze/crash This is about average for the runs I tested while flying in the sim since adjusting the paging file (the highest use of RAM it ever got to was 12.4GB - and frame rate was averaging 30 FPS) but was still getting the occasional freeze/crash. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.