Viewing profile — mindbrix

Ruffle is cool. From pixel inspecting the demo, it looks like they are using triangle fans with stencil & cover + MSAA, which was how I started!

The depth buffer is used for opaque path interiors.

My original target was iOS, so this was unavailable. I did experiment with their algorithm, but 4x MSAA was slow and had poor quality compared to Core Graphics, which was my refere…

My email address is in every file ;-)

Drawing cached renders in quads is how Core Animation works, but they do not scale well. You are ultimately limited by the CPU. Rasterizer enables a fully-animated canvas @ 60fps.

The longer answer is that using straight-edged geometry to represent curves is a resolution-dependent operation, e.g. a full screen circle may need to be flattened to an 80-sided p…

Good question and answer ;-)

My reference renderer has been Core Graphics. If it looks like CG I assume it's OK - and if it's not OK I'm in good company ;-) You can switch between CG and Rasterizer in the demo…

Thanks, you imagine correctly ;-) The current version uses Metal. I haven't even considered GPU ports yet, as my methodology is to get it working well on one platform first. For si…

Thanks. I couldn't really say without doing proper research.

Rasterizer excels at animation and complex scenes, e.g. 2D CAD documents. The original inspiration was Flash, as I love innovative design tools. Flash 1.0 could easily be used by d…

The Rasterizer algorithm handles self-intersecting paths without issue. Removing them requires expensive and complex computation geometry.

I can't really answer that in detail yet. I suspect Rasterizer will be faster for complex scenes.

No magic, just 10+ years of experimentation and optimisation.

Linear at present.

The "traditional graphics pipeline" approach was chosen to maximise the platforms Rasterizer could run on, as GPU compute support at the time was patchy. Compute is now more univer…

Winding numbers are easy to explain, but hard to compute efficiently: https://en.wikipedia.org/wiki/Winding_number

The core problem is path winding: https://en.wikipedia.org/wiki/Winding_number Paths can be any size, and the problem is hard to parallelize. GPUs like stuff broken into small regu…

Slug is primarily designed for text rendering. Vello is general purpose, like Rasterizer, but is based on GPU compute. Rasterizer uses the 'traditional' GPU pipeline. Performance n…

No. I'm hoping someone else will do that ;-)

None of that yet. The underlying SVG library, nanosvg, is very simple with no text support. The first priority was to solve paths to pixels efficiently, including text (50,000 glyp…

Hi Steve. Yes, it is! 10+ years in the making.

Thanks for the feedback. I will work on one.

I've been working on this problem on and off for over 10 years. AMA ;-)