
We've launched our beta access portal on @ahodzil so you can test DMM for Blender without needing a manual signup process anymore! :3 Link in the post below, enjoy the trailer in the meantime:

:3 | Energysaving for software: ahodzil.com | Next-gen interactivity: cavia.site

We've launched our beta access portal on @ahodzil so you can test DMM for Blender without needing a manual signup process anymore! :3 Link in the post below, enjoy the trailer in the meantime:

I was completely unprepared that this would do numbers... X'3 Sorry I can't reply to everynyan but I am working on the next release launch of DMM4Blender, which is very skoro. TwT)/
In 2011 while at EA I worked on this kind of "strand based"-hair rendering that GTA6 is using. Too bad EA decided against using it for the games I had intended for it to be used for... Feels weird to have worked on this technology 15 years ago. TwT

Since people were asking about how it is to implement, I made this post:
Regarding the implementation: This is technically close to cloth physics with shapematching, so not that hard to execute in real-time (it was done before 2010 too). Transparency is the only demanding aspect, but can be LOD'd to a tolerable degree.

In 2011 while at EA I worked on this kind of "strand based"-hair rendering that GTA6 is using. Too bad EA decided against using it for the games I had intended for it to be used for... Feels weird to have worked on this technology 15 years ago. TwT

Van Buren is now running natively on 64bit! I had to migrate to newer granny3d library, remove DirectMusic dependency (only referenced in unused code) which was removed from modern Windows SDK, and then fix a lot of address truncation caused by code that only accounted for 32bit

I am so tired of every day war propaganda by unelected psychopaths who want people like me to die for their entertainment in a battle for nothing. This has to end.

I just reported all Norwegian media as supporters of war and dehumanisation of Russians based on unsubstantiated propaganda and mouthpieces. The only thing this will expose is a bunch of undeserving retards who will never go to the frontlines but expect others to do so for them.

Kevin Cloud created the palette for Q1. Most of the colors were selected during the time much of the design centered around an Aztec theme. I can’t remember why we didn’t change it. I created some if not all the Q2 palette. Unfortunately I cant remember why I chose that palette at the moment.

He was such a tech-optimist, but up until the mid-2000s it was hard not to be. TwT)7
“I like to rehearse for an optimistic future because why not rehearse for the best performance possible?” -Syd Mead, 1992


Carmack is really close here, but I think his reasoning is a bit limited. The distance is not unidirectional. A 0.2 pixel has twice the distance from full darkness relative to a 0.1 pixel, but a 0.98 pixel also has twice the distance from full brightness relative to a 0.99 pixel.
Both NeXT and 3DFX tried to “do the right thing” with color spaces, and it wound up generally making them look worse than competing options. I didn’t really understand it properly until years later. It is natural to think that a pixel with a value of 1.0 is emitting twice the photons as a pixel with a value of 0.5, so you can do the obvious linear math to calculate partial pixel coverage, blending a foreground over a background, or interpolating between colors in a texture. If displays are “linear”, that is correct. NeXT and 3DFX were much closer to linear than other contemporary displays. NeXT had crossover from the deep graphics understanding at Pixar, and 3DFX had the SGI heritage. They did this intentionally. If you have 10+ bits per channel like the professional rendering systems, linear displays are The Right Thing. Unfortunately, NeXTStation Colors were 4 bits per channel and 3DFX was 5 or 6 bits per channel, and there… it was not the right thing. Human eyes aren’t linear intensity sensors. We mostly register relative changes in intensity, so we can tell the difference between 0.01 and 0.02 as a huge doubling, while 0.99 to 1.00 is almost imperceptible. This distribution of intensities is often referred to as the “gamma” of the display system, but the actual curves like sRGB are a bit more complicated. If you only have a small number of discrete pixel values, you definitely don’t want to spread them evenly from 0 to 1! If you do, you will have good precision in the brights, but very stark “intensity bands” in the dark colors. If everything was authored specifically for 3DFX, you would still have the fundamental problem with the dark bands, but more accurate blending and filtering. The problem was that artists made all of their textures in paint programs on conventional non-linear displays, so when they were drawn by 3DFX cards, they got the characteristic “washed out color” look. You can mathematically correct textures for differences in display gamma, but I didn’t really understand the issue back in the glQuake days, and we were so enthralled by the absolute performance of 3DFX that the color fidelity didn’t get as much attention as it should have. Even today, tons of games don’t properly handle gamma across their textures and render targets. High resolutions and 24 bit color masks most of it, but you still see it in some slight shimmerings in high contrast textures and edges.

If text can be automatically made longer and summarised then maybe text is no longer a good way to express matters.

Blender's UX past 2.79 dropped off such a gigantic cliff it's still not hit the bottom. Why do I have to watch videos to find out how to display vertex and triangle counts, which were on by default in 2.79? And why do I have to click a trillion times for for simple operations?


When everyone can compete, competition ceases to exist.
The "missing out" sentiment is dangerous I think. Beginners and small indies will think they have to use AI now, use it, and never learn anything, including how to properly check the output.
