argent77 Posted November 18, 2013 Share Posted November 18, 2013 The new BAM V2 format has been introduced in BG2EE and BGEE patch 1.2. It is similiar to the new MOS V2 format described here in more detail. BAM V2 header: Offset Size Description 0x0000 4 Signature ('BAM ') 0x0004 4 Version ('V2 ') 0x0008 4 Number of frames 0x000C 4 Number of cycles 0x0010 4 Number of data blocks 0x0014 4 Start offset of frame entries 0x0018 4 Start offset of cycle entries 0x001C 4 Start offset of data blocks Frame entry: Offset Size Description 0x0000 2 Frame width 0x0002 2 Frame height 0x0004 2 Frame center x coordinate 0x0006 2 Frame center y coordinate 0x0008 2 Start index of data blocks 0x000a 2 Number of data blocks in this frame Cycle entry: Offset Size Description 0x0000 2 Number of frame entries in this cycle 0x0002 2 Start index of frame entries in this cycle Data block: Offset Size Description 0x0000 4 PVRZ page 0x0004 4 Source (PVRZ) x coordinate 0x0008 4 Source (PVRZ) y coordinate 0x000C 4 Width 0x0010 4 Height 0x0014 4 Target (BAM) x coordinate 0x0018 4 Target (BAM) y coordinate BAM V2 resources refer to MOSxxxx.PVRZ files, where xxxx is a four-digits decimal number (PVRZ page). The transparency information required by most of the BAMs is stored in the pixel data of the PVRZ files itself. Link to comment
Mike1072 Posted November 18, 2013 Share Posted November 18, 2013 0x000C 4 Number of cycles = practically unlimited amount of state icons! Link to comment
argent77 Posted November 18, 2013 Author Share Posted November 18, 2013 0x000C 4 Number of cycles = practically unlimited amount of state icons! Yes, but you have only as many as 9999 PVRZ files where you can fetch the icons from. Link to comment
PapySilk Posted November 20, 2013 Share Posted November 20, 2013 So it is normal if my new BAMs are ignored by BG2EE ? (I just created one with bamworkshop2 - a simple recolor - and it's blank in game) Link to comment
Kaeloree Posted November 20, 2013 Share Posted November 20, 2013 Description bams are not currently supported; you have to use 24bit BMPs with transparency. A version of DLTCEP that can save bams as this type of bmp should be out soon if it's not already. If you're talking about item icon bams, that should be working fine. Are you sure you've created your bam correctly? Link to comment
PapySilk Posted November 20, 2013 Share Posted November 20, 2013 It's a spell BAM. I took the 813 wizzard icon (exported via NI), changed slightly the color, saved it. Doesn't work. But NI said it was corrupted somehow so I guess it's normal. Waiting for a new version of NI then. Link to comment
Wisp Posted November 20, 2013 Share Posted November 20, 2013 If all you did with NI was exporting the file, it is highly unlike that's what corrupted it. I'd sooner look to whatever tool you used to edit the BAM. Link to comment
PapySilk Posted November 20, 2013 Share Posted November 20, 2013 NI considers it corrupted like all spell BAM. I can still export it even though it says it's corrupted. So I exported it anyway, modified it, saved it. Doesn't work. If the BAM format changed, maybe it's the BAM workshop update I need. Link to comment
argent77 Posted November 20, 2013 Author Share Posted November 20, 2013 NI considers it corrupted like all spell BAM. I can still export it even though it says it's corrupted. So I exported it anyway, modified it, saved it. Doesn't work. If the BAM format changed, maybe it's the BAM workshop update I need. Yes, the official NearInfinity version w1.3.0 cannot display many BG(2)EE icons correctly (if at all). This issue has already been addressed in the current development branch. If you are really desperate, you can use this development version of NI. It doesn't yet support the new BAM format, but it should display the spell icons correctly. Please note that the current development versions may break compatibility with older NI versions under certain circumstances (i.e. you may have trouble starting older NI versions after using the current one). Edit: updated link Link to comment
Avenger Posted November 20, 2013 Share Posted November 20, 2013 DLTCEP supports the description BMP, but it doesn't have much idea about the new BAM/MOS stuff. Link to comment
Kwiat_W Posted November 21, 2013 Share Posted November 21, 2013 0x000C 4 Number of cycles = practically unlimited amount of state icons! If someone is going to release a mod with a custom states.bam and thus incompatible with other mods that do the same, they could probably find a way to make it work with limitations of old bams. It would be much more useful if beamdog would modify opcode 142 (Display Special Effect Icon) to allow use of custom bam files. Does bgee engine allows bam frames grater than 256x256? Link to comment
Mike1072 Posted November 21, 2013 Share Posted November 21, 2013 0x000C 4 Number of cycles = practically unlimited amount of state icons! If someone is going to release a mod with a custom states.bam and thus incompatible with other mods that do the same, they could probably find a way to make it work with limitations of old bams. You can patch new cycles into a .bam file. Link to comment
PapySilk Posted November 23, 2013 Share Posted November 23, 2013 Well, anyway, the last patch made all BAM modifications impossible as long as a tool as not been updated. (BAM Workshop I believe) Am I right ? (If not, can you explain me how to make a new HLA / innate icon ?) Link to comment
argent77 Posted November 23, 2013 Author Share Posted November 23, 2013 Well, anyway, the last patch made all BAM modifications impossible as long as a tool as not been updated. (BAM Workshop I believe) Only a selected few BAMs have been converted into the new BAM V2 format (about 100 out of 16000 for BG2EE). You should have not trouble modifying the majority of BAMs (including states.bam), theoretically. Link to comment
igi Posted November 24, 2013 Share Posted November 24, 2013 Added to local copy. The PVRZ format would be kind of useful to detail... Link to comment
Recommended Posts
Archived
This topic is now archived and is closed to further replies.