Quoting: rea987Cause, Linux Mint will stick with kernel 4.4 for 2 years until the next LTS of Ubuntu released. Of course it will be possible to install backports but it still will be a hassle for end users.

No need for backports. 4.8 is available in the official repositories, and can be installed using Mint's kernels dialog. It only takes a few clicks.

Quoting: liamdawe

Quoting: tuubiBTW: Compton's VSync guide also has this to say about NVidia's ForceFullCompositionPipeline option:

However it’s indicated that it introduces huge (~30%) performance loss on some OpenGL applications.

I guess this info could be old and obsolete though?

That's very outdated information, my own tests have shown it to be a 2-3FPS difference, so that can be written off for benchmark differences each time you run it. Old cards may have more of an impact, but it hasn't been a problem for quite some time.

Good to hear.

View this comment - View article - View full comments

Quoting: GuestFor those who don’t know already, you can also use Compton to disable tearing, which may work with more than just the nvidia drivers:
compton --vsync opengl-swc --backend glx

Compton seems to be a popular choice for Xfce users like us, and for me it works pretty much perfectly, but looking at this [External Link] I think the optimal settings might be different for different graphics hardware. In fact the guide suggests that it might be better to use VSync options provided by the driver over Compton's own, if available.

The new Mint 18.1 Xfce actually includes a setting to use Compton as the compositor instead of Xfwm's own, making the switch as easy as clicking a checkbox, but I haven't looked at their default Compton config.

BTW: Compton's VSync guide also has this to say about NVidia's ForceFullCompositionPipeline option:

However it’s indicated that it introduces huge (~30%) performance loss on some OpenGL applications.

I guess this info could be old and obsolete though?

View this comment - View article - View full comments

Quoting: pete910I'll stick to two cups and some string thank very much :P

Isn't that one cup, two...

Nevermind.

View this comment - View article - View full comments

Quoting: Alm888

Quoting: TwombyWasn't able to upgrade to latest version.

Maybe you should try official drivers from www.nvidia.com.

Isn't that exactly what he did?

If your distro packages the latest proprietary drivers, there's rarely any reason to use the Nvidia installer instead. For Mint I recommend Ubuntu's semi-official Proprietary GPU drivers PPA [External Link].

View this comment - View article - View full comments

Quoting: Mountain ManAh, I was hoping it was a real fix that didn't rely on hacky work-arounds.

That fix is called Wayland.

View this comment - View article - View full comments

Quoting: ShmerlKnowledge usually isn't dumped, it's simply extended. I.e. they might be invested in C++, but if they are smart, they can start shifting things to Rust gradually.

Maybe Rust will replace C++ in the industry one day, who knows. I don't think this will happen quickly though.

In any case, the thread is about VkHLF, which is a C++ library. I think most games that would benefit from Vulkan are still developed in C++ so this library certainly seems useful.

We'll see if AMD and/or Intel deem it necessary to provide their own competing abstractions. They could always try to optimize them for their own hardware's strengths. Nvidia certainly might.

View this comment - View article - View full comments

Quoting: M@yeulC

Quoting: MohandevirYep. It feels like corruption of some sort. If you try to restart the game immediately after a crash it will crash again, everytime, in the first minutes of the "relaunch". After a reboot, the crash doesn't occur for quite a while... Until another "corruption".

Actually, this sounds a bit like a RAM issue. I would do a memtest if I were you, just in case :)

A game known to be rather crash-prone crashing is hardly a good indicator of hardware problems, but a memtest won't hurt I guess.

View this comment - View article - View full comments

Hmm... I wonder why I've had no need for this stuff on at least three generations of Nvidia cards. Maybe it's down to my choice of compositor? I remember having trouble with video tearing at some point, but that was before VDPAU support in players.

EDIT:

Quoting: Twomby

Quoting: liamdawe@Twomby, you likely need to update your driver.
Also, as stated, click Advanced.

Whether I click Basic or Advanced, I get the same screen. Should have posted a screengrab with Advanced settings to avoid confusion. My NVIDIA drivers are the latest version (375.10 BETA).

Did you update nvidia-settings as well? Also, the latest version is 375.26, right?

View this comment - View article - View full comments

Quoting: Shmerl

Quoting: tuubi

Quoting: ShmerlVulkano is easier to use than raw Vulkan: https://github.com/tomaka/vulkano [External Link]

Yeah, but I don't think game devs will switch to Rust just to use it. Anyway, the more the better. There's never a single approach that works best for everybody.

Some already might. Rust can remove a lot of pains that exist in C++ despite all the latest advancement in the language. The only thing that can slow down such adoption would be middleware. Tons of stuff exists in C++ for gaming engines to use, and so far there is no interop with Rust (or with any other language for that matter really). Libraries in C are better in this sense - you can use them from Rust. SDL is a good example.

Sure, but this only applies to projects that start from scratch. And besides, you're underestimating the effort and the risk of dumping existing code bases and know-how in any organization larger than a single developer.

I don't doubt that Rust is a nice programming language though.

View this comment - View article - View full comments

Quoting: jasondaigotyping in a nickname of your choice and using an email adresse of your choice will not harm you in any way if they sell it later because they already have my email adresse from amazon or netflix or whatever.

It's not our emails or personal details we're talking about, but anything we write or say using their services. You know, content, whether it's public or private. It's okay if that doesn't bother you personally.

View this comment - View article - View full comments