martix Posted January 21, 2010 Share Posted January 21, 2010 I have this editor with template capabilities and I decided to make me a parser for IE files based on IESDP. However the moment I started actually making it I found out I don't really how to read bitfields. Take for example the Creature flags in the CRE format. Does it mean that the Most Significant bit of the Most Significant Byte is bit 0 and Least Significant bit of Least Significant Byte is bit 31 OR do I take into account endianness which makes ordering bytewise something like [bit 24-31] [bit 16-23] [bit 8-15] [bit 0-7]. So how exactly is it? Link to comment
lynx Posted January 21, 2010 Share Posted January 21, 2010 The main question aside, are you aware that we already have a few parsers for IE files? DLTCEP and NearInfinity are the ones most widely used. Link to comment
martix Posted January 21, 2010 Author Share Posted January 21, 2010 Yes I am... Its just my choice in source material for becoming familiar with the editor's features. P.S. On the main topic - here's a typo I discovered - in the Creature Flags, the last two bits are both listed as bit 30, not bit 30 and bit 31. P.S.2 Another typo: The GAM header description: Offset:0x001c Size: 2 (dword) [my guess is size should be 2 (word), not (dword)] Description: Count of NPC structs for party members (excluding Protagonist) P.S.3 Here are more inaccuracies and tidbits: IESDP: bit 0: (0) Party AI disabled / (1) Party AI enabled Proper: 0 for enabled, 1 for disabled. Link to comment
Avenger Posted January 21, 2010 Share Posted January 21, 2010 If you want to get familiar with fileformats and can read C code, then i recommend reading IELister source. http://sourceforge.net/projects/gemrb/file...er.zip/download Link to comment
martix Posted January 23, 2010 Author Share Posted January 23, 2010 Hmm... thanks for that. My original issue has been resolved for some time. However I keep finding typos and errors in the IESDP and will continue posting them. Here? Or maybe split this thread from my last post into its own error report thread. All of this applies to the BG2 descriptions. Here's the next error from the EFF description: 0x0080 8 (resref) Caster X coordinate - Obviously its not 8 (resref) 0x0084 4 (dword) Caster Y coordinate Link to comment
devSin Posted January 23, 2010 Share Posted January 23, 2010 Check out the Near Infinity source code. Our handling of the resource formats is up-to-date too. Link to comment
igi Posted September 25, 2010 Share Posted September 25, 2010 Typo's updated in local copy. Link to comment
Recommended Posts
Archived
This topic is now archived and is closed to further replies.