Leaderboard

You spoiled me with weekly improvements. Can you offer any general clues, Jan et al, what kind of stuff we can expect next, and roughly when? I fully understand that works in progress are works in progress and that the course of development is rarely certain. Best, Marshall

I wanted to thank you guys for this aircraft, it has the best flight model ever created in xplane, no other aircraft can compete with the IXEG when it comes to flight dynamics, the systems simulation is great also.I really enjoy flying this aircraft a lot.keep up the great work guys.

Hi there. I'm curious which yokes are used most commonly here? I for myself use the Saitek Proflight Yoke, however I'm not really satisfied, as the yoke is pretty unprecise and mechanically not the best choice. Regards, T

I enjoying the aircraft alot (with many others). I agree that the VNAV is not optimal. But what is wrong with the MCP ?

I am the same way, anxious about another update. I keep checking in hopes of seeing that .8 update but sigh everytime I check when its MIA. Of course they want to do it the right way but the anticipation is killing me....lol Hopefully we will see or hear something soon

Thanks Chris. If I understand correctly from your thread on XPD, your issue is performance degrading over time as you fly. There's nothing in your log that implicates SkyMaxx Pro or Real Weather Connector, or anything else; the information there is inconclusive. But, it looks like you're using HD Mesh in addition to orthophoto custom scenery, which is certainly taxing your system. It could be that all of our extra 3D clouds are just pushing your system over the edge over time. Removing HD mesh or your custom scenery might help if you need an immediate solution. But as I mentioned in the thread, we also have a new version of SMP coming out that will use far fewer resources than version 3.2.2, and that might be what you need in order to keep the demands of your simulation within the bounds of what your hardware can do. So, let's wait and see if SMP 3.3 clears things up when it comes out. If not, you may need to make some compromises on the add-ons you have installed - but I'm cautiously optimistic that SMP 3.3 will help. You should receive an email when it's available.

Your best bet for any tech support on this would be the DJI forums. Lots of helpful people who have felt your pain. I have no experience trouble shooting anything like yours.

Just had a crash starting XP...here's the logs. Thanks! Log_Metar.zip

Thank you for capturing the offending METAR.rwx. Based on the reports it seems this was only an issue for one hour's worth of published METAR data. As before, the problem is a bug inside the METAR parsing library we're using from NOAA, and as before, I've patched it so this particular problem won't happen again once our next update of SMP goes out. The culprit this time was KGRK: KGRK 152107Z 04010KT 3SM RA BR SCT010 BKN014 OVC024 22/21 A3001 RMK AO2A CIG 014V024 BKN V SCT CIG 012 That final "CIG" (ceiling height) entry is what did it in. The NOAA code didn't handle the case of this being the last thing in the entry (but it will now that I've fixed it...) If anyone is still having trouble launching X-Plane, just delete your METAR.rwx file in your X-Plane installation folder, and that should clear it up for now. Sorry for the trouble, everyone.

In my Fave flying over Reno/Sparks Nevana area Dion MarkgrafAKA: DionsolFlight Simulation (X-Plane 10 pilot) & Aviation EnthusiastVoice Com's channel: https://discord.gg/aH7x774Youtuber: https://youtube.com/user/dionm01

This makes the two of us. Log.txt

