crosscore_dev VS filament

Alternatively you can write a script or plugin to save what you need from inside Maya scene. It's a bit of code, as an example of this approach here is a set of Houdini export scripts that I'm using for my own projects: https://github.com/schaban/crosscore_dev/tree/main/exp What you're getting from this approach is that data is represented in convenient way, and in many cases you don't need any preprocessing or special run-time representation to use the data (for example XCOL format for collision geometry in the scripts above already has BVH structure already baked-in to speed-up collision queries, you don't need to generate it upon loading, dynamic allocations are minimized etc.).

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