| WDump writing [message #469405] |
Sun, 17 June 2012 12:10  |
 |
Sonarpulse
Messages: 18
Registered: April 2012
Karma: 0
|
Recruit |
|
|
First of all, do all the fields displayed in WDump together account for all the data in a w3d file?
Regardless, I think it would be very handle of WDump allowed fields to be modified. This would be especially useful for w3ds where the source is no longer available.
Lastly, I remember two tools, w3d2xml and w3dxml that seem to export a subset of the data w3d like WDump, and the rest as binary blobs. Could that XML import-export functionality be integrated into WDump? except that all fields were imported/exported?
|
|
|
|
| Re: WDump writing [message #469419 is a reply to message #469405] |
Sun, 17 June 2012 16:53  |
 |
saberhawk
Messages: 1068
Registered: January 2006
Location: ::1
Karma: 0
|
General (1 Star) |
|
|
| Sonarpulse wrote on Sun, 17 June 2012 12:10 |
First of all, do all the fields displayed in WDump together account for all the data in a w3d file?
|
No, there are chunks that wdump doesn't understand.
| Sonarpulse wrote on Sun, 17 June 2012 12:10 |
Regardless, I think it would be very handle of WDump allowed fields to be modified. This would be especially useful for w3ds where the source is no longer available.
|
Yes, it would be, but changing WDump itself is highly unlikely (no source code, no prior code work done inside, and it's MFC based using Visual Studio 6)
| Sonarpulse wrote on Sun, 17 June 2012 12:10 |
Lastly, I remember two tools, w3d2xml and w3dxml that seem to export a subset of the data w3d like WDump, and the rest as binary blobs. Could that XML import-export functionality be integrated into WDump? except that all fields were imported/exported?
|
I wrote those, and don't understand w3d files beyond a superficial "they are chunked files" sort of way. You could run them on objects.ddb and get much the same output. They are only really useful for isolating specific chunks inside a chunked file for additional editing.
|
|
|
|
|
|
|
|
|
|
| Re: WDump writing [message #469490 is a reply to message #469405] |
Tue, 19 June 2012 07:21 |
|
|
We only have the source to the Tiberian Technologies tools, namely ddbedit.exe, fixplanes.exe, makemix.exe, mergelod.exe, tdbedit.exe, w3ddepends.exe and zorient.exe
makemix.exe and tdbedit.exe source code is in the 4.0 source download. ddbedit.exe is closed source because it contains a lot of code we would rather not release for various reasons.
The other stuff (fixplanes.exe, mergelod.exe, w3ddepends.exe and zorient.exe) are closed source for reasons I dont know exactly.
We do not have source code for wdump.exe or any of the other Westwood tools.
Jonathan Wilson aka Jonwil
Creator and Lead Coder of the Custom scripts.dll
Renegade Engine Guru
Creator and Lead Coder of TT.DLL
Official member of Tiberian Technologies
|
|
|
|
| Re: WDump writing [message #469512 is a reply to message #469490] |
Tue, 19 June 2012 15:48 |
|
Sonarpulse
Messages: 18
Registered: April 2012
Karma: 0
|
Recruit |
|
|
| jonwil wrote on Tue, 19 June 2012 07:21 |
We do not have source code for wdump.exe or any of the other Westwood tools.
|
Well, that explains why doing anything with LE is such a pain. Thanks for the info.
|
|
|
|
Search
Help
Members
Register
Login
Home
