Log in to check your private messages
Do you want to advertise at Project Perfect Mod. Find out how to do it
The time now is Fri Aug 17, 2018 2:47 am
All times are UTC + 0
OS SHP Builder
Error opening unknown Sole Survivor shp
Post a reply
View more Emoticons
[quote="Blade"]If I come across any more I'll let you know, the screenshot you provided allowed me to determine the file names (sradar.shp and hsradar.shp for the record), which is the only information I was interested in for now.[/quote]
Disable BBCode in this post
Disable Smilies in this post
If you are visually impaired or cannot otherwise answer the challenges below please contact the
Write only one of the following words: Brotherhood, unity, peace!
OS SHP Builder
Select a forum
Page 1 of 1
Posted: Wed Apr 08, 2015 6:54 pm
Thanks a lot. It has been applied at revision 84.
Posted: Tue Apr 07, 2015 5:17 pm
Curiosity killed me so I still went for it this morning and it turns out the bug in OSSB has to do with passing a longword as a word parameter in the function HuntMyOffset(...). It was afterall an easy bug to find, my bad :v I was debugging at like 0-15FPS in a vm so I took shortcuts thinking the bug was elsewhere but that bit me in the end..
pic for proof:
For Banshee, to try:
Todo: change "const Offset: word;" to "const Offset: longword;"
Posted: Tue Apr 07, 2015 3:34 pm
SHP Builder uses the XCC algorithm of opening SHP files IIRC so no surprises there. Noidea what Katz used tho.
Posted: Tue Apr 07, 2015 3:32 pm
Using 2 other tools (XCC and Katz's) also brings the conclusion of a damaged frame, kinda interested in how your program is decoding it ok compared to the rest.
Figured I'd contribute that data is all.
Posted: Mon Apr 06, 2015 4:34 pm
If I come across any more I'll let you know, the screenshot you provided allowed me to determine the file names (sradar.shp and hsradar.shp for the record), which is the only information I was interested in for now.
Posted: Mon Apr 06, 2015 12:53 am
Where it is supposed to be all zeros, we find the filesize, and where it is supposed to be the filesize, we find a reference to a frame which supposedly contains the diffs between the first and last frames. Which, by the documentation, is a characteristic of .wsa files. So that is that.
But I didnt find what the error is in OSSB's impl, and tbh debugging it is hell so I'd rather replace this impl with my own, but is it even worth it? If you have other shps(td) that result in errors when opening, pls tell me. Otherwise, ... well, for now, I'll just stop working on this until further news.
Posted: Fri Apr 03, 2015 10:21 pm
Weird, I've tried it with my viewer and it opened fine. I'll see what is wrong with OSSB's impl.
pic for proof:
EDIT: just noticed the insane values in the filesize and zero fields. i guess my program is interpreting them wrong, hm
Posted: Thu Apr 02, 2015 9:30 am
I'll upload one of the files when I get chance later this afternoon, they are both the same so either should be fine.
Yeah, I'm referring to Delta, the dword that starts at 0x0A in the WSA header. It's the maximum buffer size needed to hold an XORDelta for a frame (otherwise called format40). shp(td) is pretty much a version of wsa that uses LCW compressed key frames to better support random access from what I can tell.
I've attached one of the files.
Posted: Thu Apr 02, 2015 2:27 am
I dont have the mix from that game. Can you tell me where I can find it? or can you just upload those 2 files?
EDIT: also, to be clear, are you referring to the Delta field in .wsa format, or to another field?
Funny that you pointed it out, and to now compare .wsa to shp(td), because it would make sense that all the unknown fields in shp(td) are in fact the known ones from .wsa as their header would be almost exactly the same, with the exception that frame headers contain only one offset in wsa and 2 in shp(td).
Posted: Tue Mar 31, 2015 11:06 am
Out of interest, is there some place to get that files from?
edit: Ignore me.
Posted: Mon Mar 30, 2015 7:54 pm
Post subject: Error opening unknown Sole Survivor shp
I'm trying to determine the filenames for a few unknowns that remain in the sole survivor mix files and I've found two shp files that XCC thinks are unknown files and that OS Shp Builder encounters an error decoding. The two files are in sole.mix and have ID's 623E17FC and B7623E17. The files are actually identical and I'm fairly confident are TD style .shp files given the header structure. The error message indicates the fault occurs decoding a format40 frame.
I had a quick look through the source and it looks like the code allocates width*height to buffer the encoded data, but worst case for format40 is larger than the destination image for highly varying data and so could be larger than this (and for this file may well be). I suspect the unknown field C is actually the max buffer size required to hold an encoded frame as a similar field exists in the wsa format for much the same reason.
Page 1 of 1
© phpBB Group
[ Time: 0.1442s ][ Queries: 10 (0.0378s) ][ Debug on ]