Goran_M

Are you running any other kind of plugin that can conflict with the viewpoints? You can set this to auto renew in the Gizmo settings.

Apologies for being late again. Hard to keep up sometimes. We're looking at some kind of maintenance addition. No promises yet, but it's on the table.

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

We never give out time frames until we're literally 100% certain we can get it out on the date. It is getting worked on at the moment, with one of the big additions being libturbine. libturbine is a completely custom engine model. We'll post more information as time goes on.

Little bit late on this one, but this warning is because you rotated at too high a speed. IIRC, once you pass 190kts on the ground, this warning will come up if you have not started closing the gear doors.

https://discord.gg/QudA23f5

We would appreciate it if you did what Pils asked, and then we can investigate further. Going back and forth with daemotron is, pretty much, an exercise in futility. We need hard figures to dig in to.

You need to assign BOTH throttle levers to the "Throttle" axis. You have to assign a key press or button press to the Flight Idle Latch manipulators located under the actual hand grips on the Power Levers. You can assign 1 key/button for both, or a separate key/button for each one. To find them, go into the key assignment tab in the settings, and just do a search for Flight Idle Latch.

It will get looked at, but at this time, it's a little lower on the priority list. What's the 2nd issue?

I'll discuss with Saso on this. If you mean the gloss is excessive, I can reduce it, but then it would take on a more matte finish during daylight hours. I've experimented previously with finding a good balance, with not much being achieved in the way of looks. I'll note it down for future reference. Possibly. But I don't want to go finger pointing just yet.

Correct. Reflections from the surroundings. I'm considering reducing the reflectiveness in an update.

Check in your CL650 user settings. Under User Interface. Make sure you have a check mark next to "Simulate walking around aircraft and FBO"

This is done deliberately, and is meant to simulate blown out screens, that are on full brightness, at night. To fix this, you need to dim the lights (BRT/DIM switch on the overhead) This is an XP12 lighting issue. I can certainly lower the reflections down, but the glass will look very dull during daylight hours. I'll mess around with it some more and see what I can come up with. We're not really sure. But it's possible.

And a Happy New Year to you, too. Let's see if we can sort out these crashes. The log file doesn't show a crash, but it doesn't show a clean exit, either. It's like X-Plane just decided to say, "No", stopped and went to desktop. I'm seeing some concerning things in the log file, though. I still see plugins, and definitely a few that could be causing the problem. Marginal Ground Traffic is a very old plugin, and one I strongly suggest you remove. It looks like it's part of your SBRJ scenery. I would also suggest you try running X-Plane without Autogate (also a Marginal plugin) and Python Interface. Try those and see how you go.

It's there. With a working ADG. I'm going to add the metal strip around it in another update. You just can't see the seam because of the lighting.

This looks like a bug with MacOS and the ARM CPU. I also have an M1 Max, and I am getting the same thing. It's not something that can be easily fixed, if at all, on our side. This looks to be squarely in Apple's court. The map will show on Intel CPU's. It has something to do with OpenGL texture loading. It MIGHT fix itself when Gizmo (our DRM) is compatible with the M1 CPU. But other than that, I'm afraid we're stuck with it. Apologies for this.

Yes, there is a seam around the emergency exit, but the seal for that seam is on the interior. I suppose I could add something and make it part of the exterior to block it off.

That's quite the eye you have. I'll address each one. I can't do anything about this one. It was brought up in XP12 testing, and I checked it. The mesh is there, but it's the way X-Plane 12 renders lighting that gives this result. I'm guessing you're talking about the visible seam in the nose equipment bay doors. The nose equipment bay will be added in the next update, however, it's likely the seams will still be visible, as we do something called an "object kill" if objects are not visible. This helps with performance, but shows a sliver of background light. Another example of object kill. The object that is getting killed is behind the door. The problem with fixing it on that side of the door, by adding it to the cabin, is that it will be culled when on the other side of the door. Other than not killing the object, there's nothing we can do about this one. This is another object kill. When not in the cabin, the cabin is killed. Purely for performance reasons. If the cabin isn't killed, X-Plane loads the mesh and textures, and the computer hardware takes a hit. I'll look into this one. It may be another X-Plane issue with the lighting.

Try running the X-Plane installer and repair the airport database.

We want to take our focus away from turboprops for a little while. We've had meetings and discussed the next project. But for now, the focus for Saso will be on the TBM XP12 update, while I continue with more 650 updates and a few things on the DC3.

Width - 17.4cm Height - 7.13cm And here's a reference image for you to use.

You just missed the Black Friday sale about a week ago.

I think it's in the list of updates, but it's lower on the priority list than other items.

Please post a log.txt file immediately after the crash, so we can see what's happening.

A log.txt file will always help. Thanks.