-
Notifications
You must be signed in to change notification settings - Fork 1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Final Fantasy IX (377840) #708
Comments
Just tried it myself. I just had a crash to the desktop. No Launcher or Game. my steam info: |
The game launcher crashes indeed. Using the latest Beta. System info attached. |
I get the same behavior as well. However running it directly with wine-staging using a 32-bit prefix works perfectly. |
Referencing #18 |
I can confirm that as stated at some point in issue #18, installing .NET and wine-mono does indeed let the game run. If you have all the necessary packages (wine-staging, wine-mono, etc.) The Wine prefix for FFIX is under "steamapps/compatdata/377840/pfx". |
Final Fantasy IX - No Sound Issue transferred from #2349. Compatibility Report
System Information
I confirm:
SymptomsNo Sound Tried installing directsound via winetricks [This fixed sound in FF8] but no luck. Can't find anything else on protondb or in this github. Steam Controller and graphics are flawless, even on 4k monitor. |
Follow up. two machines = machine A machine B will keep digging for now. |
Compatibility Report
System Information
LOG: SymptomsCrashes at launch |
@kisak-valve On KDE there are two entries for Final Fantasy IX on the Should be worth noting that protonfixes with this game works pretty well other than the sound issue on KDE, which might just be a quirk of the DE. What is valve's policy regarding including protonfixes as a community driven patching tool with the default proton distribution? |
The game starts normally with 5.13. The game appears to be playable now. |
Just came here to say that Proton 6.3-1 fixes all the launcher issues - one of the long remaining issues with FF9. Well done Valve 👍 now the game runs well without modification |
Only started playing this on 20th July 2021, with Proton 6.3-5, so everything's been flawless for me so far - no launcher issues or anything like that. Am about a third of the way through the story. Oh, I can confirm @Eoin-ONeill-Yokai's observation regarding the double entries for the FFIX application in KDE audio, but only the second one is effective. Not sure if that's specific to Proton or the game itself - I've seen some games, even native ones, have duplicate entries or list a second entry for a platform like FMOD, etc. The sounds itself works fine, though, at least on Proton 6.3. |
Having started the game again recently on a fresh install, I've noticed a regression on Proton 6.3-5 where the game isn't saving correctly. I've played again up to the first save point (Chapel in Alexandria) and tried to save the game and quit. Next time I opened the game up, all the save slots are empty. I was able to reproduce it again to confirm it. |
Hello @Eoin-ONeill-Yokai, please add |
Hi @kisak-valve , I've done more experimenting and saved a log file. (Tangential note, is there a way to specify a desired Log folder for proton?) I tried a few more things this time just to see if I could tell what's going on. It seems to me like the save functionality is off-loaded to another part of the game as saving the game and returning to the main menu will allow you to load the game as usual. However, after closing the game (and subsequently relaunching), the game will lose all save data. Here's a summary of the proton log (gzipped): And, since I'm not sure entirely if the issue occurs on launch or on close, I've also included a second run. This second run is when loading the game, seeing the menu, and witnessing no save files available. Another important note for testing is that the game's built in "checkpointing" system (represented as "Continue" on the main menu) also resets. This means that you could probably test this quickly by simply playing far enough to trigger the first checkpoint and then closing and reopening the game. I can't recall where this happens, but I think getting to Vivi after the Zidane controlled introduction might be a safe place to start. This is useful, since the first save moogle requires going through a few events that can take a few minutes. My intuition would be that the game is trying to move a set of files form Anyway, hope that wasn't too long and thanks for taking the time to read this. I know it's busy over there at Valve right now. Cheers! |
I believe auto-save or 'check-pointing' occurs with every screen load, ie moving to a new area in town, or entering/exiting the field in the main map. But I've been playing entirely on Proton 6.3-5 and don't observe (at least not yet) any issue with saving or loading, so I'm a bit confused as to what's going on here... |
@Wedge009 Interesting. I guess it should be worth noting I'm using a BTRFS system, though I really doubt that would affect it. It is something that has changed since the last time I played this game though... |
@Eoin-ONeill-Yokai Were you using a BTRFS system when you first played and the saves were working? Do you have anywhere to test with a more standard file system on the same hardware? |
Yes. #4265 (comment) |
Let me start by saying I fixed this issue by symlinking
@alasky17 No I wasn't. I took some time to test it on another machine in my house running Fedora (on ext4) and can confirm that this isn't occurring on that machine. So the problem seems to stem from the use of BTRFS on my Manjaro machine. I guess I'm mostly confused by why the process would be different -- perhaps it could be that something about the CoW process is messing with Proton's ability to setup the directories in Anyway, that probably means that this being a regression is a false alarm. Sorry about that, I think the BTRFS element of this new install was working so well that I kind of forgot to mention it. Let me just say that the process of launching this game is much better than in prior proton versions, and even installing mods is relatively easy compared to prior attempts (though moguri's installer is still broken, for those who are curious.)
@madewokherd Nice! I'll probably set that globally to my temp folder then since I often don't need them to persist, but I like the option of checking after launch. :) |
Didn't notice any issues after a quick test with Proton 7.0-1. |
Using Proton 3.7-3.
After the "preparing to launch" Steam popup, the game silently exits without any error or additional popup. No launcher or game.
Ubuntu 18.04, NVIDIA Quadro 1800
Full specs: https://gist.github.com/adrianlshaw/13b21eae4d9ad3c6c79474396110feed
The text was updated successfully, but these errors were encountered: