Adding 3D render flag#1834
Open
Knightmore wants to merge 1 commit into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Setting this to true will take the render short path: It clears the back buffer with a solid color, runs post-effects and then returns, skipping all 3D world rendering.
I'm using this actively over around two months now and so far also some other users of it didn't report any problems either. It keeps my GPU load down to ~0-3% without any errors or crashes.
I would have added 0x3834C too as this seemed like a bitflag for Shader Init States, but I haven't grasped the full picture yet...
[FieldOffset(0x3834C)] public uint ShaderInitFlags;
somebody smarter with this needs to properly check that out, especially individual flags and the naming.
if you guys are fine with it though, I'd just push another PR to this one