oopps, I was looking at the wrong stream, that explain why I couldn't find the scene version. it's in TLShell->Version then, not tlshell->VersionInfo softimage 2010 is version 801, 2011 is 900
On Thu, Oct 11, 2012 at 3:08 AM, A D <adla...@gmail.com> wrote: > It's not so hard, I've already alter emdl versions safely, you have to look > for TNOC string, it's usualy on offset 800h and the version is word on 80Ch. > For 2012SAP it is 3E8h (1000 decimal) and for 2011SAP it is 384h (900 > decimal). There are of course another textual versions numbers which are > displayed by printver.exe app but thoses aren't checked when you are opening > emdl in XSI. I believe that is same works for SCN ços there is the same > string TNOC. > > Btw. TNOC is reversed short for word CONTent > > Cheers > > > > On Wed, Oct 10, 2012 at 11:59 PM, Matt Lind <ml...@carbinestudios.com> > wrote: >> >> After seeing the data with my own eyes, I don’t understand why on scene >> load Softimage can’t report the name of the missing shader instead of >> spitting out the CLSID / GUID. The shader name is clearly stored with the >> CLSID. >> >> >> >> Matt >> >> >> >> >> >> >> >> >> >> >> >> From: softimage-boun...@listproc.autodesk.com >> [mailto:softimage-boun...@listproc.autodesk.com] On Behalf Of Rob Chapman >> Sent: Wednesday, October 10, 2012 1:42 PM >> >> >> To: softimage@listproc.autodesk.com >> Subject: Re: EMDL file description >> >> >> >> think this just blew my mind, a scene containing many compounds is in >> itself a compound! :) >> >> >> >> also it looks like we may be able to edit scene version numbers with >> something like this...? could have come in REAL handy today when I opened a >> scene in 2013 by accident, did some work for an hour then tried to open >> again in 2012 production version.... and yes transferred some geometry bits >> with .xsi format as .emdl is useless for this task but ICE trees just got >> turned into nulls :/ >> >> >> >> >> >> >> >> On 10 October 2012 20:56, Eric Cosky <e...@cosky.com> wrote: >> >> This utility appears to be able to manipulate compound files fwiw, >> http://www.coco.co.uk/developers/CFX.html >> >> >> >> >> >> From: softimage-boun...@listproc.autodesk.com >> [mailto:softimage-boun...@listproc.autodesk.com] On Behalf Of Luc-Eric >> Rousseau >> Sent: Wednesday, October 10, 2012 12:30 PM >> >> >> To: softimage@listproc.autodesk.com >> Subject: Re: EMDL file description >> >> >> >> Needs to be investigated. As far as I know, it doesn't use the "version" >> stream to do that validation, but rather some byte in main data stream. You >> cant look at or patch ole compound file with a hex editor, unfortunately. >> You have to write a small app that is specially aware of compound files and >> enumerate the streams, because they will change location inside the file. >> >> On Oct 10, 2012 2:57 PM, "Alan Fregtman" <alan.fregt...@gmail.com> wrote: >> >> What are the chances one could hack a modern file to appear to be in an >> older format if one could swap the "Version" file with that extracted from >> another version? >> >> (That is, assuming no new tech was used that didn't exist in the old >> version.) >> >> On Wed, Oct 10, 2012 at 2:46 PM, Luc-Eric Rousseau <luceri...@gmail.com> >> wrote: >> >> it's a practically impossible file format to decode outside of Softimage; >> if we could have documented it or write a utility to dump it to ascii >> ("bin2ascii"), we would have done it already. >> 7zip is able to open it because it's an OLE Compound File, but it's gets >> very complicated from there, with various forms of compressions, guids and >> other OLE contructs, and exactly how stuff is persisted is specific to each >> kind of objects and therefore you'd have to know the implementation of that >> object to figure it out >> >> >> >> > >
