-
Notifications
You must be signed in to change notification settings - Fork 1
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
Feature/perspective #4
Closed
InstrinsicAutomations
wants to merge
10
commits into
arnovanliere:master
from
InstrinsicAutomations:feature/perspective
Closed
Feature/perspective #4
InstrinsicAutomations
wants to merge
10
commits into
arnovanliere:master
from
InstrinsicAutomations:feature/perspective
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
…ons were only drawn with the x and y (translation and scale). I tested against writing my own simple perspective correction step in _drawface() and this proves my suspicion. However, the user of the perspective matrix does not seem to work at all.
…ug camera controls for now to test.
…cup snaps to the camera after 1 frame of looking correct. Also my right vector seems to become inverted. I think the math for strafing is now correct as it uses the cached Forward/Up/Right vectors for the heading.
…ay need the inverse of the whole MVP matrix to determine which triangle I have clicked...
… ray test function. Fixed view matrix by returning the inverted camera matrix. Cofnirmed ray tests successful.
…use them in the recolor step for comparisons against the ray hit face object. Also a side question to optimize the rendering a bit and handle the edge case when the object is behind the camera.
…bject and the lookAt function needs to be fixed. TODO: move everything mesh-related into a controller so data can be cached more efficiently. Should boost speeds. TODO: faster Z-sorting algorithm...
…ilding the painting widget without rebuilding the gesture controller and other widgets. Culled verts are skipped and the back of the buffer is filled with transparency. This allowed culling to be achieved with a slight performance gain. TODO: sorting is still choking the paint step.
After a few months of working on this, the changeset to properly apply the features we are looking to add will be too great and should move to a new library that originally forked from this one. Closing. |
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.
No description provided.