While i appreciate the pixeled genre, i cannot understand why one should buy one of that games, when he can play tons of similar abandonware.
https://en.wikipedia.org/wiki/List_of_commercial_video_games_released_as_freeware

View this comment - View article - View full comments

Oh man, i played it in the past via wine.
This game is so soporific!
Not going to play it again... meh!

View this comment - View article - View full comments

Quoting: liamdaweJust because you don't agree with the method

-BIG EDIT-
Sorry Liam, i completely missed that the first time i read the article.
"This does not include cache (which can differ from machine to machine), just the actual RAM being used."

My apologies

View this comment - View article - View full comments

Quoting: liamdaweSince Linux memory management is quite complicated at the best of times, this was a simple test using system monitors to check total listed RAM use. Going through virtual, shared, cache and so on is a bit out of our scope and current knowledge.

Quite the opposite!
Not knowing if the tool you used to measure memory usage includes the buffers and the caches makes the whole article pointless.

Anyway, anybody concerned about desktop memory usage, should really avoid KDE:
https://www.youtube.com/watch?v=K3nbY0xNykA

View this comment - View article - View full comments

Woo, that's too much for me and my knees, i'm still playing Grid Autosport :D

View this comment - View article - View full comments

libstrangle seems really great, thank you!

View this comment - View article - View full comments

Quoting: [email protected]An important point to note is that if you enable FCP, you might want to disable in game vsync. You'll encounter performance hits that can be pretty massive. In game vsync is no longer necessary.

Not quite right, on contrary, you may waste GPU/CPU cycles trying to render more frames than the monitor would allow; if the game has no vsync logic enabled, it is probably completely unaware of the monitor refresh rate, so it will render as fast as it can, and that could lead to jerkyness because the couple [compositor+monitor refresh] is not synced to game frames.

Indeed, one thing i noticed with compositors that do vsync (*AND* vsync is disabled in games) is that motion is jerky/jumpy in games (it is still smooth in movies because the fps is limited by the movie itself).

The workaround for that is:
Given "C" a compositor that provides a working vsync (nvidia forcefullcompositionpipeline, kwin with tearing prevention on, compton with vsync enabled and so on):

* If the game provides a working vsync, enable it and disable "C"

*If the game provides a non working vsync, enable it and leave "C" enabled; this is needed because even if you got tearing with the Game's non-working vsync option turned on, it will still be useful, because it limits the framerate to the monitor refresh rate; this helps "C" to stay in sync with the frames -> provide a smooth gameplay.

I've tested that on trine 2 and grid autsport.

My current setup is as follows:
Desktop Use:
- KDE/Plasma, compositor enabled but with "tearing prevention" disabled
- ForceFullCompositionPipeline enabled.
- vsync disabled in mpv (framerate is limited anyway by the movie)

Gaming:
- KDE/Plasma compositor completely disabled (to gain some fps)
but with frame limiter set to 75 (because my monitor uses 75hz).
Do that in ~/.config/kwinrc, add MaxFPS=75 in the "[Compositing]" section.
- Vsync option in game enabled
- If the games has a working vsync -> ForceFullCompositionPipeline disabled.
- If the games has a non-working vsync -> ForceFullCompositionPipeline enabled.

All the switches are bound to shortcuts alt-shift-f12 and alt-shift-f11
alt-shift-f12 comes with kdekwin and completely disables the compositor
alt-shift-f11 is bound to the following:
> cat ~/scripts/nvidia.compositionpipeline.switch.sh 
#!/bin/bash
killall aosd_cat
if nvidia-settings -t -q CurrentMetaMode|grep 'ForceCompositionPipeline=On' &>/dev/null ; then
    ~/scripts/nvidia.compositionpipeline.disable.sh &
    echo "FFCP=OFF" | aosd_cat -n "Sans Bold 15"  -x 0 -y 0 -p 0 -t 0 -b 255 -s 255 -d 10 -R yellow  -u 5000 &
    echo "FFCP=OFF" | aosd_cat -n "Sans Bold 15"  -x 0 -y 0 -p 2 -t 0 -b 255 -s 255 -d 10 -R yellow  -u 5000 &
        else
    ~/scripts/nvidia.compositionpipeline.enable.sh &
    echo "FFCP=ON" | aosd_cat -n "Sans Bold 15"   -x 0 -y 0 -p 0 -t 0 -b 255 -s 255 -d 10 -R "#99ccff"  -u 5000 &
    echo "FFCP=ON" | aosd_cat -n "Sans Bold 15"   -x 0 -y 0 -p 2 -t 0 -b 255 -s 255 -d 10 -R "#99ccff"  -u 5000 &
fi
###########
> cat ~/scripts/nvidia.compositionpipeline.disable.sh 
#!/bin/bash
sh -c "nvidia-settings --assign CurrentMetaMode=\"$(nvidia-settings -t -q CurrentMetaMode |tr -d "\n"|sed 's/.*:://'|sed 's/^ *//;s/ *$//'|sed "s/CompositionPipeline=On/CompositionPipeline=Off/g")\""
###########
> cat ~/scripts/nvidia.compositionpipeline.enable.sh 
#/bin/bash
sh -c "nvidia-settings --assign CurrentMetaMode=\"$(nvidia-settings -t -q CurrentMetaMode |tr -d "\n"|sed 's/ViewPortIn=/ForceFullCompositionPipeline=On, ViewPortIn=/g'|sed 's/.*:://'|sed 's/^ *//;s/ *$//')\""
Hitting a shortcut is faster than opening the nvidia's control panel, and the aosd_cat command is useful because it show the current FFCP (ForceFullCompositionPipeline) state.

View this comment - View article - View full comments

Grid Autosport.
I really enjoied playing it hours and hours with a thrustmaster steering wheel and pedals, till my knees started to hurt for days, damn.

View this comment - View article - View full comments

Love the music

View this comment - View article - View full comments

What bundle? Humble monthly?

Anyway, i get no music nor sound effects from the demo. just the voice speaking.

View this comment - View article - View full comments