duststorm wrote:No, currently there is no tool to convert binary back to ascii files, though it is possible to do using the API. But the original files are never deleted when conversion happens.
How difficult is it to do? Can you point me to any info that'd help me devise such a tool? I kinda need it.
duststorm wrote:As for a disable feature: work is better spent in fixing the bug than disabling the binary format.
Can we have both? I'm sure there is some use of .npz I don't know about (proprietary assets, maybe?), but personally I see no reason for them at all. This binary format autoconversion does nothing for me apart for causing trouble. I end up resorting to a hack of disabling write permissions in certain folder to block the binary files from spawning.
ThomasL wrote:It seems like the .mhpxy and .npz files are really zip archives, so if you change the file extension you should be able to extract the files. Unfortunately, this is of little help, because the archives extract to .npy files which do not seem to be any of the usual archive formats.
Yeah, I know what they are. I'm one of the people who see the world through Linux console:
- Code: Select all
$ file worksuit.npz
worksuit.npz: Zip archive data, at least v2.0 to extract
$ unzip -l worksuit.npz
Archive: worksuit.npz
Length Date Time Name
--------- ---------- ----- ----
34296 2015-04-15 22:54 texco.npy
99 2015-04-15 22:54 fgstr.npy
55968 2015-04-15 22:54 fvert.npy
120496 2015-04-15 22:54 vface.npy
45236 2015-04-15 22:54 coord.npy
84 2015-04-15 22:54 fgidx.npy
3843 2015-04-15 22:54 nfaces.npy
7066 2015-04-15 22:54 group.npy
55968 2015-04-15 22:54 fuvs.npy
--------- -------
323056 9 files
$ file texco.npy
texco.npy: data
This all doesn't help too much/at all. I need a way to convert this data format (numpy?) back into plain text.