Got it, thank you! I'm flying on IVAO, and an active transponder on the ground is not desired as it will clutter the ground controllers picture with several aircraft nearby.

Sorry you're having issues. I hope you're enjoying the upgrade from the 2020 Analog Series, though! Everything has been working well on SU4 Beta for me (well, apart from all the beta bugs). I assume you checked the engine condition in the tablet visualizer, and they are not at 0%? If they're good to go, a video would be very helpful for me to diagnose.

Well I think I answered my own questions here. Seems the Duke will go up to just under 250kt IAS without any airframe vibration. It will comfortably cruise above the indicate Vne but you get that nasty overspeed warning. If you want to silence that you can pull the “stall horn” 5a breaker on the right hand vertical breaker panel. Now this is not how the plane was designed to operate so it could cause issues that I am not aware of yet as I just did a 5min test with it but I’m going to attempt a longer flight and see how it does.

I have not yet tried the TP Bonanza, but this seems like the normally Throttle 1 Axis (0-100) axis that works for all other BS products with beta and reverse ranges might not work here? Is that a correct assumption?

@Black-Square pms50-gtn750

For me the GPS setup, options in the EFB and loadout (pilot/pax positions and weights) are properly saved, the fuel and state of the covers and chocks are somehow not. I always start with half tanks and half tips.

All we can tell you at the moment is that there are tech issues at their end that they've been unable to resolve. This is linked to the submission process and mechanics of the way the products are placed on Marketplace and not to do with the specifics of any of the products. There are other Just Flight titles that have and suffering the same fate. There are no finer details to give that would help you here. We do continue to ask the questions of various contacts at their end who are involved and the general response is, without quoting directly is "Still trying to get the bottom of things to fix the issues". Frustrating for all of you, for Nick at BS and for ourselves and rest assured we continue to seek updates and information on a regular basis in the hopes of a breakthrough. That's all we can really say at this point, sorry.

I might have missed it, but will there be a Black Square King Air for MSFS 2024? If yes, any ETA? Thanks.

Awesome, thanks so much, I wondered if it were that simple. I appreciate the quick response!

wha?! i have lot of fun and still fly the birbs, why i can think about refund? i even don't use external views, but once walkaround before flight and, as i mentioned, some time after flight. i thought about refund just about principle stuff, as this method still in use, after months ago i said this is the problem in the velocity x ported... but. by same principle, if i still enjoy and flight, and flight with enjoy, about what refund we can talking about?! so no. no refund. and even if you haven't the solution, i can live without, and with hope, nick will solve this one day or another. but thanx for the offer:) this is my gratitude video(sure there not about this bug, and there only inside view). this bug pretty close to nothing for me. i just wanna this stuff get off from my eyes, just for not distraction on that bye bye. let me know when you found the solution not connected to reinstall, moneyback and stuff like those no sense things.

I do hope this will be improved. Engine temperature modelling seems such a fundamental thing for a study-level add-on like this. At the moment deciding whether/when to use cold or hot start procedure seems unrealistic due to the short times. Its ironic that the manual states there is a "realistic battery temperature simulation" yet the engine doesn't seem to have one. Don't want to appear negative, this really is such a great add-on that the very few things which aren't quite perfect just stand out more.

repair as expected change nothing. i guess reset won't as well, but i won't check that.

@Mark The issue seems very interesting. When you look from above the light seems to be spinning faster compared to from the side. This may just be a illusion though. I have made a youtube short with a quick video of the issue. https://youtube.com/shorts/egJCva37LXo?feature=share I am on SU4 Beta so maybe thats causing the issue. And it seems not to be livery specific as i have the same issue with different liveries as well.

@Black-Square said in The “Door Seal - Press" variable does not work for me!: If you want to try something that should be more reliable, try:

@Mark ok thanks Mark

A humble request to the JF staff: please bring back down votes.

The titles in the livery_config.ini for the RJ use the Title= entry from the Aircraft.cfg with the "Just Flight" prefix removed. There are two Northwest liveries included with the RJ, they each have their own entry in the livery_config.ini file as follows: [RJ85 Northwest Airlink] hasTailskid=0 hasVHF3=1 hasHF=0 hasMetAlt=0 [RJ85 Northwest Jet Airlink] hasTailskid=0 hasVHF3=1 hasHF=0 hasMetAlt=0 The 0s and 1s after the equal signs will indicate whether that piece of equipment is fitted by default. For example: hasTailskid=0 // The tailskid will not be fitted by default hasTailskid=1 // The tailskid will be fitted by default The livery_config.ini only supports the default liveries in the RJ at the moment, and I believe any third-party liveries will always load in with all equipment enabled. We recently added support for custom external equipment configurations for third-party liveries in our F28 Professional, and we plan on bringing that across to the RJ in the next update. Hope that helps. Mark - Just Flight

The GA expansion to FS Traffic isn't abandoned, but it is currently on hold for various reasons. The product was being worked on in MSFS 2020, and we did have a functional product being tested by our internal testing team; however, the development team ran into a roadblock following an MSFS 2020 Sim Update that broke some of the core functions that the product was using to control the AI traffic, and it required further investigation. Following the release of MSFS 2024, the majority of our development resources have since been allocated to upgrading all of our MSFS 2020 products to MSFS 2024 native products (the latest status of all of our products can be found here). These upgrades spanning the last year have prevented the development team from working on a workaround for the GA expansion in MSFS 2020, as well as investigating its feasibility in MSFS 2024. Once we are clear of the MSFS 2024 native upgrades of our existing products, we'll be able to take stock and assign resources back to other in-development products, such as the GA expansion. We'll be sure to share more news if/when there is something to share. Mark - Just Flight