GenericRipper wrote: ↑

Sun Nov 08, 2020 6:03 pm

I get an "incomplete input file" error on this file (both platforms)

Well, there're 5 files of zero size in both PAKs, which corrupted the script. Patched script is posted at the same post.

Thanks man! I always feel such words are pale while a simple click on the thumb button can speak louder. :wink: I had to change idstring ... however. Script updated at the same post for compatibility with PS3 files. Now I've got pairs of *.PAK/*.toc files & I'd love to get a bit of assistance with ...

This BMS script for now can help you unpack the conatiner.

ナット wrote: ↑

Mon Sep 14, 2020 6:23 am

When I try to export an .uexp file noesis said that the file couldnt be determined. Can someone tell me why does this happen and how can I fix it?

You quoted, but never read, did you?!!

Well, apparently you noticed the integral-multiple-of-3 trick, which I forgot to memtion. Another auxiliary criterion is to check if there're duplicate faces in the indices. For this ibuf, there's another face using the indices 0, 1, 2 at address 0x32EE, which is easy to spot. And once you knew the ...

You should upload some clearer images.

Like, for example, if I had 2A 05 then 00 0F ... I'm starting to think I confused big-endian with little-endian lol Yes, you should read them in little-endian, which's from the right to the left, as I've already said. So it's 0x52a followed by 0xf00, which's almost 3 times of the former value. but ...

Last time you told me that listing all the places where there was a huge difference in the bytes I don't know if you actually understand what a jump discontinuity means. The reason I chose this term is that it's a really vivid concept for such situation. (reference image from Wikipedia) https://upl...

Refer to this post.
viewtopic.php?p=139002#p139002

What would the best way be, then? I suggest to use a hex editor that supports color schemes, which's more friendly to human eyes, and easier for recognizing bytes in different ranges. The proper way is to work on the byte level and focus on the values of the most significant byte (MSB) of the indic...

So is the right way to find them taking each pair of bytes, reading them right to left, and comparing them to see if they're in order that way? Not exactly. I'm using HxD for my hex editor If that works for you. I found an option in HxD to put them into groups of 2 so I switched the attachment to h...

xpunkrockyugox wrote: ↑

Wed Aug 26, 2020 4:35 pm

I found over 25 jump discontinuities

These are not the so-called jump discontinuities.
You need to understand that the data in the ibuf are all two-byte little-endian short integers. So you need to read from the right to the left.

This time I did something different and tried to take notes of everything I was doing and connections I made between the numbers. Make sure to use proper terms like position address, normal stride, texcoord type etc. instead of phrases like "top address", to avoid confusion. I'm trying to figure ou...

I was looking at it and frantically searching for the exact things you typed and getting myself utterly lost on the first screenful of addresses :lol: Believe me, most people feel the same when they attempted to take the shortcut instead of learning from the beginning. Yet not much people have the ...

I've been looking at the picture, opening up the files in AMR and even trying to look at it in a hex editor EVEN? Observing the data within a hex editor is what you're supposed to start with. 8D but could I possibly ask where you got the numbers from in the Grem screenshot? Refer to the below image...