XeNTaX

zestoflemon wrote: ↑

Sat Feb 08, 2020 6:36 pm

Code: Select all

>>> 
XAS1 dll detected.
EASpeex dll detected.
EALayer3 tool detected.

Traceback (most recent call last):
  File "D:\BFV Dump Tools\BFVdecoder\BFVdecoder.py", line 540, in <module>
    main()
  File "D:\BFV Dump Tools\BFVdecoder\BFVdecoder.py", line 537, in main
    dbx.decode()
  File "D:\BFV Dump Tools\BFVdecoder\BFVdecoder.py", line 398, in decode
    for i in self.prim.get("$::SoundDataAsset/Chunks::array").fields:
  File "D:\BFV Dump Tools\BFVdecoder\BFVdecoder.py", line 169, in get
    raise Exception("Could not find complex with name: "+str(e)+"\nFull path: "+name+"\nFilename: "+self.dbx.trueFilename)
Exception: Could not find complex with name: $::SoundDataAsset
Full path: $::SoundDataAsset/Chunks::array
Filename: Sound/PlaceholderDummy_Casablanca
>>> 

I'm having the EXACT same error, unfortunately just like you I can't tell what's the problem here: the dumper or the decoder.

Hopefully someone will update them to work with the latest version of the game.

It's either that or both of us are making the very same mistake lol

I get the exact same error, its most likely on the games update side

I'm getting the same error as zestoflemon, Sebastiel, and BRAGme. Does anyone have access or knowledge to create an updated decoder script for the latest version of BFV?

I finally solved the problem in which the script could not "find complex with name: $::SoundDataAsset"
I'm a noob in programming/coding so this took me hours.

Anyway i converted some bf4 and bfV .ebx sound files to .txt files in order to compare them, after all the audio decoder works fine with bf4 .ebx files. The python script tries to reach the Chunk datas with the given path but since the recent bfv updates the path has changed as you can see.

"$::SoundDataAsset/Chunks::array" has to be replaced by "$::SoundWaveAssetBase/$::SoundDataAsset/Chunks::array"

Line 419, fb3decoder.py file

Damoclès wrote: ↑

Fri Oct 09, 2020 2:30 pm

...The python script tries to reach the Chunk datas with the given path but since the recent bfv updates the path has changed as you can see.

"$::SoundDataAsset/Chunks::array" has to be replaced by "$::SoundWaveAssetBase/$::SoundDataAsset/Chunks::array"

Line 419, fb3decoder.py file

That is a nice find, i haven't messed with these Frostbite games in so long, will give it a try myself, had no clue there was an issue before, hm.

PS:
Although i'd normally do NOT recommend those decoders any more since at the time they where the only solution available, and results where not always accurate, and ever since these: https://github.com/NicknineTheEagle/Frostbite-Scripts have become available, the rest of old stuff has rendered obsolete.

Will this work on Star Wars Squadrons? I want to get some certain files for personal reasons. And is there even a tutorial that I can learn from this step by step?

Eradicon wrote: ↑

Mon Oct 12, 2020 3:52 am

Will this work on Star Wars Squadrons?

The above link ONLY works for audio extracted AFTER the game has been dumped first with the old SWBFII script, as both games share same structure as BFV.

Eradicon wrote: ↑

Mon Oct 12, 2020 3:52 am

And is there even a tutorial that I can learn from this step by step?

Yes, this forum is FULL of them, and your in the right thread too, read a long and you'll see what you need to do.

have fun

anyone else manage to get models and textures from star wars squadrons? so far i have only been able to extract everything and get the ebx files

A common problem with the latest BF5 updates downloaded via the origin platform. Honestly, many players are just tired of developer errors that prevent you from performing any actions with the game, I have it started to hang and lag very much that even my skill does not help to play. So I took and downloaded the cheats from wallhax.com/hacks/battlefield-5/ to play and after a couple of updates do not go into this game anymore. BUT I enjoyed playing with cheats so much that now it's a great pleasure for me, I do 13 kills per game. I think this is a very good result for such a level of play as I have. I advise developers to fix their errors.