@eltoppolino said in understanding pricing: One additional thought directly for you Nick From my perspective, Just Flight and I agree on a single fixed price in USD/GBP, and I include this exact USD price coded into the marketplace build of the aircraft. For the Caravans, that was $47.99 USD. Currently, when I view the Just Flight store, I see $47.99 USD. In the marketplace, I see $46.99 USD, making the marketplace one dollar cheaper than the Just Flight store in my region. One of the selling points for me with Just Flight as a partner was their "multi-currency" website, which presents the price to users in their local currency, with all exchange rates and taxes accounted for. I figured this simplified the process for my users, as there would hopefully be no surprises or confusion at checkout. In so many words, I select exactly one price, code this price into the marketplace package, and what happens from there is up to Microsoft. From my desk, all of my aircraft are priced identically between the Just Flight store and the marketplace, except the Caravan, which is ironically one dollar cheaper on the marketplace for some unknown reason. If there is any reason I would ever encourage someone to purchase from the Just Flight store directly, it would be for the easier/faster update deployment and direct email communication, but never over pricing differences.

Hi, Stuart. Thanks for the screenshot. Unfortunately, I've checked everything here, and there is absolutely no difference between the instrument face, and the rotating card in texture, material, object, or anything else I can think of. From my perspective, they should be treated identically to each other. Additionally, there should be no LOD drop of the interior when seated inside the aircraft, only small object culling. I know that's not a very satisfying answer, but I genuinely don't think there is anything I can do to improve the situation on my end, sorry to say.

Usually a sign of a conflict with another program. I would recommend going back to support.

Hi, I'm the developer of the KLN-90B. The real unit does not calculate a VNAV path and therefore does not output any sort of VNAV information to other avionics or to the autopilot. You would need to fly those approaches with CDFA manually. The manual of the KLN mentions that the database only contains approaches that the KLN is capable of flying. However, a pilot who still uses the KLN in the real world, showed me, that the database actually contains pretty much all RNAV approaches, even those that the KLN would not be legally allowed. Therefore, there is now hardly any filtering for the approaches anymore. Handy for us sim pilots... If you are interested in discussing the KLN capabilities further, there is a link to the Discord server on the Github page of the KLN-90B. I only check the JF forums occasionally.

I definitely know how I'll be spending my weekend

Thanks for the notes, I'm glad to hear you're enjoying the aircraft! There is a lot of love for the TBM in the community, so I am always happy to apply fixes and port new features to it over the years. I know I fixed the trim master switch issue a while back (awaiting the next update), but I'm surprised nobody else reported the window rain effects yet! I've just fixed that for the next update too. I also fixed the composite mode electrical issue a while back, which was a little less trivial to unravel. The DME issue was actually just a display problem, rather than a radio problem, but it reminded me of a limitation with the aircraft, just in case you go looking after the next update. I boxed myself into a corner, because there is a limit on the number of NAV radios we can "spawn" in MSFS, and I need at least one to drive the DME holding. With the KNS RNAV, that leaves only one DME holding receiver to share between the pilot and copilot's DME unit. This means that whichever one is put into hold mode last will override the holding frequency of the previous one. With what an infrequently used feature this is, I figured it would go unnoticed in normal operations. Lastly, I'm not surprised about the FD in MSFS 2024... Last time I checked, there were some undocumented changes made to the flight director that I had yet to fully investigate. I had hoped they would be reverted, but apparently not. I'll take a look later today, and see what I can learn about the new behavior. Thanks again, and let me know if there is anything else I can do for you!

I haven't seen any reports like this with any of my aircraft, but the only thing that should affect the aircraft like this is obviously the weight and balance. I suspect you had an enormous baggage payload, which was recalled when the aircraft loaded. Can you share a screenshot of the tablet's payload page when the aircraft loads? Just resetting it once, and ensuring the state was properly saved should spare you the trouble in the future.

I opened a ticket with SI on this also. For me, it wasn't doing this a couple weeks or so ago and doesn't do it when the SI app is closed. Must be they are turning com1 back on in MSFS due to tickets with people that don't know how it works. X-Plane 12 works perfectly, I can switch mics and turn off radio receivers without the com1 receiver coming back on after a few seconds with the SI app connected.

