Search the Community
Showing results for tags 'alignment'.
Found 3 results
I'm no expert builder, but I bought Zimberlab's mesh wall pack and have been playing with it for some time. I'm working on the fourth prototype of this particular house, after learning more and more tools that help me make it perfect. I last learned about the align tool. I've made a floor or two before calling it a day and I know that everything was lined up PERFECTLY. I've found out that linking it causes it to screw up, so I've left it unlinked, and scooped it all up. This time when I rezzed it, pieces are STILL becoming unaligned. I see the edges of a straight wall that took multiple pieces and it's bugging the heck out of me. I can't keep fixing it and I rather not put it in a rez-box just yet. I don't even know if it will work like that. I could try for test #4. There's just so many mesh pieces I was hoping I wouldn't have to do that. I've been in the same sandbox building it the whole time. Any suggestions? Thanks. I haven't posted in forums before so I don't know if there's an answer out there.
I'm building a very large and complex shaped house, which at the moment is made up of 7 separate objects and will likely increase further and it has many curved surfaces that have to be accurately aligned together when assembled inworld. So far on the beta grid I've just been eyeballing the alignment to check build quality and physics models etc, but as I progress further away from what I'll call my anchor object (first object imported) that I started aligning subsequent objects to any discrepancy in the initial alignments is telescoping out to larger misalignments further down the assembly process. This hadn't bothered me so far as I had read in the past of something called cube/box alignment where each mesh object is imported as a linkset with a common single cube that you then make the root prim and set to say X:10 Y:10 Z:10 and as you import each object you set that root prim to the same coordinates then delete it and everything should align perfectly, which it does. However the problem that I've run into is that it is breaking all my physics models. First of all for ease I used just one common cube for all the mesh objects set to 0,0,0, , but inworld as I imported pieces that were further away from that location the cube was outside of the bounding box or rather the bounding box that was dictated in the original object and it broke its physics model. I slapped myself for not realising that would happen beforehand and then gave each object its own cube but nestled within each object's bounding box and each cube was a set distance from the previous one so that I could easily replicate the offset inworld. Once again though, for whatever reason the physics models were broken and I ended up with convex hulls even though the prim option was there and enabled. My only workaround at the moment is to use the method above to get everything inworld and correctly aligned and then import the objects again without a cube and copy paste them to already aligned objects' coordinates, which I guess will work, but is tedious and obviously more expensive once I import to the main grid. So my questions are, does the cube alignment system really work, if so what am I doing wrong and is there an easier or better way? I did search the forum(s), but I couldn't find a similar topic or the original thread/post I recalled about this process so thanks in advance for anybody who links/points me to some.
Hi everyone! I'm posting today about my mesh body I am making. It's fitmesh, it's bento, and sadly the neck is giving me issues. When I look at the weights on the Avastar mesh and copy those weights to my custom body - even when I use the exact correct neck-piece of geometry from the Avastar - there is a gap between my custom body's neck and my CATWA Bento female head. Here's a picture of how the weights look for Avastar's neck: And, here's the weights for my custom body's neck: And here's the neck inworld when my avatar turns it's head to the side: Any help on this issue would be appreciated.