My raspberry pi 3 B+ configuration


I have bought a rpi 3B+ only for testing parsec, because 5ghz wifi looked promising. I didn't found much information about how to configure it, so i give my configuration here for the community.
Because I'm lazy, i chose raspbian over raspbian lite, to simplify wifi and bluetooth connection.

My rpi and my parsec server are both connected to my router with 5ghz wifi. Bandwidth between them is 70 MB/s (measured with iperf) and latency is 1-2ms. Could be better on ethernet, but is not an option for me.
Installation of parsec on raspbian is explained here:, no change for the 3B+. Don't forget to increase the gpu memory size. I personally use 320MB.

during first run, i noticed a lot of lag and input lag, gaming was not really an acceptable experience, has it was showed on parsec youtube channel, but demo are performed with the rpi 3B not 3B+.
The cpu of the 3b+ is different from the previous rpi, and some default value for it in config.txt have changed as well. rpi 3b+ cpu throttle its speed since it reach 60°C. during parsec session, I was hitting this threshold (it's summer here), even with a heatsink, and it was making parsec stuttering.

To avoid that, you have to edit /boot/config.txt and add: temp_soft_limit=70.
You could also use force_turbo=1, in order to reduce frequency throttling, but not sure if it is necessary as the cpu is not working hard during parsec session.
To improve h264 decoding performance, you could also overclock part of GPU (at your own risk). I used those settings gathered on internet without noticeable problem:

over_voltage=2 (Be careful to have a good PSU and usb cable for your RPI3B+)

Then you reboot, and experience should be better.

my .parsec/config.txt is:


As stated in the installation guide, playing using raspbian desktop create some artifact once in a while.
To avoid that, you could start parsec instead of LXDE at boot using a script and a xsessions profile.

the script (/usr/local/bin/startmyparsecsession)

#wait for the network

until $(curl --output /dev/null --silent --head –fail; do
if [ ${attempt_counter} -eq ${max_attempts} ];then
echo "Max attempts reached"
exit 1

sleep 5

exec /usr/bin/parsec server_id=?????? #your ID session

the xsessions profile (/usr/share/xsessions/parsec.desktop)
[Desktop Entry]
Comment=boot directly in parsec

Change to perform also in /etc/lightdm/lightdm.conf
session-cleanup-script=/usr/bin/sudo -u pi /usr/bin/startlxde-pi
# Fallback to lxde session when parsec quit

Now, when I boot my rpi, parsec is automatically connected, performance is good, and dualshock 4 via bluetooth works without issue too.
I'm very happy with Parsec on this raspberry pi 3B+, I played FFXV all afternoon on it and forgeted that I was on streaming session. I have few stuttering, induced by wifi jitter, but is playable and enjoyable for casual game on TV.





  • HELLO!


    Can you please check the my topic and try to help?

    About your topic... thanks a lot for the info, i'm not a "linux" expert. my setup is very similar to yours.

    i use in my ~/.parsec/config.txt also:

    encoder_min_qp = 5

    It's a parsec team sugestion.


    About gaming, I also use a dualshock 4 via bluetooth with ds4drv and run games like "witcher 3" in 50-60 fps with no lag or glitches. 

    PS: connected by cable, not wifi.


  • Thanks for the encoder_min_qp, as I understand it, it reduce compression strengh, and make Parsec use more bandwidth.

    As a result on a raspberry with a good connection, the quality is greatly improved and the gameplay is no more stuttering.

    For your other question, I will reply in your thread.

Please sign in to leave a comment.

Didn't find what you were looking for?

New post