One of the developers of Desktop Dungeons has written a blog post from a Windows user point of view about getting Unity games to play nice on Linux.
Blog posts like this are a great resource for developers who need that little helping hand in getting their Unity games to work properly on Linux.
A lot of it may seem trivial to someone with half-decent Linux knowledge, but remember it is from a Windows developer point of view.
The first point is perhaps the most important
Don't just publish your game from Unity and expect roses, it will probably need some tinkering and how can you support buyers of your game if you haven't even tested it? I fear a fair few developers still don't do this basic step.
It's great to see developers give back to others to help out with Linux, kudos to the Desktop Dungeons guys. I feel developers who do this kind of thing are worth supporting, don't you?
See the full post on it here. Be sure to share it to any Unity developer you feel it may help.
Blog posts like this are a great resource for developers who need that little helping hand in getting their Unity games to work properly on Linux.
A lot of it may seem trivial to someone with half-decent Linux knowledge, but remember it is from a Windows developer point of view.
The first point is perhaps the most important
QuoteYou're going to need to test in Linux
Don't just publish your game from Unity and expect roses, it will probably need some tinkering and how can you support buyers of your game if you haven't even tested it? I fear a fair few developers still don't do this basic step.
It's great to see developers give back to others to help out with Linux, kudos to the Desktop Dungeons guys. I feel developers who do this kind of thing are worth supporting, don't you?
See the full post on it here. Be sure to share it to any Unity developer you feel it may help.
Some you may have missed, popular articles from the last month:
9 comments
There's quite a few mistakes in there.
2) chmod 777 is very bad. chmod 700 should suffice
4) Don't use getconf LONG_BIT (that will also output 64 on a lot of non-x86 architectures). Use uname -m
6) "en" is not really a valid locale. A valid locale consists of a language, a region and an encoding. For example: "en_US.UTF-8". Just "en" might work, but it might not
2) chmod 777 is very bad. chmod 700 should suffice
4) Don't use getconf LONG_BIT (that will also output 64 on a lot of non-x86 architectures). Use uname -m
6) "en" is not really a valid locale. A valid locale consists of a language, a region and an encoding. For example: "en_US.UTF-8". Just "en" might work, but it might not
1 Likes, Who?
Quoting: DrMcCoyThere's quite a few mistakes in there.
2) chmod 777 is very bad. chmod 700 should suffice
4) Don't use getconf LONG_BIT (that will also output 64 on a lot of non-x86 architectures). Use uname -m
6) "en" is not really a valid locale. A valid locale consists of a language, a region and an encoding. For example: "en_US.UTF-8". Just "en" might work, but it might not
Good tips. A thing to note that I learned recently is that when publishing to Steam, Steam will a+x dang near every file in the install directory. I am guessing it's for people who want to store their SteamApps in a shared location, but still doesn't make sense for most file types.
0 Likes
Quoting: DrMcCoy2) chmod 777 is very bad. chmod 700 should sufficeThat would mean that only the owner would be able to update the game, which might be a problem for some people.
0 Likes
Quoting: AnonymousQuoting: DrMcCoy2) chmod 777 is very bad. chmod 700 should sufficeThat would mean that only the owner would be able to update the game, which might be a problem for some people.
and it should stay a problem. it would be much better if steam worked like package managers and simply provide ipc to its client where client could request update at any time. that way all files could stay protected full time and every legitimate user would be able to update it
thing only works because steam is checking integrity if file that was launched really is file that was copied. but, 777 opens whole sh1tstorm of bad karma
0 Likes
Well, I tried to register on this website to post a comment on this (mostly the `uname -m` thing, plus export LC_ALL=C which often causes problems in unity games. But I don't understand the verification question :
Since I don't know the answer, I can't register and comment -_-
QuoteWhich kind of farm animal features prominently in Desktop Dungeons? (Hint: The forum bot is one of these):
Since I don't know the answer, I can't register and comment -_-
0 Likes
Quoting: MayeulCWell, I tried to register on this website to post a comment on this (mostly the `uname -m` thing, plus export LC_ALL=C which often causes problems in unity games. But I don't understand the verification question :
QuoteWhich kind of farm animal features prominently in Desktop Dungeons? (Hint: The forum bot is one of these):Since I don't know the answer, I can't register and comment -_-
goat
0 Likes
Thank you ;-)
0 Likes
Well, reading this as a long-time linux user, for me those "issues" are non-brainers.
But he's right, for a Windows-Dev who never used Linux and just wants to publish the game, it can take some time. But not more than a day.
But he's right, for a Windows-Dev who never used Linux and just wants to publish the game, it can take some time. But not more than a day.
0 Likes
I thought that pipelight has brought the solution already.
0 Likes
See more from me