Comments on: Plane Scaling and Positioning with Papervision http://blog.melihelibol.com/?p=3 on pertinent substance, and persistent deliberation on quaint curiosities. Fri, 04 Jun 2010 23:27:14 -0700 http://wordpress.org/?v=2.8 hourly 1 By: H http://blog.melihelibol.com/?p=3&cpage=1#comment-12001 H Fri, 04 Jun 2010 23:27:14 +0000 http://blog.computerelibol.com/?p=3#comment-12001 Hey Matt, Let's call the parent of the target element the "branch element" and the actual target element the "leaf element." We will also refer to the viewport as the "root." The branch element's transform must be recalculated relative to the root's transform. The leaf element's transform must be recalculated relative to the branch element's transform. Perhaps there are multiple leaf elements that we want to leave unchanged. One solution is to apply the calculations that would occur between the root and branch element to the leaf element, as well as the branch and leaf element calculations. In this scenario, we take two passes to compute the target leaf element's transform, one with the root and branch element's transforms, and one with the branch and *the original* target leaf element's transform. Sample algorithm: Create a copy of the target leaf element's transform. Apply root to branch calculations to the copied transform. Apply branch to leaf calculations using the original leaf element's transform to the copied transform. Set the target leaf element's transform to the copied transform. Force render if needed. Hope this helps, Melih Hey Matt,

Let’s call the parent of the target element the “branch element” and the actual target element the “leaf element.” We will also refer to the viewport as the “root.”

The branch element’s transform must be recalculated relative to the root’s transform. The leaf element’s transform must be recalculated relative to the branch element’s transform. Perhaps there are multiple leaf elements that we want to leave unchanged. One solution is to apply the calculations that would occur between the root and branch element to the leaf element, as well as the branch and leaf element calculations. In this scenario, we take two passes to compute the target leaf element’s transform, one with the root and branch element’s transforms, and one with the branch and *the original* target leaf element’s transform.

Sample algorithm:
Create a copy of the target leaf element’s transform.
Apply root to branch calculations to the copied transform.
Apply branch to leaf calculations using the original leaf element’s transform to the copied transform.
Set the target leaf element’s transform to the copied transform.
Force render if needed.

Hope this helps,
Melih

]]> By: Matt http://blog.melihelibol.com/?p=3&cpage=1#comment-11331 Matt Thu, 13 May 2010 09:12:47 +0000 http://blog.computerelibol.com/?p=3#comment-11331 I know this is a really old thread and chances are nobody checks it anymore but I was wondering how I would modify this to get it to work on planes which are children of other planes. This works great when the child is a direct descendant of the viewport but not once it is reparented. I thought first that adjusting the calculations so that it takes into account the containing plane width and height as opposed to the viewport but I am getting odd results. Any help would be much appreciated... Thanks I know this is a really old thread and chances are nobody checks it anymore but I was wondering how I would modify this to get it to work on planes which are children of other planes. This works great when the child is a direct descendant of the viewport but not once it is reparented. I thought first that adjusting the calculations so that it takes into account the containing plane width and height as opposed to the viewport but I am getting odd results.

Any help would be much appreciated…

Thanks

]]> By: syamsundars http://blog.melihelibol.com/?p=3&cpage=1#comment-3548 syamsundars Wed, 20 May 2009 06:07:12 +0000 http://blog.computerelibol.com/?p=3#comment-3548 provide more samples codes (papervison) provide more samples codes (papervison)

]]> By: Random Lucubrations » Blog Archive » Coordinate Utility class for Papervision 3D http://blog.melihelibol.com/?p=3&cpage=1#comment-125 Random Lucubrations » Blog Archive » Coordinate Utility class for Papervision 3D Fri, 10 Oct 2008 00:54:37 +0000 http://blog.computerelibol.com/?p=3#comment-125 [...] Some time ago I wrote an article titled Plane Scaling and Positioning with Papervision. I shared the solutions I had used to over come some of the challenges us RIA developers face when [...] [...] Some time ago I wrote an article titled Plane Scaling and Positioning with Papervision. I shared the solutions I had used to over come some of the challenges us RIA developers face when [...]

]]> By: Mark http://blog.melihelibol.com/?p=3&cpage=1#comment-58 Mark Sat, 30 Aug 2008 05:03:41 +0000 http://blog.computerelibol.com/?p=3#comment-58 That sounds amazing, I'm excited to see the final function (as I've been trying to figure it out for a week and it's wayyy beyond me apparently). Thanks for sharing your amazing work, I really appreciate it. *bookmarked, checking daily* That sounds amazing, I’m excited to see the final function (as I’ve been trying to figure it out for a week and it’s wayyy beyond me apparently). Thanks for sharing your amazing work, I really appreciate it. *bookmarked, checking daily*

]]> By: admin http://blog.melihelibol.com/?p=3&cpage=1#comment-53 admin Sat, 23 Aug 2008 00:27:11 +0000 http://blog.computerelibol.com/?p=3#comment-53 Hey Mark, Check out this discussion: <a href="http://www.nabble.com/Re%3A-align-objects-to-camera-or-stage--p19037587.html" rel="nofollow">http://www.nabble.com/Re%3A-align-objects-to-camera-or-stage--p19037587.html</a> I have code posted there that should work with the latest build of paper vision. I have been real busy this week, but I think this weekend I will have some time to post a new article with the final function. Thanks a lot for pointing out which build has the change in how perspective is computed. I will make a note of it in this article. As for -1, I am not familiar with this equation. Though, when I had a look at the source, I saw that focus is not used when computing the difference in z from object to camera during projection. Since zoom is a factor of focus in the equation (cam.zoom - 1) * cam.focus) - Math.abs(cam.z) I can only assume that -1 would serve to cancel out focus since it was a part of the z distance. Since it is no longer used to compute the distance, it is no longer needed. Hey Mark,

