Page 1 of 1

XAML Vector vs Rasterized Image Performance Question

Posted: 15 Feb 2022, 18:45
by stonstad
After the initial load is there a performance difference between immediate mode rendering of vectorized XAML vs rasterized PNG? Does Noesis construct and display XAML so that successive renders are competitive with rasterized rendering?

Re: XAML Vector vs Rasterized Image Performance Question

Posted: 15 Feb 2022, 21:10
by jsantos
Vectors are not converted to images internally. They are rendered per-frame. In general, Noesis is fast enough to avoid the over-head of an image but we are working on an extension to control this kind of caching because sometimes it is useful to convert a complex path to an image.

Re: XAML Vector vs Rasterized Image Performance Question

Posted: 16 Feb 2022, 19:25
by stonstad
Vectors are not converted to images internally. They are rendered per-frame. In general, Noesis is fast enough to avoid the over-head of an image but we are working on an extension to control this kind of caching because sometimes it is useful to convert a complex path to an image.
Rasterizing paths and effect output (i.e. drop shadows) is desirable from a performance perspective. Perhaps it increases memory utilization.

I would like to convert all of my images to vectorized XAML, but I'm hesitant to do so because I don't know what the FPS cost will be....