view-frustum culling implementation with jit.gen & matrices
Pointed there by Robert R., i'm trying to implement view-frustum culling into my system.
I'm using : http://www.lighthouse3d.com/tutorials/view-frustum-culling/ which seems to be a great reference (I saw this link a bit everywhere)
I'm currently into the Geometric Approach and, for sure, I need some generous hands to help me.
I understood the demo there : http://www.lighthouse3d.com/tutorials/view-frustum-culling/geometric-approach-extracting-the-planes/
This is the global description.
Implementation is a bit more tricky (for me)
As attached, I'm okay (I guess) with the setCamInternals.
I'm stuck in implementing the setCamDef which has to compute 3 vectors and to render the 8 points of the frustum (=the 6 planes used for checking which object has to be sent to the openGL pipeline)
I'm stuck because I don't know how to grab those 3 vectors required.
The first one is ok, this is the position of the cam.
The second one is "a point to where the camera is pointing" … How can I find/calculate it ?
The third is the up vector, same .. . how can I grab it ??
ANY help would be amazing for me.
"The second one is "a point to where the camera is pointing" … How can I find/calculate it ?
The third is the up vector, same .. . how can I grab it ??"
both of these attributes can be retrieved.
you have to attach a jit.anim.node to your jit.gl.camera in order to make it work. (this requirement will be removed in an upcoming release)
the camera-point-position is the @lookat attribute of jit.anim.node.
the up vector can be calculated from the anim.node’s @quat attribute, by sending it to a jit.quat object, and querrying the yaxis attribute. (the up vector is the Y axis transformed by the camera’s current quaternion)
check out the patch below.
----------begin_max5_patcher---------- 1042.3ocyY1sjZCBEG+Z8ofIW6lIP9vXuZeJ5Mc53fF1HaS.Kg3Zam9tWfDs wVMAccwbShgPfC+37+vA7WSm3shumT4A9D3KfIS90zISLEoKXR6yS7Jw6WWf qLUyaMurjvjdyZdmjrWZJufy+F9XwuvYxJ5OI5WAQ9AsEuUPpTeLVR4rkBxZ YSOmfRTUAD0bKn8B3qseEqtjWKKHRiEbrsvx0anr7NsSbp4aCSL2RizWQwcZ IZlwV4qd8Iz7t1JCWZrUuOSDYXF16ucMkcnmgsEtpd0phlgltfeOcp9xLKAX IopBmS9O.9TpeBLIIdA.F5u.gRCf.DzeNLNJM813Z3hPCWihsfqGFcMEI+wV RSi34c7CNCxCQwcPNJxbCt3BLO5pYN5FHLi7lp29O.+JU5iYzReFOi.dtjui Tp+UAeMtX..eJpPWDUyF.WHTCmZwUfAdpY4yiK306hdC35RJ55sfcJCmKtJ1 DbhHohlYpd3kQBrU7GOeXQKLcjIZC7iCPIwgJc07jzfHH3o.+vEIoWEytMoW quTjUROX7iT5ITiLB3G38zJ2JzhBanRPPeBMH7QBGIHmHMrA33vPsQsGfNnP mDFpWWmuWik.qRw3TDE1KhrESMNQGhceILgtZLEdeWbSCo6iCTAsRZMcVXkD atSjXWJNsRgooyLsT6FbidWAngMYkBQndCPGNJxMJSP2oRNpltT6CPX.niBI cHVTKrl2q2T5iLhjlU4E94BZV0F7VEsJn4aj5gCggUIY.ffmadiJ4o5iq3UP Yj07Zlrafo2GUUlxxRrTP2OHeaRO.ECM3s4o3fyiW2DvWxyyKHdWmfipw2fC yHy9dZBaGdgA4BuishPMDkDQ6zW2rX+n7gjfU.h.WQtOpqUXVt1CnoIGlOPn 4VRTehr4ORQ12UyHBNH99Dl1vmgwRSrmjj9nRxiNL8aTVF+MvyuTgw2qnyG7 erIBBrc0rd25ZzHH.sfvxHBmCHXrUIU6D.gkRQM8lzPZZt7MZlbitzjziU+5 xAJ5jU06mIVsEU8PxT9KEbrdQWG4MsVYOBr2caY67hk5tnVPr9PirKQ6wti0 Ud9hIc26Uq15hhpqyCRk2zVd1ciIWZuG57pWpOfVo63UaBdog8dbruu0xLMo Iq1+4OPvXV5xOEVU7Zw5CCh1r3A+0vxHUJ4r4Hr6TG8Yf1oRanYYDV2LzxnU 5j1LipfyNqYq47Oc04sG2YN5MDN5vCbH6A4N6IdjwmjQl8frY9J5jJ8gaOCx mP2ourRtG6L9nOgrAmufty+wF4UjyrFaDWycl0XyTExoVSvnwZVXg0jLpXCz cAcP1rnNbtasG3Gk8zjgHd61cDQUaaZLEUhyuxMIgmLy7Hk07noE8DjczC0O dpt098z+.96x.3C -----------end_max5_patcher-----------
a big thanks to you.
I even understood how jit.anim.node object worked :)
implementing my calculation about view-frustum culling in next hours and posting here the result!!
I finally have little problem to retrieve ratio parameter :-/ (in setCamInternals : http://www.lighthouse3d.com/tutorials/view-frustum-culling/geometric-approach-implementation/)
I guess it is the ratio between height and wide of frustum?!
so, I have some difficulties about 2 things:
– to retrieve the ratio parameter in order to calculate my 8 points defining my 6 planes for the culling
– to put that into my jit.gen.
basically, here is my current implementation on jit.gen
ratio & planes implementation are missing, and of course, the objects matching test.
probably, I'll create a matrix with my 8 points, then another jit.gen which would be fed by objects positions matrix + my 8 points matrix, calculating which objects is in or out of scope…
would you help me with that Robert, or Wes or ?
ratio is window-width divided by window-height.
@Robert.. thanks for this obvious thing I didn’t even notice :-/
@maybites: thanks a lot for your link.
I don’t know how to apply your nice patch (which I understood btw) to my "case"
I’m trying to implement http://www.lighthouse3d.com/tutorials/view-frustum-culling/geometric-approach-implementation
if I sent an n planes matrix to a jit.gen, what is the rule to retrieve a particular plane ??
I’m currently sending an 1×1 matrix with 4 planes to the first inlet of my jit.gen
I’m mapping the in 1 to a codebox, on the first inlet too
so in1.x, .y, .z are the first 3 planes
how can I have the fourth ?
so here is where I went.
I have that huge jit.gen (finally not that big)
It takes some parameters as input:
– position of the cam
– a point on the view direction of the cam (lookat)
– the up vector
It takes also cam parameters like:
– lens angle
– ratio of the view (w/h)
– nearClip distance
– farClip distance
it processes the whole parameters to render the 8 points of the view frustum.
As shown there: http://www.lighthouse3d.com/tutorials/view-frustum-culling/geometric-approach-extracting-the-planes/
The calculation is there:
I need to normalize a vector inside the codebox.
I did the basic calculation including sqrt()
does it exist a better way inside GenExpr / codebox ?
Now, I have my eight point defining my view.
They defines my 6 planes too.
I have to "test" all my object according to those planes in order to have a list of objects I have to inactivate and activate, according to the position & orientation of my cam.
That part is done in the second codebox and has to be done for the 6 planes.
Knowing I have a matrix with all my objects' positions, how can I test each one against those 6 planes ??
any help would be appreciate.
I don't know if this is the best implementation I could make of that concept.
Only to clarify my approach (which is quick and dirty compare to the road you are taking).
As far as I understand you wanna have a tool that tells you if your object is inside the viewing frustum. my patch does that insofar, that it calculates the x-y screen-coordinates of a 3d vertex. if the x-y coordinates are not inside the screen, the vertex would be outside the frustum.
But I might have missunderstood your problem.
x,y aren’t enough because my cam doesn’t have to be locked in only one plane.
if I understand you correctly: my patch works with all sorts of camera-transformations.
this would be nice if I could test it.
I’m currently trying to make a calculation for all objects around the cam for pure sound purpose. I already need that.
The position of the object relatively to the cam would be defined by azimuth/elevation/distance.
Then, I’d like to make a one pass calculation and calculate if the object has to be activated or not according to azimuth/elevation.
Indeed, all in one could be nice & efficient.
Forums > Jitter