![]() ![]() If you are using Mac but you don't have chrome canary is almost the same command: Open -a "Google Chrome Canary" -args -disable-gpu-vsync -disable-frame-rate-limit If you are using Mac you can open chrome canary with vsync disabled with this command in a terminal: Go to chrome://flags and switch on Hardware acceleration Now I recommend not to disable acceleration: This is a big problem they must solve before rolling out the base product, as it needs to work out of the box else people will dismiss it.Īnother tip, disabling vsync when you open chrome:Īnd using chrome canary (with step of vsync above): ![]() I think the client or chrome has a to get a balance between the priority it puts on sending and receiving. That ties in with the improvement people getting when lowering the mouse polling rate. I think the stadia client or chrome is not handling sending packets very well, especially when there are lots of updates to send (such as moving the mouse). Moving with the mouse, stuttering graphics, high lag (maybe 400+ ms).Moving with keyboard, very fluid and good graphics and slightly increased lag when firing (but still pretty low, maybe 150ms).Sanding still, good graphics and very low lag when firing a gun (On my DChromebook (through a USB Ethernet port) I get this (tested in Destiny 2): I can run Stadia on a high end laptop with no problems (after disabling mouse acceleration). ![]() I think you are right about the the problem that some people are seeing with desktop gaming is the way that the Stadia client is running under Chrome. This is my concern because I want Stadia also to play games in desktop with keyboard and mouse, not only with Stadia very interesting post. I think that google has to provide a better client for stadia in desktop environments and don't to be the users whose has to deal with hw acceleration flags, mouse pointer lock and external tool setups and whatever. I think that is because the NVIDIA has a desktop client that can deal with GPU options and behaviors to make a better experience, I don't know exactly but I think that the client (Chrome) is the main problem because is not optimized yet. I don't want to make silly comparisons and controversy about game streaming services, but, I'm trying in my Geforce Now account with the same game (Destiny 2) and same net conditions and the mouse works smooth and this problems are inexistents. (This is the better option for me, no input lag and very low mouse stuttering (but still there), is sad that this option cannot be reproduced in MacOS and Linux)
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |