Rich, also try the PoissonMesh node; It builds a mesh that might take care of the edges better.
On 1 March 2013 10:56, Rich Bobo <[email protected]> wrote: > > > On Feb 28, 2013, at 4:31 PM, Deke Kincaid <[email protected]> wrote: > > Hi Rich > > I just ment when you use the geo input on the modelbuilder that it > essentially snaps any geo your creating in the modelbuilder into roughly > the same scale/space as the one in the input. So while you can’t use it to > modify/edit existing geo, you can use it to almost add additional geo onto > it. > > > I see that now. Thanks… > > Rich > > > > ----- > Deke Kincaid > Creative Specialist > The Foundry > Mobile: (310) 883 4313 > Tel: (310) 399 4555 - Fax: (310) 450 4516 > > The Foundry Visionmongers Ltd. > Registered in England and Wales No: 4642027 > > > On Thu, Feb 28, 2013 at 11:41 AM, Rich Bobo <[email protected]> wrote: > >> Deke, >> >> I have been unable to get ModelBuilder to modify a mesh created by >> PointCloudGenerator. I sent an email to Support a little while ago with the >> object attached so they can see what's going on… Have you tried modifying >> a mesh created by PointCloudGenerator, yet? I can selected any type of >> elements or the entire object, but I get no transformation axes to >> manipulate whatever I've selected. If, however, I create a default shape in >> the same node - a cube, for instance - I have no problem modifying it. I'm >> wondering if the mesh that PointCloudGenerator creates is a particular type >> of geo structure that ModelBuilder is not programmed to handle…? >> >> >> Rich >> >> >> >> On Feb 27, 2013, at 3:25 PM, Deke Kincaid <[email protected]> wrote: >> >> You can plug the pointcloud or mesh generated by it into the geo input of >> the ModelBuilder so you get roughly the same scale. >> >> ----- >> Deke Kincaid >> Creative Specialist >> The Foundry >> Mobile: (310) 883 4313 >> Tel: (310) 399 4555 - Fax: (310) 450 4516 >> >> The Foundry Visionmongers Ltd. >> Registered in England and Wales No: 4642027 >> >> >> On Wed, Feb 27, 2013 at 12:20 PM, Rich Bobo <[email protected]> wrote: >> >>> Marten, >>> >>> Thanks for the reply! I was afraid of that. Oh, well… ;^) And, thanks >>> for the link to Polytools - I'll definitely check them out! The first >>> thing I plan to try, though, is to see how much luck I have extending the >>> mesh with the new ModelBuilder node. I used it for a photo of a house that >>> I wanted to model and re-project and it worked pretty well. This may be a >>> bit more challenging, since the glacier and rocks have a ton of craggy >>> detail, but maybe I can cheat (a lot)! ;^) >>> >>> Thanks, >>> Rich >>> >>> >>> On Feb 27, 2013, at 2:48 PM, Marten Blumen <[email protected]> wrote: >>> >>> Mesh edge clipping is normal - you can use GreyAngle's Polytools, >>> PolyEdit to extend the edges. >>> >>> http://greyangle.com/nuke/docs/geometry/PolyEdit.htm >>> >>> >>> On 28 February 2013 08:08, Rich Bobo <[email protected]> wrote: >>> >>>> Hey all, >>>> >>>> I've finally had a chance to start messing around with the new >>>> PointCloudGenerator node. I'm hoping some of you with more experience in >>>> this area can help me with a couple of things that I don't quite >>>> understand… >>>> >>>> The main question I have deals with point coverage. I have a test clip >>>> I'm using that is shot from a boat, looking onshore at some glacial ice, >>>> with rocky mountains in the background. I can get a lovely CameraTrack, >>>> thanks to all of the available points to track. The parallax is good as the >>>> boat moves up and down and goes slowly past and around the glacier ice. In >>>> the PointCloud Generator, I've tracked points and get a pretty good lock >>>> with points on the foreground ice and on the background rocks. However, I >>>> do not get full coverage of points in the shot. For example, the foreground >>>> ice is truncated on the left hand side at the beginning of the shot (the >>>> boat moves from left to right across the scene, so the footage moves from >>>> right to left). Also, as the boat bobs up and down, it reveals more >>>> truncated points at the top. I never lose coverage on the right of the >>>> frame, however. I can't tell what's happening on the bottom of the frame, >>>> since I am masking out the water that is there. I'm guessing that the lack >>>> of coverage on the left probably has to do with the fact that there are no >>>> prior frames to look at for parallax reference. But, still, a regular >>>> camera track seems to have more coverage. I can't quite wrap my head around >>>> this. Can anyone explain it to me? And, is there a way to do the analysis >>>> to get greater point cloud coverage…? >>>> >>>> I watched the demo video that Steve Wright put together - >>>> https://vimeo.com/54931986 - and his mountains clip happens to be very >>>> similar to my test clip. Looking at his result, I can see that he is also >>>> getting the same sort of clipping - not getting complete coverage of his >>>> scene. So, maybe the rest has to be hand modeled after a mesh is generated? >>>> I mean, in order to do a projection on a mesh derived from the point cloud, >>>> you'd absolutely have to extend it. Is this always a manual process…? >>>> >>>> Thanks for any help! >>>> >>>> Rich >>>> >>>> >>>> Rich Bobo >>>> Senior VFX Compositor >>>> Armstrong-White >>>> http://armstrong-white.com/ >>>> >>>> Email: [email protected] >>>> Mobile: (248) 840-2665 >>>> Web: http://richbobo.com/ >>>> >>>> "I have long been of the opinion that if work were such a splendid >>>> thing the rich would have kept more of it for themselves." >>>> - Bruce Grocott (1940 - ) >>>> >>>> >>>> >>>> >>>> >>>> >>>> _______________________________________________ >>>> Nuke-users mailing list >>>> [email protected], http://forums.thefoundry.co.uk/ >>>> http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users >>>> >>> >>> _______________________________________________ >>> Nuke-users mailing list >>> [email protected], http://forums.thefoundry.co.uk/ >>> http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users >>> >>> >>> >>> _______________________________________________ >>> Nuke-users mailing list >>> [email protected], http://forums.thefoundry.co.uk/ >>> http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users >>> >> >> _______________________________________________ >> Nuke-users mailing list >> [email protected], http://forums.thefoundry.co.uk/ >> http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users >> >> >> >> _______________________________________________ >> Nuke-users mailing list >> [email protected], http://forums.thefoundry.co.uk/ >> http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users >> > > _______________________________________________ > Nuke-users mailing list > [email protected], http://forums.thefoundry.co.uk/ > http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users > > > > _______________________________________________ > Nuke-users mailing list > [email protected], http://forums.thefoundry.co.uk/ > http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users >
_______________________________________________ Nuke-users mailing list [email protected], http://forums.thefoundry.co.uk/ http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users
