View Issue Details

IDProjectCategoryView StatusLast Update
0000707NoesisGUIC++ SDKpublic2019-01-15 17:09
Reportermovra Assigned Tojsantos  
PrioritylowSeverityminor 
Status resolvedResolutionfixed 
Summary0000707: Fullscreen XamlPlayer big difference in GPU usage with MSAA
Description

When running certain XAMLs in fullscreen XamlPlayer there's a big difference in GPU usage between the MSAA modes.

Steps To Reproduce
  • Load TicTacToe.xaml or MasterMind.xaml in XamlPlayer.
  • Disable any animations.
  • Maximize the XamlPlayer window.
  • When switching from MSAA 2x to MSAA 4x or MSAA 8x the GPU usage will jump from about 1% to 70%.
Attached Files
TicTacToe-1920x1148-MSAA8x.png (187,356 bytes)   
TicTacToe-1920x1148-MSAA8x.png (187,356 bytes)   
TicTacToe-1920x1148-MSAA4x.png (172,317 bytes)   
TicTacToe-1920x1148-MSAA4x.png (172,317 bytes)   
TicTacToe-784x562-MSAA8x.png (92,057 bytes)   
TicTacToe-784x562-MSAA8x.png (92,057 bytes)   
PlatformAny

Activities

jsantos

jsantos

2015-10-08 18:25

manager   ~0003085

Yes, what you are observing is normal because MSAA demands more bandwidth to the GPU so the time is moved there.

Could you elaborate more about this ticket?

Thanks for your feedback!

movra

movra

2015-10-19 23:23

reporter   ~0003122

Hm, I didn't get an e-mail about your reply.

I just retested the TicTacToe example in XAML Player. See screenshots.

MSAA 4x Maximized: 1.6 ms
MSAA 8x Windowed: 0.58 ms
MSAA 8x Maximized: 66.59 ms (sometimes it jumps to 133 ms)

See, there's a huge jump.

There should be enough video memory available. With MSAA 8x Maximized it sits at about 820 MB out of 1 GB. After closing XAML Player it's 383 MB.

But there's something else strange going on. Sometimes the MSAA 4x Maximized jumps to 33 ms and stays there until switching the AA or resizing the window.

jsantos

jsantos

2019-01-10 14:08

manager   ~0005391

Last edited: 2019-01-10 14:09

So many changes in XamlPlayer since this report. :)

Did you have the chance to test the latest version of NoesisGUI? In these new versions you need to indicate the multisample level at the command line (--samples 8)

movra

movra

2019-01-10 23:40

reporter   ~0005392

Hey jsantos. I just tested 2.2.0b5. Looking good so far!

Of course, since my bug report in 2015 I have upgraded some hardware. From an i7-920 and a 460 GTX to a Ryzen 5 2600 with 1070 GTX.

Also the example TicTacToe.xaml has changed and MasterMind.xaml is removed.

So it is not really a fair comparison. But with Palette.xaml at 8x MSAA 1080p 60 fps, GPU time is max 2.39 ms.

jsantos

jsantos

2019-01-15 17:09

manager   ~0005395

Those are good numbers I think, you will probably get better GPU numbers if you disable vsynv (--vsync 0).

So many optimizations happened since the last version you tried. :)

Issue History

Date Modified Username Field Change
2015-08-16 16:52 movra New Issue
2015-08-17 18:53 jsantos Assigned To => jsantos
2015-08-17 18:53 jsantos Status new => assigned
2015-10-08 18:25 jsantos Note Added: 0003085
2015-10-08 18:25 jsantos Status assigned => feedback
2015-10-19 23:08 movra File Added: TicTacToe-1920x1148-MSAA8x.png
2015-10-19 23:08 movra File Added: TicTacToe-1920x1148-MSAA4x.png
2015-10-19 23:08 movra File Added: TicTacToe-784x562-MSAA8x.png
2015-10-19 23:23 movra Note Added: 0003122
2015-10-19 23:23 movra Status feedback => assigned
2018-11-01 02:14 jsantos View Status public => private
2019-01-10 14:08 jsantos Status assigned => feedback
2019-01-10 14:08 jsantos Note Added: 0005391
2019-01-10 14:08 jsantos View Status private => public
2019-01-10 14:08 jsantos Platform => Any
2019-01-10 14:08 jsantos Note Edited: 0005391
2019-01-10 14:09 jsantos Note Edited: 0005391
2019-01-10 23:40 movra Note Added: 0005392
2019-01-10 23:40 movra Status feedback => assigned
2019-01-15 17:09 jsantos Status assigned => resolved
2019-01-15 17:09 jsantos Resolution open => fixed
2019-01-15 17:09 jsantos Note Added: 0005395