Leaderboard

I would like to chime in here - I have worked with Tom on this over the last week intensively - previously I had test flown the 737 in XP12 (after we fixed the major roadblocks of even getting if flyable, like making the flaps work, etc.) and I had tuned the flight model. Tom worked hard on 3D modeling over the last months with little for me to do (I am too stupid for blender and those things) and now with him approaching the end of that work, I dove back into flight and system testing. The more I test, the more stuff shows up that does not work anymore, because Laminar changed things - and these changes are all improvements in modeling systems, yet they still leave our "old" way of doing/overriding them unusable. So in a very real way we have to redo a lot of the things we already did for XP11, it is not a quick conversion at all - and this is something we definitely underestimated when we initially said to "upgrade to XP12 for free". The move from XP11 to XP12 is not an upgrade, it is in many areas a repeat of the dev work work we already did for XP11. And I am thankful for most of our customers to be very understanding of the fact that we charge a small price to compensate us for this! I think the old 737-300 still has a lot of life in her, I thoroughly enjoy my "test flights" and find myself again and again to "just finish this approach" even though I was just testing some autopilot PID constant ... simply because it is fun to fly and looks great in XP12 . Cheers, Jan

@DomWin No ETA yet. Here's how it looked about a week ago.

And for every 1 of those 10, there are probably some number who bought it & are not using it. So, I have a FlyWithLua script that refers to a dataref: laminar/B738/toggle_switch/vhf_nav_source. It was working in an earlier XP12 release. FWL suddenly decided to quarantine the script because the dataref was no longer available. True enough it seemed the dataref had been removed. So, I simply replaced the dataref with an alternative: laminar/B738/toggle_switch/vhf_nav_source_lft. And FWL quarantines the script again with the complaint that this dataref was also not available. My point is not about the error although it is an issue. But it's a beta release. So some things won't work. But imagine the time spent on this & other bugs like this when I could have used that time flying. I don't want to turn this thread into a school yard level argument like the "community leaders" do in the other forum. I simply state my experience with XP12 & will let readers decide for themselves what to do. Apologies for this rant.

Funny, I never had issues with CTDs (apart from those caused by third-party addons, or by segfaults I built into my own plugins ) since the first early access version of XP12. I was expecting a far worse experience in early access, but found that (vanilla) XP12 was pretty solid right from the beginning on. After 12.00 became final, I stopped hopping onto the betas though, since I need a halfway stable platform for my purposes. What I will never get: people are disappointed to experience crashes when they run add-ons explicitly marked as experimental (e.g. Zibo for XP12), and then blame the platform for the experienced issues. If you want a stable experience with XP12, then restrict your flying to aircraft which are marked final by their developers. If your favorite aircraft isn't yet out of beta for XP12, stick with XP11.