Encryption is mostly broken

[MSFS 2024] Bug Reports SDK: Tools/Samples/Documentation
1

Version: from last week

Frequency: Consistently

Severity: Blocker

Marketplace package name: marketplace itself

Context: All aircraft in marketplace

Bug description: see here: https://devsupport.flightsimulator.com/t/encrypt-also-the-gltf-files/18008

Repro steps: buy a marketplac plane

download with visual file system. it says 0% but keeps downloading in the background. After that .gltf files can be imported in Blender etc.

2

Can you please :

  • Avoid creating multiple posts on the same topic.
  • Read the documentation: only LOD0 is encrypted, as has already been explained to you here.
  • Be more specific when reporting a bug: which payware aircraft did you use? Did you manage to import its LOD0 in Blender?
  • What “visual file system” are you referring to? Is that the “VFS Projector”? VFS stands for “Virtual File System”.
  • What “0%” are you referring to? Do you mean Windows Explorer shows a size of “0 bytes” until the file has really been accessed?

Best regards,

Eric / Asobo

1 Like
3

Yes, copy paste to windows explorer. And yes Lod00 has not been downloaded. So it’s ok, thanks for the hint.

4

Hey Eric,

would it be possible to include LOD01 in the encryption as well as a future addition?
Many developers might just hide little parts such as screws on LOD01, with the main detailed mesh still being included. Then only in LOD02 the main mesh would start to be simplified.
Having only LOD00 encrypted makes it very easy for people with bad intentions.

I know that there are always ways for people to steal the mesh but making this as difficult as possible would be a great support for us developers.

And something else I would like to ask. Can you please clarify the difference between LOD00 and LOD0, are they the same and will both be encrypted or is LOD0 the correct naming convention for encryption to be successful?

2 Likes
5

This will have to be discussed with and validated by Microsoft. I can already foresee a lot of anger from livery makers who were already complaining that LOD0 was encrypted and that they had to base their work on LOD1.

They are the same indeed - when looking for which files to encrypt, we match against both patterns.

Best regards,

Eric / Asobo

6

Thanks for the clarification regarding the naming.

I can definitely understand that livery makers will be frustrated. In the end however, the developers are the ones who are suffering from the piracy damage. Depending on the criminal energy of the thief it will almost be impossible to get the situation under control.
Knowing this limitation in the encryption I will likely restructure my whole LOD workflow before the product can be released, to ensure that the LOD01 includes less detailed meshes. This is not optimal and work intensive but I am glad that I found out about it before it is too late.
I am sure that the majority of developers would be very happy about a more strict encryption. As a compromise maybe this could be implemented in an optional way, so that developers can decide if they want more or less encryption.

7

Please refrain from speaking for the “Majority of developers” As a developer I’d prefer not to annoy livery makers with something that won’t slow down piracy at all…
Anyone stealing your models isn’t doing it from your LOD0 or LOD1, they are taking from memory, something the file encryption can’t stop.

1 Like
8

Why would livery creators need Lod0 at all? You could simply provide a paintkit.- As for me Lod1 - 3 or so should be encrypted. Or even all files? Copying from memory seems to complicated for most pirates…

9

Exactly for that reason I recommended to make it an optional choice so that every developer can make the decision for themselves.

10

It is impossible to do the recommended decal workflow without the 3d geometry to shrinkwrap.

1 Like