Hi Fabrice, thank you very much, now it makes sense :) . Nevertheless I spent almost 12 hours to figure out how to move the flying pieces to where they belong to, and I was not able to do it. I must confess that I have massive problems understanding the 3d space in Away3D. Even in a simple-as-can-be test scene with just a cube and a grid-plane in it I run into issues that I cannot explain. I opened up another thread for this one, hopefully the last.
Best regards, Moritz On 7 Jun., 11:28, Fabrice3D <fabric...@gmail.com> wrote: > Looked at it again more closely. You're right, looks like path is indeed > correct, the "holes" are not created by the path but by the position updates > I saw the class has been updated and lost its "auto adjust" in the process. :( > if I trace the position of the extrudes, the result is a 0,0,0. while it > should be by default the first entry. > > I'll try fix this bug asap. In meanwhile you can either offset the position > via movePivot or MoveTo > or use previous version or latest 4.0. > > Fabrice > > On Jun 7, 2011, at 9:55 AM, Moritz wrote: > > > > > > > > > ??? But my path series is like [a,b],[b,c],[c,d]. Please look again at > > this screenshot:http://tiny.cc/cxqod. The black line visualizes the > > path series path for path, there are no holes. Besides that it's not > > like my path-extrusion has holes, it's like they are flying all around > > space. > > > That strange "flying all around space" is what my wondering is all > > about :( . My paths are correct, but the extrusions are all displaced. > > It's like they use a different coordinate system or something. > > > (I'm using 3.6 btw, maybe we talk about different versions?) > > > On 6 Jun., 22:37, Fabrice3D <fabric...@gmail.com> wrote: > >> of course you can, its not to me to tell you how to build your project! :) > >> but see if you generate this way, it will fail kuz your path has holes! > > >> when you pass in one part it works because you say [a, b,c,d,e,f...] > > >> but when you cut you also need to say where it starts and ends > > >> so the path series should be like this [a,b],[b,c],[c,d],[d,e],[ef...] > >> you do now [a,b][c,d][e,f] ... > > >> hence the holes! > > >> Fabrice > > >> On Jun 6, 2011, at 6:06 PM, Moritz wrote: > > >>> :( But that was exactly what I intended to do. You are right: When I > >>> add all segments together to one big path and do a path-extrusion on > >>> that it works allright (See the first picture in my first post). > >>> Nevertheless it is indeed my intention to create a path-extrusion for > >>> each single path-segment (30 mini paths instead of one big one). The > >>> reason for that is that I want to be able to dynamically delete or > >>> replace certain parts of the track without deleting the whole one. So, > >>> do I understand you right in that it is not possible to do path- > >>> extrusions on paths that contain only one path-segment (à 3 > >>> Vector3Ds)? > > >>> If so, then how many path-commands are required for a path to be > >>> successfully path-extruded? > > >>> (Maybe I can bypass the problem by just subdividing my litte mini > >>> paths, so that they still look the same, but contain two path-commands > >>> instead of only one? I'll try that right away ;)) ) > > >>> On 6 Jun., 16:49, Fabrice3D <fabric...@gmail.com> wrote: > >>>> k, runned your code > > >>>> added just before the extrude > >>>> trace("pathSegment:"+pathSegment); > >>>> trace("pathSegment .length:"+pathSegment.length); > > >>>> pathSegment:[object Path] > >>>> pathSegment .length:1 > >>>> pathSegment:[object Path] > >>>> pathSegment .length:1 > >>>> pathSegment:[object Path] > >>>> pathSegment .length:1 > >>>> pathSegment:[object Path] > >>>> pathSegment .length:1 > >>>> pathSegment:[object Path] > >>>> pathSegment .length:1 > >>>> pathSegment:[object Path] > >>>> pathSegment .length:1 > >>>> pathSegment:[object Path] > > >>>> + few more exact same lines of traces. > > >>>> in short the extrusion is correct, your path is not! > >>>> you call many times (like once per segment) your "generateLevelElement" > >>>> method while it should happend only once with a full path definition. > >>>> you probably reset the array instead of filling it somewhere. (finding > >>>> where exactly will be your job :)) ) > > >>>> Fabrice > > >>>> On Jun 6, 2011, at 11:27 AM, Moritz wrote: > > >>>>> I'd be really pleased if you do. For making it as easy as possible for > >>>>> you to reproduce the problem I reduced my code to just the very > >>>>> necessary functions and packed *.fla and *as files in one WinRAR- > >>>>> archive. Unfortunately I cannot find any button to upload it in here, > >>>>> so I am going to send you an e-mail with that file right-away :-) . > > >>>>> Thank you for your great support! > > >>>>> On 6 Jun., 00:27, Fabrice3D <fabric...@gmail.com> wrote: > >>>>>>> Now I wonder why each new path-extrusion gets so awfully offset to > >>>>>>> its predecessor? > > >>>>>> Can you send/show me the path so I can test. please. > > >>>>>> Fabrice > > >>>>>> On Jun 5, 2011, at 4:58 PM, Moritz wrote: > > >>>>>>> Hello alltogether, > > >>>>>>> I have something really weird going on with my PathExtrusions. > > >>>>>>> First I had a function that created one path-extrusion composed of 30 > >>>>>>> generated path-commands and added it to the stage, which worked really > >>>>>>> fine. See a picture here:http://tiny.cc/sa6gb. > > >>>>>>> Then I tried something else: I rewrote that function to create a path- > >>>>>>> extrusion that is always made of only 1 single path-command (or 3 > >>>>>>> Vector3Ds). That path-extrusion always begins at the exact same > >>>>>>> position where the previous path-extrusion has ended (have them all > >>>>>>> stored in an array). Logically if I call this function a 30 times I > >>>>>>> would get a similar result to the picture above. Unfortunately I > >>>>>>> didn't, my level now looks like this:http://tiny.cc/k0sp5. The parts > >>>>>>> are all terribly offset. > > >>>>>>> So I wanted to know what was going on and visualized the path and > >>>>>>> profile I used for the extrusion. I took line-segments to display the > >>>>>>> path and cubes to display the profile-points. The lines and cubes are > >>>>>>> being created in the very same function that is called a 30 times, > >>>>>>> right before the path-extrusion happens. Now look at what I get: > >>>>>>>http://tiny.cc/cxqod. The lines and cubes prove that my paths and > >>>>>>> profiles look exactly like they should while the path-extrusions are > >>>>>>> still flying all over the place. Tracing paths and profiles confirm > >>>>>>> the validity of them both. > > >>>>>>> Now I wonder why each new path-extrusion gets so awfully offset to > >>>>>>> its predecessor? > > >>>>>>> I suspected that the parent-objects drawing position might move after > >>>>>>> each completed path-extrusion, like it does when you use flash's > >>>>>>> curveTo()-function. But I traced the XYZ-coordinates and the pivot- > >>>>>>> points of both the generated path-extrusions and their parent- > >>>>>>> ObjectContainer3D and they all stay at (0, 0, 0) all the time. > > >>>>>>> I really don't understand what's going on there. It's like as if I > >>>>>>> missed some key concept about Away3D :( .
