-
Notifications
You must be signed in to change notification settings - Fork 27
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
only black screen #166
Comments
Same result with Gog version: |
#158 is not about the host CD path, but the emulated CD drive for the game. That log ends like this:
However, if the game finds all paths as expected, the loadscreen will only appear around 32000 calls into emulation (the entire screen will be blue in OpenSWE1R then). The actual menu displays around 100000 calls into emulation. As long as stuff is happening in the log, OpenSWE1R is probably still working fine - it's just slow. If you are running on x86 Linux, you can use KVM using the UC_VM option. Also see #159. If the swep1rcr.exe is unable to locate data on the emulated CD, this will take even more than 32000 or 100000 calls, because it attempts a handful of paths for each file before giving up (#158 addresses this by improving CD emulation). |
Ok, I understand better, I was too impatient and closed the window before the game to start. If I wait a little more, I obtain the blue screen, then the main menu. But it's very slow, the cinematics don't play and I hear a noise instead of the music, is all of this the actual state of the project or I made a mistake? |
Answered in my previous post:
Closing. |
Thank you for your support and keep the work of this very interesting project. |
Hello,
I just compiled the last git version, put the content of the "gnome" CD folder in the "openswe1r" build folder, launch "openswe1r" and I obtain only a black window. This window does not close when I click on the cross, I have to kill it.
infos:
swep1rcr.exe Time/Date Wed May 12 02:03:30 1999
I joined you the log, thank you for your help.
openswe1r_CD.log
config:
Ubuntu 18.04
The text was updated successfully, but these errors were encountered: