Patreon Logo Support us on Patreon to keep GamingOnLinux alive. This ensures all of our main content remains free for everyone. Just good, fresh content! Alternatively, you can donate through PayPal Logo PayPal. You can also buy games using our partner links for GOG and Humble Store.
Latest Comments by crazyg4merz
Stardew Valley Linux version is official, being ported by Chucklefish
3 May 2016 at 12:13 am UTC

Instabuy for me, I thought Ethan already has a playable version available for donator? Have been replaying Harvest Moon FoMT this entire week on emulator and now this news comes out. Can't wait :)

Virtual Programming have setup github issue trackers for their Saints Row Linux ports
25 Apr 2016 at 1:47 pm UTC

Quoting: tuubi
Quoting: crazyg4merzIt's better to let them know though, whether they are going to fix it or not at least it shows that we care about their games. There's no such things as bombarding when the issue is really happening :)
I'm not sure this is what you mean, but bug spam is a thing. If the bug is already reported and known, only comment if you have useful information to add. Duplicate reports help no one and saying "me too" is rarely useful. But by all means, please do report a bug if it's not already on the tracker, even if you think it might be trivial and/or obvious. Just check existing reports first and follow any guidelines set by the developer.
Yeah, just found out this is already reported here: https://github.com/virtual-programming/saintsrow3-linux/issues/4 [External Link]
Just keep tracking there instead of making a new report then, hopefully the developers can find a workaround or fix for it soon. :)

Virtual Programming have setup github issue trackers for their Saints Row Linux ports
24 Apr 2016 at 3:09 am UTC

Quoting: fagnerln
Quoting: crazyg4merzJust post the problem you have and attach your hardware information and the log file of SR4. You can read the instructions here: https://github.com/virtual-programming/saintsrow4-linux/blob/master/README.md [External Link]
Hope they'll fix it for you mate :)

Edit: so your problem is with SR3, I thought it was SR4. I only played SR4 and SRGOTH, sorry but I haven't bought the 3rd version yet. But still posting it to them doesn't harm. :)
I have SR4, and their first loading takes some time too, I tested it now and takes 59sec.
This is "acceptable", and I don't want to bombarding them with issues (for now at least :P )
It's better to let them know though, whether they are going to fix it or not at least it shows that we care about their games. There's no such things as bombarding when the issue is really happening :)

Virtual Programming have setup github issue trackers for their Saints Row Linux ports
24 Apr 2016 at 12:15 am UTC

Quoting: fagnerln
Quoting: crazyg4merzUsing the ssd for the os and Hdd with ext4 for the game files too. Loading time is not the problem here too, under 4 seconds on every scene too. I think you need to post the bug in their github. :)
I will post at their github, but I don't know what to say. I recorded with my camera, and ironicaly this time takes about 4 minutes. lol

To be clear, is only the first load, the other loadings after is very fast.

View video on youtube.com
Just post the problem you have and attach your hardware information and the log file of SR4. You can read the instructions here: https://github.com/virtual-programming/saintsrow4-linux/blob/master/README.md [External Link]
Hope they'll fix it for you mate :)

Edit: so your problem is with SR3, I thought it was SR4. I only played SR4 and SRGOTH, sorry but I haven't bought the 3rd version yet. But still posting it to them doesn't harm. :)

Nvidia 364.19 stable driver released, featuring Vulkan, Wayland & Mir support
24 Apr 2016 at 12:11 am UTC

Quoting: kon14
Quoting: crazyg4merzAfaik weston is not used by Gnome and other WM as they have their own compositor. So if Gnome developers decided to support it, we can get it working in Gnome right? Is Nvidia doing it the right way or is it just Gnome doing it using their own way? I really don't understand why are there different ways just to support wayland, so what's working on Nvidia driver if we can't even test the weston itself which is the default compositor of Wayland? Sorry I'm a noob in this kind of thing. :)
I only referenced weston cause it's the example/reference compositor maintained by the wayland devs that's meant to showcase wayland and its capabilities. No serious de is going to use weston as a base (besides most of the big de's wms are already ported over and standalone compositors won't fork it either).

Basically my understanding of the whole situation goes like this: The wayland devs and everyone related decided to go with gbm while nvidia was totally absent and now nvidia comes along with their own alternative after everyone has implemented the solution agreed upon.

