-
Notifications
You must be signed in to change notification settings - Fork 13
support smaller aperture domes #1
Comments
Hola! So, if this is correct, then i have a solution using a sort of raycasting in the fragment shader, which enables any value for apertures. (TODO-1: make the rendering of the sixth side toggleable) Custom sweet spot (TODO-2) should also be doable, needs some testing though. This approach eliminates the need for a textured sphere (which was imho optically imperfect anyway). TODO-3: make the debug grid also ray-traced. Work in progress: If the time is right, i will make a pull request. In the meantime, i might ask for some advice trying not to mess up your code and the Processing canon – hope this is ok. Btw, the current official version is not working due to a change in the signature (logic?) of Cheers! |
@diroru hola, thanks so much for looking into this! You can make a pull request now, and I will take a look at your changes directly from the PR. |
@diroru Thanks for your contributions, your PR is already merged into master. A friend of mine, @janebeta7, is actually testing the new version of the library with the setDomeAperture() functionality at the SAT statosphere dome, which has an aperture of 210 degrees: She will give us some feedback on how it is working. |
Hello all! yes, i am at SAT Montreal http://sat.qc.ca/en/satosphere
tomorrow i will test aperture with |
Hello all! |
i.e., where the projection doesn't cover 360 degrees but smaller ranges like 210, etc.
The text was updated successfully, but these errors were encountered: