JohnMAXX Posted April 5, 2014 Report Share Posted April 5, 2014 Ooooo soo exciting! Quote Link to comment Share on other sites More sharing options...
sundog Posted April 6, 2014 Report Share Posted April 6, 2014 (edited) We'll take a second look at the code your log is pointing at. There is no obvious cause for this happening in 1.3.2 so bear with us - especially given our inability to reproduce the error. (For others reading this thread thinking "OMG SkyMaxx is going to crash on me" - probably not. This issue only affects MacOS and has only been observed while flying for many hours in one sitting while using the XSquawkBox add-on - sometimes.) Edited April 7, 2014 by sundog Quote Link to comment Share on other sites More sharing options...
vgmm009 Posted April 7, 2014 Report Share Posted April 7, 2014 thank you very much for the support, I appreciate. hope you will find a fix. We'll take a second look at the code your log is pointing at. There is no obvious cause for this happening in 1.3.2 so bear with us - especially given our inability to reproduce the error. (For others reading this thread thinking "OMG SkyMaxx is going to crash on me" - probably not. This issue only affects MacOS and has only been observed while flying for many hours in one sitting while using the XSquawkBox add-on - sometimes.) Quote Link to comment Share on other sites More sharing options...
sundog Posted April 7, 2014 Report Share Posted April 7, 2014 (edited) thank you very much for the support, I appreciate. hope you will find a fix. vgmm009, can you please check what your overcast quality setting is at in the SMP configuration? Do you happen to remember if you were flying into overcast conditions when this happened? If it is set to "low", I suspect setting it to medium or high instead will clear this up. Edited April 7, 2014 by sundog Quote Link to comment Share on other sites More sharing options...
vgmm009 Posted April 8, 2014 Report Share Posted April 8, 2014 please the attached capture for my usual SMP settings ! I ll try to select the overcast setting to medium even if for the last crash I was on cruising level above clouds, at night time and no overcast weather conditions. Quote Link to comment Share on other sites More sharing options...
sundog Posted April 8, 2014 Report Share Posted April 8, 2014 It could've hit you just as an overcast layer was about to be injected - I think this might be it still. It also explains why many other people reported that the 1.3.2 patch cleared this up - I bet they were running on medium or high. Look forward to hearing the results, and thanks for working with us on this. Quote Link to comment Share on other sites More sharing options...
Nano Posted April 19, 2014 Report Share Posted April 19, 2014 (edited) Just purchased SMP yesterday and must say it is a vast improvement over the stock XP cloud renditions. I have had 3 CTD scenarios out of 6 flights so far. These have all happened on VATSIM through XSB. Today I flew about halfway from RJAA to PANC before the CTD and then I removed XSB from the plugin folder and successfully made the same flight with the X-IvAp plugin. I'm on a i7 iMac running Mt Lion (10.8.5) and XP 10.25 SMP is an awesome plugin that I wish I'd had earlier. I'll continue to switch off between XSB and X-IvAp to see if this is my issue. Thanks, Nano Edited April 19, 2014 by Nano Quote Link to comment Share on other sites More sharing options...
JohnMAXX Posted April 19, 2014 Report Share Posted April 19, 2014 Thank you Nano for looking into it further, can you provide some error logs when a crash occurs, this can help us pinpoint the issue for you Quote Link to comment Share on other sites More sharing options...
Nano Posted April 20, 2014 Report Share Posted April 20, 2014 John, I had another CTD today on a VATSIM flight using XSB. The crash happened 3:12 into the flight at FL350 with scattered clouds below. I was flying the FF B777 Worldliner and everything appeared to be going well. Attached are the log files including the crash report that posted immediately after the CTD. Hope this is valuable. Nano CTD.rtfLog.txt Quote Link to comment Share on other sites More sharing options...
sundog Posted April 20, 2014 Report Share Posted April 20, 2014 Nano, what is your "overcast quality" set to in SkyMaxx Pro's settings? We think this issue might be limited to using XSB on MacOS when running with overcast quality set to "low". Quote Link to comment Share on other sites More sharing options...
Nano Posted April 20, 2014 Report Share Posted April 20, 2014 Yes Frank, the overcast quality was set to low. Being a new SMP user and having only 512 MB of VRAM, I figured that was the best setting to start out at. I'll try a flight today with it set to medium and see what happens. Will report back. Nano Quote Link to comment Share on other sites More sharing options...
JohnMAXX Posted April 20, 2014 Report Share Posted April 20, 2014 Thanks again Nano, this will help us pinpoint the problem.... Quote Link to comment Share on other sites More sharing options...
Tom Knudsen Posted April 20, 2014 Report Share Posted April 20, 2014 (edited) Love the debugging here and the collobrative progress following, not sure if it helps but I have never had any form of CTD with SMP version 1.3 Setting will be posted here soon, on my ipad right now EDITHere it is Edited April 21, 2014 by Tom Knudsen 1 Quote Link to comment Share on other sites More sharing options...
Tom Knudsen Posted April 21, 2014 Report Share Posted April 21, 2014 updated Quote Link to comment Share on other sites More sharing options...
Nano Posted April 21, 2014 Report Share Posted April 21, 2014 Well, I successfully accomplished 2 long range flights today with no issues. I varied all the settings on the configuration panel including the "overcast quality". The second flight was 5 hours with overcast quality set to "low" for the entire flight. No issues. There were no segments of the flights that were overcast as the VATSIM weather was better than expected. I will continue to watch this closely and forward any crash reports that result from a CTD. For now I'm enjoying the SMP product with what appears to be an improvement in frame rates on my 2009 i7 iMac. Quote Link to comment Share on other sites More sharing options...
sundog Posted April 21, 2014 Report Share Posted April 21, 2014 Thanks. Based on an analysis of the code, I think this error would only get triggered on MacOS when flying into overcast conditions with the overcast quality set to "low" - and even then it's a matter of chance as to whether it would happen. It seems like long-haul VATSIM flights are more likely to trigger it for some reason. My advice for MacOS users however is to avoid the "low" overcast quality setting until we issue an update to plug this rare problem. Quote Link to comment Share on other sites More sharing options...
Nano Posted April 21, 2014 Report Share Posted April 21, 2014 Just had another CTD today. A fresh load of XP10 with B777 Worldliner. Planned flight from VABB to LTBA. Changed "overcast quality" from Low to Med during climb out CTD occurred shortly after level-off apps 35 minutes into flight. Crash reports attached. Log.txtCTD.rtf Quote Link to comment Share on other sites More sharing options...
Ben Russell Posted April 21, 2014 Report Share Posted April 21, 2014 XSB 64bit is on my personal blacklist. Your mileage may vary but I consider it not worth touching. Quote Link to comment Share on other sites More sharing options...
Tom Knudsen Posted April 21, 2014 Report Share Posted April 21, 2014 What u got against xsquawkbox then Quote Link to comment Share on other sites More sharing options...
Ben Russell Posted April 21, 2014 Report Share Posted April 21, 2014 The fact that its been crashing since it was released and wasted probably a hundred hours of my time.... 'cause, you know, it couldn't be XSB64 that crashes, it has to be Gizmo64... Nearly every single crash to desktop currently happening to users is caused by having XSB64 installed. Quote Link to comment Share on other sites More sharing options...
sundog Posted April 21, 2014 Report Share Posted April 21, 2014 (edited) Nano, that most recent crash was not caused by SkyMaxx Pro. Rather SASL got fingered for it in your logs, following what looks like a lost connection to a server. SilverLining (SkyMaxx's plugin name) doesn't show up at all in your crash log. Ben's probably right. I think setting overcast quality to something other than "low" did actually prevent SkyMaxx Pro from crashing in response to whatever odd conditions were going on, but there is a source of CTD's outside of SkyMaxx Pro going on here. Edited April 22, 2014 by sundog Quote Link to comment Share on other sites More sharing options...
Nano Posted April 21, 2014 Report Share Posted April 21, 2014 I certainly don't doubt it that this is a problem with another plugin. In fact, I believe XSB64 is a prime candidate. I'm currently on a 6 hour leg using XSB with OQ set to "Med". We'll see how it goes. BTW, the lost connection to server is a result of running XHSI on another computer on my network. XHSI doesn't play well with B777 Worldliner FMS and I forgot to shut it down before the flight. Nano. 1 Quote Link to comment Share on other sites More sharing options...
Tom Knudsen Posted April 22, 2014 Report Share Posted April 22, 2014 Strange, never noticed Quote Link to comment Share on other sites More sharing options...
Nano Posted April 24, 2014 Report Share Posted April 24, 2014 Hi Gentlemen, Attached are more log files of my only CTD today. I was just flying around KSEA in the BK117 when I had the CTD. Note that XSB was removed from the plugin folder for this load of XP. SilverLining is listed in the crash log. Hope this helps. NanoCTD.rtfLog.txt Quote Link to comment Share on other sites More sharing options...
sundog Posted April 24, 2014 Report Share Posted April 24, 2014 Just to double check, your overcast quality was on "medium" for this flight? Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.