bunchy

Yes that's right. VNAV will reset after 5 mins if it hasn't reached TOD within that time. Stu

Hi Goran, I'm getting these exception handler problems too. They are quite intermittent for me, about once every three flights. Just before the crash, my sound goes off for a second, then recovers for about 2 seconds, then a CTD. I run Ortho for pretty much all of Europe, the latest crash was flying from Rhodes to Florence. My Plugin folder content image is attached. The strange thing is, 66% of the time, I have no problems. I use consistently, with every XP flight, the following: ASXP, EFBv2, ProjectFly. Sometimes, as an alternative to EFBv2, I use Navigraph's simconnect. Never at the same time though. If I'm not using Navigraph's simconnect, I uninstall the plugin. Hope this helps Stu Log.txt TBM900_Log.txt

Thanks, Ben. This update has fixed my memory leak issues. Much appreciated Stu

No, I haven't. I'm going to buy an iPad now and try it out. Stu

Congratulations, Ben. I'm liking this news very much. Good work indeed. Look forward to the update. Stu

Ben, Am I correct in assuming the new 1.2 update doesn't include a fix for the memory leak you found? Thanks Stu

Ben, You've made me a happy man. Thank you so much for all your hard work in this. Thanks also to everyone else who has helped with their advice. I can relax now, knowing it will be fixed at some point in the future. Thanks again Smiling Stu Merry Christmas everyone!

The full reinstall of Xplane achieved absolutely nothing. It looks like I need 16GB of RAM to successfully run this addon. Same old out of memory after about 1.5 hours. Back to default clouds again Stu

A full reinstall had crossed my mind. It's not too much of a PITA compared to FSX to reinstall! The problem is clearly local to my machine. I may do just that over the Christmas period, while my port and cheese settle.......burpy pardon. Thanks Stu

Ben and AJ, I was pointed to this mistake earlier. I had already deleted the SASL folder from my plugin folder, so it now only resides in my carenado B58 folder. Out of Memory problems were still noted. I'm not really sure how it ended up in the plugin folder in the 1st place but it's gone now. I have been flying X Plane with just the default clouds for now, with no out of memory issues. As I have 8GB of RAM, I'm assuming it is generally enough RAM to have for XPlane ? When I monitored RAM with SkyMAXX, i get the WIndows memory warning before the RAM is saturated. On my last flight it was warning me when my RAM usage was at 67%, not even 3/4 used? Windows always closes Xplane before RAM is anywhere near 100%. I don't know what the normal RAM usage would normally be for Xplane, does anyone know? Thanks Stu

I guess there's no break throughs with my out of memory problem, then? Stu

Yes, I only use real weather Stu

Cameron, I have compiled a chart of my RAM usage. Just to explain the chart: Column 1 is the flightplan (I reckon you already guessed that) Column 2 shows system RAM usage at each waypoint using a SASL aircraft but no SkyMAXX/Gizmo64 Column 3 shows system RAM usage at each waypoint using a default non SASL aircraft with SkyMAXX and Gizmo64. You can see that the RAM usage steadily climbs throughout the flight and culminates in this message: This out of memory occurred whilst compiling column 3 with the C90. These are my SkyMAXX settings Hope this sheds a little light on whether the seat of the problem lies with SASL or SkyMAXX/Gizmo64. Thanks Good luck Stu

Thanks for your ongoing help, Cameron. I will re-install SkyMAXX and do the test flight again with the default KingAir, real weather and return my observations. Thanks as well for your input, Ben. Much appreciated. Top customer support. Like it lots. Thanks Stu

Thanks, John. It's a mystery to me. I don't know if you have the Carenado B58 to test but this is my flightplan I've been using to test with real weather: EGPF NGY-DCS-LAKEY-CALDA-CROFT-BARTN-LOVEL-LISTO-HON-FINMA-HEMEL-LAM EGLC. On my decent into EGLC, somewhere between HEMEL and LAM is where I tend to run out sys RAM. Thanks and good hunting Stu

Hi Flo, I haven't tried that but the Carenado B58 works fine with default clouds. In fact, it works with SkyMAXX fine, provided my flights are under 1 hour. I have done some serious long distance flights (long distance for the B58) without issues prior to SkyMAXX. On a relatively short flight within the UK, I run out of system memory if I use SkyMAXX. Here's a screen of my XP rendering settings (clouds at 40% due to not using SkyMAXX at the moment) Other information is that I use V2 mesh. Thanks for chipping in, I really want to fix this. Stu

