Render target implementation adapted for the main branch #111
Conversation
This file contains 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
Brachi
approved these changes
Jul 20, 2024
There was a problem hiding this comment.
Looks good in general. What is not clear to me is how to actually modify an rtex. Should one create a .tex file next to the .rtex with the same name? If so, we could use that instead of a UV GRID, so e.g. computer screens will show.
But certainly can be done later.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Complex effects use render-to-texture render targets, the .rtex file looks like a regular .tex texture that contains a header only.
This pull request adds parsers and serialization code for both rtex-112 and rtex-157 formats. MRL uses a type hash that allows detection render targets, RE5, unfortunately, had to use brute force by trying to find .rtex if .tex is missing