Phantom Dust: Random freezes

[danielw1990]

Title
https://xemu.app/titles/4d530046/#Phantom-Dust
The application seems to freeze completely.

If I run it from the command line I get no new information after launch:
xemu_version: 0.7.57
xemu_branch: master
xemu_commit: 6a8a967
xemu_date: Sun Jul 3 01:05:50 UTC 2022
xemu_settings_get_path: config path: /home/daniel/.local/share/xemu/xemu/xemu.toml
CPU: AMD Ryzen Threadripper 1900X 8-Core Processor
OS_Version: Ubuntu 20.04.4 LTS
GL_VENDOR: NVIDIA Corporation
GL_RENDERER: NVIDIA GeForce RTX 2070/PCIe/SSE2
GL_VERSION: 4.0.0 NVIDIA 470.129.06
GL_SHADING_LANGUAGE_VERSION: 4.00 NVIDIA via Cg compiler

After that nothing, but that seems to be normal as that also applies if I let it run. At some point the game enters a demo mode and plays a video. The video runs fine.

So the 2 behaviors seem to be:
Boot -> Freeze
Boot -> Game -> freeze at end of campaign load

as I am writing this behavior 3:
Now it froze some while after playing through the complete demo video. I saw the screen where it tells me to press start again for a while so my guess is that it froze when it tried to start the video again.

Expected Behavior

Well, according to the compatibility list the game should work. And that seems to be the case until it just freezes.

xemu Version

xemu_version: 0.7.57
xemu_branch: master
xemu_commit: 6a8a967
xemu_date: Sun Jul 3 01:05:50 UTC 2022

System Information

OS: Ubuntu 20.04.4 LTS
CPU: AMD Ryzen Threadripper 1900X
GPU: some Nvidia RTX2070 (if the exact model matters I can go check the box in the attic) driver:
VBIOS Version: 90.06.2e.40.dc
NVIDIA Driver Version: 470.129.06

Additional Context

I thought it might be related to:
#54

Because if it goes into the game that has been where it froze the 2 times it got that far.

When it booted into the game for the first time I got pretty optimistic because the menu worked flawlessly.

Is there a way to enable more debug output?

[abaire]

You appear to have omitted the most important part of the issue template, and have provided no info indicating what game you're talking about.

Please edit the report and add a link to the compatibility page for whatever game this is so that it is properly linked and can be investigated.

[abaire]

Also be aware that use of a debug bios is not recommended and can lead to bad behavior (including freezes) in various games. If you're not doing actual xbox program development you should not use a debug bios.

[danielw1990]

Thanks. It was most likely the bios. Another bios got me in game and I did not notice a problem that was for sure a bug.
As in game ran fine only problem I found was memory card related which I would chalk up to "user error".

Sorry, I wasn't clear on the game: Phantom Dust

But now with the same bios int run fine with I get the error: “Guest has not initialized the display (yet).”

Also:
Is there a way to manually provide a config file? The random freezes make it hard to change the bios. Being able to swap configs faster would drastically help narrowing down the problems.
Ideally that config would also provide a way to add a memory card. The freezes also make entering the 4 necessary commands manually every time a bit of a chore.

I feel like a config file was hinted in some article I stumbled over but it did not explain how to use it. So I did not deem it sufficiently valuable at the time.

[abaire]

Thanks. It was most likely the bios. Another bios got me in game and I did not notice a problem that was for sure a bug. As in game ran fine only problem I found was memory card related which I would chalk up to "user error".

Sorry, I wasn't clear on the game: Phantom Dust

If the random freeze is no longer a problem, please close this issue.

If it still is a problem, please edit the title of this bug so that it's clear what game freezes without read the thread. Please also edit the content and add https://xemu.app/titles/4d530046/#Phantom-Dust so it's associated with the compatibility page.

But now with the same bios int run fine with I get the error: “Guest has not initialized the display (yet).”

Also: Is there a way to manually provide a config file? The random freezes make it hard to change the bios. Being able to swap configs faster would drastically help narrowing down the problems. Ideally that config would also provide a way to add a memory card. The freezes also make entering the 4 necessary commands manually every time a bit of a chore.

Yes, you can edit the xemu.toml file directly. This doesn't have anything to do with the reported problem, so please ask on the #help channel (make sure you include what OS you're using) in Discord if you're unable to find the file.

[danielw1990]

Edited title, as for the issue:
xbox-4134.bin
Also has random freezes.

xbox-4817 used to work perfectly (aside from memory card missing -49998 blocks to be able to save, but I assume that's user error with memory card usage) but now gives: “Guest has not initialized the display (yet).” That was confusing.

This issue however does not freeze the application, everything stays responsive. I can change settings etc. But 4134, seems to be the same as the initial problem, it appears to freeze earlier if it does.

As for the Discord: It requires a phone number as far as I can see. I am not comfortable with giving that company this type of info.

[Triticum0]

@danielw1990 If you want to play Phantom Dust It free on the xbox store for pc now https://www.xbox.com/en-us/games/store/Phantom-Dust/9PCDNBHR11MR =)

[danielw1990]

I would not call those conditions "free". At that price I would rather pay 20€. To my knowledge there is no practical way to get those applications running without the Xbox app. And good luck (I mean that. I would appreciate a way to break those shackles!) running such a convoluted mess on anything not Microsoft approved. Which is probably the point of that system to begin with.

[gelatinbomb]

Same problem here on Fedora 38 with a Intel HD 5500. I tried all the bios I could find without any sucess. I usually have to kill the process with the task manager because Xemu dies each time I try to open the game. I hope something can be done to solve this since I can't use the pc port due to the Microsft Store requirement.