I'm trying to switch my fairly large app from Away3D 3.5 to 3.6 and I’m seeing some problems:
Scene3D No more updateLight property. I don’t use lights. Is there an equivalent I should use to make things run a little faster? There is an autoUpdate, but no update. If autoUpdate == false, what am I supposed to call to update? Seems like you should either have both autoUpdate and update or neither. Drag3D Fabrice, we used to be able to pass in coordinates to getIntersect. I found this really handy and use it for all sorts of things. Now apparently it only accepts the mouse coordinates and no args? Comparing the two versions (3.5 and 3.6), the tiny bit of performance gained sure doesn’t seem worth the loss of flexibility. It can’t have been a very performance intensive op anyway. I bet you could keep the flexibility and get back most of the performance diff using Jackson Dunstan’s improved “isNaN” code. Matrix3D Is there code somewhere to convert a vertex or Vector3D to screen coordinates? I had been using some code ripped off from ZoomFocusLens.project: v.x = (v.x * view.camera.viewMatrix.sxx + v.y * view.camera.viewMatrix.sxy + v.z * view.camera.viewMatrix.sxz + view.camera.viewMatrix.tx); etc. Of course it is no longer viable since Matrix3D came along and the code in 3.6’s ZoomFocusLens.project seems a lot more daunting to repurpose. You will notice the similarity of purpose to what I use Drag3D.getIntersect for. Seems like utils to help people go from Away3D coordinates to ordinary Flash graphics coordinates would be very popular. Best, BW
