Skip to content

Conversation

@gkjohnson
Copy link
Collaborator

@gkjohnson gkjohnson commented Jul 29, 2019

Related to #17078, #16423

This is just a suggestion for how to more explicitly document and expose the Raycaster.camera field and (hopefully) make it feel less like magic when calling Raycaster.setCamera. I feel that treating the Raycaster object as a kind of context that hold data needed for different types of objects to perform their raycast is a useful pattern. camera is something that can be used when implementing custom raycast functions for objects that scale based on camera distance or billboard in shaders (such as with lines).

@Mugen87
Copy link
Collaborator

Mugen87 commented Jul 29, 2019

Don't forget to update the TS file for Raycaster.

@Mugen87
Copy link
Collaborator

Mugen87 commented Aug 13, 2019

@gkjohnson Can you please resolve the merge conflicts? I'd like to merge this PR in order to see if it helps to avoid such problems: #17142 (comment)

@gkjohnson
Copy link
Collaborator Author

@Mugen87 Just merged and readded the changes!

@Mugen87 Mugen87 merged commit 5d68fa6 into mrdoob:dev Aug 14, 2019
@Mugen87 Mugen87 added this to the r108 milestone Aug 14, 2019
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