Page 2 of 2

Re: PS All-Stars Battle Royale(final version ea05-cskn)

Posted: Sun Mar 20, 2016 10:21 am
by shakotay2
then read my post as of Thu Oct 09, 2014 3:06 pm:
dataTableOffs = 0x1546 also to be changed for different models.
indOffsArr = [...] and for j in range(0, numberOfSubmeshes): also have to be adapted.
(numberOfSubMeshes has to be set manually)

You best start of setting it to 1 for a first test with one submesh.

Doing some research I got this:
cskn_secTest.jpg
(search pattern for dataTableOffs: FFFFFFFF2000, -> 2 submeshes)

btw: getting the startaddressses of the (edged) indices blocks automatically should be possible soon.
Only need to find/calculate one required offset value.

Re: PS All-Stars Battle Royale(final version ea05-cskn)

Posted: Mon Dec 18, 2017 4:23 am
by You'reAnAllStar
The MediaFire links are dead. Were these scripts backed up anywhere?

Re: PS All-Stars Battle Royale(final version ea05-cskn)

Posted: Mon Jan 22, 2018 2:30 pm
by Tosyk
can anyone post current script for this? I'm totaly lost in updates and string replaces for it

Re: PS All-Stars Battle Royale(final version ea05-cskn)

Posted: Tue Jun 11, 2019 4:51 pm
by Doctor Loboto
Yeah, I can't find the current scripts anywhere for this game. The only version I found was the older version and the link was dead anyway. I'd really like a method of getting the proper meshes and such from this without the ever-present error I remember encountering last time.

https://www.dropbox.com/s/6ygqbgc72oayr ... s.zip?dl=0

Re: PS All-Stars Battle Royale(final version ea05-cskn)

Posted: Tue Jun 11, 2019 8:43 pm
by shakotay2
Afair the scripts in this thread were used for cskn files with the signature 45413035 (EA05 - as the thread title says, surprise :D )

But fat_princess.c0.p0.cskn from your zip for example starts with 4D4F444C "MODL".

Re: PS All-Stars Battle Royale(final version ea05-cskn)

Posted: Sun Aug 18, 2019 8:16 am
by You'reAnAllStar
Really? I could have sworn there was a version of the script that didn't have that error, but I might be misremembering.