-
-
Notifications
You must be signed in to change notification settings - Fork 950
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
UI Rendering Slowness (Sync Point?) #455
Comments
@DevJarmo Try throwing in more UI elements in the world. Also try moving your camera closer and farther away from those elements, if you can. |
Hmm, on the game I was working on that had this problem, it seems to have been fixed since xenko v 3.0.0.3. I just tested again today with the profiler and on latest 3.1 beta, and I don't get the same issues I had before. FPS maintains around 120fps. I wonder if it was a vulkan issue maybe? I tried setting my project to vulkan (my default in 3.0), but have weird issue with gamepad not being found, so game throws exception. Don't want to dig any further on it though. |
@xen2 for reference, same scene on my system (i7 920 + R9 390) also a release build |
My spec's are: 8th Generation Intel® Core™ i7-8750H Processor I have no problems with UI while plugged in (Laptop), though after profan had the issue I saw it on a number of other systems during a demonstration/test. I am also able to repo the issue when I run on battery power and my CPU is rate limited. Fairly certain the issue is on the CPU side. During the demonstration, In all cases, I could just toggle off the scroll viewer and/or game UI and the update time would generally drop down below 16 ms... the boxes would have no problems with 3d rendering, shadows, or particle effects. @xen2 Interesting thing, I have a couple of older Alienware Alpha I3's with Nvidia's and they do not have the issue (at least not impacting the update rate above 16ms). Could the issue be Xenko UI rendering with Radeon graphics cards? I believe the systems in the demo which were having slowness may have also been Radeon, I will reach out and inquire and return with infos. |
Other systems that experienced this were: AMD FX6300 |
@xen2 as promised on my system (CPU: i7 920, GPU: R9 390) it generally oscillates between 7-8ms to 12ms, so.. yeah 👀 (sorry about the delay, more things got in the way) |
@profan can you check the UI on my fork to see if you experience the same problem with Vulkan? |
I have noticed some intermittent framerate issues, even on high end hardware. It's only happened once, but Xenko Studio game window was running at ~10fps for no reason on my machine, when it's normally closer to 100fps. Closing and opening the project fixed this, which suggests something intermittent. I wonder if this could be related. |
Release Type: Official Release
Version: 3.0 and 3.1
Platform(s): Windows
Describe the bug
UI Rendering on systems with slower processors (previous generations, a couple years old) but still very capable graphics cards experience frame rate/update rate loss when rendering Xenko UI. Toggling the UI off on these systems and the frame rate/update rate resumes to normal (or as fast as it can when running with the profiler). These are not significant UI implementations, a simple player name and HP bar player panel above a character and a kill log scroll viewer in the lower left of the screen (no greater than 8 entries).
Render groups 1-3 bypass the forward renderer and are rendered in their own single stage renderer or a shared renderer (both have been tested). Also tested with the default compositor, same results.
I've had another developer take a look at the implementations and the logic is sound, no unnecessary UI changes or updates per tick.
A number of things have been tested:
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Minimal UI shouldn't cause such a significant performance impact and limits release of the game.
Additional notes
If one of the engine developers are interested I can share out my game to them, however it includes all the binaries so will be at download.
Issue may also somehow be related to #101
The text was updated successfully, but these errors were encountered: