ssgl VS filament

It's here. I made a post about it too, there's some details in the comments on how this works.

Here I'm doing GLSL and running it via OpenGL on top of my own helper library (the main branch of the code repo explains it pretty well). For me it's the easiest way to code for a GPU by a wide margin, but I guess that's to be expected. For performance, the most important things here are using shared memory and persistent threads so there are less global reads and especially atomics (I wanted to do a local reduction on the end result but for whatever reason subgroup operations don't work on 64-bit integers and I didn't bother to write it out with shared memory)

Some of it is fine-grained control, some is how it’s nice to be able to treat shaders as separate entities, some is just different preference. But no actual limitation, in fact I built a thing for that on top of OpenGL.

Include is probably your best bet there. Personally I use this system that I made, which borrows the single source programming model from CUDA so that shaders are just reinterpreted C++ code that can sit within the rest of the program. This means I can call the same functions from C++ and the shaders, and includes work just like any other includes.

I also already have a library that gives compile time errors, by having the shaders just be a part of the C++ program :) This would also benefit slightly from having embedded files, as I wouldn't need to do the runtime hacks that are currently in place.

As a side note, you may be interested in this library that someone posted on /r/GraphicsProgramming awhile ago. Haven't used it, but it seems like it might fit in with your general design philosophy.

Because mine is the most faithful reproduction of GLSL I've seen. Almost all features work the same in C++ as they do in shaders -- the notable difference is that you can't pass swizzles by reference, and inout arguments have to be defined with a slightly wonky syntax.

The culmination of my attempts at wrapping OpenGL is ssgl, which foregoes basically all binding and lets you write shaders along C++ with semi-automatic lambda capture. The underlying implementation is filled with dragons, but from personal experience it's just bonkers how much nicer it is to work with compared to any other approach I've used.

I have a library that due to its nature (it defines a domain-specific language within C++) has to define macros for a bunch of words that some standard headers use as variable names. This causes the standard headers to completely break if my library headers are included before them, and the errors are less than intuitive. Is there a simple way to produce a meaningful error (like "library header must be included last") if a standard header is included after the library headers? Googling didn't help much, and at a quick glance standard headers don't appear to contain too many extremely common names that I could #define to static_assert or something. I'm fine with the sensible error being limited to a few of the big standard implementations, so the option of just going through the headers and finding enough such names is doable, but it'd be nice to have a cleaner solution.

Yeah, the state machine aspect does make debugging cumbersome, and it's very easy to forget some option in the wrong setting. But I don't fully agree with "a collection of spells", I think the steps to achieve something are (mostly) pretty straight forward. Though maybe memories go sweeter with time, I haven't written any binding code after making ssgl :-)

Also: Filament is a real-time physically-based renderer written in C++. It is mobile-first, but also multi-platform.

https://google.github.io/filament/

Also beginner here, I think you can learn other's codes to get a better understanding of the API by learning how others can abstract these concept into higher level. They're many great projects out there like Google's pbr renderer filament https://github.com/google/filament, AMD's gltf sample https://github.com/GPUOpen-LibrariesAndSDKs/glTFSample and also as many suggested, the Sascha Willems's repos https://github.com/SaschaWillems and the official sample https://github.com/KhronosGroup/Vulkan-Samples

In the Flame discussions page, there is a request for 3D, and Flame developers write that they will be happy to start working on support once when Impeller is stable on most major platforms. So what can the community do? 1) Create discussion topics, just like these posts. Or in other discussion forums. 2) Learn about Impeller, Filament, Flame, and Flutter and be willing to contribute to their development. 3) Join Flame now and try to do something or contribute. 4) Study the implementation of Flutter 3D, and try to do something together with ARCore or ARKit plugins.

Anyone know much about how this compares to Filament by Google?

https://github.com/google/filament

Have you tried Filament? https://google.github.io/filament/

I was looking through the Google Filament repo and I noticed that the classes in include/filament use a trick I haven't seen before that hide implementation details similar to PIMPL.

There are a handful of other examples out there of high-level shading languages - Cg (long deprecated), whatever Filament Material system uses (example), and various GLSL preprocessors (example).

I'm loading a texture using OpenGL enjoy this glTexImage2D( GL_TEXTURE_2D, 0, GL_RGBA, texture.width, texture.height, 0, GL_RGBA, GL_UNSIGNED_BYTE, texture.pixels.data()); The issue is that the color of the image looks different from the one I see when I open the file on the system image viewer. On the screenshot you can see the yellow on the face displayed on the system image viewer has the color #FEDE57 but the one that is displayed in the OpenGL window is #FEE262 Is there any flag or format I could use to match the same color calibration? Displaying this same image as a Vulkan texture looks fine, so I can discard there is not an issue in how I load the image data. [EDIT] In the end it seems like‏‏‎‏‏‎‏‏‎‏‏‎­the framebuffer in OpenGL doesn't gets color corrected, so you have to tell the OS to do it for you #include void prepareNativeWindow(SDL_Window *sdlWindow) { SDL_SysWMinfo wmi; SDL_VERSION(&wmi.version); SDL_GetWindowWMInfo(sdlWindow, &wmi); NSWindow *win = wmi.info.cocoa.window; [win setColorSpace:[NSColorSpace sRGBColorSpace]]; } I found this solution here https://github.com/google/filament/blob/main/libs/filamentapp/src/NativeWindowHelperCocoa.mm https://preview.redd.it/2td3rs19p4f71.jpg?width=1476&format=pjpg&auto=webp&s=454d4e554d47e3a4e11a16c938304f1125ed7622

I found this issue on github https://github.com/google/filament/pull/3190/files