Streaming issues in draft repo

[AZP]

Version: Any SU3/SU4 version

Frequency: Consistently

Severity: Blocker

Marketplace package name: azurpoly-aircraft-jaguar-a (native MSFS 2024 version)

Bug description:

Hello,

We currently have an issue with the streaming of our native MSFS 2024 Jaguar in draft repository. Martkeplace teams have been looking at it for three weeks without success, hence they asked us to open a post.

The current release version is v1.0.1. We have an update (v1.1.0) that we uploaded on MCP in order to test it in draft repository before release.

The upload on MCP is successful and the page shows that v1.1.0 is now available in draft repository.

In order to test, we open the simulator in draft mode:

We launch a flight with the Jaguar GR1. We can see that the HTML/JS is correct as the version displayed on our custom EFB is the new one:

However, when clicking on over-wing weapons (which is a new feature of this version), they do not display in the model.

We also did some changes in cockpit tooltips in this update but they do not show (parachute is not inop any more):

So the XML is still the one from the release version (1.0.1) while the HTML/JS is the one from the draft version (1.1.0). It seems different versions are mixing up.

Please note that we had a similar issue once even with the Jaguar project opened (the XML was the older release version), so it definitely looks like strange streaming issues.

If we extract the exact archive we uploaded on MCP and put in in the Community folder, everything works correctly.

The same issue was experienced on PC and Xbox with two different accounts.

We already tried to re-upload the package on MCP (even with a new simulator export) without success.

We can send you the new version privately if this can help.

Thanks, kind regards.

[Boris]

Hello,

We have already logged the issue in our backlog and this is under investigation.

I (or the marketplace team) will let you know when we have some news to share.

Regards,
Boris

[AZP]

Thanks @Boris, do you think it could be resolved before the end of year?

Our customers have been waiting for this update for almost one month now, and Marketplace team could not help which is quite disappointing.

[Boris]

Hi @AZP ,

This is beeing investigated.
Can you tell us what’s the name of the xml file you are talking about please ?

Regards,
Boris

[AZP]

@Boris From what we observe, all the XML from the aircraft is not up to date and showing the previous version.

One example in Jaguar_A_int.xml:

In v1.0.1, parachute handle code was:

<Component ID="MISC_Parachute_Handle" Node="MISC_Parachute_Handle">
   <UseTemplate Name="AZP_JAGA_SWITCH_CODE">
      <ANIM_NAME>MISC_Parachute_Handle</ANIM_NAME>
      <LEFT_SINGLE_CODE>(L:AZP_JAGA_MISC_PARACHUTE_HANDLE, Bool) ! (&gt;L:AZP_JAGA_MISC_PARACHUTE_HANDLE, Bool)</LEFT_SINGLE_CODE>
      <ANIM_CODE>(L:AZP_JAGA_MISC_PARACHUTE_HANDLE, Bool) 100 *</ANIM_CODE>
      <TOOLTIPID>PARACHUTE HANDLE (INOP)</TOOLTIPID>
      <WWISE_EVENT_1>handle_toggle_on</WWISE_EVENT_1>
      <WWISE_EVENT_2>handle_toggle_on</WWISE_EVENT_2>
   </UseTemplate>
</Component>

In v1.1.0, the code is:

<Component ID="MISC_Parachute_Handle" Node="MISC_Parachute_Handle">
   <UseTemplate Name="AZP_JAGA_SWITCH_CODE">
      <ANIM_NAME>MISC_Parachute_Handle</ANIM_NAME>
      <LEFT_SINGLE_CODE>(&gt;H:AZP_JAGA_MISC_PARACHUTE_TOGGLE)</LEFT_SINGLE_CODE>
      <ANIM_CODE>(L:AZP_JAGA_MISC_PARACHUTE_HANDLE_PULLED, Bool) 100 *</ANIM_CODE>
      <TOOLTIPID>PARACHUTE HANDLE %((L:AZP_JAGA_MISC_PARACHUTE_HANDLE_PULLED, Bool))%{if}(DEPLOYED)%{else}%{end}</TOOLTIPID>
      <WWISE_EVENT_1>handle_toggle_on</WWISE_EVENT_1>
      <WWISE_EVENT_2>handle_toggle_on</WWISE_EVENT_2>
   </UseTemplate>
</Component>

When testing v1.1.0 in draft repository, we can still see the older tooltip from v1.0.1.

The same issue happens with other parts of the XML (see description above about over-wing weapons not displaying), this is in exterior XML.

Kind regards,

Romain

[Boris]

Hi Romain,

We tested your package in the draft repro and could not replicate the behavior.

Are you sure your Community folder is empty, and that you haven’t used the Download function in My Library for the public package (for example)?

In Tools → Virtual File System → Browse, you can see all loaded files (except encrypted ones like XML). So, if you open this tool and you can see the XML files, it means local files are being loaded.
Can you check ?

Regards,
Boris

[AZP]

@Boris Checking VFS menu put me on the right track.

We have a very old test package uploaded on MCP (named “azurpoly-jaguar-a”), which was used for beta testing.

Even though we asked MS to delete this definitively, it is still here and streamed in draft repository.

I used to disable this package manually from my library but I found that it is currently enabled, probably after a recent FS24 update/reinstall.

Hence this old package was overriding some files of the correct package because it is considered with higher priority.

Maybe it is not in your scope, but are you able to delete this package “azurpoly-jaguar-a” on your side?

We want to keep only “azurpoly-aircraft-jaguar-a” for the future.

Thank you very much for your help.

[Boris]

You’re welcome.
Glad we found the culprit

We removed an old reference in our tool. Could you please restart the game and let us know if things are better now?

If the old package is still showing up, you’ll need to contact the Marketplace team on Teams so they can disable it (and investigate if it’s already disabled but still beeing displayed).

Regards,
Boris

[AZP]

@Boris I still see it displayed, but we will ask the Marketplace team, thank you very much!

Kind regards,

Romain

[system]

This topic has been automatically closed after 60 days of inactivity since it was marked as by-design.

If there is important new information about this same report, you can use the “Request reopen” button below to ask the moderation team to review it again.
For other issues or broader discussion, please open a new topic in the appropriate category.