Invalid Session Id received with PS4 Pro

[wiiaboo]

Renderer window opens up and eventually shows an error popup with "Chiaki session has quit: Unknown Ctrl Error".

Using 1.0.0 Windows build as released here in Github.
Trying to remote play with a PS4 Pro PS4-095 in LAN. Changing resolution or frame rate did nothing.

Verbose log only contains additional Session Response Header content, which was successful.

Log:

[2019-08-20 19:06:13:952952] [I] Logging to file C:/Users/xxx/AppData/Roaming/Chiaki/Chiaki/log/chiaki_session_2019-08-20_19-06-13-952952.log
[2019-08-20 19:06:13:952952] [I] Chiaki Version 1.0.0
[2019-08-20 19:06:13:958958] [I] Controller 0 opened: "PS4 Controller"
[2019-08-20 19:06:13:958958] [I] Starting session request
[2019-08-20 19:06:14:020020] [I] OpenGL initialized with version "3.2.0 NVIDIA 430.86"
[2019-08-20 19:06:18:477477] [I] Trying to request session from 192.168.1.90:9295
[2019-08-20 19:06:18:482482] [I] Connected to 192.168.1.90:9295
[2019-08-20 19:06:18:484484] [I] Sending session request
[2019-08-20 19:06:18:490490] [I] Session request successful
[2019-08-20 19:06:18:501501] [I] Starting ctrl
[2019-08-20 19:06:18:506506] [I] Connected to 192.168.1.90:9295
[2019-08-20 19:06:18:506506] [I] Sending ctrl request
[2019-08-20 19:06:18:515515] [I] Ctrl connected
[2019-08-20 19:06:18:559559] [W] Received Ctrl Message with unknown type 0x5
[2019-08-20 19:06:18:559559] [W] Received Ctrl Message with unknown type 0x6
[2019-08-20 19:06:20:535535] [E] Invalid Session Id received
[2019-08-20 19:06:23:501501] [E] Ctrl has failed, shutting down
[2019-08-20 19:06:23:501501] [I] Ctrl requested to stop
[2019-08-20 19:06:23:502502] [I] Ctrl stopped
[2019-08-20 19:06:23:502502] [I] Session has quit

[thestr4ng3r]

Those unknown ctrl messages are expected currently, the real error is [E] Invalid Session Id received. Can you please try this build and post the log again? https://ci.appveyor.com/api/buildjobs/yndtuvksbhiu4wng/artifacts/Chiaki.zip

[MuchiMuchiPink]

I get the same error on Linux with a regular PS4.

[wiiaboo]

With that build remote play worked fine.

1. Tried connection without logging in PS4.: Failed to connect
2. After logging in PS4 locally, connecting via remote play in 360p30: worked but forgot to plug in the controller, so I connected it with the stream still on and it worked instantly.
3. After changing to 1080p60 and connecting the controller to PC
   On the third one I tried using the menu, but it looked as though there was too little bitrate and some frame drops, didn't try playing.

[wiiaboo]

Also, the wakeup didn't work, but I'm connected through WLAN both from my PC and PS4, so that might not be expected to work.

[thestr4ng3r]

Thanks, those logs were very helpful. Binaries for Version 1.0.1 with a fix should be up soon. It's interesting that the PS4 sends InvalidSessionId, but streaming still works.

Low Bitrate is expected currently and something I plan to investigate further. Wakeup should theoretically work, but I didn't do much testing on Windows, so I might just have to try it myself.