Fate/Extella: The Umbral Star [PCSE00928]

[wfscans]

Game summary

• Game name: Fate/Extella: The Umbral Star
• Game serial: PCSE00928

Vita3K summary

• Version: 0.01
• Build number: 408
• Commit hash: https://github.com/vita3k/vita3k/commit/8b50c0b

Test environment summary

• Tested by: waterflame
• OS: Windows 7
• CPU: Intel i7-2600
• GPU: AMD Radeon HD 6700 Series
• RAM: 8 GB

Issues

Okay... so since I already had them... I have logs for all 6 modes of Mai. I also have with and without putting the dumped shaders in the shader folder(which causes 3 of the modes to load further or less). Only mode 4 dumped any shaders(and it dumped a lot of them). "ws" stands for "with shaders"(from mode 4 dump). I'll only be including ws logs that their was a difference between the two... don't expect this from now on :p Another mention to addcont0: so take this as me reporting it to the devs :p(like with DRv3).

Crash: 2 2ws 3 3ws 4(? It just closes, no log output or crash popup) 4ws(same) Softlock: 0 1 5 6

So what does each mode mean... here is a list taken from the maidump app. I assume 6 is support for an older version of 5. "p.support" is most likely referencing "plugin support".

0. Load dual libfios2 (p.support) (recommended)
1. Only load libfios2_m (p.support)
2. Load dual libfios2 and dual libc (p.support)
3. Only load libfios2_m and libc_m (p.support)
4. Use original eboot (no p.support)
5. Load mode 0+ IO hook (supports plugin and DLC)
6. 2z2 Mode 5 loading

Screenshots(mode0)

Screenshots(mode1)

Screenshots(mode2)

Screenshots(mode2ws)

Screenshots(mode3)

Screenshots(mode3ws)

Screenshots(mode4)

Screenshots(mode4ws)

Screenshots(mode5)

Screenshots(mode6)

Log

vita3k_0.log vita3k_1.log vita3k_2.log vita3k_2ws.log vita3k_3.log vita3k_3ws.log vita3k_4.log vita3k_4ws.log vita3k_5.log vita3k_6.log

Recommended labels

• crash
• softlock

[wfscans]

Vita3K summary

• Version: v0.1
• Build number: 571-70599d3
• Commit hash: https://github.com/Vita3K/Vita3K/commit/70599d3

Will carry on with Mode 0 as it's the default dump mode. Softlock on loading archive.pkh

FateExtella.log

[CelesteBlue-dev]

Why don't you use FAGDec instead of mai dump tool ?

[VelocityRa]

@CelesteBlue-dev This isn't the place to talk about this, please ask him on Discord in #testing or something.

[wfscans]

Vita3K summary

• Version: v0.1
• Build number: 984
• Commit hash: fb0798e of pull/456 (I don't want to append every issue to the PR)

Fate Extella - [PCSE00928].log

Issue

stat file error

[wfscans]

Vita3K summary

• Version: v0.1
• Build number: 1315
• Commit hash: https://github.com/vita3k/vita3k/commit/5b070aac

Softlocks stating archive; Also sceKernalSignalLwCondAll: SCE_KERNEL_ERROR_LW_MUTEX_RECURSIVE

[othmanead]

Vita3K summary

• Version: v0.1.5
• Build number: 2630
• Commit hash: https://github.com/vita3k/vita3k/commit/18dacae2
• CPU backend: Dynamic

Test environment summary

• Tested by: othmanead
• OS: Windows 11
• CPU: Intel i5-10300H
• GPU: RTX 3060 mobile
• RAM: 16 GB

Issue:

• Game goes ingame but it crashes after a while (see second screenshot)

Screenshots:

Log

vita3k.log

Recommended labels

• Ingame -
• Crash

[GamingDucking]

as of https://github.com/Vita3K/Vita3K/commit/b39d9bc427ceaa9d3f68eeb6f58fcaea0049512b, the game doesn't crash anymore and its now playable.

Screenshots

Log

vita3k.log

Recommended Labels

• Playable

[Champiggi]

I'm trying to play this game on the V8 android release of Vita3k, and all works well up until the tutorial (as in the menus work), where I get a white screen although the interface works. Anybody got an Idea for how I could make it work. I'll try it out on my pc this week-end but I don't have access to it right now

[D4sbo]

White screen problem persists on Android, the game is unplayable, performance is horrible