EPTPTR coming back - Page 2
| Forum Index > BW General |
|
A.Alm
Sweden534 Posts
| ||
|
Poegim
Poland266 Posts
On May 16 2020 21:49 Bakuryu wrote: can we just get tec27 to get hired by blizzard to work on SCR? this would be a win-win situation for everybody. You have my sword. | ||
|
TelecoM
United States10700 Posts
| ||
|
SchAmToo
United States1141 Posts
On May 16 2020 05:14 tec27 wrote: What is even more perplexing is that they've seemingly spent the last few months writing a brand new rendering backend for Windows users (who was asking for that or even complaining about performance outside of the CEF bug and other things that have nothing to do with the rendering technology?), and even more perplexing is that they wrote one for macOS too. . Mmmmm Windows performance on non-game screens is pretty bad. I've noticed memory hogging and a ton of bugs on Windows. | ||
|
tec27
United States3702 Posts
On May 19 2020 07:23 SchAmToo wrote: Mmmmm Windows performance on non-game screens is pretty bad. I've noticed memory hogging and a ton of bugs on Windows. Thing is, switching to a new rendering backend isn't going to change that at all. It may even make it worse, given that they seem to devote a lot less energy to actually ensuring things work before they push them out to everyone at this point. All the non-game UIs (and the in-game observer UI) are handled via CEF. CEF is an embeddable version of Chromium, which renders via Skia. In a "real" browser, or when CEF is managing an actual window, Skia supports hardware acceleration (e.g. using DirectX or OpenGL to render graphics with your graphics card, rather than software implementations), but CEF does not support hardware acceleration when rendering in "offscreen mode", which is how SC:R uses it. Thus, all CEF is doing here is rendering out to an image via your CPU, telling SC:R what pixels have changed, and letting SC:R deal with putting those pixels on the screen. This isn't a hard operation for a graphics card to do, and there's really nothing complex about the code they'd have to do it, regardless of graphics API. There's no real room for further optimization by choosing a different rendering API, as the bottleneck is not there. Very likely, memory problems and bugs you are seeing are due to things that they aren't working on at all here: wasteful allocations and initialization of things that aren't needed, not following or paying attention to best practices when it comes to developing web UIs, inefficient communication between UIs, spinning up far more expensive background processes than is actually needed, etc. This is like painting your car a different color because you see it's been getting bad fuel efficiency. | ||
|
MeSaber
Sweden1235 Posts
| ||
|
TelecoM
United States10700 Posts
Grant Davies @ forums 15m This is live now. Have a great weekend! | ||
|
LML
Germany1781 Posts
On May 22 2020 06:43 GGzerG wrote: Apparently the PTR is live, but I don't see the option to join it. Blue post on StarCraft.com forums 15min ago. Grant Davies @ forums 15m This is live now. Have a great weekend! ![[image loading]](https://i.imgur.com/ImSNiRb.png) | ||
|
TelecoM
United States10700 Posts
| ||
|
tec27
United States3702 Posts
| ||
|
TelecoM
United States10700 Posts
| ||
|
TelecoM
United States10700 Posts
| ||
|
QuadroX
386 Posts
On May 22 2020 08:11 tec27 wrote: The version of CEF is still unchanged, which seems absurd since this was they thing they've been trying to roll forward for months now. Seems like an important piece to test as well, given how many problems it caused before. How do you know? I noticed huge performance boost on PTR, menus are ligheting fast and now SC:R supports my Intel HD Graphics 620 which was a pixelated mess before the update. | ||
|
TelecoM
United States10700 Posts
On May 23 2020 01:58 QuadroX wrote: How do you know? I noticed huge performance boost on PTR, menus are ligheting fast and now SC:R supports my Intel HD Graphics 620 which was a pixelated mess before the update. Yea, it is working amazingly well. I can't wait for them to push this through, can finally stream again, and don't have to buy a new computer it seems! | ||
|
LG)Sabbath
Argentina3024 Posts
| ||
|
tec27
United States3702 Posts
On May 23 2020 01:58 QuadroX wrote: How do you know? I noticed huge performance boost on PTR, menus are ligheting fast and now SC:R supports my Intel HD Graphics 620 which was a pixelated mess before the update. You can compare the versions of libcef.dll in the PTR and non-PTR versions and see they are they same: ![[image loading]](https://i.imgur.com/2qRpzz3.png) Thus, this update still hasn't been rolled forward. I had never actually gone and looked up what Chrome version that corresponds to, but apparently it's from April 2015, which... oof. | ||
|
QuadroX
386 Posts
| ||
|
tec27
United States3702 Posts
The patch doesn't seem to contain many other changes from further inspection. The UI scripts look to be the same other than a few things renamed here and there, nothing functionally different as far as I can see. | ||
|
fazek42
Hungary438 Posts
I imagine that's because the display is 60 Hz -- however, and I'm not sure if this is placebo or not, but now both modes feel (equally) a little choppy, whereas SD at 200 FPS seemed to be smoother previously (and HD unplayable). SD graphics is still looking terrible, so no improvements there. | ||
|
tec27
United States3702 Posts
On May 24 2020 02:44 fazek42 wrote: On a macbook pro late 2015 model, with Catalina, FPS in HD is increased to 60 FPS (which is great! I think I used get around 39 FPS), but SD is now also capped at 60 FPS. I imagine that's because the display is 60 Hz -- however, and I'm not sure if this is placebo or not, but now both modes feel (equally) a little choppy, whereas SD at 200 FPS seemed to be smoother previously (and HD unplayable). SD graphics is still looking terrible, so no improvements there. Is vsync on perhaps? Or maybe enforced by your graphics driver for directx or something? The settings don't save/share between PTR/non-PTR so that may just be something you have set differently between the two (although I don't think vsync defaults to on so who knows, really) | ||
| ||
