![]() Deck has haptic feedback, dont know how much different it is from the rumble.Lag. After some more trying, I found that the rumble works. It worked good so far now.ĭeleting qtaudio_windows.dll help remedi the sound. I really2 like the (almost) instant connection, and the difference of 2w tdp is bearable I think, so I now used chiaki at 7w tdp. ![]() I upped this to 2600mhz, and now I could play chiaki at 720p 30hz resolution with 7w tdp and 1080p 30hz with 10w tdp (with no flicker at all). I tried again, and it seems it was because I limit the cpu to 2400mhz. Too bad, I really2 like the (almost) instant connect of chiaki, but I'd still use official remote play on my onexplayer because of this flickering and tdp problem.īut steam deck's steam os seems to function on the higher tdp so this might not be a problem ? I dont know if installing windows with lower tdp would work better. as using 5w tdp, my onexplayer could last 4.5-5 hours remote playing (with official app), while with 10w tdp, it would only last like 2.5-3 hours (with chiaki), and even with flicker. I have tried 720p and 1080p resolution, and 30 and 60 fps, and even tried 1000 bitrate (the default is auto 15000 it said) but I dont really see any improvement, and the flicker still there. Just fyi, trying to down the tdp to 5w and the flicker goes crazy, it's like the screen always flicker, and the good screen only last a second sometimes. I might need to up the tdp again for it to really function without this flicker, but I dont want to do it. I usually using 5w tdp using official remote play, but with chiaki, I need to use 10w tdp for the app to function properly, even then I still experience some flicker (the screen would go like grey yellow for a second, before back to good again). On the downside, chiaki needs more tdp to work good. This is much better and things that I missed from the official remote play. I mapped the touch pad function to pressing start button a long time (with rewasd), but chiaki, weirdly, wouldnt recognized this, but instead, it has mapped the touch screen of onexplayer as the touchpad. I think it is becauses the official remote play needs to check online here and there on the opening that makes it very slow when opening it. It made the official remote play like snail. I like how chiaki could connect almost instantly to the ps5. Sound function the same, control feels just as responsive. The graphic is around the same, none is better, but if I have to choose, official remote play's graphic is a bit better, mainly because it seems chiaki is heavier and suffering from the tdp (more on this below). It has all feature that official remote play has. ![]() I have been able to use chiaki as a full remote play ps5 app. I found how to do full screen yesterday by using F11. You can now double-click your Console in Chiaki's main window to start Remote Play. To do this on a PS4, simply go to: Settings -> Remote Play -> Add Device, or on a PS5: Settings -> System -> Remote Play -> Link Device. To register a Console with a PIN, it must be put into registration mode. You will likely never have to do this process again. Simply run it in a terminal and follow the instructions. ![]() A Python 3 script which does this is provided in scripts/psn-account-id.py. This ID seems to be a unique identifier for a PSN Account and it can be obtained from the PSN after logging in using OAuth. Starting with PS4 7.0, it is necessary to use a so-called "AccountID" as opposed to the "Online-ID" for registration (streaming itself did not change). You will need two more pieces of information to do this. You will then need to register your Console with Chiaki. To do so, click the "+" icon in the top right, and enter your Console's IP address. If your Console is on your local network, is turned on or in standby mode and does not have Discovery explicitly disabled, Chiaki should find it.
0 Comments
Leave a Reply. |