Hey there @Razakhel ! 🖐️

Is there a planned roadmap for this framework? Or are there expected timelines when newer features are going to be added? In addition, is there expected to be features like alpha channel support soon? Or is this project considered to be "abandoned" and will no longer be updated or worked on?

And gratz in advance!

We can already have textbox using ImGUI but when typing wasd for example, it will also trigger the callbacks attached to the key events W, A, S and D.

See https://github.com/ocornut/imgui/issues/703 and https://github.com/ocornut/imgui/issues/1219#issuecomment-313683169 if needed :D

Good luck, I love your work!

The window class was reworked in a way that you can now set a custom window close callback. VSync is now working as well on MacOS.

The .gitignore was also modified to exclude DS_Store when using a MacOS workspace.

Using quaternion for composing non-translation transforms is more efficient than matrix composition.

This PR adds the necessary functions. They were written by @Razakhel first and fixed by myself.

xvfb-run allows a program to be run in a new xvfb server without having to take care of the lifecycle of the involved server.

See there for inspiration and usage: https://github.com/zestedesavoir/zds-site/pull/5122/files#diff-b67911656ef5d18c4ae36cb6741b7965R37

After having tried many different things, launching unit tests which require graphics capabilities (using GLFW in this case) always fail. It is yet unknown if this is due to:

• A technical issue of macOS VMs/servers without any available workaround (which doesn't seem like it, since there are reports that it can be done, at least could have been some time ago);
• Something missing concerning the window's initialization: GLFW may need specific settings to be able to start under those conditions;
• Specific arguments to launch Xvfb and/or the tests executable with.

See:

• https://github.com/go-flutter-desktop/go-flutter/issues/186

Note: Xvfb needs the package xquartz to be installed by brew.

Separate steps

- name: Starting Xvfb
  run: |
    export DISPLAY=:99.0;
    ( sudo /usr/X11/bin/Xvfb :99 -ac -screen 0 1280x720x24 +render +iglx )&

- name: Test
  working-directory: ${{ runner.workspace }}/build-${{ matrix.compiler.c }}
  run: ALSOFT_DRIVERS=null ./tests/RaZ_Tests

Unable to create basic Accelerated OpenGL renderer.
Unable to create basic Accelerated OpenGL renderer.
Core Image is now using the software OpenGL renderer. This will be slow.
GLFW error 65545: NSGL: Failed to find a suitable pixel format
libc++abi.dylib: terminating with uncaught exception of type std::runtime_error: Error: Failed to create GLFW Window
/Users/runner/work/_temp/62d6113c-982d-45c8-abf4-0294b9601198.sh: line 1:  2157 Abort trap: 6           ALSOFT_DRIVERS=null ./tests/RaZ_Tests
Error: Process completed with exit code 134.

See:

• https://github.com/vispy/vispy/blob/master/.travis.yml#L127

Single command

- name: Test
  working-directory: ${{ runner.workspace }}/build-${{ matrix.compiler.c }}
  run: /usr/X11/bin/Xvfb :99 & export DISPLAY=:99 & ALSOFT_DRIVERS=null ./tests/RaZ_Tests

Unable to create basic Accelerated OpenGL renderer.
Unable to create basic Accelerated OpenGL renderer.
Core Image is now using the software OpenGL renderer. This will be slow.
GLFW error 65545: NSGL: Failed to find a suitable pixel format
_XSERVTransmkdir: ERROR: euid != 0,directory /tmp/.X11-unix will not be created.
_XSERVTransSocketUNIXCreateListener: mkdir(/tmp/.X11-unix) failed, errno = 2
_XSERVTransMakeAllCOTSServerListeners: failed to create listener for local
(EE) 
Fatal server error:
(EE) Cannot establish any listening sockets - Make sure an X server isn't already running(EE) 
libc++abi.dylib: terminating with uncaught exception of type std::runtime_error: Error: Failed to create GLFW Window
/Users/runner/work/_temp/1e2bfa6e-3279-423e-aa75-96161a9cb859.sh: line 1:  2149 Abort trap: 6           ALSOFT_DRIVERS=null ./tests/RaZ_Tests
Error: Process completed with exit code 134.

See:

• https://superuser.com/questions/962490/xvfb-run-on-mac-osx

Many resources are available, which need to be tested further:

• Scratchapixel's explanation: https://www.scratchapixel.com/lessons/procedural-generation-virtual-worlds/simulating-sky
• Frostbite's papier on physically-based sky, atmosphere & clouds: https://sebh.github.io/publications/egsr2020.pdf
  • Related presentation: https://www.ea.com/frostbite/news/physically-based-sky-atmosphere-and-cloud-rendering
• GPU Gem about atmospheric scattering: https://developer.nvidia.com/gpugems/gpugems2/part-ii-shading-lighting-and-shadows/chapter-16-accurate-atmospheric-scattering

It has been pointed out that Cook-Torrance's most common explanations don't include the fact that the Fresnel component is actually symmetric.

See:

• Earl Hammon's GDC talk, particularly from slide 99 to 108, although many slides prior to these are worth looking at.
• This good short explanation post: https://computergraphics.stackexchange.com/a/2289/9321.

Instead of the common Fresnel calculation, Brian Karis suggests using a spherical gaussian approximation, which he deems more efficient with unnoticeable differences.

As such, the current Fresnel calculation:

vec3 fresnel = baseReflectivity + (1.0 - baseReflectivity) * pow(1.0 - cosTheta, 5.0);

would become:

vec3 fresnel = baseReflectivity + (1.0 - baseReflectivity) * pow(2.0, (-5.55473 * cosTheta - 6.98316) * cosTheta);

In RaZ's case, this actually fixes black artifacts when the light's position is strictly equivalent to the camera's (which should not happen in real life cases):

This optimization should probably be investigated, as the artifacts may come from a small blunder in the implementation.