SqrtOfNegOne I did some digging on the Nvidia site and found 331.65 only supported OpenGL 4.3. It looks like XP10.25 is OGL 4.4. I have since updated my driver to 331.82 which now supports OGL 4.4. I am sad to report that although it's cured that OGL error, I'm no further forward with the out of memory issue with SkyMaxx. When I run in a default cloud config and I monitor system RAM usage it increases and decreases as the flight progresses. For instance, the test flight I'm using from EGPF to EGLC, RAM usage starts at 36%, enroute abeam Manchester rises to 49% and abeam Birmingham 54%. In the less congested areas between cities the RAM usage falls back to 43-47%. Bottom line is, that I can complete the flight because RAM is being used and released. When Skymaxx is running along with Gizmo 64, for the same flight, I see RAM usage start at 52% and climb throughout the flight until approaching London when Windows warns me I am running out memory and to close programs. I believe the memory is not being released by SkyMaxx and/or Gizmo64. At least for now that is the only info I have from my testing. I have 8GIG of RAM, by the way, and the flight is approx 1.5 hours duration. Test aircraft: Carenado B58 64bit. Real weather used during testing. Thanks for your continued support Stu

I installed the driver using the clean install method, as per Nick Needhams advice in his FSX bible. I can say this driver has never caused any issues since install with either FSX or Xplane. I installed SkyMAXX last night and have not completed a flight successfully since. This is the fulcrum point of the trouble. I bet if I uninstall SKymaxx, I will have no trouble with system memory usage or these driver crashes. The only thing changed on my system is skymaxx and the Gizmo 64 plugins. How do I uninstall sky maxx properly and reinstate the default cloud textures? Do I just uninstall through programs and features or is there another way.? Thanks for your support. Stu

Thanks for this advice, all. I have removed the SASL folder from the global plugin folder and made sure it just appears in the aircraft folder concerned. I reduced texture resolution to very high. Took the B58 on a test flight from EGPF Glasgow to EGLC London City. I ran in windowed mode so I could see system RAM usage on the flight. VRAM was around 668MB at beginning of flight fluctuating between that and 700MB. System RAM kept on creeping up through the flight, from a start point of 48% used to approaching London of 68% used. I call this progress, as in previous test flights it had run out of system RAM long before this point. So while I was excited I may just complete this flight, I suddenly see the screen lock up. I had to ctrl-alt-del to get out and was confronted with the message attached. My Nvidia drivers are 331.65. When all is said and done, this has only started to happen after the skyMAXX install. There is either something wrong with the plugin or it has damaged my install somehow. I've attached my latest xplane log also. Log.txt

I'll carry on testing. The SASL folder within the plugin folder appeared there after the carenado install. It wasn't placed manually. Stu

No Xplane crash, Just high memory usage in windows. If I click cancel, the warning disappears for a few minutes before coming back. In process explorer it is reporting 73% RAM usage. In Xplane , I have texture res set to extreme and that reports 1.3 gig of 2 gig used, so there is some overhead in both system RAM and VRAM. I have 8gig of system RAM and it's the first time I've seen this error. I removed everything out of my plugin folder but realised I need SASL for the Carenado B58, Gizmo64 and Silverlining for skymaxx, so apart from XUIPC, there's nothing I can remove. Any thoughts most welcome. Stu

Hello all, John was helping me over at Avsim and suggested I jump over here. Hey Stuart, for more support you can head over to X-Pilot, we have a dedicated SkyMAXX support thread there. I am not trying to steer AVSIM users but as to properly support the product As far as the pauses with changing weather conditions, we are working on smoothing out these transitions as we speak. Our clouds are procedurally drawn and regenerate differently each time, and we found a few things to help drastically speed up the regeneration. Keep your eyes open for another update in the future.... The algorithm we use for cloud generation will create massive cloud structures and they may intersect with the ground from time to time, you can adjust the Max and Min cloud sizes in the UI to combat this...... We haven't seen any kind of memory leakage with SkyMAXX at all, as a matter of fact it runs much lighter then default, after the 1.1 update, if X-Plane crashes post your log.txt over at X-Pilot so we can look at it. It may be something specific to your system.... -John So, to follow up, John, I've set the cloud max and min size to half way, so now everything is set midway. I've attached my xplane log file for you to take a look at. The Windows memory warning occurs when flying the Carenado B58 but has only occurred after the skyMAXX install. Let me know if you find anything in the log. Thanks StuLog.txt