Cars Issue with unpacking

[LiveryDeliveryAC]

So I am trying to unpack a model of an A90 supra I downloaded for the wheels. KN5 file, some of the cars that I downloaded seem to have a tool for unpacking and some do not. Is there a way to walk around that issue? Using it for educational purposes. Example of one car being locked from unpacking and another being available from the tools section.

Thanks in regards

 

[AKF_FPV]

wish i know thats as im having exact samne problem XD

 

[whydoigottasignup]

I suspect the original creator of the car intentionally hid this feature

 

[Geggo_]

So I am trying to unpack a model of an A90 supra I downloaded for the wheels. KN5 file, some of the cars that I downloaded seem to have a tool for unpacking and some do not. Is there a way to walk around that issue? Using it for educational purposes. Example of one car being locked from unpacking and another being available from the tools section.

Thanks in regards

I had the same issue. I enabled the developer mode of CM and it works now for me.
(To turn on the dev mode just go to "about" on the top right, then again on "about" and spam click on the little text that shows the current CM version. Then Press "Yes" and dev mode is enabled.

 

[l0ckenwickler]

From what I can tell, they just increased the texture count in the KN5 by 1 and added a dummy texture before the rest.

Imaging the beginning of the kn5 file:

• The first 6 bytes are the "magic number" of the kn5 file -> always "sc6969" as a string
• The next 4 bytes are the version of the kn5 file -> should be "6" as an int
• The next 4 bytes only exist if the version is "6" -> should be "0" as an int
• The next 4 bytes is the count of textures in the kn5 file -> Here they increased the int value by 1
• If the file is "protected" there are another 4 bytes -> "0" as an int

So to remove that "protection" you could use an hexeditor and reduce the texture count by 1 and then remove the four bytes after the texture count. Don't forget to make an backup before you mess with your files.

 

[V1nn7]

From what I can tell, they just increased the texture count in the KN5 by 1 and added a dummy texture before the rest.

Imaging the beginning of the kn5 file:

• The first 6 bytes are the "magic number" of the kn5 file -> always "sc6969" as a string
• The next 4 bytes are the version of the kn5 file -> should be "6" as an int
• The next 4 bytes only exist if the version is "6" -> should be "0" as an int
• The next 4 bytes is the count of textures in the kn5 file -> Here they increased the int value by 1
• If the file is "protected" there are another 4 bytes -> "0" as an int

So to remove that "protection" you could use an hexeditor and reduce the texture count by 1 and then remove the four bytes after the texture count. Don't forget to make an backup before you mess with your files.

You are an absolute legend, thank you so much