"everything is fine" getting an omnigraph going and seems we have some problems with the lite version of our digital twin errrr model for the workshop we are preparing
1
87
About one year ago. I was remote desktop-ing into the robot and trying to figure out the limits of my depth camera. Pre-lidar for the GOAT RACER was tough times. Keep grinding, you will make it better!
4
127
would be a lot more without: github.com/dietrichgebert/po… i think
1
1
89
Astra and Fable cooked this up in KiCAD and LTSpice these past few weeks. Will see if it works in the real world. Is funny we are trying to lower our price and we go and design and fab a custom pcb. The world has changed quite a bit since the last time I exported gerbers from eagle cad.
5
9
226
Rob retweeted
Love seeing what people build with the AR4.
This Florida Tech student team turned one into a chess-playing cobot, and the 3D sim mirrors every move it makes.
Junfu Cheng / Florida Tech ECE 4242
Rob retweeted
pro marketing tip: bring this GR3 to any tradeshow and watch the crowds form. #Robotics
3 hours → 10 minutes 🏎️
@CryptideRL now provisions every GOAT Racer 3 18× faster on Avocado OS. Same base on every car, ~400 KB policy updates over the air, days without a reboot.
Sim to real on @NVIDIARobotics Jetson.
peridio.com/use-cases/crypti… #Robotics
Bring back the man in the leather jacket! Everyone else will be a poor substitute. Here I am at Maryhill loops road about 8 years ago
4
81
google analytics dashboard... i just want to see who is referring me and my search terms. i think i might have to get off this platform. i'm too dumb for it
1
1
58
Rob retweeted
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.












