The Khronos Group is opening the call for submissions for the Real-Time Shading Symposium 2027, taking place February 11-12, 2027 at Howest University of Applied Sciences in Kortrijk, Belgium. It runs immediately after Vulkanised 2027, so you can make a single trip for both.

The symposium brings together shader programmers, technical artists, researchers, shading language and compiler developers, engine developers, and hardware vendors to talk about practical shading workflows, production pain points, and emerging techniques.

Topics of interest include:

• Shading language design
• Neural graphics and AI-assisted shading
• Production workflows and shader authoring tools
• Debugging and profiling tools
• Portability and performance optimization
• Open source tools and frameworks

Submitting is simple: send a short talk proposal through the online form. New speakers are welcome, and talks may build on previous work as long as they include updates or enhancements. This is an in-person event, and at least one presenter per accepted talk is expected to attend. Vulkan-specific talks may be a better fit for Vulkanised, and you can submit to both events, though a talk can only be accepted into one.

Proposals are due Sunday, October 25, 2026, and notifications go out the week of November 9.

Submit your proposal and learn more: [https://www.khronos.org/events/real-time-shading-symposium-2027?utm_medium=social&utm_source=reddit&utm_campaign=Real_Time_Shading_CFP&utm_content=events

I wanted match-style gems that behave like liquid, so there are no sprites at all. The whole board is one full-screen fragment shader on iPhone, and every gem is a signed distance field.

• Same-coloured neighbours get a "liquid bridge" shape between them, then a smooth union inside each colour and a hard union between colours. That's what makes blobs fuse without different colours smearing together.
• The light bars from special gems are global shapes that every gem melts into as they pass.
• For speed, the CPU sorts gems and bridges into 1×1 cell bins each frame. A ray only tests the cell it's crossing, and each march step is clamped to the cell exit so nothing in the next cell gets skipped.
• It ray-marches at a reduced resolution that adapts to the GPU's frame time, then upscales, aiming for 60 fps.

Happy to go into any of it. The game is Glissa, free on iOS with no ads: https://apps.apple.com/gb/app/glissa/id6821629542

Crash pc chargement shaders Dune Awakening version Xbox sur PC

Bonjour,

J'ai un souci avec le jeu Dune Awakening, je l'ai installé via l'édition du gamepass sur mon pc mais lorsque je lance le jeu ma première fois que je souhaite y jouer dans la journée au moment d'arriver au chargement des shaders mon pc plante et redémarre instantanément.(La fois d'après ça ne le fait pas et je peux jouer sans soucis pendant des heures)

J'ai désinstallé et réinstaller le jeu, fait un nettoyage des fichiers de celui-ci, mis a jour tout ce que je pouvais, baissé la qualité du jeu car il était en ultra et je l'ai mis en élevé ( j'ai même testé intermédiaire) mais rien n'y fait le problème persiste.😔

J'ai un Ryzen 7 5800 X, 32 go de ram, une RTX 4060 ventus 2x black 8g OC, un disque dur 100go pour le systeme puis un second d'1to pour les jeux.

Si quelqu'un est susceptible de m'apporter son aide et surtout une solution svp

I've been a software developer for 3..4 years now. Graphics programming always looked so cool and yet so unreachable. With everyone using ai everywhere these days, I decided to reach for a fresh air and started the book of shaders. And I love it! I do use ai to revisit the math behind it and the stuff I've forgotten since my university days. But I love the feeling of using my technical skills to create art. I've never mixed code with visual arts before. I've been playing the guitar for 14 years, but never did I let code into that world either. This feels like an exciting way to do that.

Just wanted to share my feelings on the topic 😁❤️

Hi — question about shader behaviour in Unity 6 / OpenXR on Quest 3, Vulkan, Single Pass Instanced.

My scene is built entirely at runtime. Every mesh currently gets `new Material(Shader.Find("Sprites/Default"))`. In a player build that renders solid magenta or nothing at all — only the camera clear colour comes through. Switching to Multi Pass renders the same materials fine.

Two things I've been told so far, and I'm trying to separate them: 1. The shader is being stripped because nothing in a scene or Resources references it. 2. Sprites/Default has no SPI variant, so even forcing it into the build would not fix the SPI case.

If I write my own minimal unlit texture shader and ship it with a referenced material, what does it actually need to work correctly under Single Pass Instanced? Is `#pragma multi_compile_instancing` plus the usual stereo macros (`UNITY_SETUP_INSTANCE_ID`, `UNITY_INITIALIZE_VERTEX_OUTPUT_STEREO`) enough for a simple textured quad/sphere, or is there more to it?

Also curious whether anyone has confirmed the "Sprites/Default has no SPI variant" claim directly, or seen a case where Always Included Shaders alone fixed this in SPI.

Thanks for any pointers.

Hey I was trying to figure out how color ramps worked all I know it that is if you have a valve you can use that value to pick a color off the color ramp that’s about it and how to make them in substance designer to use in unity shader graph for stylized VFX.

Any help is appreciated :)