Sabitlenmiş Tweet
Xor
24.9K posts
Xor
@XorDev
Shader Artist. Building https://t.co/kaSRjYGvsp
🇺🇸 Katılım Kasım 2014
964 Takip Edilen39.8K Takipçiler
@DrewPavlou It’s exactly where my mind has been for 10 years. Researching, debating, imagining, designing, painting, writing, programming with my team, to show how Ai will completely reshape civilisation this century, in the most grounded way possible.
Surreal to see it start happening.
English
Imagine showing this to someone 10 years ago
Disclose.tv@disclosetv
NOW - Pope XIV says the church and Anthropic, will work together to "find the way for humanity, in this time of artificial intelligence."
English
Xor retweetledi
Xor retweetledi
If you're a graphics programmer and haven't looked into reverse-Z depth buffers yet, I highly recommend implementing them in your engine.
Massively improved depth precision at effectively zero cost:
developer.nvidia.com/content/depth-…
English
Xor retweetledi
For those who hesitate: install Codex or Claude Code.
Have a literaly genie that can script anything on the fly in your terminal, work on your files, interpret pictures, understand your voice, code anything you want, use a browser to do stuff on your behalf, and connect to any app to carry entire tasks across them. All just by talking to it. And the $20/month starter is quite generous.
That's it. Do it. Stop ruminating, stop waiting, stop hesitating, stop delaying, stop denying. Just do it. This is how computers are used by power users in 2026, and for everyone else in 2027.
English
Designed this as part of the SpaceXAI website overhaul. And I'm kind of obsessed with it.
English
"Fire"
vec2 p=(FC.xy*2.-r)/r.y,R;p*=1.-vec2(.5*p.y,.5/(1.+p*p));p.y-=t;float F=11.,N,d;for(R.x=F;F<50.;F*=1.2)p+=.4*sin(F*dot(p,sin(++R))+6.*t)*cos(R)/F;N=snoise2D(p*4.);d=length(p+vec2(0,t+.5))/.3-++N;N+=snoise2D(p*8.);o=tanh(++N/(.5-.1*N+max(d/.1,-d)*abs(d)/.3)/vec4(1,3,9,1));
Français
#glsl vec2 p=(FC.xy/r-.5)*2.5;float h=.7,a=.6,f=2.,u=fract(t*.111);for(float i=0.;i++<9.;a*=.5,f*=2.){vec2 q=p*f+vec2(sin(.7*t+i),-u*f*6.3);h+=mix(snoise2D(q),snoise2D(q+vec2(0,f*6.3)),u)*a;}float E=exp(1.5*h-3.*length(p*vec2(3,1)));o=vec4(pow(E,.3),pow(E,1.5),pow(E,4.)*.3,1);
Xor@XorDev
"Fire" vec2 p=(FC.xy*2.-r)/r.y,R;p*=1.-vec2(.5*p.y,.5/(1.+p*p));p.y-=t;float F=11.,N,d;for(R.x=F;F<50.;F*=1.2)p+=.4*sin(F*dot(p,sin(++R))+6.*t)*cos(R)/F;N=snoise2D(p*4.);d=length(p+vec2(0,t+.5))/.3-++N;N+=snoise2D(p*8.);o=tanh(++N/(.5-.1*N+max(d/.1,-d)*abs(d)/.3)/vec4(1,3,9,1));
Français
@XorDev Thanks, that's great Feedback!
Having some decals to break things up might help. I was also experimenting with No Rest for the wicked style rim highlights that could help distinguish silhouettes — but haven't be able to hit the right look yet.
English
Rendering / GI pipeline is finally coming together:
- sky visibility / PRT probes
- micro occlusion textures
- directional SSAO
English
Hurricane process.
Zero shader code written, all base layers in Unicorn. Lot's of craft went into this one.
Live demo: unicorn.studio/embed/bG5xs8kL…
English
@BrianBreiholz It could be tackled either way. When you look at a distance, it's hard to distinguish shapes from texturing. Shadows help a little, but gray on gray can only tell you so much.
The lighting helps a lot, but still highlights texture over form. Large scale AO could help
English
@XorDev Thanks! Do you mean lighting/material-wise or just on the asset front (i.e. more varying textures)?
English
Xor retweetledi
People underestimate the power of shaders! 😎
Most environments look artificial cause the surfaces feel flat and lifeless
So, inspired by Forza Horizon, I created this shader to add depth and atmosphere!
Completely changing how flat surfaces are perceived
Coming soon on Patreon
#VRChat #Shader
English
Xor retweetledi
Hard agree on this. Exactly what I've been doing with File Pilot from the start. Although I have very few of those, and they're mostly single headers.
Mitchell Hashimoto@mitchellh
Fork your dependencies, trim them to only your use case, never update unless it breaks for your users. I’ve been vocal about this for 10+ years. I’ve always said that updating is way riskier than latent bugs (which can be tracked and CVEs monitored). If you are updating a dependency, it’s on you to analyze every single commit in the full transitive set of dependencies. If you dont see anything compelling, dont update! I remember at HashiCorp once in awhile an engineer would try to update a dep or replace a DIY lib with an external one and id always ask “show me the commit we need.” Dont update for the sake of it. Feeling pretty swell about this mentality with all the supply chain attacks happening.
English