@Black-Square said in Awesome but .....: I thought you were going to complain that the horizontal position of each screw seamed not to be aligned with anything else on the panel, but I made sure to place them correctly when I modeled it! Unfortunately, editing textures is not as simple as it once was... There are two textures you would have to edit, and then you would have to compile them into MSFS 2024's proprietary version of a proprietary file format, and then rebuild the package layout file, even if you could find those two small screws. Luckily for you, I am a sucker who likes to see all of my users as happy as possible with their flying experience, so I have prepared a version of these two files, just for you. Please contact Just Flight support, and let them know that I sent you. I will have them share the files as quickly as possible EDIT: Actually, can you please tell me which simulator you're running? They use different file formats. Wow! That is awesome Nick! Thanks so much! Thanks too for the explanation of what's going on these days .. sounds like I need to take a semester of MSFS cockpit editing at the local university level lol, yeah things were definitely easier back in the day. Simulator wise I'm running 2024, and I agree with V1 Kevin .. you've out done yourself on this one and its now my new favorite as well. I cant wait to see what your cooking up next!

@Voxen I too ignored it when I first ran the installer, but when loading the plane in the sim the engine visualizer and the storm scope did not work. So I uninstalled it and installed it to a custom path. Now everything works just fine

Thanks, it works

@JakeBunny That's disappointing. I dearly hope we get the option to remove them.

Chef kiss

Great, thank you! I’d seen someone mention on the MSFS forum that you can click and hold LMB and then use the wheel to accelerate it. I’ll check that out.

STATE SAVE Was the source of my problem. I fixed my start failure issues by loading a flight and going into the Fokker100 settings in the EFB and disabling “State Saving”. Then restarted the same flight and my engines started again. I believe the issue is more related to the State Save functionality than anything else. Especially if the last flight with State Save enabled resulted in a crash, pulling engine fire levers, or engine flame out before being unable to start engines as per normal. Didn’t need to remove my mixture settings from my Flight Yoke System, just need to be sure the mixture lever is always on full rich as with any add on. This was my solution, there could be others as well. Good luck all.

Yes. I was using the MX170Bs. There is a planned power is outage here most of the day, so I will get to this when it come back on this afternoon (Pacific Time). As I’m thinking on this, I wonder if any of my troubles were due to after effects of “hot swapping” the avionics. On initial load, it had the TDS unit, and I switched it to the MX. However, my initial load of the aircraft was in a different flight session (same sim session, though) than when I actually flew the aircraft. On that second flight session, the MX units were already enabled, so you’d think there would have been no after effects, as such. It will be interesting to see how it behaves with a fresh load cycle of the sim itself. I just know that Matt at Working Title had mentioned that hot swapping wasn’t a clean solution in 2020. I’m unsure if that continues to be so with 2024. Anyhow, I’ll get back when I can.

Ignore, just seen this is a duplicate issue. Sounds like it's just an animation bug

@Black-Square That's sad xD But I understand, thanks for answering and trying your best to find a solution. Best regards.

i hope that would bring so much visual realism to the propellers !

@jiangnan22406 This definitely sounds like a problem for Just Flight Support.

@WelshyV1 You too! Happy flying!

There was some talk about a possible issue resulting from not being able to do multiple offset waypoints. @Black-Square might have more information when he isnt busy with the commander 114

Update - Just went through everything again, made sure my physical default control positions matched the proper pt6 “just started” state and everything worked as expected, no abnormal issues. I restarted everything and went through it a few more times and everything worked correctly. For now the problem now seems resolved for me.

Awesome here