Goran_M

I've been working on the switches some more, to keep them black, but also visible. They'll be in an upcoming update.

When you asked "Has it been modelled after?", I assumed you meant "Have we made it for this TBM after release." Anyway, thank you for the comments. Very happy to see you enjoying it.

Usually when we make an add on, we mostly keep it as if it came direct from the factory. So no after market additions. That looks like some kind of TCAS or something. If it is, or even if it's any kind of radio, there's really no need for it, as the G1000 we have included has every radio covered. Plus, Saso added his very own TCAS as part of the G1000. Adding what is in that image would very much be a step backwards in technology, when compared to what is already included as part of the G1000.

Can't answer your question, but including a nice tailwind in your configuration would be very beneficial, too.

the dial on the overhead (left side) is for panel backlighting

11.3?

Short answer is, because they were not in the TBM we modelled it after. However, a placard IS on the top edge of the pilots door.

For now, we need to wait until 11.3 is out of beta. After that, it depends how complex the new update is and what it's done to the TBM systems. We'll need to address those first, before moving on to the rain and ice in VR

HA. You boofhead, John.

Hot Start. (Not Hot Shot)

Did you check your nav equipment in the maintenance manager? It looks like a G1000 fault.

Always a chance for anything. But when it comes to heli's, I think it's, kind of, an unwritten thing where developers leave the heli's to Dreamfoil. It's pretty much all he does, and he does it quite well.

This is being explored, and a fix on our end may be in a future update.

The map is the laminar G1000. It can't be changed, unfortunately. It can be added to. If/when Laminar decide to grant access to the G1000 API, then more areas of the G1000 will be editable.

Just a stab in the dark. Do you guys turn your yaw damper off prior to landing? I've seen a lot of people leave it on accidentally.

We have. We had a large group of streamers and testers who put the aircraft through its paces. In earlier versions, the ground handling was worse than it is now. That's when Toto fine tuned the ground handling via code, and made a specific point to all testers to really put the ground handling through its paces. Many of them had the same issues as what is being brought up here. Very sensitive ground handling, etc... and it was pointed out that it was supposed to be a little sensitive. But they did manage to get used to it. There's the odd 1 or 2 that are still having trouble though, for whatever reason. I mean, I guess we can revisit the issue, but the question remains. Do we want to make it handle easier for some people in the community, or do we want it realistic, no matter how hard it is? For some, not an easy question to answer. With regards to your takeoff, go for maximum torque, but rotate more gently. You'll find the torque a lot less pronounced. Watch the video I posted of Jason Miller flying the TBM in sim. Many thanks!

I hear you, @oldflyguy. We always have, and always will listen to criticisms. If something isn't right, in most cases, we'll fix it...whether it's got to do with the artwork (my area) or the systems and flight model (toto's area). Jason Miller came into the project well before I was asked to come on board (January of this year), and it was this very aircraft that swayed Jason to X-Plane from FSX. I didn't make the flight model. That was all Toto and Jason, with Jason providing feedback and testing. But what Toto DID do, was actually code the flight model in areas where Planemaker couldn't go. That includes ground handling. Is it accurate? I can't say it is or it isn't, based on my TBM experience (none). But if Jason Miller, who owns and flies one on a regular basis, as well as owning X Plane for over a year, tells us the ground handling is accurate, or as close to accurate as Toto could get it, we have to listen to him. Considering all factors affecting the flight model (prop wash from a PT6 hitting the vertical tail, P-Factor, weight of the aircraft vs propwash), I can certainly see how it could be a very sensitive aircraft as far as ground handling is concerned. We can certainly triple check the flight model with Jason and get a final word from him.

Toto is looking into the exception handler crash (which is what is happening in your case.) We'll hopefully have it included in the next update, due out in a few days.

He actually flies X-Plane quite a lot as well.

Please get back to me @SchwabeVR if the above post is what is happening to you as well.

That might be it. I run X Plane in windowed mode. I can run it by toto and give him this extra information. I will try what you suggested and take it from there. Again, your patience is appreciated. We'll get it sorted out.

Excellent. Glad to see you have it sorted. Enjoy.

IIRC, this is one of the things that was broken in the last update, but will be fixed in the next update, due in a few days.

I have a 980ti, and I'm only using the multi monitor set up to undock the displays and put them on my 2nd monitor. To do that, I use the nvidia control panel. I can drag the X Plane window across both monitors, but I prefer to use just my main monitor for X Plane and the 2nd monitor for other things. The image posted in my previous post was from another user in the Hot Start discord group. I can ask him what his specs are, if you like. This is my current set up. Both are 4K displays.

We do support multi monitor set ups. Always have from the beginning. But trying to figure out why some people have problems and most don't, can be a little difficult. We ARE trying. And I can safely say it's not, as you suggest, everyone with multi monitor setups having these issues. I have two 4K monitors, and I have no issues. The image below was taken on a 3 monitor set up, and he doesn't have the problems you are describing. Some of our testers also have 3 monitor setups, and they had no problems. I can understand your frustration, but we need you to please be a little more patient. Posting more than 1 thread on the same topic won't get this issue fixed any sooner. This image was taken on a 3 monitor setup.