@Sundog. Again love your product and you asked that I send you a copy of my log text if it shows Skymaxx crashed the sim. Here is a little of it and I will attach the entire log for you. SkyMaxx Pro: Raised stratus layer to avoid a layer collision. SkyMaxx Pro: Raised stratus layer to avoid a layer collision. SkyMaxx Pro: Raised stratus layer to avoid a layer collision. 0:06:17.302 I/ATC: Airport flow changed at KCMI! CurFlow: AUTOGEN: East NewFlow: AUTOGEN: South 0:06:17.302 I/ATC: Changing KCMI CabState from 0 to 1 0:06:17.302 I/ATC: All departures are done at KCMI. Advancing... 0:06:17.302 I/ATC: Changing KCMI CabState from 1 to 2 0:06:17.302 I/ATC: All arrivals are done at KCMI. Advancing... 0:06:17.302 I/ATC: Changing KCMI CabState from 2 to 0 0:06:17.302 I/ATC: Airport flow changed at KARR! CurFlow: AUTOGEN: East NewFlow: AUTOGEN: South 0:06:17.302 I/ATC: Changing KARR CabState from 0 to 1 0:06:17.302 I/ATC: All departures are done at KARR. Advancing... 0:06:17.302 I/ATC: Changing KARR CabState from 1 to 2 0:06:17.302 I/ATC: All arrivals are done at KARR. Advancing... 0:06:17.302 I/ATC: Changing KARR CabState from 2 to 0 0:06:17.302 I/ATC: Airport flow changed at KCGX! CurFlow: AUTOGEN: East NewFlow: AUTOGEN: South 0:06:17.302 I/ATC: Changing KCGX CabState from 0 to 1 0:06:17.302 I/ATC: All departures are done at KCGX. Advancing... 0:06:17.302 I/ATC: Changing KCGX CabState from 1 to 2 0:06:17.302 I/ATC: All arrivals are done at KCGX. Advancing... 0:06:17.302 I/ATC: Changing KCGX CabState from 2 to 0 0:06:17.302 I/ATC: Airport flow changed at KBMI! CurFlow: AUTOGEN: East NewFlow: AUTOGEN: South 0:06:17.302 I/ATC: Changing KBMI CabState from 0 to 1 0:06:17.302 I/ATC: All departures are done at KBMI. Advancing... 0:06:17.302 I/ATC: Changing KBMI CabState from 1 to 2 0:06:17.302 I/ATC: All arrivals are done at KBMI. Advancing... 0:06:17.302 I/ATC: Changing KBMI CabState from 2 to 0 0:06:17.302 I/ATC: Airport flow changed at KPWK! CurFlow: AUTOGEN: East NewFlow: AUTOGEN: South 0:06:17.302 I/ATC: Changing KPWK CabState from 0 to 1 0:06:17.302 I/ATC: All departures are done at KPWK. Advancing... 0:06:17.302 I/ATC: Changing KPWK CabState from 1 to 2 0:06:17.302 I/ATC: All arrivals are done at KPWK. Advancing... 0:06:17.302 I/ATC: Changing KPWK CabState from 2 to 0 0:06:17.302 I/ATC: Airport flow changed at KMDW! CurFlow: AUTOGEN: East NewFlow: AUTOGEN: South 0:06:17.302 I/ATC: Changing KMDW CabState from 0 to 1 0:06:17.302 I/ATC: All departures are done at KMDW. Advancing... 0:06:17.302 I/ATC: Changing KMDW CabState from 1 to 2 0:06:17.302 I/ATC: All arrivals are done at KMDW. Advancing... 0:06:17.302 I/ATC: Changing KMDW CabState from 2 to 0 0:06:17.302 I/ATC: Airport flow changed at KIKK! CurFlow: AUTOGEN: East NewFlow: AUTOGEN: South 0:06:17.302 I/ATC: Changing KIKK CabState from 0 to 1 0:06:17.302 I/ATC: All departures are done at KIKK. Advancing... 0:06:17.302 I/ATC: Changing KIKK CabState from 1 to 2 0:06:17.302 I/ATC: All arrivals are done at KIKK. Advancing... 0:06:17.302 I/ATC: Changing KIKK CabState from 2 to 0 0:06:17.302 I/ATC: Airport flow changed at KLAF! CurFlow: AUTOGEN: East NewFlow: AUTOGEN: South 0:06:17.302 I/ATC: Changing KLAF CabState from 0 to 1 0:06:17.302 I/ATC: All departures are done at KLAF. Advancing... 0:06:17.302 I/ATC: Changing KLAF CabState from 1 to 2 0:06:17.302 I/ATC: All arrivals are done at KLAF. Advancing... 0:06:17.302 I/ATC: Changing KLAF CabState from 2 to 0 0:06:17.302 I/ATC: Airport flow changed at KDPA! CurFlow: AUTOGEN: East NewFlow: AUTOGEN: South 0:06:17.302 I/ATC: Changing KDPA CabState from 0 to 1 0:06:17.302 I/ATC: All departures are done at KDPA. Advancing... 0:06:17.302 I/ATC: Changing KDPA CabState from 1 to 2 0:06:17.302 I/ATC: All arrivals are done at KDPA. Advancing... 0:06:17.302 I/ATC: Changing KDPA CabState from 2 to 0 SkyMaxx Pro: Raised stratus layer to avoid a layer collision. SkyMaxx Pro: Raised stratus layer to avoid a layer collision. SkyMaxx Pro: Raised stratus layer to avoid a layer collision. SkyMaxx Pro: Raised stratus layer to avoid a layer collision. SkyMaxx Pro: Raised stratus layer to avoid a layer collision. SkyMaxx Pro: Raised stratus layer to avoid a layer collision. 0:07:19.084 I/ATC: Airport flow changed at KORD! CurFlow: East flow (low vis) NewFlow: West flow (low vis) 0:07:19.084 I/ATC: Changing KORD CabState from 0 to 1 0:07:19.084 I/ATC: All departures are done at KORD. Advancing... 0:07:19.084 I/ATC: Changing KORD CabState from 1 to 2 0:07:19.084 I/ATC: All arrivals are done at KORD. Advancing... 0:07:19.084 I/ATC: Changing KORD CabState from 2 to 0 SkyMaxx Pro: Raised stratus layer to avoid a layer collision. SkyMaxx Pro: Raised stratus layer to avoid a layer collision. SkyMaxx Pro: Raised stratus layer to avoid a layer collision. SkyMaxx Pro: Raised stratus layer to avoid a layer collision. SkyMaxx Pro: Raised stratus layer to avoid a layer collision. [SASL DEBUG] 08/15/16 17:48:04 --------------------------- [SASL DEBUG] 08/15/16 17:48:04 Refreshing cache 1 [SASL DEBUG] 08/15/16 17:48:04 --------------------------- [SASL DEBUG] 08/15/16 17:48:04 --------------------------- [SASL DEBUG] 08/15/16 17:48:04 Refreshing cache 2 [SASL DEBUG] 08/15/16 17:48:04 --------------------------- [SASL DEBUG] 08/15/16 17:48:04 --------------------------- [SASL DEBUG] 08/15/16 17:48:04 Refreshing cache 3 [SASL DEBUG] 08/15/16 17:48:04 --------------------------- [SASL DEBUG] 08/15/16 17:48:04 --------------------------- [SASL DEBUG] 08/15/16 17:48:04 Refreshing cache 4 [SASL DEBUG] 08/15/16 17:48:04 --------------------------- SkyMaxx Pro: Raised stratus layer to avoid a layer collision. SkyMaxx Pro: Raised stratus layer to avoid a layer collision. SkyMaxx Pro: Raised stratus layer to avoid a layer collision. SkyMaxx Pro: Raised stratus layer to avoid a layer collision. SkyMaxx Pro: Raised stratus layer to avoid a layer collision. SkyMaxx Pro: Raised stratus layer to avoid a layer collision. SkyMaxx Pro: Raised stratus layer to avoid a layer collision. SkyMaxx Pro: Raised stratus layer to avoid a layer collision. SkyMaxx Pro: Raised stratus layer to avoid a layer collision. SkyMaxx Pro: Raised stratus layer to avoid a layer collision. SkyMaxx Pro: Found new METAR.rwx file SkyMaxx Pro: Parsing METAR data --=={This application has crashed because of the plugin: SkyMaxx Pro}==-- log for skymaxx crash.docx

