Piston & Turbine Dukes

@Black-Square said in Turbine Duke minor tablet/cabin temp bug: It's done I forgot that the sound was already there, so it was much less trouble than I was expecting. Thanks for prompting me to add this feature. Awesome, thank you for your quick response! This will be a major quality of life improvement for me in the TBM. I asked the Turbine Duke owner my aircraft is modelled after, and he confirmed that it often requires differential power lever settings, which is why he prefers not to use the air conditioning at all, since it puts differential wear on the two engines. Very interesting input, thanks! That's what I was wondering about. I had to taxi with the left engine in beta and the right engine above idle which felt quite odd. It was too hot not to use the AC though. Can you give me some more specifics on what scenario you have produced where the target temperature does not turn red? Fortunately I took a screenshot. I was cruising at FL270, -33°C OAT and had the temp mode in auto heat. I played around with the press. air temp/bleed air handles and pushed both fully in. As expected the cabin temp started to decrease rapidly but the target temp did not turn red. I was under the impression that it would turn red as soon as the desired temperature was unable to be reached but if there is a threshold that probably explains it. I only waited a couple of seconds so I don't know how low the cabin temp would've gotten. [image: UzgO9yc.png]

FWIW, my set of files in the Community folder hasn’t changed at all since I thought I had everything running fine prior to v1.1., other than the PMS GTN 750 update. I’ve done some more testing today, and now I wonder if there might merely be something I don’t understand about the Century IV autopilot. Specifically, it seems that anytime I manually disengage ATT mode by clicking ATT, the autopilot lights up the GA button (which I don’t understand the purpose of) and thereafter I cannot reactivate ATT mode again while GA is lit (the latter just stays lit). But if I instead enable ALT mode while GA is “stuck”, then the GA light goes out, and after that I can reselect ATT mode and have it actually kick in again. Is this the intended behavior, and if so, is there an explanation for it?

@Black-Square Does that also apply to the Turbine Duke though? I find it a bit odd that the AC won't work at flight idle. It does in the TBM.

It's amazing how many things can get by you when you have to hyper-focus on a different system every day... My apologies. I found the mistake in my code. Thanks for pointing it out!

I cant seem to get the plane to descend with AP on at all. Climb works fine and as described in the manual, but when I go to descend, lower the altitude selector, and press ATT, the only thing that happens is that it resets the altitude selector to my current altitude? I've also tried turning AP off, starting the descent, then pressing ATT and turning it back on, but it seems to do the same thing, resetting the preselector to the altitude I was already at. In the C414, I have to deactivate ALT mode manually before starting a descent, and I was hoping the same thing would work here, but clicking on ALT does not turn it off.

The standard high quality people models that show up in some add-on airports and also the Milviz C310 are great, I can't understand how some people think they look bad or fake. It's a flight sim, not Grand Theft Auto, they are the best looking people I've seen in any actual flight sim. Other planes like the Hjet have some awful looking fake and polygony people models I've not seen anywhere else. The ones the CJ4 with Woosel Mod are pretty nice too but I haven't seen them elsewhere.

Feels normal to me. I've only taken the plane on two flights but have had to do a lot of hand flying due to issues with the AP, and it flies smooth and steady and feels like it has some weight to it.

I just went looking now. It was a single character error in the XML. The failure triggered from the tablet would have worked correctly, believe it or not. Thanks for pointing it out. It's nice when the problems are easy, but then it takes me ten times longer to reply and document the change than it did to actually fix the problem!

I just saw it. Thanks so much. Fabulous repaint as always.

Toddimus from siminstrumention (https://github.com/Simstrumentation/Air-Manager) is working on this. On the 22 May 2024, he stated it will take a while to complete the project. I am using few free instruments from the AirManger store as a stop gap until the Toddimus's work is completed. There is a siminstrumention Discord where Toddimus post updates.

I've had the same issue since I first installed, then reinstalled, then cleaned my Community folder and reinstalled. I've never been able to get the frequencies or fuel state to save, or the engine to show wear. I've worked with Simon from JustFlight extensively on it, but we haven't found a solution. On the other hand, we did discover that failures work, and are persistent from flight to flight.

It remains a mystery to me as to why this LUA script does not work for the right mags in the BKSQ Piston Dukes, but it does work for the left mags. And on top of that, this same script works both mags without any issues in the BKSQ Baron. Until I can figure this out, I decided to bind the BU0836X mag switches directly in MSFS, and both mags are working as expected. What a fun plane to fly!

@Black-Square said in Thanks Nick: Thank you for taking the time to write and let me know what you think of the aircraft. As much as I am guilty of enjoying the praise, the real reward is knowing that there are virtual pilots out there engaging with my aircraft as deeply as they were designed to be engaged with. I know that my brand of "unapologetic realistism" is not for everyone, but I know there is a certain constituent of simulator users who would settle for nothing less, because I am one of them! Thanks again, and please let me know if there is ever anything I can do to help improve your experience! You really do take it up a level compared to even a lot of the major players, and my only issue with Black Square products is that there's just one of you because if you made more planes I'd likely never fly anything else again. I have been spending a bunch of time recently in a certain 50s vintage propliner made by a large flight sim studio (who shall deliberately remain nameless, I'm not here to disparage anyone specifically), and while she's one of the most fun and rewarding planes to fly IMHO, when listening to the purr of the engines at 13,000ft, all I wanted to do was tap on the damn gauges. I thought "wouldn't it be fun if engine four was reading a higher fuel flow because it's stuck?" It's that extra mile you go through with all those tiny little things that make your aircraft feel so damn alive. It's such a small thing that it makes flying some other products infuriating because, if they put just a bit more TLC into them, they could be the same way. Plus your support is top notch. Sometimes it feels like other developers put a plane out and forget it in lieu of the shiny, new one they just put out, but you put how many man-hours into poking the WT AP looking for an issue with the Caravan that affected maybe 12 people here on the forums? I've been at the point where my sim time is drastically exceeded by the number of planes I have/want to fly for a while now, but your aircraft are always at the front of the purchase line.

Throttle1=-24000,-512,512,16380/32 for My DUKE ОК! Maybe I'll tweak it and get -23,000, too. Many Thanks!

@SMN204 I'm using K:AVIONICS_MASTER_1_ON and K:AVIONICS_MASTER_1_OFF events. You should be able to find those among in the list of events in FSUIPC, no need to define your own for them.

Thanks brennan. Could you please elaborate what you meant by entering Beta range ? Found the Beta range in the manual. Checked and it is the cause. Thanks

It is easy made with the MSFS controls. With Honeycomb Alpha in my case, but also can be made with other hardware. [image: d0a16850-873a-4b7e-9da3-a0baa9c3609b.jpg] Hope this help.

As always, a problem with the Community Folder. Wrong gtn750 folder. subfolder gtn750

Thanks for the explanation.