I would be interested in knowing that too.

You don't need to do anything special. Simply use the Just Flight installer and the add-on will be installed in your Community folder. If you have the Community folder defined on drive D, it will be installed there.

After spending the entire afternoon doing various in-depth tests, my conclusion is that sometimes it works and sometimes it doesn't. I don't know who's to blame, the simulator or the add-on, but I haven't found a logical explanation. I used the same settings in both the simulator and FS Traffic. Sometimes traffic is displayed and sometimes it isn't, both on the ground and in flight. I've tried larger airports (where it's impossible not to have ground traffic), doing shorter flights and slightly longer ones. I've changed the time of day, changed options in FS Traffic, like Time Before Departure Value, deleted traffic, and then regenerated it, but there doesn't seem to be a pattern. When it works, everything works fine, and when it doesn't work from the start, no matter what I do, it doesn't work. The truth is it's a bit frustrating and the program's behavior is quite random.

@Black-Square Haha all good man - yea and I am not saying it's not me that's the problem with loading or a selection in the CDU or something lol. I have NAV source set to VOR. I enter the departure airport to say NZWN, click button by yellow 'enter', then again by 'OK', but when I enter OH for Ohakea VOR in next line and try to hit 'enter' button - nothing happens at all. Almost like it is waiting for at least a 3-letter waypoint name. But yea no rush or anything, aircraft still tunes up the VOR's correctly, both manually and in auto-tune in RTU, and displays correct identifier etc. on displays and maps. So can still navigate by VOR, just not as an actual waypoint in the FLT PLN.

@Black-Square said in An update for 2024 compatibility please: .... Instead, there will be Professional Series, which is their replacement with many more features and far better graphics. That's great news! Cant wait!!!

@SirPilot Your MS Store screenshot is from MSFS 2020 (SU16). But you are correct, latest MSFS 2024 SU4 beta version is 1.6.5.0. What's your MSFS 2024 page say?

@dadgametime said in Bundle or discount for 2020+2024?: If it went to spam, it’s long gone. That's a shame. Contacting Just Flight Support would be ytour best bet. They can send you another code.

Any updates on this? Really looking forward to the update for the Duke in 2020.

Perfect. Thank you very much @Mark

Ok. Nvm. I’ve abandoned repainting it

I think there are issues with many 3rd party aircraft in SU4 beta at the moment, WASM issues? I think Asobo are aware and will fix it in a future SU4 beta build. Probably best to stick clear of the beta for the moment until later more stable builds

I'll say it again.. Thank you Nick for all your aircraft.

thx for that was looking everywhere

Still having no sounds in the TBM.

@Black-Square in Germany we have a saying: Ich nehme alles zurück und behaupte das Gegenteil. Which translates to: I take verything back and am now saying the opposite. I just did a longer flight. The problem isn't your plane, it's the simbrief profile that seems to be a bit off, predicting a lot more fuel burn. On shorter flights that are between one or two hours airtime it's so severe that it actually presented to be in parallel with my use of the sim-rate. After a four hour flight (with a noticeable headwind) it's a bit closer and not in parallel with my use of the sim-rate. Hope you didn't put any time in investigating this, yet. Sorry about this.

I absolutely love it. The very rudimentary FMS is insanely unique and honestly fun to learn.

@Mark Hey, thanks for the work on this and following up. I've meant to stop back by, but loving the 2024 Vulcan update w/ the included static weapons, have had a great time enjoying them all while flying around.