Hi Everyone,
Recently, we released our Kennedy Space Center V2 for MSFS2020, featuring on-demand rocket launches, relying heavily on custom VFX and SFX. Then, our title was ported (by Microsoft) to MSFS2024 and released. However, while 2020 version is behaving as expected, 2024 port is being rather glitchy and exhibiting some frustratingly bad behavior:
- The rocket trail VFX gets cut off and dissapears shortly after the rocket leaves the launch pad. In 2020, the rocket trail lingers for an intentionally long time, as the particles are assigned a long life span.
- The rocket launch sound FX, which we control using custom LVARS to turn on and off, cuts out at a certain distance from the SimObject it is attached to. When we get back closer to the object, the sound kicks back in and plays.
This to me sounds as if 2024 is limiting the resources for these. The methods we used to implement these were strictly by the book SDK-compliant, however, the original scenery was built and compiled using MSFS 2020 SDK.
So, before I start dissecting my project, my questions are:
-
While, as far as I understand it, SDK documentation is unified for both 2020 and 2024, how different are actual SDKs?
-
What is the purpose of MS-performed port of 2020 to 2024 compatibility? Is it, sort of, let’s see if we can do it the quick way, and if there are problems, the developer has to open the project in 2024 SDK and re-compile everything, making it the “oficcial” 2024 title?
Thanks for any and all insight into this,
Mitch
TerraBuilder