-
Notifications
You must be signed in to change notification settings - Fork 32
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
What's the status of this repo? #20
Comments
(Not a maintainer of this repo but I worked on the Linux port that got merged into here.) I use a build script to build this on Linux. What distribution and desktop environment are you using? I haven't yet gotten to packaging this into a single executable because of some dependency issues (and switching to a new build system) but if you're having issues with the build you can either reply here or contact me via mail ([email protected]) or Discord (KockaAdmiralac#9306). |
Officially, we're also working on the Linux port as a fork of this repository, found on Gooborg Studios' account. @KockaAdmiralac is working on the Linux portions of this fork, and the build script minus dependency installation is included there. 😉 |
Ubuntu 18.04, Openbox WM. You're saying that |
That's correct! It's where we've implemented all the Linux code and whatnot. 😉 |
Thanks! I'll give that a try. Should I use KockaAdmiralac's build script for that repo? Or should I read the readme and figure it out myself? |
Kocka's build script is more robust than the one in the repository. I would use theirs as it installs the required dependencies along with compiling the game code! Edit: Actually reading through it a little, I realize that Kocka's script already uses the fork. XD |
Thank you so much for your help! I'll try that now. |
So, partial success.
Everything else seems to work, but running the new |
To resolve the SteamWorks API error, you can try recompiling without Steam support by removing If you want Steam support as well, you can compile the Steamshim parent, create What does the |
Removed the recommended instances of steam from mkxp.pro, then ran qmake, make, cp and ruby from the script file to hopefully update those changes. Game window opens to a black screen, then instantly closes and I get:
Empty string. (Output is a blank line.) |
Interesting. It never really segfaulted for me that early during startup, so I'll have to install Openbox to investigate this. The build script probably didn't mention or do this, but the files from synglechance/patches/assets need to be copied to the directory with the built executable (while merging the directories). Then copy OneShot's Windows files into that directory (while merging the directories but not overwriting the files, Data/xScripts.rxdata and the patches must not be overwritten) and the game should, under normal circumstances, be playable from that point. If you don't have OneShot's Windows files, the build script installs SteamCMD from which you can download them so you can:
If it doesn't work past that point then it's an issue with the executable itself. |
It still segfaults. I was planning to install a new OS soon anyway, so I could do that now and then try OneShot again, starting from scratch. Might work out. I've got a feeling something's wrong with my current setup. |
I believe the issue is that you don't have a DE so this tries to create a string out of NULL: Line 284 in 88c3867
I'll try to fix this today, but I don't know if I'll be able to replicate changing the desktop background on Openbox soon. |
Openbox doesn't have a built-in way to set the desktop background. Most people, including me, install and use
This is "fill" mode, so the background will be uniformly zoomed to cover the entire screen. The image doesn't stretch and there aren't black bars. Parts of the image may be offscreen if the aspect ratios are different. |
We'll probably use the fallback for "Other DEs" for Openbox. If |
I'm a bit late, but GooborgStudios@6ebb92c should fix the crash on Openbox. Anyways, could you do a |
Note: I've since wiped out my Ubuntu install in favour of Arch. Everything outside /home has been destroyed. I did this because I've been encountering numerous issues with building other packages that worked fine before, and I didn't want you to waste your time on trying to deal with whatever jankery was going on. I started over with Kocka's Arch install script (using the same directories and their contents as before) and the game now starts and appears to run fine after a moment of walking around and examining things. Thank you SO much for your hard work on this port! |
Cleanup (remove fiber, gamejolt and discord bindings)
I run Linux. I want to play OneShot, and I want a good first experience. I don't have a physical Windows machine.
I tried running the game in a virtual machine, and the closest I've got so far is Windows 7 in VirtualBox, and the game actually starts, but the floor texture disappears whenever I change rooms (but only after leaving the first building). It comes back when I restart the game. This is obviously not ideal.
I could try using Steam Play/Proton, but according to the ProtonDB entry the "meta" elements of the game don't really transfer over too well. I've seen a few of these meta elements already.
I see that you're still updating this repo, so my hopes are high, but is it actually a good idea to try using this repo for my first playthrough, or will the experience just sort of fall apart?
Sorry for opening an issue for this, but I couldn't find another place to contact you at. If you want to reply privately, you're more than welcome to use the contact details from here.
The text was updated successfully, but these errors were encountered: