Skip to content
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

Updates, features, and refactoring for Modular PBR Shaders #2351

Conversation

yaRnMcDonuts
Copy link
Member

A big PR that makes many minor changes to the new modular PBR system so it can work with PBRTerrains and any other potential forks.

Since no bugs were reported in the last alpha version, I've now replaced the main PBRLighting.j3md shader with this new modular version.

I'm still adding some small things to this PR, and still need to upload the new modular PBR terrain files, so there will probably be more changes to this PR soon, but feel free to review in the meantime.

I also plan to make another PR with some more minor improvements to further modularize the PBRSurface struct (and add some other similar structs) later on in 3.8 beta after collecting more feedback, so I'll be merging this PR very soon, likely before it gets full review. But I will ensure all feedback regarding the new Modular shader system will be addressed before 3.8 reaches stable.

stephengold and others added 25 commits October 22, 2024 15:35
Updated to store tbnMat as a publicly accessible variable in the PBRSurface.glsl struct, that way tbnMat won't need recalculated anywhere else in the shader it is needed.
caused a crash trying to assign a non existent variable. but it isn't needed anymore anyways since surface.geometryNormal already is set to = norm by default now
…-patch-3

Add tbnMat variable to PBRSurface.glsl
@yaRnMcDonuts
Copy link
Member Author

yaRnMcDonuts commented Jan 30, 2025

Not sure what I did with the fork I used for this PR, but it seemed to randomly include some other commits from months ago...

Usually I do my PRs by editing files in JME's repo 1 at a time and let it auto-generate a new branch for my changes prior to merging, but this time I decided to try forking master first, making my changes there, and then submitting a PR from that branch.

IDK if I messed something up, but its late now so I might just remake this PR when I have time tomorrow.

@yaRnMcDonuts yaRnMcDonuts deleted the yaRnMcDonuts-patch-2 branch January 30, 2025 11:31
@yaRnMcDonuts
Copy link
Member Author

somehow the target branch got messed up in this pr... i redid the same thing in a new pr and it worked, idk if github bugged out on me or if I made a mistake.

Either way, disregard this PR.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants