ProScene | physicalDistanceToScreen | and how to calculate the right Perspective Projection from real world data.
in
Contributed Library Questions
•
2 years ago
I am just getting my head around the proscene library for processing.
My goal is to project a virtual 3d object opon, the same real one.
For Projection Mapping to complex surfaces.
It's really hard to determine the right virtual size and camera distance, just by trial and error.
So there must be better ways.
I am not so keen with the pure OpenGL MatrixModulations.
But are the calculated Perspective Projections, in any way related to real World distances?
I've see that there is the physicalDistanceToScreen function.
Returns the physical distance between the user's eyes and the screen (in meters).
which looks like exactly what I need.
but neither this nor the focus distance seem to change when moving the camera,
or the other way around changinging these values by the setFunctions, doesn't seem to have any effect on perspective calculation.
Is this function not finished yet, or am i on the wrong track !?
My goal is to project a virtual 3d object opon, the same real one.
For Projection Mapping to complex surfaces.
It's really hard to determine the right virtual size and camera distance, just by trial and error.
So there must be better ways.
I am not so keen with the pure OpenGL MatrixModulations.
But are the calculated Perspective Projections, in any way related to real World distances?
I've see that there is the physicalDistanceToScreen function.
Returns the physical distance between the user's eyes and the screen (in meters).
Default value is 0.5m.
Value is set using setPhysicalDistanceToScreen(float)
.
physicalDistanceToScreen() and focusDistance()
represent the same distance. The first one is expressed in physical real world units, while the latter is expressed in processing virtual world units. Use their ratio to convert distances between these worlds.
which looks like exactly what I need.
but neither this nor the focus distance seem to change when moving the camera,
or the other way around changinging these values by the setFunctions, doesn't seem to have any effect on perspective calculation.
Is this function not finished yet, or am i on the wrong track !?
1