-
Notifications
You must be signed in to change notification settings - Fork 13
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
How do I use the Flatpak version of GZDoom with this? #82
Comments
Honestly, i don't know, i never used it. |
@Espio419 you could probably do this: make a "gzdoom" script in ~/.local/bin/ with the contents:
(make sure ~/.local/bin is in your path) |
No luck. Runs fine when executing out of the mod loader. |
Make sure the script is executable (i.e. |
@Espio419 works for me: $ mkdir ~/bin
$ echo -e '#!/bin/bash\nflatpak run org.zdoom.GZDoom $@' > ~/bin/gzdoom
$ chmod ugo+x ~/bin/gzdoom Then use the "Initial setup" menu to set |
Can you please give me an example of shell command that you use to start the Flatpack version of GZDoom with additional parameters (WADs, ...) ? |
The above script do the job, basically the command is: $ flatpak run org.zdoom.GZDoom ...<any parameter>... |
I'm having a similar issue. I'm using the flatpak version of Doom Runner with the flatpak version of GZDoom, and it's detecting that engine fine, but when I install the flatpak version of Crispy Doom it isn't detecting it. |
Please take a look at this README for using other sandboxed engines. |
Those instructions aren't working for me. Is the flatpak version of Doom Runner supposed to automatically detect the existence of the flatpak version of Crispy Doom, like it did with the flatpak version of GZDoom? edit: The error message is |
DoomRunner didn't automatically detect GZDoom, it was included with the DoomRunner Flatpak. Crispy Doom would need to be added as well. |
Please, provide more details about your environment:
No, as @poperigby pointed, the GZDoom engine is embedded within the app. Any other engine (even Flathub GZDoom) must be properly configured and it's not auto-detected. From README:
|
Oh, my mistake. In that case, I think for my use case I'll just continue to use GZDoom for now, and possibly build it from source later so I don't have to use any of the Flatpak ecosystem in the first place. Thanks for the help. |
@Espio419 the engine "executable" is |
No description provided.
The text was updated successfully, but these errors were encountered: