Well, it took about 2 weeks longer than I expected (spare time for programming is especially spare at times!) but I finally finished swapping out the graphical backend of my roguelike project with a handrolled one using #wgpu! I'm super excited to be fully in control of my #gamedev destiny!
Wgpu is still pretty difficult, even if it is cleaner than opengl with glow and #glutin. (And up-to-date with its own dependencies, always nice!) #rust
It does, but #Bevy falls into a sort of middle-zone for my #gamedev desires. I like working on my RL in Rust because I know how everything works down to a pretty low level, and that's a good learning experience and fun for a simpler 2D game.
If I just wanted to focus on the "game" and not the engine, I'd use #Godot and take advantage of the high-level features.
I do love that Bevy exists and wish them great success! I just don't need it right now.
In terms of inspirations, I have looked into some Bevy code (I'm eventually going to have to do something about my ECS, and was checking theirs out) but I've mainly based my code on bracket-lib and a little referencing of a project called chargrid. The #winit examples were also very helpful. Winit made a big change in their model in v0.3, the very day I was starting my rewrite, and no one has caught up to that yet.
Is there anyone on here that has a recommendation for NVIDIA graphics cards? I haven't used them for a very long time, only AMD, so not really up to date on them.
I need it to run fine on Linux, which I hope has improved now. I will use it for not very demanding games like WoW, and for Machine Learning. I currently have an AMD Radeon RX 5700 GPU.
I was considering a Dual GeForce RTX 4070 OC, since it would fit in my box. I can't have any of the super long ones.
Take a look at this project by Runi: a preliminary language server for WGSL. IMO this is one of the biggest barriers in making graphics programming genuinely approachable: I'd love to see this catch on!
@alice_i_cecile There is also wgsl-analyzer ( https://github.com/wgsl-analyzer/wgsl-analyzer ) though I'm not sure how good it is for bevy. It's already pretty frustrating to use for plain wgsl so I guess it can only be worse with bevy preprocessor.
Ready for opening! At TaKe Sushibar in #Palma, "A Life Cycle" will evolve on the Mediterranean island during the next 4 months. Very much looking forward to see some good old friends. #algorithmicart#MastoArt#shaders#slowArt
Yeah some people asked if the wall was painted for this occasion ;) it was a super nice evening with close friends and even my old startup colleagues who I had not seen maybe in 20 years. Now waiting for boarding and still feeling warm from all those smiles and hugs <3
#FluidX3D#CFD update alert! v2.15 speeds up framerate in interactive graphics by 20-70%. 🖖🥳💻
How? Turns out iterating over 2 million pixels with a single CPU core is... really slow. I did that 3 times more than necessary for every frame rendered on screen! 🖖😆
I've now eliminated a memory copy of the frame (in favor of pointer swap), and a clear frame/zbuffer operation on CPU since that's already done on #GPU.
‼️ New rayrender update! v0.33.0 introduces instancing with create_instances(): copy/paste an existing scene (either a single 3D model or a collection of objects) and translate/rotate/scale it to a new location! This allows you to generate extremely large scenes with a low memory footprint. For example, here's 4,000,000 dragon models with about half a million vertices each: this would take about 150 terabytes of memory if loaded raw!
One of my #PhD papers got selected for the 2022 Best Paper Award of MDPI Computation! 🖖🥳📃🏆
That was a very bold publication for multiple reasons:
I solo-authored it
I wrote that paper in only 2 weeks
the title contains "Esoteric" twice
I submitted it on April 1st
It's serious science though: I discovered a simple algorithm to cut memory demand of the #LBM in half, allowing huge simulations on cheap #GPUs. This is one of the key innovations in #FluidX3D#CFD.
1/2 So this small, rather un-assuming render is kind of insane...
Earlier today, I posted a video showing an animation where each of the 435,545 vertices were themselves a complete Stanford dragon--cool. Instancing! However, when I implemented instancing in #rayrender, I made sure to do so in a way that supported nested instances: e.g. you can create an instance, and then instance that instance, and so on. So why am I posting a 400x400 still image of a dragon again?
(Finally started working on a new rayrender feature that's been on my to-do list for a while: instancing! This video would have taken about 10 terabytes of memory if rendered raw)
I know SPIR-V is not meant for human readability and all that, but damn. Is there not any way that the variables were named anything closer to useful than %13525? I understand that it's not a one-to-one match with my glsl variables, but like... This feels like it's actively trying to obfuscate the code 🥲
Maybe there's some glslang option I don't know about that tries to make them a bit clearer?
Ha, in the light of the whole discussion around how people treated the original maintainer of #xz, I'm having a little moment of self-awareness as I complain about the features in the open source software I'm using for free, while the amazing people who actually work on it like @gfxstrand and @crzwdjk patiently explain to me why it's not that simple... 😅
@julienbarnoin You're welcome! And we do it gladly, or at least I do. As long as I can keep getting a paycheck to go along with it, I see no reason to stop.
But also, it's okay to gripe a little about things that suck. I know they suck, too. It usually only gets frustrating when people expect me to get out my magic wand and pointy hat and retroactively fix a feature that shipped 25 years ago. 😅
Learn how to change the look of the halftone pattern shader with different blend modes. View the Shadertoy demo to see it in action, and change the options.
