True. It boils down to time management for me. Time spent trying to figure out another app and manipulating the package size to fit under the 2-gig limit, is time not spent on updating the game. Ren'Py has an emulator built in. I've tried using it. When I distributed it out to my Patrons, they had issues with it working.
Hello Black_Prince, I'm sorry to hear you are having problems running the game. I'm at a loss since I have 0 Linux experience. Maybe someone else on the thread can help you. Are you using the latest full update? (10.0 Part one) There's an old 9.0.1 partial update posted. Don't use that.
Assuming you have a Linux distro based off Debian (more than likely), I'm thinking it's probably about /dir permissions (all depending on where you unpacked the game archive because seems to me you're running the correct file).
Ok I've just ran a small test on an Ubuntu VM Fully updated etc. And I'm getting same results as you are, Shell window runs and then quits. And it's nothing to do with /dir permissions. Let me look into this and I'll get back to you shortly.
First of all, many thanks for all answers on my matter so far!
I understand your situation, I'm sort of in the same boat myself. Although I enjoy playing in linux now and again, I'm not a "guru" per-say.First of all, many thanks for all answers on my matter so far!
I am also pretty new to linux myself, so don't expect an advanced expertise about linux from me, but of course I want to provide more information hoping this helps my helpers to help me run the game ;-)
I downloaded the game the first time and just today, therefore I chose the full one, not just an update. Unfortunately you were wrong, I am using Linux Mint 21.1 with Cinnamon 5.6.8, which is based on Ubuntu afaik.
Something I witnessed, some ren'py games after extracted to their chosen directory come with already set permission to run the .sh file as application - some don't. Why? Maybe this is an useful hint for those who know linux more than I?
I thought okay, just set this permission in the .sh file properties access tab and there we go, but seems as it is not that easy
Guide me to get the information you need and I will provide it if this was still too less information, I will be very happy and thankful if this can be solved. Thanks for all your efforts!
although it is not solved yet I believe this is a promising direction towards solution, at least it is a step forward and more than I would have been capable of, so let me thank you so far.
Hmm
I did as you recommended and what can I say? It simply worked! I still don't understand the reasons, but I am glad and happy that it really seems to work now. I will definitely remember this if similar problems occur in future with other games and try this again, thanks for solving my issue dude!Seems both LongRoadHome.sh and lib/linux-*/LongRoadHome don't have the execute bit set -- unarchived via Debian UnZip 6.00 (20/04/2009)
chmod u+x LongRoadHome.sh lib/linux-x86_64/LongRoadHome solved things for me.
In other words, set the executable flag on both LongRoadHome.sh and lib/linux-x86_64/LongRoadHome (or lib/linux-i686/LongRoadHome if you're on a 32-bit system) in a file manager.
I know Funky in real life (I'll gladly accept pity), looks like he didn't unarchive it properly -- lib/ was missing -- therefore problem exists between keyboard and chair there
You're an ass, but I lub you anyway!I know Funky in real life (I'll gladly accept pity), looks like he didn't unarchive it properly -- lib/ was missing -- therefore problem exists between keyboard and chair there
NotQuiteHere explained it - Windows archive utilities tend to not understand the way unix (and so Linux & macs) do file permissions. The chmod u+x command he gave gives the file's owner permission to execute that file. Otherwise the OS will refuse to treat the file's contents as something run-able. You'll def want to remember this tho - if it's anything like my mac you'll be seeing this a LOT when DLing things that need to be executable.
I'm just glad we have a very knowledgeable community willing to help others.NotQuiteHere explained it - Windows archive utilities tend to not understand the way unix (and so Linux & macs) do file permissions. The chmod u+x command he gave gives the file's owner permission to execute that file. Otherwise the OS will refuse to treat the file's contents as something run-able. You'll def want to remember this tho - if it's anything like my mac you'll be seeing this a LOT when DLing things that need to be executable.
Dev just posted this on Patreon.