Check out this discussion:
http://www.nabble.com/Re%3A-align-objects-to-camera-or-stage–p19037587.html

I have code posted there that should work with the latest build of paper vision.

I have been real busy this week, but I think this weekend I will have some time to post a new article with the final function.

Thanks a lot for pointing out which build has the change in how perspective is computed. I will make a note of it in this article.

As for -1, I am not familiar with this equation. Though, when I had a look at the source, I saw that focus is not used when computing the difference in z from object to camera during projection. Since zoom is a factor of focus in the equation (cam.zoom – 1) * cam.focus) – Math.abs(cam.z) I can only assume that -1 would serve to cancel out focus since it was a part of the z distance. Since it is no longer used to compute the distance, it is no longer needed.

]]> By: Mark http://blog.melihelibol.com/?p=3&cpage=1#comment-52 Mark Fri, 22 Aug 2008 23:46:17 +0000 http://blog.computerelibol.com/?p=3#comment-52 The sample file seems to be broken with build 639 and later? The scaling seems to work (gives a perspective of 1 at distance = 1000) but the shape is positioned too far towards whatever edge it is near. This is very pronounced at plane.z = 1000, and very slight at plane.z = 10000. I've heard that the following equation no longer needs the "-1" after build 639, but I'm not sure if it is relevant: plane.z = ((cam.zoom - 1) * cam.focus) - Math.abs(cam.z) Any tips? The sample file seems to be broken with build 639 and later? The scaling seems to work (gives a perspective of 1 at distance = 1000) but the shape is positioned too far towards whatever edge it is near. This is very pronounced at plane.z = 1000, and very slight at plane.z = 10000. I’ve heard that the following equation no longer needs the “-1″ after build 639, but I’m not sure if it is relevant:

plane.z = ((cam.zoom – 1) * cam.focus) – Math.abs(cam.z)

Any tips?

]]> By: Papervision3D - Links para desvendar o caminho das pedras | Cabanoblog http://blog.melihelibol.com/?p=3&cpage=1#comment-44 Papervision3D - Links para desvendar o caminho das pedras | Cabanoblog Tue, 19 Aug 2008 14:12:46 +0000 http://blog.computerelibol.com/?p=3#comment-44 [...] Ramdom Lucubrations Entenda como dimensionar e posicionar em 3D. [...] [...] Ramdom Lucubrations Entenda como dimensionar e posicionar em 3D. [...]

]]> By: pixelplacement.com » Plane Scaling and Positioning with Papervision http://blog.melihelibol.com/?p=3&cpage=1#comment-38 pixelplacement.com » Plane Scaling and Positioning with Papervision Fri, 15 Aug 2008 16:00:03 +0000 http://blog.computerelibol.com/?p=3#comment-38 [...] Go here to check it out. [...] [...] Go here to check it out. [...]

]]> By: admin http://blog.melihelibol.com/?p=3&cpage=1#comment-37 admin Thu, 14 Aug 2008 03:58:48 +0000 http://blog.computerelibol.com/?p=3#comment-37 Hi Tulio, I'll try to. If not I'm planning on writing another article that emphasizes this, but I have a different navigation scheme in mind that I've been meaning to try - it's like a multi axis carousel. I can release the source for that... Hi Tulio,

I’ll try to. If not I’m planning on writing another article that emphasizes this, but I have a different navigation scheme in mind that I’ve been meaning to try – it’s like a multi axis carousel. I can release the source for that…

]]>