Where did you download this from ?

Hi . Is there any news on this ? Thor H

@MD82 said in Perfection defines the BS Starship: @alanfernandes said in Perfection defines the BS Starship: Hi! You can find the cruise performance tables in the official Pilot's Operating Manual for the Starship. Here's the link: https://rps3.com/Files/Starship/Flight%20Deck%20Publications/Starship%20Pilot's%20Operating%20Manual.pdf It includes all the power setting data and performance charts you're looking for. Hope this helps! Cheers. Those I have and use since day 1. I was merely asking because your picture is in digital format. I actually use the manual along with AI to interpolate and calculate the numbers. Those results you saw were generated by the AI, and they line up perfectly with the manual.

Just a personal observation on this. When i bought the baron and bonanza packages and did my first flights. The same happened to me. What i noticed was that on my yoke profile in controll settings, i had "set nosewheel limit" mapped for the piaggio 180 on a button. Maby i pressed that in flight. After i removed it on a new profile i never had this issue ever again. I only had the locked steering issue on day 1 of owning these planes and it has never happened again since. This is on msfs 2020. Maby it helps.

The new weather radar API applies only to WASM based instruments, so unfortunately not right now. Sorry to disappoint.

It's simply the difference between ISA and OAT. You will come up with either a + or a - difference from ISA. With that you enter the tables. Say you're at FL370. Either the POH (ISA Power setting table) or the aircraft will tell you that ISA is -57°C. Now check you're OAT (IOAT). If your OAT is -47°C, then you're at ISA+10 (10°C warmer). Caution against comparing IOAT value on the instrument against the table value. This value changes with speed, and as your power setting is not set yet, the difference in values might differ as you try to set the power setting.

@Voice-of-Reason said in Microprose B-17 = Version 1.30??: @udidwht Whose site? We are awaiting a 2020 version to put on sale. I know it was planned but don't believe it's completed just yet. Micropose site

@AvApollo On the 750, I clicked from GPS to VLOC (not at the sim, but I am thinking that is what I did.

@hunterdouglas You make some good suggestions. But.... not sure there is much we can do to satisfy these requests. A fleet of GA aircraft 'in a box' (as we did with the old PlusPaks) is feasible. However, standards are a LOT higher than in PlusPak days and, because there are a lot of freeware AI aircraft about, I am not sure we would be able to make much of a commercial success of this one - certainly not enough to justify costs even without liveries. More importantly, any such pack would need to function 'in game', rather than just provide aircraft. We'd need it to work (and be bought by) a decent number of ordinary users - not just DIYers (see below). Creating an airport modifying tool is not something we'd really want to get into. It's not our bag and we generally leave tools development to third party devs (see, for example, Real Taxiways from Black Square). Over the (many) years we have been doing Traffic we have seen that buyers tend to fall into three categories: Flyers - want a product that adds realistic commercial traffic to the sim so they are not flying in empty skies and don't see United Airlines 737s at Glasgow. Spotters - like to watch the 'action' happening around airports. We even built a 'Spotty' tool to satisfy this need in a previous incarnation. Suffice to say we haven't included Spotty in any subsequent version. Tinkerers - people who like to repaint aircraft, add missing planes and schedules or create flight plans from the past or in more obsure locations. The vast majority of buyers of FS200X/FSX/P3D/MSFS versions fall into the first category. We did find a higher number of Tinkerers for the X-Plane version, which is probably a function of the sim itself. X-Plane has encouraged tinkering for many years with things like Planemaker and flying on Mars. However, even 'over there' the majority of users still seem to be Flyers. What this means, of course, is that we need the software to appeal to the majority of users and that's where a big chunk of the compromise comes in. It also means that any future developments and updates after initial release are usually restricted to more planes, new liveries and updated schedules. Beyond that, we are constrained by the commercial realities of dev cost vs sales potential. So, while we dso our best to make it possible to modify and customise the Traffic offering, it's not a core part of the add-on.

it's so annoying and for 30 dollars it should be fixed at least