O_o could you elaborate a bit more on your process? That seems very odd, considering the fact that you managed to get all parts of a character that should be scattered randomly among an entire .forge archive if not even a couple of them. Did you gather a list of needed pieces from ondemand.forge? Wh...

zaramot, did you get .dat files from forge or did you grab them from game memory? If first, how did you locate all Ash related pieces?

Fml... All this time I was wondering where do they keep strings to identify models. Turns out they where stored in metadata header which I was mindlessly skipping in meshes. And same goes for texture data. Yes, Ronininja, I do plan on releasing it. However, it's not going to be a tidy and easy to us...

The tool I use is a python 3 module written to deal with forge archives. It has tools to unpack .forge, to convert textures and to encode mesh data (partially). All this stuff has a bunch of dependencies. 1. Basic .forge manipulation: zstandard to unpack compressed data 2. textures: RawTex do assemb...

Oh, yeah, about your question. At this stage I can export all meshes, all textures, but there are literally tons of them. I can also sort them into folders containing the stuff that is linked into one asset. I still can't get the skeletons linked to those assets though.

I had already contacted Luxox. He's the one who helped me to identify texture compression types. He is using Intel GPA to dump the memory and rip data from a frame render snapshot. That's too labor intensive to my liking. My approach is to reverse the actual format to know what most of the data mean...

It's stalling. I wrote some reversing utilities to ease up the data gathering process, but I'm lacking time to actually use em and move forward with reversing the assets. Too much higher priority things to do at home these months.

Sorry, I don't monitor this forum that often. Yes, my method works with textures. In fact, they store plain dx10 data, they just wrap it in a custom container. For some reason they move most of the valuable header data (dx10 packing type, image size etc) to the footer. So it's pretty trivial to deco...

Yep, there has been. I unpacked all types of meshes and seem to have found uv's block. There are some questionable blocks tho. And the biggest issue is there are no asset names. I have also found the files that tie an asset together (mesh or several meshes, textures) but it has no link to the skelet...

Ok, nevermind, I figured it out. It turned out to be 4 int16. Three for x,y,z and last is scaler.

Yes, Jojje. I have the extracted data with fancy looking file names. And me and my friend have extracted a couple of game models, like Thermite's elite mesh for example. But there are some peculiar versions of a mesh file which I can't seem to fully reverse. So I'm asking for a community's help. Her...

I have python script that unpacks current versions of forge. They switched to zstandard to pack data, but other than that structure is not much of a difference. Another bugger is that they seem to hash all strings and store hashes instead of actual names to prevent data mining. I was hoping to inspe...

Hi. I've been fiddling with rtech_game.dll for quite a while. Now I'm relatively new to reversing so the work doesn't really go that fast. But I managed to find functions that manage data chunks and the actual rpak decoder. So if anyone is interested (cra0?), I can provide functions' file offsets an...