All Activity

On a Mac Studio (M4 MAX), and X-Plane 12.4.0 b4 I got this message (after installing the G5 plugin to the A36). The message (as in the screenshot) now appears in my G5 Islander, and I guess it will in other G5 planes. I'm also adding a log.txt, which shows a few G5 "alterations". Probably due to the X-Plane beta.....? Log copy 2.txt

The tyres blowing I do believe is particular to this airport's mesh. Going over a ridge in the runway seems to set off a chain reaction. It doesn't happen with any other aircraft I've tried though, and the Challenger doesn't show it as a failure.

That's what I've done. So far no crashing. But also no traffic obviously, and I would ideally like to keep it. I've already been through the support process with Just Flight and the logs always reference the Challenger so thought there must be something on that side causing it.

Remove it and see what happens without it.

There's plenty of movement. We'll communicate about that when we feel the time is right.

OK thanks. Is that feature disabled currently or broken? Because in the beginning of this thread it sounds like it exists.

Cameron, Glad to know my consistency matches yours. Maybe next year we can both surprise each other. Friendly banter aside, the lack of movement is the real concern. If the answer hasn’t changed in years, maybe the communication strategy should. Kind regards, Lucian Anghel

Any progress on this? I tried the obj file linked above but it gave me an error

Just keeping this thread and my hopes alive...

Oh, thanks! We were worried you wouldn't come back. ...but the answer hasn't changed.

Hi all, Just dropping in for my annual reminder that the TBM 900 “update” is still… somewhere. Every year we get the same beautifully crafted PR message about a massive rewrite, unparalleled quality, and how it’ll “definitely be worth the wait.” At this point I think the rewrite might actually be longer than the lifespan of the real TBM. If there’s actual progress, fantastic. If not, maybe it’s time to retire the yearly inspirational speeches and give us something concrete.

Crashing has definitely escalated recently. It crashed twice again today in a short flight. Both times seemed to be triggered when changing or moving the camera. I would post the crash log but it's the same kind of thing as above so I never saved it. I'm not sure if there's a conflict with Traffic Global somewhere. I've read of others having issues under the same circumstances. Since I added that things have gotten worse (though it still crashed before).

New one today. I started up the battery and APU and I got nothing on the cockpit displays, despite the pop out one working fine. It could be a brightness bug, as it went overcast dark outside, but I cranked the brightness and still nothing. The AviTab brightness was definitely darker than normal but I could still see it on max. Everything else though was impossible to see. I reloaded and the exact same problem. In the end I had to create a completely new airframe.

Incredibly weird series of events today. What should have been a short hop on a Saturday afternoon between KCRW and KDCA turned into hours of restarting and weird bugs. First, when I loaded up the sim I noticed the landing gear looked very strange, with the nose gear at a 90 degree angle and the main gear twitching. I didn't leave it like that. This was a new scenery I had loaded, Yeager, which has quite a detailed custom mesh, but I don't know if that was the problem. I think the aircraft seemed to think it was in flight. gear.mov I tried reloading the aircraft, but when you reload aircraft, it is impossible to spawn because the button is greyed out? So I had to completely quit X-Plane. In any case, I created a completely new airframe, that must solve it surely, and I spawned at different location in the same airport. Again the gear was screwed up. When I started taxiing I had a 'steering INOP' message and nose wheel steering didn't work until I re-toggled that switch. On takeoff, I blew every tyre, losing control quite a bit, and X-Plane produced about 100 popup windows to tell me, which took about 3 minutes to clear off the screen. I reloaded it to before takeoff and the exact same thing happened so I just had to takeoff. I checked failures and there was nothing listed... takeoff.mov (The front gear missing was just X-Plane's replay mode not showing it for some reason). When I landed the tyres were fine. I am not saying all of these are the fault of the CL650, but it was odd.

It looks like this update isn't going to get pushed. Is anyone here using the Sundowner with the Honeycomb Bravo or Bravo LITE? If so, is the flaps lever working? I'm thinking about purchasing it.

This is expected behaviour at this time.

I have uninstalled your highly recommended $70 aircraft. X-Plane 12 now works fine, as before. Thank you for your help. It was worth the purchase price.

Are there any known bugs about state-saving? For me the saving and loading works good, but it is exactly the same state as when I last flew it, so engines still hot etc. Is there any setting for enabling the real-time based things like ice accumulation or engine cooldown? It works like 10% of the time for me if at all, most of the time the plane is in the same state as when I shut down. Engines are off and Battery switch is off most of the time and I always use time synced to realtime.

And 12.4.0 b3 is available and bug free, several flights made, no issues

Maybe it's got worse on Tahoe. Sorry for the trouble.

Using the search function here, it doesn't appear I need to explain the trash situation over there on the "other" forum. Just thought I'd say hello and see how much activity was happening over here. Currently flying XP12 with a pretty substantial cockpit setup. Usually on PilotEdge and I do some streaming when I can. Terribly upset with the state of payware aircraft for XP12 and how these devs are selling garbage flight models. Went to criticize a vFlyteAir product at the org and got the hammer. As you can imagine nobody actually helped. Just denied a problem exists. I have switched to the default Cessna 172 and I must say, I should've went back to a default aircraft much sooner. It flies BEAUTIFULLY in the latest BETA with a FFB yoke. Very good GA bones there for sure.

I had it happen again just now before taking off, I've attached a log. The first time was maybe a rounding error but the differences being referenced here are absurdly large: 128882698720.679611 < 2773.150000 Log.txt

What Mac is this? Can you post a full Log.txt, please?

Sadly, yes.