You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
These are found on COMMON\CAM?S.PRM files, the following length is of 52 bytes (vectors + something ?), still trying to figure out what these are 😅
Could these relate to the replay post each race ?
EDIT:
I am running a PRM validator against files in WIPEOUT\COMMON, for what it's worth, I am trying to make it pass the test, unless we know the real content I am simply skipping bytes to try achieve 100% success rate.
With the code from your experiment rate was 41%, now it is 76% 😄
I think that'll be a significant milestone once we reach 100% as at least we'll be able to read files from end to end ... until we understand them.
Here's the excerpt of the above test, suggesting it's replay-related as there are no vertices:
The text was updated successfully, but these errors were encountered:
aybe
changed the title
New type of polygon found (0x14)
New discoveries in the game's data files
May 9, 2015
Then there is a strange group just below which looked like vertices (64) but i don;t know, looks like a 5 branch star though:
Here are the 2 combined, star is on middle as cluster of dots:
The only hint in the header is Index1 if you subtract 100, though ...
Polygons: 118 (see just below)
I have a high confidence in it since manual count yielded same count as in header but there is a block of 448 * 8 bytes I couldn't explain the meaning, after the vertices and before those polys. To find this count I started counting right before next object and climbed up until reaching 118 polys.
Just found a new type of polygon: 0x14
These are found on COMMON\CAM?S.PRM files, the following length is of 52 bytes (vectors + something ?), still trying to figure out what these are 😅
Could these relate to the replay post each race ?
EDIT:
I am running a PRM validator against files in WIPEOUT\COMMON, for what it's worth, I am trying to make it pass the test, unless we know the real content I am simply skipping bytes to try achieve 100% success rate.
With the code from your experiment rate was 41%, now it is 76% 😄
I think that'll be a significant milestone once we reach 100% as at least we'll be able to read files from end to end ... until we understand them.
Here's the excerpt of the above test, suggesting it's replay-related as there are no vertices:
The text was updated successfully, but these errors were encountered: