MSFS2024 compatibility?
-
@SwissairMD11 These are all due to the integer division operator, believe it or not.
@LostPilot I actually doubt it's a standard library, or at least one anyone would recognize, because I believe the MSFS RPN implementation has been virtually unchanged since 1995. If I had to guess, I believe this change was probably the result of experiments with compiled RPN, which is a new option for developers seeking a little performance boost to their animation code. You can imagine how this might entail porting the RPN interpreter to a new language in the process. Hopefully you can all understand how this affects us developers, and why I'm not rushing to update my code in twelve aircraft across two simulators for such a fundamental oversight.
@Black-Square I understand it's quite the job to change it. And am willing to pay for it. Not sure for others but I surely will if the time is very consuming. I love the dynamic engine parts of it so that is worth a lot in my books.
-
@Black-Square I understand it's quite the job to change it. And am willing to pay for it. Not sure for others but I surely will if the time is very consuming. I love the dynamic engine parts of it so that is worth a lot in my books.
If the problem is with the host application and one of the libraries. I belive BKSQ probably has more interesting stuff to do (that we will enjoy more too), than spending a vast amount of resources on a workaround that may not be needed in a week or two.
-
@Black-Square I understand it's quite the job to change it. And am willing to pay for it. Not sure for others but I surely will if the time is very consuming. I love the dynamic engine parts of it so that is worth a lot in my books.
@SwissairMD11 Asobo wrote on their developer forum less than 24 hours ago, that the bug has been logged and that a fix is being implemented. Let's hope the correction can make it in one of the first patches that are coming.
-
Doesn't look like it's made it into 1.1.10.0 :-(
-
Hi, All. I haven't made a comprehensive statement about compatibility since MSFS 2024 released, but I thought I would address these particular issues, since they are all related.
All three of these bugs in MSFS 2024, as unrelated as they may seem, are the result of an incorrectly implemented mathematical operator in the Reverse Polish programming language called "integer divide". In MSFS 2020, the integer divide operator correctly divided two numbers, and then rounded down to the nearest integer. This rounding does not happen in MSFS 2024, resulting in the wrong output.
As you might imagine, this is roughly equivalent to changing how a button on a calculator functions without telling your accountant. This operator is used over 1,000 times across all my aircraft, so replacing it would be no small effort. We have notified Asobo of this issue, but have not heard any acknowledgement of the issue as of this writing.
I hope this explains some of what you are seeing, and might also give you a glimpse into what kind of issues my fellow MSFS developers and I are facing in MSFS 2024.
@Black-Square seems like a big miss on Asobo's part!
-
The patch notes for the latest update (1.2.7.0) include
Fixed integers division in RPN expressions
So hopefully that will allow work to move forward
https://www.flightsimulator.com/release-notes-1-2-7-0-available-now-msfs-2024/
-
Update: When piston is removed from community folder then all liveries are shown for turbine duke.
I suggest that BSQ investgates a potential conflict when both versions are installed in community.
For the moment you can't have both aircrafts installed.One more thing. The engine sound is fading in and out or some kind of phasing during flight.
Sounds like if the pilot is moving around in the cabin. -
Update: When piston is removed from community folder then all liveries are shown for turbine duke.
I suggest that BSQ investgates a potential conflict when both versions are installed in community.
For the moment you can't have both aircrafts installed.One more thing. The engine sound is fading in and out or some kind of phasing during flight.
Sounds like if the pilot is moving around in the cabin. -
@npoulis if you are in 2024, then I don't think Nick has guaranteed compatibility. I believe he's planning a patch or similar once all the bugs of 2024 are worked out.
@lilycrose So I'm communicating my observations to help them tackle the incompatibilities.
-
Update: When piston is removed from community folder then all liveries are shown for turbine duke.
I suggest that BSQ investgates a potential conflict when both versions are installed in community.
For the moment you can't have both aircrafts installed.One more thing. The engine sound is fading in and out or some kind of phasing during flight.
Sounds like if the pilot is moving around in the cabin. -
@npoulis I had some oddball sound as well, and turned off the Volume Limiter in the MSFS settings. That did the trick for me.
-
Love the Duke, but after the 2024 release I haven't had it out of the hangar quite as much. After Asobo fixed their RPN issue a while back, the plane/systems themselves seems to be working well in the 2024 flights I have done. Someone seems to have dropped a powerful flashlight on the floor (which even shines through to the outside a bit), but otherwise it looks fantastic with the updated lighting.
Unfortunately the save/state functionality doesn't seem to work over on 2024 so it is like a new plane every flight (including having to choose avionics in the tablet).Still - to get the occasional "fix" of flying the Duke, it is pretty useable in 2024 already.
Really looking forwards to when the full update is released. -
I'd gladly take the next update for the Duke in 2020, even if I am in the minority here. I suspect it may have been delayed due to 2024's release, which is understandable. There are a few fixes and improvements which are noticeably missing in 1.1 but due to release, such as the headphone simulation clickspot and sound of rain on the windscreen (if I remember correctly).
I mainly fly the Duke & Comanche so I'm not doing much with 2024 until everything is officially updated and 2024's initial issues are ironed out, especially in VR (looks like a long wait for SU2 though). My flying time is limited enough without having to contend with new problems and annoyances which I don't have in 2020. I want to switch to 2024, but I'm happy enough with 2020 so I can wait :)
-
Just fired it up in the SU1 beta in 2024 and looks like state saving is working as intended now (perhaps related to the sim now properly honouring tail numbers?). The weird light at the floor from my last flight is also gone.
So from my quick test it seemed to be working just as well as in 2020 with all the nice improvements from 2024 like faster loading, a built in efb, improved lighting and weather etc.
Would of course be cool at some point to have the 2024 walkaround feature integrated with the chocks/covers from the tablet.
-
Hi Folks,
I am new to this forum so please excuse if I am asking anything too stupid here.Is it in the meanwhile possible to install the BS Dukes into 2024?
I have not kept my old 2020 community folder and need to reinstall all payware. Some payware won’t let me do the install at all without 2020 on the disk.
Thank you for your support!
Boomer -
Hi Folks,
I am new to this forum so please excuse if I am asking anything too stupid here.Is it in the meanwhile possible to install the BS Dukes into 2024?
I have not kept my old 2020 community folder and need to reinstall all payware. Some payware won’t let me do the install at all without 2020 on the disk.
Thank you for your support!
BoomerI too find myself wondering this. I didn't get around to buying these Dukes in 2020 but really want them in 2024. From what I have been able to read it's possible to get them running in 2024 but only if you have it installed in 2020 as the installer doesn't give the 2024 option. However, there are some issues with it as it's not really properly compatible yet.
This makes me wonder how long it will be until I can buy these planes.
