Welcome to the Onshape forum! Ask questions and join in the discussions about everything Onshape.
First time visiting? Here are some places to start:- Looking for a certain topic? Check out the categories filter or use Search (upper right).
- Need support? Ask a question to our Community Support category.
- Please submit support tickets for bugs but you can request improvements in the Product Feedback category.
- Be respectful, on topic and if you see a problem, Flag it.
If you would like to contact our Community Manager personally, feel free to send a private message or an email.
Low frame rates
bill_daniels
Member Posts: 278 ✭✭✭
in General
A problem has suddenly appeared with my system. As you can see below, the FPS is just 24.5. Nothing in the hardware has changed and the problem surfaces on all browsers. Nothing other than Onshape seems to be affected.
.
.
0
Comments
That message is a warning - it is saying that because of the low refresh rate, any performance numbers could be error prone. The error in reporting for 30Hz is twice that for a 60Hz refresh rate. End of story - it's a warning. This does not mean that you will (necessarily) have bad performance.
Next - why are you only getting 30Hz?
Depending on the power of your graphics card and the number of pixels being pushed, it may not be able to refresh all of them at 60Hz. Got a 4K monitor? What about an 8K monitor? Think just how many bazillion pixels that it! Paul has a 4K monitor driven off his macbook. The monitor refreshes at 30Hz and his laptop screen at 60Hz. That's it. The performance test will run on the laptop screen and not the monitor.
I hope this clears things up
The performance test is designed to maximize the information we can provide, while minimizing the amount of time we take to run the test.
The performance test is structured as follows:
1. We render a bunch of triangles,
2. Measure the FPS
3. If the FPS stays above 45, we increase the number of triangles and repeat step 1 - 3
The 45 FPS is an arbitrary number to avoid putting unnecessary load on the browser. Some systems refresh the browser at 30 FPS. In the past, this would cause the test to stop early, because the very first measurement was well below 45 FPS. This would result in an incorrect report that only a small number of triangles that could be rendered by the system.
To avoid producing misleading results, we start by creating a few empty frames. We are trying to gauge the maximum refresh possible for the browser by rendering empty frames. If we detect that the empty frames are below 60 FPS, we avoid running any further tests.
The refresh rate provided by the browser can change over time. Sites like UFO Tester performs a longer test to get a more consistent result. Given that people are hitting false positives for slow refresh rates, this indicates we can do a better job finding the balance between speed and accuracy.
That's it, nothing bad is happening and you don't need to do anything!!
Just trying to eliminate possible causes
I am not sure if it's the last update either that might be the source of the problem. On their end, everything works great. I suspect the problem is a latency issue and I cannot improve that any more than I already have on my end.