I'm still too dumb to break through such protection measures, but I have unpacked samples. I was hoping to inspect the game process with debugger to see how they threat those hashes, but legal exe is virtualized and has attach protection (圆4dbg throws an error upon attach, on launch it hits the debug warning or BE warning). Another bugger is that they seem to hash all strings and store hashes instead of actual names to prevent data mining. They switched to zstandard to pack data, but other than that structure is not much of a difference. Tushkan wrote:I have python script that unpacks current versions of forge. This also works best when exporting weapons and attachments that have small individual pieces that are for some reason separate UIDs in the game.ĭumpallmeshprops: I reckon this exports every single texture and forge from a given forge archive. And best of all, you can figure out the other objects UIDs as well with this method. You can use this to dump textures and every associated object, including the head and eye/mouth objects even if you don't have their UIDs. UHD textures are in datapc64_mtx_bnk_textures4.forge, however the tool will automatically export them if you simply select the ondemand archive.ĭumpmeshprops: Once you have run either of the findallmeshprops commands, you now have the UID of an object. For example, it seems that most packages are always in the datapc64_ondemand.forge archive. Sometimes different headgear have similar looking head objects, even if they belong to different headgears, so keep that in mind if you are wondering about getting textures you're not looking for.ĭump: When you want to export a single object or texture, use this.ĭumpall: Dumps everything in a given forge file (not sure if it works on textures)įindallmeshpropsglobal: Once you have found a UID of an object (maybe a texture works too on finding objects, I'm not sure as I haven't tried), use this command to look for the corresponding package from each one of the forge files (that is if you do not know its location).įindallmeshprops: If you know where the packages are located, use this to speed up the finding process, as it will only look for them in this single archive. No need to find both the objects if you just need the textures. Note, operators' head object will dump all of the textures belonging to the spesific headgear, with the headgear included, same as when extracting the textures from a headgear with it dumping the head object's textures. If UHD pack installed: 4k normal + cavity detail map List of assets and their UIDs made by DeadmanWasTaken:Ĭatalog of my findings for AssetCatalog (paste it to the main folder, replace if needed), mostly first and third person view models for the operators and also some gadgets:ĭiffuse + Translucency (light shines through cartilage -effect) Location for textures usually used by player characters, NPCs, their equipment and probably weapons: (If you have the UHD pack properly installed, the HD textures get exported with rest of the standard resolution textures) Here is a UID spreadsheet done by me with everything I have found from specific archives:
0 kommentar(er)