In order for EGLStreams to work out wayland compitors are going to have to support them and, apart from software not being written and maintained by its own, that would fragment development and possibly even the wayland compositor scene (an already fragmented place compared to X11 where there's something more substantial besides a protocol for the compositors to implement).

tldr nvidia was late to the party and now they request that the party be restarted for them, the wayland devs are not against eglstreams due to design issues, but rather due to the fact that nvidia are being assholes trying to fix a non existent issue all over again just cause they like their solution better and don't much care about everyone else. (not really a tldr)
I see. So the only way out is Nvidia to cooperate as the others are not gonna redo their works and it's not good when you have to support drivers with different approach. So is it hard for Nvidia to change their Wayland implementation? Is it gonna be a whole lot to do for them to change? I hope it's just an easy fix so we don't have to wait too long for it, or Nvidia is done in Linux community when Fedora is using Wayland by default. Really a dumb move by them though :(

Virtual Programming have setup github issue trackers for their Saints Row Linux ports
23 Apr 2016 at 4:48 pm UTC

Quoting: fagnerln
Quoting: Xpander
Quoting: fagnerlnI love SW3, it's my favorite open-world game of all time. SW4 is great too, but isn't fun as SW3. The only thing that annoy me is their loading, it takes too long in comparison to Windows.

Takes >1min in Linux and a few seconds in Windows.
really? it takes like 5 seconds to load for me
i have it on SSD though, but i doubt the difference is so big
I measured the time, actually is 2:31... It's really strange. I've a SSD but only for the OS.

ps. Is the same hardware used in Windows. And i'm using ext4 btw (I don't know if FS had much to do).
Using the ssd for the os and Hdd with ext4 for the game files too. Loading time is not the problem here too, under 4 seconds on every scene too. I think you need to post the bug in their github. :)

Nvidia 364.19 stable driver released, featuring Vulkan, Wayland & Mir support
23 Apr 2016 at 4:34 pm UTC

Quoting: kon14
Quoting: crazyg4merzWayland support without DE support. Is there any link concerning this problem in Nvidia forum? I want to see the answer from Nvidia about this. Thanks :)
idk about the nvidia forums but there was a discussion [External Link] regarding Nvidia's EGLStreams going on in the wayland-devel mailing list.

The weston guys didn't really like it enough to support it, as did everyone else.

This new update seems to be featuring some extra work towards wayland support. Perhaps they'll like it better this time.
Afaik weston is not used by Gnome and other WM as they have their own compositor. So if Gnome developers decided to support it, we can get it working in Gnome right? Is Nvidia doing it the right way or is it just Gnome doing it using their own way? I really don't understand why are there different ways just to support wayland, so what's working on Nvidia driver if we can't even test the weston itself which is the default compositor of Wayland? Sorry I'm a noob in this kind of thing. :)

Nvidia 364.19 stable driver released, featuring Vulkan, Wayland & Mir support
23 Apr 2016 at 3:26 am UTC

Quoting: kon14
Quoting: martinoj2009If I install this driver does that mean I can use the GNOME Wayland option in Fedora 23? Whenever I try GNOME Wayland it just bounces me back to the login screen and I have to use any other desktop environment. I have Nvidia 361.42.
You won't be able to use wayland with these drivers, wayland support isn't really there.
Basically Nvidia wants to provide wayland support through egl extensions and nobody seems to like their approach so it's not getting upstream support for anything really.

For you to be able to use the nvidia drivers with gnome, Mutter (gnome's wm and wayland compositor) would have to support the nvidia blob's wayland implementation. I'm actually waiting for nvidia to get their shit together so as to be able to run Sway (an i3 compatible wayland wm based on wlc, a wayland compositor library) on my desktop :/
Wayland support without DE support. Is there any link concerning this problem in Nvidia forum? I want to see the answer from Nvidia about this. Thanks :)

Feral Interactive release the Linux system requirements for Tomb Raider (updated)
18 Apr 2016 at 6:54 pm UTC

Quoting: nIQnutn
Quoting: crazyg4merzDriver version 364.12, does this also mean that the driver will hit into stable version when it's released? ;)
Quoting: crazyg4merzDriver version 364.12, does this also mean that the driver will hit into stable version when it's released? ;)
It must be a joke, 364.12 is in BETA.
http://www.nvidia.com/download/driverResults.aspx/100577/en-us [External Link]
I know, but maybe it'll be out of beta by the time this game released? There's no way feral is asking the players to install the beta version to play this game right?

Feral Interactive release the Linux system requirements for Tomb Raider (updated)
18 Apr 2016 at 1:27 pm UTC

Driver version 364.12, does this also mean that the driver will hit into stable version when it's released? ;)