| Age | Commit message (Collapse) | Author |
|---|
|
Looks like only change here was that binary switch from uint32 to uint64
for some core metadata of the format. At leas, could import some 7500
files here with that mere change.
Thanks again @xchip (Raul Aguaviva) for finding the culprit in T49822!
|
|
Based on patch from T49822, thanks a bunch for investigation.
Change is actually pretty limited - 7500 now uses some uint64 instead of
uint32 integers as some root element info (like size etc.), and
accordingly raised the 'stop nested data' marker from 13 to 25 NULL
bytes.
Next step: check if we can make actual importer load FBX2016 files that
simply!
|
|
it to users.
Those ... people? at AD changed the whole format on binary level it'd seem, even low-level,
binary parsing is broken with those files, nothing else to do but go back to
binary hacking/inspection of new files if we want to support them... will let that
to someone else, FBX has successfully exhausted my patience since years already,
even all the backup emergency reserves I had.
|
|
ones.
From Campbell's repo.
|
