Yeah, I'd say it's going to be hardware specific - there are a couple other demos that crash for me, but work for my mate, and we're both on the latest Flash Player 11.0.1.3d.
Would be interesting to know what the Away3D community know about how Adobe are testing Molehill - are these hardware related crashes going to go away once FP11 is out of incubator? Or do Adobe only plan to support a limited subset of pc/gpu combinations? Again, this is probably a question for the Adobe forums - I'll have to post a couple questions over there and give an update... Adobe did announce in the forums that they are aiming for a Q2 release of FP11. Given that FP10.3 only just came out, and that we are still having these major crashes with FP11, I reckon it's going to be a while before we see FP11 released to the public... On Tue, Jun 14, 2011 at 2:43 PM, Choons <chadkim...@gmail.com> wrote: > oh duh it says it right there at the top. I haven't updated to the > latest FP 11 player yet so I hope what I made works on the one > > On Jun 13, 11:40 pm, Choons <chadkim...@gmail.com> wrote: > > Hi Jahiro - huh not sure what that means. Which version of the FP 11 > > are you using? > > > > On Jun 13, 11:11 pm, Jahiro <macro.mar...@gmail.com> wrote: > > > > > > > > > > > > > > > > > Hey Choons, > > > > > Looks beautiful for about 3 seconds, then it actually crashes my > > > NVIDIA Card with the below error :( > > > > > Win7, Google Chrome, Flash Player 11.0.1.3d, HP Elitebook 8540p, > > > NVIDIA NVS 5100M > > > > > Error: Error #3600: No valid program set. > > > at flash.display3D::Context3D/drawTriangles() > > > at > away3d.materials.passes::MaterialPassBase/render()[C:\Users\Chad > > > \Desktop\Away3DCoreGit\src\away3d\materials\passes\MaterialPassBase.as: > > > 193] > > > at > away3d.materials.passes::DefaultScreenPass/render()[C:\Users\Chad > > > \Desktop\Away3DCoreGit\src\away3d\materials\passes > > > \DefaultScreenPass.as:427] > > > at > away3d.materials::MaterialBase/renderPass()[C:\Users\Chad\Desktop > > > \Away3DCoreGit\src\away3d\materials\MaterialBase.as:342] > > > at > away3d.core.render::DefaultRenderer/drawRenderables()[C:\Users\Chad > > > \Desktop\Away3DCoreGit\src\away3d\core\render\DefaultRenderer.as:103] > > > at > away3d.core.render::DefaultRenderer/draw()[C:\Users\Chad\Desktop > > > \Away3DCoreGit\src\away3d\core\render\DefaultRenderer.as:48] > > > at > away3d.core.render::RendererBase/executeRender()[C:\Users\Chad > > > \Desktop\Away3DCoreGit\src\away3d\core\render\RendererBase.as:329] > > > at > away3d.core.render::RendererBase/render()[C:\Users\Chad\Desktop > > > \Away3DCoreGit\src\away3d\core\render\RendererBase.as:310] > > > at away3d.containers::View3D/render()[C:\Users\Chad\Desktop > > > \Away3DCoreGit\src\away3d\containers\View3D.as:351] > > > at F16UVTest/onEnterFrame()[C:\Users\Chad\Documents\AS3 > Flash\Projects > > > \F16UVTest\src\F16UVTest.as:454] > > > > > On Jun 14, 8:53 am, Choons <chadkim...@gmail.com> wrote: > > > > > > Hi guys. Finished my Broomstick F-16 flying demo. It uses a a simple > > > > large plane for the terrain and the motion effect is all done by > > > > scaling and offsetting the UV values of the terrain while the > airplane > > > > remains stationary. I kind of stumbled on the effect by accident. It > > > > solves a couple of problems automatically- the horizon looks pretty > > > > natural which was a big problem when I actually moved the F-16 higher > > > > along the y axis, and the scaling handles the apparent speed vs > > > > altitude issue. Try it out and let me know how it runs on your > > > > machines since I only tested it on my desktop so far. It's Broomstick > > > > so you need the FP 11 installed to run it. > > > > > >http://blam3d.com/demos/f16uvtest.html >
