-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Platform dependent fixes #2
Comments
edolstra
added a commit
that referenced
this issue
Feb 7, 2021
In glm 0.9.8 (Nixpkgs 20.09) vecs are still zero-initialized by default, but in 0.9.9 they're not. So restore the old behaviour. Issue #2.
edolstra
added a commit
that referenced
this issue
Feb 7, 2021
Thanks @Xin-888, I've applied your suggestions! |
Thanks, fixed! |
edolstra
added a commit
that referenced
this issue
Aug 26, 2021
In glm 0.9.8 (Nixpkgs 20.09) vecs are still zero-initialized by default, but in 0.9.9 they're not. So restore the old behaviour. Issue #2.
edolstra
added a commit
that referenced
this issue
Aug 26, 2021
edolstra
added a commit
that referenced
this issue
Aug 26, 2021
In glm 0.9.8 (Nixpkgs 20.09) vecs are still zero-initialized by default, but in 0.9.9 they're not. So restore the old behaviour. Issue #2.
edolstra
added a commit
that referenced
this issue
Aug 26, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hello, here are the fixes I needed to properly generate the displacement textures on windows (I compiled with Code::Blocks MinGW x64 and tested it with an older graphics card):
In
dhdm/src/diff.cc
Line 121 in eeb0ce2
In
dhdm/src/render.cc
Line 235 in eeb0ce2
Also around
dhdm/src/render.cc
Line 125 in eeb0ce2
I personally didn't experience the following issue, but it's a good practice to complete the framebuffer. Something like:
While we are at it, a useful qol change would be to keep track of the most positive and most negative pixel values to help detect scaling issues. Something like (in diff.cc):
The text was updated successfully, but these errors were encountered: