Conversation

Notices

1. Embed this notice
   :apa: スプリットショックウイルス † (splitshockvirus@mstdn.starnix.network)'s status on Saturday, 27-Apr-2024 15:40:59 JST :apa: スプリットショックウイルス †

   • かき@GNUsocialJP

   Hey man whatever this is that you're doing can you do that some other time.

   • ✙ dcc :pedomustdie: :phear_slackware: likes this.
   • Embed this notice
      (mint@ryona.agency)'s status on Saturday, 27-Apr-2024 15:40:57 JST 

     in reply to

     • CrunkLord420
     @crunklord420 @splitshockvirus What even happened to gallium-nine?
   • Embed this notice
     CrunkLord420 (crunklord420@clubcyberia.co)'s status on Saturday, 27-Apr-2024 15:40:58 JST CrunkLord420

     in reply to
     @splitshockvirus new csgo skins just dropped, need to compile shaders for hours.
     ✙ dcc :pedomustdie: :phear_slackware: likes this.
   • Embed this notice
     iced depresso (icedquinn@blob.cat)'s status on Saturday, 27-Apr-2024 16:15:49 JST iced depresso

     in reply to

     • CrunkLord420
     • gentoobro
     @gentoobro @crunklord420 @splitshockvirus usually the point of an ubershader is it does all of your shit so you aren't having to change shader programs during the render
   • Embed this notice
     gentoobro (gentoobro@gleasonator.com)'s status on Saturday, 27-Apr-2024 16:15:50 JST gentoobro

     in reply to

     • CrunkLord420

     @crunklord420 @splitshockvirus Things that complicated are seldom truly optimized.

     It's insane to have special shaders for each skin. There aren't that many ways you can make light reflect, even with oil-slick effects and such.

   • Embed this notice
     gentoobro (gentoobro@gleasonator.com)'s status on Saturday, 27-Apr-2024 16:15:51 JST gentoobro

     in reply to

     • CrunkLord420

     @crunklord420 @splitshockvirus What the fuck is in their shaders that takes so long? Mine compile in a couple seconds. Must be some sort of bloated middleware.

   • Embed this notice
     CrunkLord420 (crunklord420@clubcyberia.co)'s status on Saturday, 27-Apr-2024 16:15:51 JST CrunkLord420

     in reply to

     • gentoobro
     @gentoobro @splitshockvirus I don't know 100% but I assume it has to do with giant ubershaders full of compile-time ifdefs. Every new skin requires X number of minor variation shader recompiles. Every minor change requires you recompile every variation. It's just an ugly interdependence mess for the sake of run-time optimization.
   • Embed this notice
     iced depresso (icedquinn@blob.cat)'s status on Saturday, 27-Apr-2024 16:22:58 JST iced depresso

     in reply to

     • CrunkLord420
     • gentoobro
     @gentoobro @crunklord420 @splitshockvirus each shader change is a draw call, though, which is a scarce resource on PC.
   • Embed this notice
     gentoobro (gentoobro@gleasonator.com)'s status on Saturday, 27-Apr-2024 16:22:59 JST gentoobro

     in reply to

     • iced depresso
     • CrunkLord420

     @icedquinn @crunklord420 @splitshockvirus Yeah. I have one for GUI rendering. Whether you swap shader programs or not during rendering is not the point. (In CS they could swap shaders for the guns without much problem. There aren't many guns on screen at any given point in time.) The insane part is that they have special shader code for each skin, or even many skins.

   • Embed this notice
     gentoobro (gentoobro@gleasonator.com)'s status on Saturday, 27-Apr-2024 16:40:44 JST gentoobro

     in reply to

     • iced depresso
     • CrunkLord420

     @icedquinn @crunklord420 @splitshockvirus Draw calls are different. You need to have a shader bound already to issue a draw call. Shader changes go into the graphics queue, yes, but they aren't that scarce, and can be even cheaper if you do it carefully. Swapping the executable code is rather fast; reconfiguring the layout of the cache (uniforms) is the expensive part. In Vulkan you can carefully manage these costs independently. In OpenGL you can do some voodoo and the driver will probably hopefully maybe get it right. (Dunno about DirectX. Fuck Microshaft.)

     A modern game might have a dozen shader changes each frame just due to the render pipeline alone. The main thing is to not just change shaders willy-nilly between each model or primitive.

     On a side note, draw calls themselves aren't that expensive per-se. There can be some CPU overhead, but the main thing to remember is that the GPU is extremely pipelined and you want to let it crunch on as much data at one time as you can. You also don't want to cross the driver barrier too much with OpenGL, but that's a different story.

   • Embed this notice
     iced depresso (icedquinn@blob.cat)'s status on Saturday, 27-Apr-2024 16:40:44 JST iced depresso

     in reply to

     • CrunkLord420
     • gentoobro
     @gentoobro @crunklord420 @splitshockvirus a lot of modern games are also designed for a console first, where gpu interactions are cheap. this is partly why all of the ports run like shit, even the good ones, because the platforms they design for have cheaper state management.
   • Embed this notice
     iced depresso (icedquinn@blob.cat)'s status on Saturday, 27-Apr-2024 16:48:09 JST iced depresso

     in reply to

     • CrunkLord420
     • gentoobro
     @gentoobro @crunklord420 @splitshockvirus i would like to learn vulkan :ablobcatohlookaround: i was stuck on old GL for a very long time, esp. to be compatible with very old potato.
     
     now the discount 200$ mini pcs run vulkan, so its time to move on.
     :blobcathug: likes this.
   • Embed this notice
     gentoobro (gentoobro@gleasonator.com)'s status on Saturday, 27-Apr-2024 16:48:10 JST gentoobro

     in reply to

     • iced depresso
     • CrunkLord420

     @icedquinn @crunklord420 @splitshockvirus Consoles also usually have extremely fast main memory and hard guarantees about core scheduling. It's my understanding that most cross-platform games use some sort of rendering abstraction where they create a command list in their own format then translate it into whatever API is being used underneath. That sort of thing is extremely difficult to optimize for.

     As for my game, users will have the option of Vulkan or Vulkan. 😆

   • Embed this notice
     gentoobro (gentoobro@gleasonator.com)'s status on Saturday, 27-Apr-2024 16:51:05 JST gentoobro

     in reply to

     • iced depresso
     • CrunkLord420
     • :umu: :umu:

     @a1ba @icedquinn @crunklord420 @splitshockvirus Also, annoyingly, some GLSL compilers don't support line continuations, which makes using non-trivial macros difficult.

   • Embed this notice
     iced depresso (icedquinn@blob.cat)'s status on Saturday, 27-Apr-2024 16:51:05 JST iced depresso

     in reply to

     • CrunkLord420
     • :umu: :umu:
     • gentoobro
     @gentoobro @crunklord420 @splitshockvirus @a1ba sort of glad that GLSL type stuff is dead. SPIR docs might be excessively long but ime its often better to let the client send bytecode.
   • Embed this notice
     :umu: :umu: (a1ba@suya.place)'s status on Saturday, 27-Apr-2024 16:51:07 JST :umu: :umu:

     in reply to

     • iced depresso
     • CrunkLord420
     • gentoobro
     @icedquinn @crunklord420 @gentoobro @splitshockvirus isn't ubershader is just a single shader file compiled into multiple smaller ones by switching the macros (as GLSL allows C preprocessor)
   • Embed this notice
     mk (mk@mastodon.satoshishop.de)'s status on Saturday, 27-Apr-2024 16:55:48 JST mk

     in reply to

     @splitshockvirus

     Hey man. whatever this version of htop is, can you link it here right now, please?

   • Embed this notice
     iced depresso (icedquinn@blob.cat)'s status on Saturday, 27-Apr-2024 16:56:40 JST iced depresso

     in reply to

     • CrunkLord420
     • :umu: :umu:
     • gentoobro
     @gentoobro @crunklord420 @splitshockvirus @a1ba we didn't have the option of sending bytecode in the past* and you handed GLSL to the graphics driver at runtime. Pray the driver feels like giving you useful error messages. :neocat_googly_shocked:
     
     * there were some extensions but who the fuck used those
   • Embed this notice
     gentoobro (gentoobro@gleasonator.com)'s status on Saturday, 27-Apr-2024 16:56:41 JST gentoobro

     in reply to

     • iced depresso
     • CrunkLord420
     • :umu: :umu:

     @icedquinn @crunklord420 @splitshockvirus @a1ba You still write GLSL. It's a more strict version, but basically the same. You run it through a compiler (glslang) at build time. Maybe one day I'll put my tooling up on notabug. SPIR-V is for shipping, kind of like x86 machine code is for shipping.

   • Embed this notice
     iced depresso (icedquinn@blob.cat)'s status on Saturday, 27-Apr-2024 17:00:34 JST iced depresso

     in reply to

     • CrunkLord420
     • :umu: :umu:
     • gentoobro
     @a1ba @crunklord420 @gentoobro @splitshockvirus i don't think arb shaders got used there were some serious bits of stupidity about them.
   • Embed this notice
     :umu: :umu: (a1ba@suya.place)'s status on Saturday, 27-Apr-2024 17:00:36 JST :umu: :umu:

     in reply to

     • iced depresso
     • CrunkLord420
     • gentoobro
     @icedquinn @crunklord420 @gentoobro @splitshockvirus remember Cg shaders? I think you still can find Cg shaders in some HL1 mods with custom renderer.
     
     Or maybe ARB shaders? The ones that's just assembly.
   • Embed this notice
     mk (mk@mastodon.satoshishop.de)'s status on Saturday, 27-Apr-2024 17:37:43 JST mk

     in reply to

     @splitshockvirus

     ty

   • Embed this notice
     :apa: スプリットショックウイルス † (splitshockvirus@mstdn.starnix.network)'s status on Saturday, 27-Apr-2024 17:37:44 JST :apa: スプリットショックウイルス †

     in reply to

     • かき@GNUsocialJP
     • mk

     @mk https://github.com/Syllo/nvtop