-
Notifications
You must be signed in to change notification settings - Fork 24
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
FFXIII crashes on startup #67
Comments
@Nucleoprotein It seems there's still something wrong with the ref count unfortunately... |
@Fwha please add system spec, CPU, GPU and OS. I think this is from Windows 7? |
1070 ti |
I do not know if this is the same problem or not but FF13-2 also crashes for me on startup. I have 7.1 audio and after some testing I noticed that the game starts without crashing if i turn off compatibility mode to windows 8, however doing so means that I now have an annoying buzzing in my ear. Removing FF13Fix but turning on compatibility mode with windows 8 lets the game launch without crashing and not having an annoying buzzing sound in the audio. It seams that FF13Fix is not compatible with windows compatibility mode since having both on causes the game to crash on startup. My system is: This is what FF13Fix.log read with out compatibility mode where the game launches without crashing: This is what FF13Fix.log reads with compatibility mode to windows 8 turned on and the game crashing on startup: |
I have the same issues as the OP. Game does not launch (or crashes, but with no error message). If I remove the d3d9.dll file from the bin folder, it launches correctly. Unfortunately I'm unable to play the game at resolutions higher than 720p, because of scaling issues. Specs :
10:28:35.698 00027060 WARNING: Reference count for IDirect3D9 is wrong: 08A50D08 0 2 |
When I start the game from launcher, it just doesn't even start. If I delete the fix though, the game starts. This is what's in the log file. The only mod I have is the playstation button mod. Otherwise, it's a fresh install.
The text was updated successfully, but these errors were encountered: