Quantifying Lag / Shaking / Rendering Ability

YSFlight addon development, questions, tutorials, & more!
Post Reply
User avatar
decaff_42
Staff
Staff
Posts: 3667
Joined: Sat Oct 29, 2011 7:23 pm
Favorite Aircraft: SR-71 Blackbird
Location: Eastern United States
OS: Mac OSX
Has thanked: 732 times
Been thanked: 1535 times
Contact:

Quantifying Lag / Shaking / Rendering Ability

Post by decaff_42 » Fri Mar 01, 2019 11:01 pm

Title kinda says it all.

What are the ways we can quantify how "bad" lag or shaking is or how hard YSFlight is working to render a map or airplane?

FPS seems like a highly relative measure as it can very widely between users and seems to largely depend on hardware.
Check out my website YSDecaff for all my tutorials and addon releases.
Visit my GitHub page for Python codes: https://github.com/decaff42?tab=repositories

YSFlight Addon Database - Find links to nearly every addon made for YSFlight!
Submit Addon To Database

User avatar
waspe414
Staff
Staff
Posts: 1403
Joined: Thu Feb 10, 2011 9:35 pm
Favorite Aircraft: Kiowa, Mitten, Hornet
Location: Canada
Has thanked: 137 times
Been thanked: 392 times

Re: Quantifying Lag / Shaking / Rendering Ability

Post by waspe414 » Sat Mar 02, 2019 1:22 am

I can't speak to the others, but I just did some tests to quantify distance shaking:
By my math, YS has 24 binary bits of floating point precision. This means just visible shaking (roughly 1cm precision) occurs beyond 80 miles from map center. See the following table:
Image

For more information regarding the specifics of floating point precision, see viewtopic.php?f=285&t=8625&p=98882
Actual UltraViolet
Image Image
Image
I stole your turnip. Now you must come and defend your honour. ~ Hank Green

User avatar
waspe414
Staff
Staff
Posts: 1403
Joined: Thu Feb 10, 2011 9:35 pm
Favorite Aircraft: Kiowa, Mitten, Hornet
Location: Canada
Has thanked: 137 times
Been thanked: 392 times

Re: Quantifying Lag / Shaking / Rendering Ability

Post by waspe414 » Fri Apr 30, 2021 4:36 pm

Some data about the render limits for the three executables:
This is performance on my computer (Ryzen 2600, GTX1660) with a 400,000 face model. Windows 2015ver.

Image

Image

D3d: 64 FPS, OGL1: 11 FPS, OGL2: bounces between 55 and 61 FPS
OGL1 runs entirely on a single CPU core, maxing out at 20% utilization. D3D seems to run more on one core, but uses all. OGL2 doesn't seem to have a CPU preference. D3d and OGL2 use the GPU, with D3d's utilization being much smoother, which reflects in the framerate stability.

With a 273MB DNM (2.7 million faces), when the visual file is loaded, YS uses up to 1.3GB of RAM then crashes. Whether that's a DNM size cap or a total RAM cap I'm not sure, but we're not likely to hit that number any time soon.
Actual UltraViolet
Image Image
Image
I stole your turnip. Now you must come and defend your honour. ~ Hank Green

Post Reply

Who is online

Users browsing this forum: Google [Bot] and 5 guests