Package Details: parsec-bin 1:147_9-3

Git Clone URL: https://aur.archlinux.org/parsec-bin.git (read-only)
Package Base: parsec-bin
Description: Remotely connect to a gaming pc for a low latency remote computing experience
Upstream URL: http://parsec.tv
Keywords: parsec remote streaming
Conflicts: parsec
Provides: parsec
Submitter: sdellysse
Maintainer: E5ten (NanoDrive)
Last Packager: E5ten
Votes: 16
Popularity: 0.313132
First Submitted: 2017-08-10 02:44
Last Updated: 2018-09-19 05:01

Latest Comments

1 2 3 4 5 6 ... Next › Last »

erkexzcx commented on 2019-02-27 09:16

FYI: https://wiki.archlinux.org/index.php/Gaming#Remote_gaming

erkexzcx commented on 2019-02-24 23:04

!!!!! How to fix -7000 error !!!!!

Edit "~/.parsec/config.txt" and add "client_vsync = 0".

eduardo_amarall commented on 2019-01-09 15:16

@tadly But what you've said had nothing to do with the problem, and you said unpolitely. Let's end the discussion here...

tadly commented on 2019-01-09 14:35

You are very welcome.
At least I got you to dig for information that was already available instead of making others do it for you :)

eduardo_amarall commented on 2019-01-09 14:18

After digging around the internet I found that after installing the package "libvdpau-va-gl" to make the program work, I had to then unninstall the package "libva-vdpau-driver" that was causing conflicts. Only after that things worked fine.

PS. Thanks @tadly for the useless advice.

eduardo_amarall commented on 2019-01-09 13:53

@tadly but there is no client connected, as a matter of fact searching on the web fo this problem I found it is a problem with libva.

tadly commented on 2019-01-09 07:13

@eduardo_amarall did you ever bother reading the error message? I don't get how people can be this lazy sometimes sigh

Edit: To be slightly less of an ass I'll give you a hint.
"Maximum number of clients reached". What could that mean... hm...

eduardo_amarall commented on 2019-01-08 16:14

No matter if I try the daemon or the CLI version it always gives me " [2019-01-08 11:07:53 D] CMD.daemon_join [2019-01-08 11:07:53 D] CMD.app_cfg_get [2019-01-08 11:07:53 D] CMD.app_get_binary_info [2019-01-08 11:07:53 D] CMD.app_whitelist_get [2019-01-08 11:07:53 D] CMD.app_get_runtime_info [2019-01-08 11:07:53 D] CMD.app_server_get_clients [2019-01-08 11:07:53 D] CMD.app_approve_get_pending [2019-01-08 11:08:11 D] CMD.app_cfg_get [2019-01-08 11:08:12 D] CMD.app_get_binary_info [2019-01-08 11:08:12 D] CMD.app_get_binary_info [2019-01-08 11:08:18 D] CLI.server_id = 2611006 [2019-01-08 11:08:18 D] CMD.app_client [2019-01-08 11:08:19 D] CLI.net = BUD|::ffff:35.237.204.248|8000 [2019-01-08 11:08:19 D] CLI.client_x = 1920 [2019-01-08 11:08:19 D] CLI.client_y = 1080 [2019-01-08 11:08:19 D] CLI.renderer = opengl Maximum number of clients reachedFloating point exception (core dumped) "

tadly commented on 2019-01-07 07:13

@thisischrys check your ~/.parsec folder.
As of writing this, you should have parsecd-149-2.so. If you don't then start parsec as app-daemon (I still suspect this is the only way of updating the binary but I'm not sure).

To do this run /usr/bin/parsecd app_daemon=1.

If you already have the latest binary and it still doesn't work, you have to be more specific on the issue you're having.

thisischrys commented on 2019-01-06 23:52

Any got this working again? I tried a clean install, still no go.