Skip to content
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

(Recent) Godot games fail to load #361

Closed
qixils opened this issue Aug 4, 2020 · 12 comments
Closed

(Recent) Godot games fail to load #361

qixils opened this issue Aug 4, 2020 · 12 comments

Comments

@qixils
Copy link
Contributor

qixils commented Aug 4, 2020

commit: 5471b77

games tested:

Attempt 1: Connected.
Godot Engine v3.2.1.stable.official - https://godotengine.org
[libTAS f:0] Thread 420534 (main) OpenGL vendor: NVIDIA Corporation
[libTAS f:0] Thread 420534 (main) OpenGL renderer: GeForce GTX 1660 SUPER/PCIe/SSE2
XIO:  fatal IO error 17 (File exists) on X server ":0"
      after 28 requests (28 known processed) with 0 events remaining.
[libTAS f:0] Thread 0 (main) ERROR: send() returns -1 with error Broken pipe
XIO:  fatal IO error 2 (No such file or directory) on X server ":0"
      after 28 requests (28 known processed) with 0 events remaining.
[libTAS f:0] Thread 0 (main) ERROR: send() returns -1 with error Broken pipe

no window ever opens

a much older game from jan. 2017 appears to load and run fine, though i didn't extensively test

@clementgallet
Copy link
Owner

Looking into gdb and at Godot's code, the engine uses forked processes (without exec) as part of execution (see https://github.com/godotengine/godot/blob/master/platform/linuxbsd/detect_prime_x11.cpp), and libtas does not like this (at least for socket communication between game and program).

@InfoTeddy
Copy link
Contributor

Does the latest commit 499fd07 improve behavior with these games?

@qixils
Copy link
Contributor Author

qixils commented Aug 13, 2020

unfortunately not, same error(s) as before

Interim commit 499fd07 built on 2020-08-13
Icon theme "deepin" not found.
Attempt 1: Connected.
Godot Engine v3.2.1.stable.official - https://godotengine.org
[libTAS f:0] Thread 500645 (fork) OpenGL vendor: NVIDIA Corporation
[libTAS f:0] Thread 500645 (fork) OpenGL renderer: GeForce GTX 1660 SUPER/PCIe/SSE2
XIO:  fatal IO error 17 (File exists) on X server ":0"
      after 28 requests (28 known processed) with 0 events remaining.
XIO:  fatal IO error 2 (No such file or directory) on X server ":0"
      after 28 requests (28 known processed) with 0 events remaining.

@clementgallet
Copy link
Owner

out-of-controls working with the last two commits (fd46d4f and fe7b8dd). Default audio driver seems to be pulseaudio, so by default audio is not hooked. The engine also implements ALSA audio driver, so there should be a setting or command-line option to use ALSA instead.

@qixils
Copy link
Contributor Author

qixils commented Aug 14, 2020

running the game with --help shows all the options which includes --audio-driver ALSA, though it seems to cause the game to freeze on frame 0 when used in libTAS

loading savestates seems to cause stack smashing, though that could also be because i'm running unsupported graphics drivers?

*** stack smashing detected ***: terminated
recv() 0 bytes instead of 4
Got wrong message after state loading

thanks for working on this by the way ^^

@InfoTeddy
Copy link
Contributor

No, the stack smashing when loading savestates is probably #359. As a workaround, just disable savestate compression for now.

@qixils
Copy link
Contributor Author

qixils commented Aug 14, 2020

Ah, correct guess! That fixes it. Won't close this issue yet though as the ALSA hang remains.

@clementgallet
Copy link
Owner

Commit 3904615 should fix the alsa driver output.

@qixils
Copy link
Contributor Author

qixils commented Aug 25, 2020

awesome, can confirm it works as expected! only issue left is there's still savestate smashing with compressed savestates enabled, but i'm guessing that's not related to godot in any way

@InfoTeddy
Copy link
Contributor

Yes, that's unrelated, and #359 has been fixed anyways if you're on the latest commit.

@qixils
Copy link
Contributor Author

qixils commented Aug 25, 2020

i'm on latest commit and still experiencing the issue.

@InfoTeddy
Copy link
Contributor

Weird - could you try VVVVVV? That's the game I tried it with, and it works fine for me.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants