I was informed by someone at the Xentax forum that the .3dm model files used for these cars were just .objs encoded with base64 and I was directed to luigi's bde64 tool. However, after running it with a .bat and specifying the decode option, output file etc all i'm left with is a 54 byte file that has no 3D Data within it (obviously). Now either, this guy is either incorrect (which I don't think so as he must of downloaded the file to see the encryption method) or there really isn't any data to extract and it's further encrypted OR i'm a pillock who can't use CMD and should be dealt with accordingly. Can someone put me out of my misery?
.3dm link (the file is in the archive alongside with some necessities for the website itself which aren't needed in this case):
or 2) The fact that the file type is still recognized as a Rhino 3D Model (from when I first tried to open it) Two of the dumbest explanations for this happening, second one especially (I mean jesus christ ) but I can't really see what else would cause it. and a 6.72MB Text file? The guy at Xentax must be wrong then
aluigi wrote:Is your bde64 version the 0.2.3 ? maybe add a PAUSE at the end of the bat to check if there are warnings and additional information from bde64.
I am using that version, added a space then PAUSE in caps in the .bat, no difference. Perhaps there is an older version I can download, like it'd make a difference. Any suggestions on how to decode these then?
If it's reading the same input file it's not possible that the output is 54 bytes. If you want you can send me the output via PM, there it's written for sure what's the problem.
aluigi wrote:If it's reading the same input file it's not possible that the output is 54 bytes. If you want you can send me the output via PM, there it's written for sure what's the problem.
I have exact same problem, i hope im doing this right since im completely new to most of this. i have a .bat file in the same location as the exe with the code: bde64 d export.3dm export.obj And i also end up with an incredibly small file with no 3D geometry. Help will be greatly appreciated, thanks!
That file is different than the others. In my opinion it's still base64 BUT there is some obfuscation on it that avoids to decode it. I can't figure what type of obfuscation has been used.