has this been fixed by either dxvk or proton???
@CarnageDevs Hello there. I assume this does not happen with wined3d?
This is normal and appears to be a race condition within the game. I've seen this happen on Windows, albeit rarely, but at the same time running the game on Windows with DXVK doesn't trigger the hang any more often, so I doubt this is our bug.
Why is it so much more common on steam deck/linux? I can play for hours on windows and ive never seen it once, whereas i see it every play session on deckEl 28 ago. 2023 6:32, Philip Rebohle @.***> escribió:
This is normal and appears to be a race condition within the game. I've seen this happen on Windows, albeit rarely.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you commented.Message ID: @.***>
@CarnageDevs Hello there. I assume this does not happen with wined3d?
I just tested it, out of the 4 tests I ran, 2 of them had the same freeze and the other 2 had the game boot to the menu with a black screen (audio and buttons working), so it seems to happen with WineD3D as well. As doitsujin said, it looks like it may not be an issue with DXVK, though I'm not sure why it occurs so often on Linux.
Is there anything that can be done to mitigage it a bit at least? So ita not constantlt happening on linux?El 28 ago. 2023 6:57, Carnage @.***> escribió:
@CarnageDevs Hello there. I assume this does not happen with wined3d?
I just tested it, out of the 4 tests I ran, 2 of them had the same freeze and the other 2 had the game boot to the menu with a black screen (audio and buttons working), so it seems to happen with WineD3D as well. As doitsujin said, it looks like it may not be an issue with DXVK, though I'm not sure why it occurs so often on Linux.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you commented.Message ID: @.***>
If it's a race condition then anything that alters the execution time of the problem code can shift it from working to not. This means it might differ widely between setups since it could be affected both by the specific hardware and software and just something like having logging turned on vs off can make a difference for some of these issues (don't know about this specific one).
These types of bugs can be annoying to debug.
Is there anything that can be done to mitigage it a bit at least?
Enabling an FPS cap should help a bit (something like 30 on Deck). Other than that, not really.
proton experimentalx1 2023-08
Upon entering any loading screen in Atelier Sophie 2, the game may freeze/hang and requires a force quit. This happens sporadically but I've been able to fairly consistently reproduce it with the following:
This seems to be a longtime issue that has plagued most of Gust's recent releases, there have been people mentioning the same issue in the Proton issue tracker for Sophie 2, Ryza 2, and Ryza 3. You can see several reports of it too in the ProtonDB pages for these games as well as online such as this Reddit thread and this one too.
I can say I've experienced this issue multiple times now throughout the release of multiple Proton and DXVK versions, as well as Mesa drivers. It also happens on my Steam Deck.
Software information
Atelier Sophie 2
System information
Apitrace file(s)
N/A, the game seems to crash with the apitrace DLLs on Linux for me, and given how long it takes to reproduce (several minutes of gameplay) it may be difficult to get a trace
Log files
steam-1621310.log
Log file was taken following the steps to reproduce above, it ended up hanging after several minutes just before I reached Plachta's atelier as expected. If it's of note, I took the log file with atelier-sync-fix applied, but the issue happens regardless.