Piston & Turbine Dukes

I was using Su4. I've just tried it again with the SU4 update from last night and it seems to be OK. Still got the VR problem but at least they are moving now. My bad for not trying it with the current release

@Mustang said in Ear Discomfort Index: perhaps the sounds could be slowly dulled until you simulate 'popping' your ears I actually thought of this too. It would be a lot of fun, but as you can imagine, I'm always worried about our many niche features resulting in confusion for the more casual users.

@Black-Square you can turn off light shafts in graphics, I just want to see shafts sometimes, like in clouds so I leave it on for now. Would be cool if you could add a realistic landing lights option in tablet maybe.

@Zwoop68 Thanks for the link. I had seen that thread, but given the title, I skipped it. I confirm that's the problem, and now I've solved it. Thanks.

@Zwoop68 That did the trick! Unfortunately, the copilot seems to twitch in the seat a bit. I really hope Asobo rethinks their motives for taking away these options from 3rd party developers.

No worries! I’ll sit tight and wait for SU4 to hopefully fix those issues!

@Mustang said in v1.2 quick feedback & couple of nitpicks: the cooling lines were coloured green vs everything else in orange For future reference, when the air conditioning system is fully functioning, the refrigerant lines will be orange and blue. Orange on the return line, and blue on the feed line.

So begins the 7½ years of waiting for Microsoft to get the update to Xbox.

Latest update today, fixed it.

I'd definitely love to see external power available on demand! Some airport designs just don't have parking properly coded.

Thanks Nick. Glad to know it's already noted. It doesn't detract from the enjoyment, just struck me as odd on a few occasions. It must be so challenging to decide where to focus your efforts when there are so many areas you could work on, old and new, especially with your high standards which shine through in all of your aircraft! Letting little inconsequential issues like this go unfixed are probably frustrating for you, but you have to pick your battles

Right! Got it sorted. 4 for the 'On' + Repeat when held. Starter has a little dig but I'll live with that. Can't do a mag check though but I'll live with that as well. Thanks again for replying, I appreciate it. No need to look for another twin now.

Got it. I see the section in the manual. Thanks.

It sounds like the throttle is full forward and the engine overtorques

@Buzz you may well be right. Given that the majority of the time the aircraft is loaded in the sim, it will be in a running state, that approach won't make much of a meaningful difference vs a failure timer that only runs when engines are running. Nick said there's a reason for real inspections being "based on calendar months", which I took to mean that all the elapsed time between flights would be considered for failure generation when you next load the Duke in the sim, but I may have read too much into it. I suppose one way to test might be to set my computer clock to 1995 (furthest back Win10 will go), reinitialise the Duke by deleting any saved/state files, then load it in the present day and see if any failures had appeared. But I'll just wait and see if Nick clarifies first. If your idea is right, then maybe my idea can go on the wishlist instead - perhaps as a toggle option

I almost thought this was a duplicate, because we just had a nearly identical post a day or two ago. Here was my response: "Every time I have seen a similar complaint, the cause has been destroyed engines (usually due to improper starting procedure). Check the engine health bars on the upper right of each engine visualizer page. If they are at 100%, then we can troubleshoot further. A video or screenshots might help at that stage." If that's not the problem, let me know and we will troubleshoot together.

Every time I have seen a similar complaint, the cause has been destroyed engines (usually due to improper starting procedure). Check the engine health bars on the upper right of each engine visualizer page. If they are at 100%, then we can troubleshoot further. A video or screenshots might help at that stage.

Fixed, luckily another user had the same problem and he posted this solution and it worked for me Create directory "Microsoft Flight Simulator" inside directory "C:\Users%USERNAME%|AppData|Roaming" Copy file "UserCfg.opt" from "C:\Users%USERNAME%\AppData\Local|Packages\Microsoft.Limitless_8 wekyb3d8bbwelLocalCache" into newly created directory above (1.) That's it - then you can run installer and after install you can remove

@Gilandred Well, it doesn't seem to have been the case. I made it very clear that I didn't want price protection, especially not a year later, but only that I wanted the option to pay the difference between the Piston and the Bundle at the official price. Nothing else. The rest is just something you made up.