Open Sagez opened 1 month ago
The version range you provide has 1 server-side change and 1 client-side change that could affect performance but versions are compatible.
Can you check old server + new client and the opposite and tell which configuration has the issue? Please also provide the encoder configuration you are using.
I did roll back on both client and server together. something with both same version client/server here my config.json i normally use. config.json tho I hadn't change the configure at all along with changing apk/server versions.
I tested: old server + new client -> perfect fine. visual doing fine. yet spot tiny hiccup on blitted and displayed but cpu. new server + old client -> perfect fine, visual doing fine.
as the result i did ran without basalt for speed up compiling however with basalt it seem smooth it out. i guess. yesterday I did retry run with both new server and client after reboot my PC and wireless router. my thoughts was like.. It was random out of blue. so what do you think?
as it started as using 1.8 scale on client latest along with latest server however i tested with 1.6 scale. It ran smooth but slight spike like before i show to you. at last.. the network status got mess up.
I tried a revert of the commit that I think is breaking client on branch test/issue-116. The apk will be generated shortly in https://github.com/WiVRn/WiVRn/actions/runs/10536745192
Tested with that test/issue-116, same configures yet still noticed cpu spikes random, however still have similar issue when network went off chart. tho i find it interesting when i try screenshot, cpu spike up to 10-12
I used 90hz 1.8 scale with quest pro start the software and wait for few min then this show up. I used this version "apk-982a2557ef23bcc5850b00394ddc179acf93a87a" however i roll back to this. "apk-540f83bcec244682af55f569b3c18daecf9bc9df" everything is normal.
[Edit] I check with debug version it seem smooth out, maybe just release version part.