Thank you for the nice words! Happy flying, Jan

Hi Facu - Try removing the malformed METAR file, then disconnect from internet to avoid x-plane download it again, open x-plane, switch off real works weather. connecta back to internet. Done. Now you should be able to use X-Plane again. try again in a few hours to enable back real world weather and see in the new metar is not corrupt.

JeffLeh, it's your log.txt we asked to see - but there's good info in the screenshots you provided too. You are in fact perilously low on VRAM (only about 200MB left), and some of your rendering settings are probably to blame. I don't think you can expect a GTX 765M to run reliably with "extreme" settings and also a cranked up cloud area. If you have custom scenery or HD mesh installed as well, that's making thing even worse. In short, I'm pretty sure your crashes are due to running out of memory. You're going to have to dial back your settings until you can run reliably.

If you have a log that indicates SMP was responsible for a crash we definitely want to see it. But in either case, we will need to see your complete log.txt to understand what's going on. How are you measuring your free VRAM? You should be looking at what the SMP config screen displays, or GPU-Z if you don't trust it.

I highly suspect you are pushing your system over its limits, the addition of SMP is just the final nail in the coffin.... SMP did not crash x-plane, additionally that small snippet from the log doesn't even indicate a crash...... Now that's not to say you do not have an issue but we need all information available in your log in order to give you some proper direction...

Yeh, can not use the aircraft in the current state, FMC is buggy as heck, MCP too. But I'm patient, rather they take there time than rush!