Comments on: Papervision3D 2.0 : Public Alpha Release. http://www.unitzeroone.com/blog/2007/12/04/papervision3d-20-public-alpha-release/ A blog written by Ralph Hauwert, freelance developer&consultant, specialized in realtime visualisation, 3D and application development. Currently working on Aviary.com. Mon, 28 Jun 2010 17:24:19 +0000 http://wordpress.org/?v=2.9.2 hourly 1 By: Manuel Lepn http://www.unitzeroone.com/blog/2007/12/04/papervision3d-20-public-alpha-release/comment-page-1/#comment-1070 Manuel Lepn Wed, 02 Jul 2008 06:50:53 +0000 http://www.unitzeroone.com/wordpress/?p=109#comment-1070 I would like to get the Papervision3D 2.0 I would like to get the Papervision3D 2.0

]]> By: kay http://www.unitzeroone.com/blog/2007/12/04/papervision3d-20-public-alpha-release/comment-page-1/#comment-317 kay Thu, 10 Jan 2008 16:33:25 +0000 http://www.unitzeroone.com/wordpress/?p=109#comment-317 2.0 is absolute amazing! i'm interested in "New Rendering architecture". Is it possible tha you explain me the renderpipeline in a few simple steps?! i had posted my attempt on pv3d list (http://www.nabble.com/Renderpipeline-of-Papervision3D-td14696754.html) , but no answer so far. thanks a lot kay 2.0 is absolute amazing!

i’m interested in “New Rendering architecture”. Is it possible tha you explain me the renderpipeline in a few simple steps?!

i had posted my attempt on pv3d list (http://www.nabble.com/Renderpipeline-of-Papervision3D-td14696754.html) , but no answer so far.

thanks a lot
kay

]]> By: Mr.doob http://www.unitzeroone.com/blog/2007/12/04/papervision3d-20-public-alpha-release/comment-page-1/#comment-316 Mr.doob Fri, 07 Dec 2007 07:52:06 +0000 http://www.unitzeroone.com/wordpress/?p=109#comment-316 GOOD JOB! GOOD JOB!

]]> By: christian http://www.unitzeroone.com/blog/2007/12/04/papervision3d-20-public-alpha-release/comment-page-1/#comment-315 christian Thu, 06 Dec 2007 21:43:18 +0000 http://www.unitzeroone.com/wordpress/?p=109#comment-315 Fantastic, thanks a lot Ralph, very appreciated. On FDT3 it is almost perfect, only Mesh3D has an error, how comes that you pass 3 parameters to Math.min/max? :) Fantastic, thanks a lot Ralph, very appreciated. On FDT3 it is almost perfect, only Mesh3D has an error, how comes that you pass 3 parameters to Math.min/max? :)

]]> By: Stef http://www.unitzeroone.com/blog/2007/12/04/papervision3d-20-public-alpha-release/comment-page-1/#comment-314 Stef Thu, 06 Dec 2007 01:03:28 +0000 http://www.unitzeroone.com/wordpress/?p=109#comment-314 Thanks so much ! That's the release I was looking for. And thanks a lot for all who contributes, you guys have made an amazing job :-) Thanks so much ! That’s the release I was looking for. And thanks a lot for all who contributes, you guys have made an amazing job :-)

]]> By: Chris http://www.unitzeroone.com/blog/2007/12/04/papervision3d-20-public-alpha-release/comment-page-1/#comment-313 Chris Wed, 05 Dec 2007 17:20:59 +0000 http://www.unitzeroone.com/wordpress/?p=109#comment-313 Thanks so much for posting this! I couldn't wait to try it out, so I grabbed it from Google code and started playing with it. I got it to work, as a library project in flex ( using the example you posted above), but I had to work around a few things. I'm sure some (or most) of it was unnecessary because of something simple I'm unaware of, but whatever. Here it is anyway: I couldn't find these files: Vertex2D FaceInstance3D InteractiveBitmapMaterial As a result of those missing files (and a few other errors I didn't get a chance to dig too far into), I removed these files from the build: org.papervision3d.materials.utils.BitmapMaterialTools org.papervision3d.core.culling.CompositeTriangleCuller org.papervision3d.objects.special.Sound3D I made the following changes to the code(some changes were to files that I later removed from the build, but I left those changes in just to show everything I did): org.papervision3d.objects.special.Sound3D => add: import org.papervision3d.objects.DisplayObject3D; org.papervision3d.materials.special.CompositeMaterial => add: import org.papervision3d.core.material.TriangleMaterial; org.papervision3d.materials.special.CompositeMaterial => remove: import org.papervision3d.materials.TriangleMaterial; org.papervision3d.view.BasicView => add: import org.papervision3d.core.view.IView; org.papervision3d.objects.special.Frustum3D => Number3D is in the core.math package rather than just the core package org.papervision3d.objects.primitives => add: import org.papervision3d.core.math.NumberUV; org.papervision3d.objects.parsers.MD2 => AnimationFrame is under core.animation.core instead of just animation.core org.papervision3d.core.components.as3.flash9 => BasicRenderEngine is under papervision3d.render instead of papervision3d.core.render org.papervision3d.objects.parsers.DAE => PointLight3D is under papervision3d.lights instead of papervision3D.core.geom.lights org.papervision3d.objects.special.Sound3D => Number3D is in the core.math package rather than just the core package org.papervision3d.objects.special.Sound3D => Matrix3D is in the core.math package rather than just the core package org.papervision3d.objects.parsers.MD2 => MorphController is under papervision3d.core.animation.controllers instead of papervision3d.animation.controllers org.papervision3d.objects.parsers.MD2 => SimpleController is under papervision3d.core.animation.controllers instead of papervision3d.animation.controllers org.papervision3d.objects.parsers.MD2 => AnimationEngine is under papervision3d.core.animation.core instead of papervision3d.animation.core org.papervision3d.objects.parsers.MD2 => add org.papervision3d.core.math.NumberUV; org.papervision3d.view.BasicView => BasicRenderEngine is under the papervision3d.render package rather than papervision3d.core.render org.papervision3d.objects.special.Frustrum3D => LineMaterial is under papervision3d.materials.special rather than papervision3d.materials org.papervision3d.objects.special.UCS => LineMaterial is under papervision3d.materials.special rather than papervision3d.materials org.papervision3d.materials.BitmapWireframeMaterial => add altUV:Matrix = null as the last parameter in the drawTriangle function to correnctly implement the interface org.papervision3d.materials.special.CompositeMaterial => add altBitmap:BitmapData = null, altUV:Matrix = null as the last two parameters in the drawTriangle function to correnctly implement the interface org.papervision3d.materials.special.CompositeMaterial => add flash.display.BitmapData for new parameter in drawTriangle function org.papervision3d.materials.special.CompositeMaterial => add flash.geom.Matrix for new parameter in drawTriangle function There may be something simple I glossed over, but these changes made it work for me. This is some really bad ass stuff here, I can't wait to see the projects that people will do using the new functionality. Thanks so much for posting this! I couldn’t wait to try it out, so I grabbed it from Google code and started playing with it. I got it to work, as a library project in flex ( using the example you posted above), but I had to work around a few things. I’m sure some (or most) of it was unnecessary because of something simple I’m unaware of, but whatever. Here it is anyway:

I couldn’t find these files:

Vertex2D
FaceInstance3D
InteractiveBitmapMaterial

As a result of those missing files (and a few other errors I didn’t get a chance to dig too far into), I removed these files from the build:
org.papervision3d.materials.utils.BitmapMaterialTools
org.papervision3d.core.culling.CompositeTriangleCuller
org.papervision3d.objects.special.Sound3D

I made the following changes to the code(some changes were to files that I later removed from the build, but I left those changes in just to show everything I did):
org.papervision3d.objects.special.Sound3D => add: import org.papervision3d.objects.DisplayObject3D;
org.papervision3d.materials.special.CompositeMaterial => add: import org.papervision3d.core.material.TriangleMaterial;
org.papervision3d.materials.special.CompositeMaterial => remove: import org.papervision3d.materials.TriangleMaterial;
org.papervision3d.view.BasicView => add: import org.papervision3d.core.view.IView;
org.papervision3d.objects.special.Frustum3D => Number3D is in the core.math package rather than just the core package
org.papervision3d.objects.primitives => add: import org.papervision3d.core.math.NumberUV;
org.papervision3d.objects.parsers.MD2 => AnimationFrame is under core.animation.core instead of just animation.core

org.papervision3d.core.components.as3.flash9 => BasicRenderEngine is under papervision3d.render instead of papervision3d.core.render
org.papervision3d.objects.parsers.DAE => PointLight3D is under papervision3d.lights instead of papervision3D.core.geom.lights

org.papervision3d.objects.special.Sound3D => Number3D is in the core.math package rather than just the core package
org.papervision3d.objects.special.Sound3D => Matrix3D is in the core.math package rather than just the core package

org.papervision3d.objects.parsers.MD2 => MorphController is under papervision3d.core.animation.controllers instead of papervision3d.animation.controllers
org.papervision3d.objects.parsers.MD2 => SimpleController is under papervision3d.core.animation.controllers instead of papervision3d.animation.controllers
org.papervision3d.objects.parsers.MD2 => AnimationEngine is under papervision3d.core.animation.core instead of papervision3d.animation.core

org.papervision3d.objects.parsers.MD2 => add org.papervision3d.core.math.NumberUV;

org.papervision3d.view.BasicView => BasicRenderEngine is under the papervision3d.render package rather than papervision3d.core.render

org.papervision3d.objects.special.Frustrum3D => LineMaterial is under papervision3d.materials.special rather than papervision3d.materials
org.papervision3d.objects.special.UCS => LineMaterial is under papervision3d.materials.special rather than papervision3d.materials

org.papervision3d.materials.BitmapWireframeMaterial => add altUV:Matrix = null as the last parameter in the drawTriangle function to correnctly implement the interface
org.papervision3d.materials.special.CompositeMaterial => add altBitmap:BitmapData = null, altUV:Matrix = null as the last two parameters in the drawTriangle function to correnctly implement the interface
org.papervision3d.materials.special.CompositeMaterial => add flash.display.BitmapData for new parameter in drawTriangle function
org.papervision3d.materials.special.CompositeMaterial => add flash.geom.Matrix for new parameter in drawTriangle function

There may be something simple I glossed over, but these changes made it work for me. This is some really bad ass stuff here, I can’t wait to see the projects that people will do using the new functionality.

]]> By: Mr.doob http://www.unitzeroone.com/blog/2007/12/04/papervision3d-20-public-alpha-release/comment-page-1/#comment-312 Mr.doob Wed, 05 Dec 2007 15:39:48 +0000 http://www.unitzeroone.com/wordpress/?p=109#comment-312 I love the screencast :) I love the screencast :)

]]> By: Owen van Dijjk http://www.unitzeroone.com/blog/2007/12/04/papervision3d-20-public-alpha-release/comment-page-1/#comment-311 Owen van Dijjk Wed, 05 Dec 2007 09:14:04 +0000 http://www.unitzeroone.com/wordpress/?p=109#comment-311 Congrats on getting it out before 12:00 :) Congrats on getting it out before 12:00 :)

]]>