XeNTaX

Tushkan wrote: ↑Sat Feb 08, 2020 3:35 am As I said previously, I am planning to share my tools. Only problem is they are going to require some skills from a person using it. It's python based and it's tailored towards scripted execution i.e. there is no gui.

zaramot wrote: ↑Sat Feb 08, 2020 8:11 pm https://youtu.be/tSNCstwSzq8

Tushkan wrote: ↑Sun Feb 09, 2020 11:27 pm I'm trying to document everything I do there. But you will still most likely need to write a script to grab the actual thing you want. Right npw the process looks like this:

Code: Select all

import r6s

with r6s.forge.parse('path\\to\\forge.file') as f:
	for i, e, n, c in f.files():  # loop through all files in forge archive
	# i - file index
	# e - file entry, has info about it's uid and offset
	# n - name entry, has info about its type and lots of less relevant data
	# c - file container (may also be hash or meta dict)
	meta_stream = c.meta.getstream()  # yields stream with unpacked meta data
	file_stream = c.file.getstream()  # yields stream with actual unpacked file
	# right now module doesn't select specific parser on the fly, so you have to make it manually
	with r6s.mesh.Mesh(file_stream) as mesh_handler:
		# mesh_handler holds parameters from model file. It includes vertex buffer length,
		# number of islands, all vertices and all lods
		actual_mesh = mesh.getmesh()  # this one yields 1 specific lod. This is what I import in blender

there are more comfy modules planned designed to ease up asset search and load to avoid fiddling with all that manual work. But that is not going to happen before I crack asset files and strings linking to make search by models names an option.

comword wrote: ↑Wed Feb 05, 2020 4:09 pm Here is the link, have a try. https://www.dropbox.com/sh/sii6e34kymrk ... DBY3Qv2TUa

Tushkan wrote: ↑Mon Feb 17, 2020 10:55 pm 2. You missed some .depgraphbin file when you were backing up outbreak assets, so now I'm lacking linking data between assets.
I think it's the second one (can be proved on current full game build but I hadn't had enough time to check). What does it mean: either I will scan through all asset files and will find links there or you will be bound to manually skim through all meshes and textures to assemble the model back. Or you will be able to find another enthusiast that managed to store all necessary depgraphbins.

./datapc64_bootstrap.depgraphbin
./datapc64_fury_d01_resort.depgraphbin
./datapc64_fury_d01_resort_p2.depgraphbin
./datapc64_fury_d02_hospital.depgraphbin
./datapc64_fury_d02_hospital_p2.depgraphbin
./datapc64_fury_d03_junkyard.depgraphbin
./datapc64_fury_d03_junkyard_p2.depgraphbin
./datapc64_pvp10_chalet_set02.depgraphbin
./datapc64_pvp11_university.depgraphbin
./datapc64_pvp12_russiancafe_set02.depgraphbin
./datapc64_pvp13_border.depgraphbin
./datapc64_pvp14_favela.depgraphbin
./datapc64_pvp15_temple.depgraphbin
./datapc64_pvp16_ibiza.depgraphbin
./datapc64_pvp17_themepark.depgraphbin
./datapc64_pvp19_tower.depgraphbin
./datapc64_r6_menuworld_playgo.depgraphbin
./datapc64_ui_playgo.depgraphbin
./datapc64_ondemand.depgraphbin
./datapc64_ondemand_fury.depgraphbin
./datapc64_ondemand_playgo.depgraphbin
./datapc64_ondemand_set01.depgraphbin
./datapc64_ondemand_set02.depgraphbin
./datapc64_pvp01_house_v2_set01.depgraphbin
./datapc64_pvp02_oregon_set02.depgraphbin
./datapc64_pvp03_hereford_playgo.depgraphbin
./datapc64_pvp04_clubhouse_set02.depgraphbin
./datapc64_pvp05_plane_set01.depgraphbin
./datapc64_pvp06_yacht.depgraphbin
./datapc64_pvp07_consulate_set01.depgraphbin
./datapc64_pvp08_bank.depgraphbin
./datapc64_pvp09_kanal_set02.depgraphbin

Tushkan wrote: ↑Mon Feb 17, 2020 11:18 pm NNNNNOOOOOOOO!!!! I just found out from their update notes that they are going to restructure game data. Why?! WHY?!?!?!

Edit: checked the TTS game version. They have indeed changed file format. But it's not that severe. They seem to pack meta and file data into one block now, so file headers have changed. But overall forge structure is the same (except for file type link but it will be easy to fix), compressor is the same, models are the same. Will have to see how they handle assets. I guess I will catch up fast enough. Only problem is I will shift onto new format and stop working with older forge archives. I still can decompress them, but at some point api might diverge and not all tools will longer apply to both newer and older forge versions.