@fabristunt Fixed - sorry about that

@Voxen I had the same issue and followed your advise. But unless that, I was not able to install it into the community folder due to long file names, so I installed it in the default install adres of justflight (C:Justflight) and that worked. Thanks !

Thank you for sharing Since I always like to say that "I never get to fly my airplanes unless they are unfinished or broken", I derive most of my enjoyment of them from hearing that you've enjoyed them

@SkipperMacz In case you are interested, I have completed the project based on v1.1a. I have also updated the accompanying document. Check out the link: https://drive.google.com/drive/folders/1bt0euYHjSdla7srvA_8fSl4J8yQjiLlk?usp=sharing I added in all the axes and reconfigured a few things. There is now no need to have anything configured in FS2024 itself.

@MiRexer Well, that's the same technique I used when creating Turbine Duke panels . But I still think the results are preety nice

Glad I could help. Good luck!

I would love to see the ProLine 21 avionics but it feels a bit counter to the Black Square ethos… I hope I’m proven wrong!

Again a few minutes ago, huge storm over Geneva with many lightnings and not a single dot in the vectorscope. I eventually got some random dots when I switched the gear out.

@Mark fair enough, appreciate the thorough response

@Mad_X i am sorry, my english is very bad, i am not from the US. i dont understand what you mean, sorry

@venemair thanks for your reply . My experience echoes your own as flew back to EGNX from EIDW last night and no such issues. I was keeping a much closer eye on the amber band on the speed tape and the ATS handled things fairly well, all be it with a bit of hunting when heading downwind, but it did a reasonable job of maintaining the speed. Wind on finals was realistic and did a pretty smooth landing, so inconsistent, but will keep persevering!

@Black-Square I am also experiencing some strange behaviour. I am not sure if this started after 1.1 or was there with 1.0. The "VR Tablet Static Position" option in the tablet is always resetting back to an "On" state for every flight. I turn if off and at the start of the next flight, it is back on again. This is happening for the TC variant only. I am able to toggle it off on the normal variant and it stays off.

In the engines.cfg documentation for the SDK, it says that the default airspeed minimum for the Hobbes elapsed time is 25 knots. So given that, you should have less time on the Hobbs meter than the tach time.

I bought BATC and I can confirm it works great, it avoids the native ATC bug and does better traffic injection than other tools.

Interesting. I didn't change anything either. I'll work on it on my side then to see what I can find. Thanks for the quick confirmation.

The change in new update seems to be good for me. Needle moves in NA and TC no problem.

got it - button needed to be pulse/momentary....thanks

@Rich said in Commander Update v0.1.1: @Fabbi It's down to how long the paths get inside the package folder. In the case of the Commander, this html path often pushes users over the limit: bksq-aircraft-commander114\html_ui\Pages\VCockpit\Instruments\Generic\Misc\bksq-aircraft-commander114\BlackSquareTablet\Shared\Assets\commander114ElectricalVisualizer.svg If you add the path to your Community folder to that, in my case it becomes 271 characters long and Windows won't allow it, even with 64bit versions of the installation software. Other aircraft have shorter names and more people fall under the path size limit. As this is one of the longest we've had, more people are seeing it. For the Commander, I've expanded the default installation option in the installer to pre-check whether the package will fit inside the path limit, and if it won't it will send you to the custom location option that will get you around this limit. Hope that helps explain what's going on. Thank you so much for this information.