XAML Vector vs Rasterized Image Performance Question
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
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
Rasterizing paths and effect output (i.e. drop shadows) is desirable from a performance perspective. Perhaps it increases memory utilization.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.
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....
Who is online
Users browsing this forum: No registered users and 5 guests