Jump to content

tekbench

Member
  • Content Count

    61
  • Joined

  • Last visited

Community Reputation

29 Great

About tekbench

  • Rank
    Apprentice

Personal Information

  • Occupation
    Audio Engineer
  • Location
    United States

Recent Profile Visitors

497 profile views
  1. tekbench

    make basic tools persistent

    @Matt Overton - Yes. I am a huge 'X' shortcut key user. Then I get into annotations, and editing text in viewports and end up cursing myself for having the muscle memory in my hands.
  2. tekbench

    3d point clouds - need to rethink

    @Peter Neufeld - Thanks so much for the info on 'Cloud Compare'. I downloaded it, and it gives me a very clear view into the source material. that is an incredibly powerful app. The Vectorworks import point cloud options' tool set seems, well, totally useless. You can import (in my case) 20,000,000 points in a few seconds. It's not until you get into 'extract 3d Loci' that Vectorworks seems to do anything. Frankly, I can find zero things that the Import tool is good for. It should just be like a PDF. Drag it and drop it into the vectorworks document.
  3. tekbench

    Electrical Switches

    I gave this a shot. I'm not able to reproduce your issue. Both items scale just fine for me. If I have some time I'll poke around on it some more. Kelly.
  4. tekbench

    Berm/Swale Question - How do I delete it?

    Nice. It sure seems that 'Delete' isn't a thing. The Swale/Berm tool looks to be a way to quickly 'hard' modify the site plan. Kind of like a hard edit tool. Undo doesn't work, delete doesn't work, and none of the 'select' type tools will select the berm object once created. So the 'Berm' tool doesn't put an object, or a 'thing' on your site plan. It simply permanently modifies your site plan shape. If you need a berm, I think the only way to do that intelligently is to create it as a poly, make it a 3d blob, and put it on the drawing.
  5. tekbench

    Berm/Swale Question - How do I delete it?

    Answering my own question here. You can't. If you have, in my case, 3 berms drawn, and one berm that is incorrect, the only thing you can do is 'recreate from source data'. that deletes ALL the surface modeling you've done. I'm drawing a parking area, with interlocking berms to hide cars from both the highway and from the interior site elements. I have berm one and berm two right where I want them. Berm three gets drawn incorrectly. Only recourse here is to delete all the work i've done using 'Recreate from source data', then re-draw all three berms. Unless i'm missing something, this is your only option to delete a berm or swale created in the site sculpting tool. I think I'm back to creating a 3D poly/shape, and calling and it a berm.
  6. This seems silly, but here goes: How does one delete a berm? It appears that once i've created it, it is permanently attached to the site plan. I can pull the points of the triangles around with the Surface Sculpting tool, but I can't just seem to delete the whole berm. Am I missing something?
  7. tekbench

    .LAZ file coming in to document way out of scale.

    @bgoff any update on the workflow that you used to fix Vectorworks to accept the .LAZ file at the correct scale? I have some more work coming in, and using the .LAZ file is something we really need in the workflow.
  8. tekbench

    .LAZ file coming in to document way out of scale.

    I spent all day yesterday tweaking on this drawing. Some talking points and a new bug has appeared (I think): KEY INFO NEEDED - Need to know how this was re-scaled/fixed/adjusted to be the correct dimensions. ORIGINAL BUG - The original issue of not being able to correctly import .LAZ files is still accurate and still stands. NEW BUG - Can't seem to undo 'Create Berm' within the edit surface window without hanging machine. Regardless of how easy it was to create the berm or work with the berm. If you pull the .LAZ in, isolate points, and create a Site Plan using the all the 'defaults' - depending on your system this is fine. Otherwise It will end your afternoon with a beachball. If you pull the .LAZ in, isolate points, and create a Site Plan using custom settings that seem fairly reasonable - depending on your system this can end your afternoon with a beachball. If you pull the .LAZ in, isolate points, and create a Site Plan using about 50,000 points- in my case on my hardware this can be a delight. What I can say is this - The number of points selected in the 'create site plan' dialog is key in determining how long your computer will churn on the file. the 'other stuff' matters, but in short, this number is critical IMHO. I've attached a file called "LAZ File Corrected FRESHTEST" for anybody that wants to try this out. The file is 3.4meg. hardly a large file. ON MY HARDWARE - NON-FUNCTIONING METHOD, CAN'T SEE THE BUG DUE TO THE BEACHBALLS AND CRASHES - Open the file. Select the isolated Point Cloud. Landmark - Create Site Model - Site Model from Source Data. There are 111,683 points. Pull all those points in. Select 3D Mesh, no smoothing and all the rest of the default dialogs. Click OK. Site model appears eventually. Maybe an hour later, maybe 11 hours later (seriously, all night, finally appeared), maybe never. maybe crashes. If it DOES appear- Click on 'Edit Proposed Site Model Surface' Wait. Select the Berm/Swale tool. Click ok on the dialog. Wait. Draw your Berm with settings 16' wide, 10' tall. Make it a couple hundred feet long, with a little bit of a curve. Wait. It appears. Maybe an hour later, maybe never. maybe crashes. If it DOES appear - Apple+Z to Undo Crash. Woe be unto you. Beachball. FUNCTIONING METHOD, BUT BUG UNCOVERED - Open the file. Select the isolated Point Cloud. Landmark - Create Site Model - Site Model from Source Data. There are 111,683 points. Move slider to about 50,000 points. Select 3D Mesh, no smoothing and all the rest of the default dialogs. Click OK. Site model appears quickly. Click on 'Edit Proposed Site Model Surface' Wait a tiny little bit. Select the Berm/Swale tool. Click ok on the dialog. Wait a tiny little bit. Draw your Berm with settings 16' wide, 10' tall. Make it a couple hundred feet long with a little bit of a curve. It appears rather quickly. A delight. Apple+Z to Undo Crash. Woe be unto you. Beachball. From what I can tell, 111,683 points to create a site plan will crush the spirit of a brand new MacBook Pro. Drawing will not function, will not work and will constantly hang and crash. 50,000 points is a delight and an ease to work with and looks OK on a 2019 MacBook Pro. In BOTH of these cases - You can't 'undo' create berm in the site surface edit window. It will hang, and eventually you will need to crash out of the application. Hope these repro steps and attached file help get to the bottom of the issue. Machine performance details also attached. Cinebench score of 2899 points. Screen shot of my 'about' page. LAZ File Corrected FRESHTEST.vwx
  9. Yeah. I'm doing some reading on this. If I have a nice LiDAR point cloud, I'd like to use that level of resolution. But as you and @Benson Shaw have pointed out, it is a trade off. I'm testing things today by ramping down the number of points i'm using in my site model to a 'reasonable' level for the machine at hand. It sounds trite, but the honest answer to the original question is: "It totally depends". As for Windows OS vs an integrated Software/Hardware solution - It's not Apples to Apples. The overhead that the Windows OS hangs on hardware can vary pretty wide. Especially if you are using a fixed, non-auto updating version or a 'retail' version of Windows. When you're on a Mac, the closed garden rule applies, and you can often get better actual 'performance' out of your software with 'lower' benchmarks. Ive seen this over the last 25 years working very closely with both platforms on audio and video editing setups. I can say, without hesitation, that under no circumstances are straight benchmarks ever the whole story. Ever. It's all about the thousands of variables each system has to offer. Remember WindowsME? It was horrible. The worst garbage Redmond released upon the planet. Unless you cared about sample accurate timecode or digital audio. Then, it was the only option if you didn't want glitching and popping in your audio recordings. Benchmarking Pentium chips VS Athlon back in the day also showed that sometimes the 'less powerful' chip did what we wanted, better and sometimes faster. This was the case with CoolEdit2000 (remember that?!) to some level. Per this - "However... I am now investigating the possibility of a workspace outside the home. Probably a fixed desk in a shared workspace. Ideally I'd like to retain the ability to work in either location. I'd probably keep my multiple monitor setup at home, and invest in another set of monitors at the workspace. As for the 'computer' bit of the setup, options seem to be:" I do this exact thing. Except I use one big monitor in each location instead of dual. As of last week, I have moved to 2 laptops. One 2016 Macbook pro (very first model), and now one brand new Macbook pro (current model). At work, I use a Kensington 'expert mouse' trackball and a CalDigit dock with an LG 43" display. At home I have a Kensington 'expert mouse' trackball, a wad of USB cables, 4 empty coffee cups stacked on a drafting table and an ACER 4K Thunderbolt display. Prior to this, I would just shuttle my laptop between work and home. I designed a lot of AV systems that way. I did a lot of site work documenting AV systems and as-built scenarios all over the world. I did a lot of residential design stuff for personal use that way. I can't say I was held back in those circumstance. I had a nice 4 year run without being worried about my setup. Generated some very nice drawings with Heliodon tools, some surface textures and some, albeit rudimentary, site plans. Prior to the MacBook Pro, I used my old MacBook air until VW no longer ran on the CPU. And that was a fair lifespan for that laptop. The good news about sticking with a Mac is the resale/eBay value is almost always where you can scrape some of your initial investment back. If you work that into the equation, you come up with a very clear answer: "It totally depends". I have no answer for you. Only things to consider and confuse. But FWIW, I'm working with 2 laptops in 2 work environments. And it's not too bad other than site model stuff or heavy duty rendering.
  10. I just had my company buy me a brand new MacBook Pro. Results below. I will say - I can do lots of 3D Building/Construction stuff, and some rendering stuff on this with very few issues. The Civil stuff, Site Modeling and 'berm' creation have been pretty slow. If you are a civil engineering or Landscape person, not sure this tiny laptop is for you. In any event, i'm churning along fairly well with my basic stuff. I've been running VW on a laptop for years. It's a total trade-off. It's fantastic to stand on a foundation pour, look at a laptop and make corrections. It's not fun waiting for a site model to render. All Night. I'm getting ready to buy a desktop just because of the Site Model stuff i'm getting tasked with. Also - TO BE CLEAR - I have absolutely zero idea what any of the numbers in the Cinebench window are. But they apparently are important to those who care about this kind of stuff. Macbook Pro. CalDigit dock, 4K LG 40-something inch display.
  11. tekbench

    .LAZ file coming in to document way out of scale.

    OK. This is plenty to get me started. I appreciate that. I still would like to get the actual import of .LAZ files sorted out. Or at least get how you managed to fix the point cloud within Vectorworks to get it to relatively the correct size and shape. Or at the very least, get a clear breakdown from engineering on how the tool is supposed to work, and if there has been a bug or known issue assigned to the problem. Thanks again for fixing that particular file for me.
  12. tekbench

    .LAZ file coming in to document way out of scale.

    Ahhh. cool. appreciate it. I see it in the ol' inbox. Thanks.
  13. tekbench

    No Stories, No Problem

    I'm in the process of trying this new story workflow. I've always done floors as slabs or layers and refined them as needed. One for joists, one for plywood, one for gyp or concrete fill - Like Christiaan described above. I think like a contractor (coming from actually building things) so my flow is very much like building. From the ground up, one 'thing' at a time. If that thing is suitably complicated, or needs to be in the drawing with suitable detail, I make a new layer for it. I never took time to use the binding functionality of walls to floors. it feels easier to just get my horizontal/walking surface planes built, then build the walls up to wherever they are supposed to end. If a wall is supposed to hit the ceiling above, at some point I will be bound by the overall height of the structure. The wall height usually dictates the ceiling level, not the other way around for me. So Stories seems to be a natural solution for that, but I just haven't really worked through the tool. Thanks again @Wes Gardner for the tips. Maybe i'll give it another push.
  14. tekbench

    .LAZ file coming in to document way out of scale.

    Just checking in here. Haven't seen the fixed/corrected file yet. I tried to scale my point cloud yesterday (that worked), but after 19 hours of building a site model, VW just hung. So i'm interested in if this new scaled file you guys are putting together works any better to build a site model.
  15. tekbench

    .LAZ file coming in to document way out of scale.

    Thanks for that. I'll keep a look out for the new file. Again, every other software package seems to import the file just fine. It's just the Vectorworks import math issue that is creating problem here. I appreciate you guys getting that all set to go for me. Kelly

 

7150 Riverwood Drive, Columbia, Maryland 21046, USA   |   Contact Us:   410-290-5114

 

© 2018 Vectorworks, Inc. All Rights Reserved. Vectorworks, Inc. is part of the Nemetschek Group.

×