January 22, 2025, 02:01:36 AM

Recent Posts

Pages: 1 2 3 [4] 5 6 ... 10
31
NFL Blitz 2018 (NFL blitz 2000 hack) / Re: NFL Blitz Data File Editor (work in progress)
« Last post by dmgambone on March 17, 2020, 12:23:13 PM »
Ugh, nevermind about the previous post regarding the Versions.  Not every V3 has the same offset.  Some don't have an offset at all...  :(

32
NFL Blitz 2018 (NFL blitz 2000 hack) / Re: NFL Blitz Data File Editor (work in progress)
« Last post by dmgambone on March 17, 2020, 12:06:23 PM »
I figured out the issue with some images not being extracted properly.  So the UInt32 value stored prior to the format appears to be a version number.  When the value is 2, the image data comes immediately after the header.  When the value is 3, the image data is offset by 2,560 bytes.  I'm not sure why it's 2,560 bytes. 

One thing that I saw while trying to build the image processing code was that the images are padded at the end.  Each image block (start of image to end of image + padding) is a data block that is evenly dividable by 512.  I'm wondering if the reason to add the padding in there is to move past a boundary and ensure that the image doesn't pick up any artifacts.  Not sure, but it looks like those trouble images are extracting properly now.
33
NFL Blitz 2018 (NFL blitz 2000 hack) / Re: NFL Blitz Data File Editor (work in progress)
« Last post by dmgambone on March 17, 2020, 10:25:24 AM »
Hmm, I'm looking at the ARHLML.WMS entry in the data file.  This is what I see:
Code: [Select]
Offset(d) 00 01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47

00000000  41 52 48 4C 4D 4C 2E 57 4D 53 00 00 84 AB 24 80 00 00 2A 43 00 00 00 43 00 00 AA 42 00 00 80 C2 00 00 00 00 00 00 2A 3F 00 00 00 00 00 00 80 3F  ARHLML.WMS..„«$€..*C...C..ªB..€Â......*?......€?
I don't see the values you wrote out there.  I'm noticing some oddities in extracting the image data as well.  For example, the Cowboys helmets (PC version = DAHLML.WMS and DAHLMR.WMS) aren't pulled properly.  The image header record is saying the image is 256x256, where every other helmet image is 256x128.

Looks like I need to do more investigating...
34
NFL Blitz 2018 (NFL blitz 2000 hack) / Re: NFL Blitz Data File Editor (work in progress)
« Last post by jaker3 on March 17, 2020, 08:43:49 AM »
NFL Blitz PC 2000 Images compared against the Blitz2k Arcade raw drive. I just took the directory of PC Images, and looked up their bytes against the arcade .bin. What you see at offset 91337612 is related to how to draw it / sprite info? I'm just calling it image metadata at the moment. Similar to what I've pointed out here:
https://i.ibb.co/GHtSJWY/spritesheet.png

So decimal offset 24659972 is the actual image bytes for ARHLML.WMS
Offset 91337612 seems to contain a pointer and info needed to draw it (where on the screen, x1,y1,x1,x2, ect...).

EDIT: Also the solution structure sounds good to me!


 
35
NFL Blitz 2018 (NFL blitz 2000 hack) / Re: NFL Blitz Data File Editor (work in progress)
« Last post by dmgambone on March 16, 2020, 07:08:57 PM »
Jaker, how did you get those offsets?  Are you using the NFL Blitz Gold CHD or the NFL Blitz Classic CHD?  I'm using NFL Blitz 2000 (Gold?) and not seeing how you got that.

Searching for ARHLML.WMS seems to find only 1 match in a list of WMS records (starts at offset 91337612).  Those records appear to be 48 bytes long and none of the values in the ARHLML.WMS seem to match what you got there.
36
NFL Blitz 2018 (NFL blitz 2000 hack) / Re: NFL Blitz Data File Editor (work in progress)
« Last post by dmgambone on March 15, 2020, 08:33:41 AM »
I've pushed the image code in the branch
Code: [Select]
image-support. 

FYI: This is how I'm planning for this solution to be structured:
  • NFLBlitzDataEditor.Core:  A .NET standard assembly that contains the core functionality around processing the data file
  • NFLBlitzDataEditor.UI:  A .NET Core WPF application that uses NFLBlitzDataEditor.Core.  This is what users will use to modify the data file

Right now, I'm just trying to get some bits and pieces together.  Ultimately, this is the structure I will have for the solution.
37
NFL Blitz 2018 (NFL blitz 2000 hack) / Re: NFL Blitz Data File Editor (work in progress)
« Last post by dmgambone on March 14, 2020, 09:42:13 PM »
Right now, I'm just finding images based on the occurrence of 0x05800000 to start of the record.  I don't know what image files they map to, although some of the one's I outputted match the offsets you've posted.

There's also WMS file records that are 44 blocks wide starting at position 0x056C0F2C.  But those pointers don't seem to match anything.
38
NFL Blitz 2018 (NFL blitz 2000 hack) / Re: NFL Blitz Data File Editor (work in progress)
« Last post by jaker3 on March 14, 2020, 06:46:55 PM »
Awesome, how are you going about doing it? I suppose now that we know a little more about the Image header it would be as simple as looking for that pattern for pulling the images out.

I did run the PC images versus the arcade and it looks like only 447/1,015 PC files are shared between the two.

I've attached the image name and offsets to this post.
39
NFL Blitz 2018 (NFL blitz 2000 hack) / Re: Can't figure out how to update arcade Blitz
« Last post by dmgambone on March 14, 2020, 05:36:09 PM »
FYI: Starting a new thread that is appropriately named.
40
NFL Blitz 2018 (NFL blitz 2000 hack) / NFL Blitz Data File Editor (work in progress)
« Last post by dmgambone on March 14, 2020, 05:24:06 PM »
Creating this new topic from the original topic "Can't figure out how to update arcade Blitz" - http://nflblitzfans.com/index.php?topic=574.0

So Jaker3... The extraction of images seems to moving along and I made a shocking discovery: blitz2k.chd contains NBA Jam images...

Pages: 1 2 3 [4] 5 6 ... 10