I do think people--especially beginners & overworked contractors--sometimes abuse 3D models, just extracting lines or rasterizing the layer instead of redrawing it appropriately for the piece.
But that just results in a piece that's kinda ugly, not unethical haha
But that just results in a piece that's kinda ugly, not unethical haha
December 13, 2025 at 11:27 PM
I do think people--especially beginners & overworked contractors--sometimes abuse 3D models, just extracting lines or rasterizing the layer instead of redrawing it appropriately for the piece.
But that just results in a piece that's kinda ugly, not unethical haha
But that just results in a piece that's kinda ugly, not unethical haha
2019 God of War's Dual Depth implementation. I still have a few issues to solve 🤔
CPU Performance is 💩because Niagara's RigidMeshCollision interface lack a much needed rasterizing function, so I had to re-implement it from scratch in BPs for this proof of concept😅
CPU Performance is 💩because Niagara's RigidMeshCollision interface lack a much needed rasterizing function, so I had to re-implement it from scratch in BPs for this proof of concept😅
December 8, 2025 at 12:23 AM
2019 God of War's Dual Depth implementation. I still have a few issues to solve 🤔
CPU Performance is 💩because Niagara's RigidMeshCollision interface lack a much needed rasterizing function, so I had to re-implement it from scratch in BPs for this proof of concept😅
CPU Performance is 💩because Niagara's RigidMeshCollision interface lack a much needed rasterizing function, so I had to re-implement it from scratch in BPs for this proof of concept😅
… pretty sure I could print it on my wide format in 3/4 passes. It looks between 9-12 feet wide and about 60 feet long. That’s not even a full roll of paper nor a full set of ink cartridges. Line up the seams, tape them down. Rasterizing an image for that kind of print is simply not that hard.
October 21, 2025 at 5:26 AM
… pretty sure I could print it on my wide format in 3/4 passes. It looks between 9-12 feet wide and about 60 feet long. That’s not even a full roll of paper nor a full set of ink cartridges. Line up the seams, tape them down. Rasterizing an image for that kind of print is simply not that hard.
Interesting semantics around OpenGL viewports, pixel indexing with gl_FragCoord is global, and does not adjust to the viewport base point... needed to pass in the zero point to get the gl_FragCoord interface I'm used to
![Each pixel's fragment shader also receives the first two values passed to glViewport as a uniform... by subtracting the zero point from gl_FragCoord, you get the expected pixel indexing within the viewport... [0..viewport size-1]
This is important for constructing an orthographic projection matrix for the first layer of impostors. It works very similarly to Chorizo, https://jbaker.graphics/writings/chorizo.html, rasterizing a bounding box, then testing against the contained primitive in the fragment shader. But moving to an orthographic projection, you don't have an origin point at the viewer's location so a couple things needed to change.
So this first layer of Chorizo-style hybrid raster/raytrace impostors generates the atlas for the octahedral impostors... a bit of a hat on a hat, but we're having fun with it.](https://cdn.bsky.app/img/feed_thumbnail/plain/did:plc:7udmbazkzmihjho24kb3zgl5/bafkreicwhtpdh3lahiad45okdnrznfm6ptdy6cx4o2psbkxw6yvlhhtxvq@jpeg)
April 29, 2025 at 2:56 PM
Interesting semantics around OpenGL viewports, pixel indexing with gl_FragCoord is global, and does not adjust to the viewport base point... needed to pass in the zero point to get the gl_FragCoord interface I'm used to
back in college the older system programmer objected to replacing the old'n'busted `lprNG` printing system with CUPS, claiming you couldn't do proper page accounting, that the only way to do it would involve rasterizing the pages and counting them, which would let him cheat accounting by […]
Original post on infosec.exchange
infosec.exchange
September 5, 2025 at 9:46 PM
back in college the older system programmer objected to replacing the old'n'busted `lprNG` printing system with CUPS, claiming you couldn't do proper page accounting, that the only way to do it would involve rasterizing the pages and counting them, which would let him cheat accounting by […]
Software Rasterizing Hair Discussion
Software rasterizing hair - Scthe's blog
Using software rasterization to render hair. Covers point projection, quad software rasterization and segment-space calculations.
www.sctheblog.com
September 5, 2024 at 10:20 AM
Software Rasterizing Hair Discussion
Nah I can tell you for a fact that won't help. Drawing requires low latency input, which isn't possible with higher than normal CPU usage. Turning off hardware acceleration for a 2K screen increases CPU usage by a fuckload. GPUs are made for rasterizing graphics, turning it off causes more problems.
July 22, 2025 at 4:03 AM
Nah I can tell you for a fact that won't help. Drawing requires low latency input, which isn't possible with higher than normal CPU usage. Turning off hardware acceleration for a 2K screen increases CPU usage by a fuckload. GPUs are made for rasterizing graphics, turning it off causes more problems.
I don't have shaders, it's a fixed-function pipeline CPU rasterizer! But yes, I'm doing exactly what GPUs do - rasterizing in groups of 2x2 pixels in order to compute the derivatives.
October 30, 2024 at 12:21 AM
I don't have shaders, it's a fixed-function pipeline CPU rasterizer! But yes, I'm doing exactly what GPUs do - rasterizing in groups of 2x2 pixels in order to compute the derivatives.
🚀 Efficiency and quality
• Surface rendering → fast but miss fuzz.
• Volume rendering → high capacity but not efficient.
• We skip sorting, skip empty space and samples number (3‑9) that are found by rasterizing smooth, lightweight meshes → quality approaching 3DGS, much higher rendering efficiency.
• Surface rendering → fast but miss fuzz.
• Volume rendering → high capacity but not efficient.
• We skip sorting, skip empty space and samples number (3‑9) that are found by rasterizing smooth, lightweight meshes → quality approaching 3DGS, much higher rendering efficiency.
May 5, 2025 at 1:00 PM
🚀 Efficiency and quality
• Surface rendering → fast but miss fuzz.
• Volume rendering → high capacity but not efficient.
• We skip sorting, skip empty space and samples number (3‑9) that are found by rasterizing smooth, lightweight meshes → quality approaching 3DGS, much higher rendering efficiency.
• Surface rendering → fast but miss fuzz.
• Volume rendering → high capacity but not efficient.
• We skip sorting, skip empty space and samples number (3‑9) that are found by rasterizing smooth, lightweight meshes → quality approaching 3DGS, much higher rendering efficiency.
Very nice! Does it rely on rasterizing out the geometry? If so how does it handle two faces in the same pixel? (Like if you zoom out a bunch so everything overlaps in screen space)
November 19, 2024 at 6:51 PM
Very nice! Does it rely on rasterizing out the geometry? If so how does it handle two faces in the same pixel? (Like if you zoom out a bunch so everything overlaps in screen space)
Yeah, it's a bad design on that front, on top of charging a massive premium this generation for a 'AI' processor with some display outputs slapped on that only has a small actual increase in rasterizing speed over the prior gen. The extra VRAM of the 5090 looks nice for VRC but I'll pass this round.
February 20, 2025 at 10:39 PM
Yeah, it's a bad design on that front, on top of charging a massive premium this generation for a 'AI' processor with some display outputs slapped on that only has a small actual increase in rasterizing speed over the prior gen. The extra VRAM of the 5090 looks nice for VRC but I'll pass this round.
In the back of my mind, I'm worried that I spent all this time wrapping my head around rasterizing polygons, only for the whole world to rug-pull me and say "haha, now we're moving to radiance fields".
March 25, 2025 at 3:37 AM
In the back of my mind, I'm worried that I spent all this time wrapping my head around rasterizing polygons, only for the whole world to rug-pull me and say "haha, now we're moving to radiance fields".
Zum Dezemberstart haben wir die GPU-Rangliste Rasterizing aktualisiert: 38 GPUs im Benchmark-Vergleich.
Hier geht es zur Rangliste mit Archiv 📊: www.pcgameshardware.de/Grafikkarten...
Hier geht es zur Rangliste mit Archiv 📊: www.pcgameshardware.de/Grafikkarten...
Grafikkarten-Rangliste 2025: 38 GPUs im Benchmark-Vergleich
Update: Grafikkarten-Rangliste 2025 mit Nvidia-, AMD- und Intel-Grafikkarten: Benchmark-Übersicht mit allen wichtigen Grafikchips.
www.pcgameshardware.de
December 1, 2025 at 11:26 AM
Zum Dezemberstart haben wir die GPU-Rangliste Rasterizing aktualisiert: 38 GPUs im Benchmark-Vergleich.
Hier geht es zur Rangliste mit Archiv 📊: www.pcgameshardware.de/Grafikkarten...
Hier geht es zur Rangliste mit Archiv 📊: www.pcgameshardware.de/Grafikkarten...
i'm a cross stitcher so anything to do with pixels or rasterizing is always intriguing... art + math!
December 13, 2024 at 10:07 PM
i'm a cross stitcher so anything to do with pixels or rasterizing is always intriguing... art + math!
Interesting. I'm taking a vector approach for my roads, expanding them fractally on zoom, and then rasterizing them on demand.
It has some issues currently mostly due to mismatches between the vector representation and the underlying landscape (e.g. near the coast), but nothing insurmountable.
It has some issues currently mostly due to mismatches between the vector representation and the underlying landscape (e.g. near the coast), but nothing insurmountable.
December 3, 2024 at 12:03 PM
Interesting. I'm taking a vector approach for my roads, expanding them fractally on zoom, and then rasterizing them on demand.
It has some issues currently mostly due to mismatches between the vector representation and the underlying landscape (e.g. near the coast), but nothing insurmountable.
It has some issues currently mostly due to mismatches between the vector representation and the underlying landscape (e.g. near the coast), but nothing insurmountable.
Word of the Day: Rasterize
With DeftPDF, rasterizing ensures your graphics look perfect on any screen—making document work easier than ever.
Try it at www.deftpdf.com
#DeftPDF #PDFConversion #ProductivityTools #pdf #pdfeditor #convertpdf
With DeftPDF, rasterizing ensures your graphics look perfect on any screen—making document work easier than ever.
Try it at www.deftpdf.com
#DeftPDF #PDFConversion #ProductivityTools #pdf #pdfeditor #convertpdf
October 31, 2025 at 10:00 AM
Word of the Day: Rasterize
With DeftPDF, rasterizing ensures your graphics look perfect on any screen—making document work easier than ever.
Try it at www.deftpdf.com
#DeftPDF #PDFConversion #ProductivityTools #pdf #pdfeditor #convertpdf
With DeftPDF, rasterizing ensures your graphics look perfect on any screen—making document work easier than ever.
Try it at www.deftpdf.com
#DeftPDF #PDFConversion #ProductivityTools #pdf #pdfeditor #convertpdf
OpenGL virgins be like: glEnable(GL_DEPTH_TEST); glDepthFunc(GL_ALWAYS); glVBAVBOPeePeePooPoo...
CPU-rasterizing Chads: uint32_t[width*height]
CPU-rasterizing Chads: uint32_t[width*height]
October 27, 2024 at 1:23 PM
OpenGL virgins be like: glEnable(GL_DEPTH_TEST); glDepthFunc(GL_ALWAYS); glVBAVBOPeePeePooPoo...
CPU-rasterizing Chads: uint32_t[width*height]
CPU-rasterizing Chads: uint32_t[width*height]
Finished my #ttrpg playtest materials & sent them out, but the process revealed I don't know what rasterizing does.
Partial rasterization: Text on every other page looked fuzzy.
Full rasterization: File blew up to 68Mb but didn't fix the problem.
No rasterization: 1Mb & perfectly legible! 🤔
Partial rasterization: Text on every other page looked fuzzy.
Full rasterization: File blew up to 68Mb but didn't fix the problem.
No rasterization: 1Mb & perfectly legible! 🤔
January 20, 2025 at 5:52 AM
Finished my #ttrpg playtest materials & sent them out, but the process revealed I don't know what rasterizing does.
Partial rasterization: Text on every other page looked fuzzy.
Full rasterization: File blew up to 68Mb but didn't fix the problem.
No rasterization: 1Mb & perfectly legible! 🤔
Partial rasterization: Text on every other page looked fuzzy.
Full rasterization: File blew up to 68Mb but didn't fix the problem.
No rasterization: 1Mb & perfectly legible! 🤔
yes thats true but they think rasterizing requires the steady hand of a paid graphic designer so the corner got cut
May 28, 2025 at 2:17 AM
yes thats true but they think rasterizing requires the steady hand of a paid graphic designer so the corner got cut
So I'm working on lowering the files sizes, too, by deleting any leftover sketch layers, layers or folders that are still there but toggled off for the final image, rasterizing any shapes and applying any quickmasks. In some cases, I literally just merged whole panel background folders.
💀💀💀
💀💀💀
September 10, 2025 at 1:17 PM
So I'm working on lowering the files sizes, too, by deleting any leftover sketch layers, layers or folders that are still there but toggled off for the final image, rasterizing any shapes and applying any quickmasks. In some cases, I literally just merged whole panel background folders.
💀💀💀
💀💀💀
Yesss! I've been using Resolve & Affinity and very happy with both!
Except for how Affinity handles sprite-art. Actually sucks real bad with preserving them when you try to scale and how it handles rasterizing.
Except for how Affinity handles sprite-art. Actually sucks real bad with preserving them when you try to scale and how it handles rasterizing.
November 7, 2025 at 5:06 AM
Yesss! I've been using Resolve & Affinity and very happy with both!
Except for how Affinity handles sprite-art. Actually sucks real bad with preserving them when you try to scale and how it handles rasterizing.
Except for how Affinity handles sprite-art. Actually sucks real bad with preserving them when you try to scale and how it handles rasterizing.
There's a lot more work before I can roll this out to users. But rasterizing this using FreeType + HarfBuzz as opposed to using the browser's canvas means that I can get deterministic rendering across browsers/OSes.
June 3, 2025 at 10:10 PM
There's a lot more work before I can roll this out to users. But rasterizing this using FreeType + HarfBuzz as opposed to using the browser's canvas means that I can get deterministic rendering across browsers/OSes.
I’d expect quadtree or grid yeah, I remember reading lots of articles about them for 2D games.
Maybe you could do something clever with rasterizing the enemies into an ID buffer or something and sampling the pixels for hits.
Maybe you could do something clever with rasterizing the enemies into an ID buffer or something and sampling the pixels for hits.
November 10, 2025 at 12:56 AM
I’d expect quadtree or grid yeah, I remember reading lots of articles about them for 2D games.
Maybe you could do something clever with rasterizing the enemies into an ID buffer or something and sampling the pixels for hits.
Maybe you could do something clever with rasterizing the enemies into an ID buffer or something and sampling the pixels for hits.
if u see this quote with the energy u bring to blue sky
September 16, 2025 at 4:54 AM
if u see this quote with the energy u bring to blue sky
forgot the label printer doesn't do grayscale but just 1-bit black/white so now i'm exporting to 1-bit png and correcting the rasterizing decisions i don't like by hand in gimp.
'cos i'm neurotypical
'cos i'm neurotypical
December 21, 2023 at 11:15 PM
forgot the label printer doesn't do grayscale but just 1-bit black/white so now i'm exporting to 1-bit png and correcting the rasterizing decisions i don't like by hand in gimp.
'cos i'm neurotypical
'cos i'm neurotypical