XeNTaX

johnathon wrote:Presumably by commenting out the other cat path definitions?

Yes, and the same answer is for "XP" packs, the script only takes CAT files its told to. So by replacing the paths to those of expansion packs, you should be able to dump it too, though I'm not sure.

There's also a project by elementofprgress user here viewtopic.php?f=10&t=13702 who tried to dump all data, including patches, you can check it too, while it had some problems with texture mips overwtiting main textures, it may be better in something.

daemon1 wrote:

johnathon wrote:Presumably by commenting out the other cat path definitions?

Yes, and the same answer is for "XP" packs, the script only takes CAT files its told to. So by replacing the paths to those of expansion packs, you should be able to dump it too, though I'm not sure.

Ah, of course. I didn't notice that the xp cats weren't included in the script.

So I ran the script again and kept an eye on the memory usage as it went. It worked as you'd expect for quite a while. Usage would go up by around 20MB while processing a chunk, and then decrease before moving onto the next chunk. However when it gets to a specific chunk (2550ad6e0c4d281384a6bf767bb7a959.chunk in Patches/chunk0.toc), it gets stuck and the memory usage keeps on growing until the process runs out of memory. So it looks like it isn't a memory leak, but instead a specific chunk is throwing it off. Surely the chunk can't be that big?

Update: I checked the chunk size in the cat and it says it's only 11132419 bytes...

Yes, must be something wrong with this chunk, but I can't check it, because I don't have this CAS file. So I can only suggest you skipping it for now. With a code like this maybe:
p.s. maybe its some problem in decompression routine...

So i've been holding onto this for awhile and since the original devs have from what i can tell no use to ever finish it here you guys go.

This tool only works with the Alpha build of the game so remember that.

The tool was edited from the Dragon Age inquisition mod tool or DAI_Tool by danielmm8888,PistonMiner and me Corra_Ashu/JakeGreen edited a couple small things after they gave it to me, the tool can easily be decompiled as that is how they originally was able to edit this tool and get it working with SWBF.

The reason for the release of this now is cause SWBF is getting harder and harder to extract stuff from and for some reason the scripts posted here aren't getting out everything from the latest updates cause it errors very close to the end of finishing and this tool here if someone was to decompile it and edit it to work with the main game then we wouldn't have to extract 30 plus gigs or more to our hard drives when we want say a new hero,villain or weapon released to this game.

This tool also can support sound extraction but atm it's not working properly in the tool and i think it's an easy fix i just don't know enough on that end to fully fix it.

There are 2 versions of the the tool one that is called SRGB which is the textures as DICE made them pre-shaders and then No SRGB which is basically DICE's PBR baked into the texture to make it brighter, i suggest using the SRGB one as it's the original textures that DICE used pre-shaders and much nicer.

You are also going to need 2 tools which i find very useful, First tool would be Visual Studio 2013 to open the dds files extracted from the tool to convert them to PNG and then Xnview to convert them back to dds otherwise without xnview opening the png in photoshop merges the alpha layer in all the RGB channels.

You can find it here https://www.visualstudio.com/en-us/d...studio-vs.aspx

an Xnview here http://www.xnview.com/en/

Finally here is the tool.
http://www.mediafire.com/download/ri5ui ... F_Tool.rar

Here is also a video on how the tool works

https://www.youtube.com/watch?v=MA_O7lw ... e=youtu.be

I really hope someone can edit this tool to work with the main game as it would be a huge help for everyone. Also something cool to note this tool works with Battlefield Hardline well last i check back in August it worked with it, the program errors close to the end of reading all the files but it still shows most of the base models from the game allowing for easy extraction.

Lastly this tool also can support the extraction of bones on the models but since the tool was never finished it doesn't work properly, maybe someone can fix that and make it so you can extract in FBX with bones.

Well, textures from Batch_Itexture are broken

stkopp wrote:Well, textures from Batch_Itexture are broken

I don't have the game, so if you want me to fix this, provide EBX & chunk files that don't work

Your Batch_Itexture_Converter is only working tool I found so far, which can convert textures from NFS Rivals .itexture files.
Especially normal maps.
But it's not fully compatible, it makes wrong (but fixable) headers and requires renaming .itexture to .texture for converting.

So, can I ask you for quick-fix version for NFS Rivals?

Only 2 changes is needed - read .itexture (again) and put correct dimensions to headers: I already fixed values on this pic, tool output is:

Sample .itexture files attached.

Another little bug with "car_astonmartin_vanquish_2013_light_e 062006af8be60dfb.itexture" - compression type detected as 47, but correct is 4D.
Attached .chunk, just in case.

PS: Same thing with "car_astonmartin_vanquish_2013_light_material b1bac978a310c44d.itexture".

Ok its not originally my tool, but I can make a version for NFS. They changed layout and compression codes. If one code changed, others may be different too.

daemon1 wrote:Ok its not originally my tool, but I can make a version for NFS. They changed layout and compression codes. If one code changed, others may be different too.

Would be really helpful, thanks!
Original author refuses to help in comments for his tuto on youtube, and his latest version of tool (for SWBF 2015), doesn't detect .itextures or .textures in NFS Rivals dump.

Can someone look at the Dumper script and see if they can edit it cause whenever i start python and start the script with what i have selected it always tells me Patched cat not found and here is what i have.

Hi!

First: I'm new to most of this, so apologies if I ask anything ignorant (and please direct me to places to learn for myself, if it's easier).

Second: I want to get the head & body mesh etc for the characters in this game. I've run the first python script and gotten my dump folders ("Bundles, Chunks, EDX"), but am stuck after that. Any help would be much appreciated

Okay so the script on this page is messing up a lot now it's not finding the proper chunk files for basic textures that were once working like helmets for the stormtroopers and a lot of character msr and normal maps and making them really small file size (under 100kb) when they should be in the range of 2mb to 5mb.

Dice must of changed something in the files for the textures, is there anyway someone can take a look at the script and possible fix it,cause i did and i've tried to fix it and nothing i've done has worked.

JakeGreen wrote:Okay so the script on this page is messing up a lot now it's not finding the proper chunk files for basic textures that were once working like helmets for the stormtroopers and a lot of character msr and normal maps and making them really small file size (under 100kb) when they should be in the range of 2mb to 5mb.

Dice must of changed something in the files for the textures, is there anyway someone can take a look at the script and possible fix it,cause i did and i've tried to fix it and nothing i've done has worked.

I'm having the same problem. I'm not sure if it's putting the wrong mip data in the chunk file, or if the correct data is getting pulled, but the hex identity in the texture file is wrong and pointing to the wrong chunk file. I guess it's possible that the correct image data is in a different chunk, but I'm not sure how to figure out which one it might be. As it is now, the DDS header end up with the wrong image size data, and had to be hex edited manually to even open up the incorrect smaller mip.

Unfortunately I can't see the pattern as far as which images get pulled correctly, and which ones are undersized, with incorrect erroneous header data.