Good to hear that, sporadically I write some installers and fix the ones that won't work with the games I have.

As Lutris mostly do "file 1" with "file 2" and "file 3" merge in same directory which could be done without any interface or even Lutris itself, in the guts every YAML / JSON script do the same thing take some files put here and there and run for everyone's fun, sometimes with some special options, a GUI to simplify the process to create "installer" will be welcome for who doesn't have any programing skills and loves Linux.

View this comment - View article - View full comments

Quoting: dpanter

Quoting: GreaserI'm currently stuck in this stupid museum mission at the bossfight against Tahir.

If you're playing on Normal, the fight is hard but manageable. There's a decent weapon nearby, find it with Survivor Sense. Throwing your broken melee weapons still cause full damage, Melee throw is a skill.
On Hard and Nightmare, it's more like wearing down a bloody tank.
You can get weapons from the soldiers by using Vault+Drop attack for a quick'n'dirty insta-kill. It's what we like to call a pro-gamer move. ;)

But hit me up on GoL Discord or Steam and I can help out. :)

Could I ask you something? Drop attack works with your card and driver, in my RX560 with Mesa 19.1.5 it freezes and many times crashes, any special config?

View this comment - View article - View full comments

I bought at the launch and I had the game for 3 years, it was long before Steam had refund option.
I wished and hoped that things was different but they lied and they didn't give a "F" for who paid for, as a customer it's the worst service by company and guy which tries to manipulate other people with some kind of "confirmation bias" that they believes, most of us linuxers just asked a playable game not the piece of cr*p that they sold, after all, EULA sucks and guess what, I think that they just trying to avoid a lawsuit for refunds.

Well, I won't have anything back, their attitude was so disgusting and because that I deleted from my Library all games from Facepunch and Garry related after their bitter post against Linux customers, anyway, IMHO, as they said "linuxers are insignificant with their 0.1% share" just pull out Linux version and give the money back, we gonna spend somewhere else, it's easy.:D

View this comment - View article - View full comments

I'm with Ubuntu at this time, even not using any *buntu or based since 2008, to isolate desktop and avoid user-space breakage we need a better solution like Dosbox did for 16bit programs, we need a real 32bit emulator and not the mess that turned nowadays as Wine evolves but 32bit libs frozen, no improvement, patches or fixes, more sooner than later 32bit libs will be incompatible with new toolkits and DE devs will just throw the towels. Since I came to Japan I stopped being a programmer afaik I guess that virtual machines in containers could be a better solution imho.

View this comment - View article - View full comments

Quoting: F.Ultra

Quoting: GuestI bought Dying Light one year ago. Actual play time 0 minutes, it never worked on my machine, neither with Mesa or Mesa-git. So if they release it for Linux, they hopefully make it work as well. Otherwise I can't see what's the difference to a Windows only release. I paid the full price for this game, but so far I got 0 fun and 0 service. Technology wise I hope they go Vulkan only for Dying Light 2 to reduce bugs.

Did you change the Launch Options in Steam to "MESA_GL_VERSION_OVERRIDE=4.5 MESA_GLSL_VERSION_OVERRIDE=450 %command%"? This is needed for it to start on Mesa since it tries to open v4.5 of the compat profile instead of the proper core profile.

I did, I did strace, gdb and no luck at all, I was thinking even use a disassembler like ida to look into source code and find what they did wrong but assembly language is my Achilles tendon, my BASIC and Pascal languages knowledge it won't help at this moment :(, after Mesa 17 the Chrome Engine 6 itself stopped work and nothing based on same engine will work, in all logs that I got it fails to detect graphics card and memory, fills up around 700mb ram and crash to desktop.
Anyone else is getting [0] vram detected in game logs "$HOME/.local/share/Steam/steamapps/common/Dying Light/DW/out/logs/"?

View this comment - View article - View full comments

If they really want us it's better to ask a real Linux professionals like Aspyr and Feral to port since their half-baked products didn't followed FOSS tendencies and neither DyingLitch nor DeadIsland it's working with latest Mesa, I own both, I love play both but without Techland wish to fix my money turned garbage because it's no more playable, if someone here have some kind of direct contact with them please send my advice to them :D

View this comment - View article - View full comments

Anyone had any lucky running Dying Light EE?
Mesa override trick start the black screen with white progress bar at the bottom but after bar fills it CTD. In the game logs it seems that doesn't detect vram, same on Dead Island DE, the engine is probably broke for Mesa 18 and above, I wouldn't recommend to buy if your graphics card is AMD or Mesa version is >= 18 :(

View this comment - View article - View full comments

I was wondering if SteamOS will jump someday in Wayland, as nothing is flawless some is more than others, X is insecure and someday not so far from today will not be the standard anymore, so, if some company use that as anti SteamOS, devs will just stay on easiest path that desktop gamers are already used to be and Valve will bleed out customers or am I too speculative about that?

View this comment - View article - View full comments

Quoting: M@GOidMultithread is bad in OpenGL? Well, call me skeptical on that.

Anyway, 4A and Feral did it, so technically OpenGL is not blocking a multicore CPU utilization in Civilization VI.

This is the simplest diagram I can do now:

Old layout:
Kernel > Driver > Single-threaded API > Application > User interactions

Intermediate layout:
Kernel > Driver > Single-threaded API > Custom multi-threading layer > Application > User interactions

New layout:
Kernel > Driver > Multi-threaded API > Application > User interactions

You probably never heard that they have a very limited way to "translate" one API to other since the application must always do the same intended result as the original and never resemble like Jesus Fresco restoration or else "you had a job".
Technically, the multi-thread support must be in the guts since the beginning of creation. To change single-threaded model to multi-threaded you must put a main thread atop and dissect entire program which gives you new bugs when the original was already debugged making you spend a lot of time redoing the job, also, since the main structure was changed you must manage all things to the intended thread which can render new bugs again. Probably nobody receives so much freedom up to optimize and implement what wasn't in original code when API translation is involved.

View this comment - View article - View full comments

Who da hell is thinking that?

AFAIK no news has copyright and only the news subject can claim something;

Well, I always read both but never saw any rip off here, but by the forums I prefer to post here in GOL because Phoronix people is less flexible and less comprehensive. I feel that you, Liam, accomplished a healthy community here and I feel good to be here, thanks man.

And... I'm sorry my bad english, I'm brazilian living in Japan and it's very hard to not forget how speak english when you use less and less frequently...

View this comment - View article - View full comments