michaelk

Weird problems in rendering are almost always caused by objects too far away from the origin. I said above that the number was 4km from the origin. Don't quote me on that. It might be 7km. I don't remember exactly.

I agree about room plan. It can get confused by soffits, vaulted ceilings, timber frame roof trusses, etc. With point clouds you can usually get a reasonable slope to a vaulted ceiling, number and approximate size of beams, placement of HVAC supplies, light switches, wall thickness, difference in elevation between floors, etc. Not perfect. But so so so much better than spending a day with two people and a tape measure.

🤣 6. Enjoy not spending an entire day measuring a building knowing that you will miss getting at least one (but probably more) critical measurements. Nomad point clouds aren't perfect, but they are way better than trying to read hand written measurements off of a crowded, incorrect old drawing two weeks after you measured the building 🙂

I see what's going on. You have two exactly coincident rectangles on a 3D plane that are very very very large. 6.5862060122072e192' x 6.5862060122072e192' That's big. VW has issues rendering when objects are more than 4 KM from the origin. This object is way way way beyond that. Delete those two rectangles and the file renders properly.

Or if you look in the same place, Vectorworks > Preferences > Interactive Click on Interactive Appearance Settings… is General - Background - 3D Views set to bright green?

Thanks for posting the image. That IS bright green. Never seen that before. Do you have any Renderworks Backgrounds? Look in the Resource Manager under Renderworks Backgrounds.

@aclymer Welcome to the forum. I'm assuming that you must be in a perspective mode in 3D? If you look at the top left of the VW window there will be a pulldown for view that will say something like Custom View or Right Isometric. Just below that is a view menu pull down perspectives. Yours probably says Narrow, Normal, or Wide Perspective (?). If that's the case the green you are seeing is the default "ground" for perspective views. To test this try setting the the view from a Perspective view to an Orthogonal view. If this makes the green go away then that the issue. You can either work in Orthogonal view or change the color of the ground in perspective views. To change the color of the ground in perspective views: Vectorworks > Preferences > Interactive Click on Interactive Appearance Settings… If you are sorting ascending by Interface Element then General - Background - Perspective Horizon Ground will be about the 7th from the top. There are color pickers on the right side to change the colors. If that's not it, take a screen shot and post it here.

Convert to 2022.zip

@Andrew Lees This is what I've found to make point clouds from Nomad work successfully. 1. Use a recent, pro version of the iPhone to get better LIDAR. 2. Smaller scans. Only do one room at a time. Maybe two if they are small. The issue is drift. The larger the area of scan the more likely that it will "drift" a little. That's why you are seeing some walls duplicated on a different axis. 3. I like to scan around the other side of connecting wall openings to get wall thickness and to help line up adjacent scans. It's important to always have objects or architectural features that will appear in at least one other scan to help line them up later. 4. Watch the screen as you are scanning. There is a slider on the bottom of the screen. It only controls pass through from the camera to the screen while scanning. It has nothing to do with what gets recorded (AFAIK). Try turning it way down so you are seeing primarily or only the points that are being recorded. Sometimes you will see a "jump" happen while recording. I can't prove it but I think that's the scan losing its place. Discard that scan and start over. 5. In the VW drawing, lay out all the rooms from individual scans. It takes a little while to rotate them all to the same direction. I've found that if you use the _VW.pts version of the file, the floors will be level, but not necessarily at Z=0. But they appear to be close to the same - usually negative - Z value. If you've got one scan of a hallway, then it's easier to align the scans of the rooms off the hallway using the door openings. If you keep each scan on a separate layer it makes it easier to work with and you are less likely to select the wrong scan by accident. 7. When you have all your room scans laid out, use the clip cube to cut the top and bottom so you only have a sliver showing about 3 or 4 feet above the floor. Try looking at it in top/plan view as well as top view in shaded rendering to see what shows up better for you. That will give you a floor plan that looks like all the wall lines are about 5/8" thick. You sort of have to draw it not too zoomed in. The closer you get the more you see the spaces between the points. You will quickly find the sweet spot. 8. Once you draw your walls, guess at window and door sizes and locations. Select one wall, turn on the clip cube and set the visibility to wireframe. Now it's really fast to use the new drag handles on doors and windows align them with then scans. 9. It also works outside. I've had pretty good success using it to get eave overhangs, roof pitches, hardscapes, external columns, existing tree sizes and locations. About half the time on a building the size you are working on it will hold together long enough to scan the exterior of the entire residence well enough to get an accurate footprint. I haven't tried this yet, but I've heard that using a tripod for your iPhone that rotates around 360 and scanning several times in the same room produces better results.

Now I see it! I didn't realize you were copying to an already existing database row. I'll write up a bug report. Until it gets fixed (no guarantee when that will be) you'll have to first right click on the row header, choose spreadsheet, then paste.

I wonder if this is another Mac OS update issue. Can you post a file to test?

Worksheet Test 1.mp4

When I copy/paste on your file it works correctly!

Do any of your database header cells reference other cells?

This is what I see when I do that. WorksheetDatabaseCopyPaste.mp4