Kevin McAllister

Check your direct messages. I sent you a 3d model. This tent is likely an S5000 given the size. Kevin

It's almost certainly from Tentnology or Warner tents. Here's the Tentnology webpage - https://www.tentnology.com/our-tents/brands/saddlespan-tents I've worked in these tents extensively. They hold the patents. @bcd there is an edge truss that holds it taught around the curve. Its assembled closed like a clam shell and then the top side is pulled over into the open position using a crane or tow truck. The tensioned skin plus a safety cable keep the trusses in place. Kevin

Who is the manufacturer? Do you know the model? Kevin

I store lots of information in my VW file so it's easily accessible. Large files can be an issue but I usually just make a file copy and purge the extra information if the file needs to be shared. I haven't found the large files to be a problem for my own use and hard drive space is cheap. Kevin

I still see it happening once and a while. Usually saving and closing the file and then re-opening it solves things. KM

I would make an extrusion of an array of oversized boards (too much thickness) and make a contoured surface. Solid subtract the two and extract the resulting board faces that are now contoured. Finally I would use shell to give the board faces thickness following their new contour. If you prefer using NURBS for part of the process, use them to make the contoured surface and use Solid section instead..... Always a few approached to things in VW. Kevin

Of course. I should have thought of that. So really its an interface wish then 🙂 Kevin

I wish there was an option to right click on an image (or even PDF) in a document and have an option to replace it with a new image. The idea being that images often get resized or cropped, so by using replace the new image would be scaled or cropped automatically by replacing the old image. So often clients request variations or send new graphics to be incorporated and this workflow would help with efficiency. Edit - images/pdfs should also have their filename retained somewhere in the "bitmap" or "PDF" object they become so you can easily track their source. Kevin

FYI this is the scale multiplier chart I shared with Adam in our message exchange..... I usually scale the object before exporting to STL and then undo. KM

Yes, likely. Years ago I wish-listed a way to output scaled objects to STL but that wish was never implemented. If you don't want to do math, then create a sheet layer viewport in the scale you want to print at and then dimension the object to the extent of its bounds on the sheet layer itself. This will give you a size dimension to input into your slicer to print at the correct size. I check print size this way all the time. Kevin

^ this definitely. My symbols often start out as just 3d but usually become hybrid at some point...... Kevin

I think I would make each artwork a symbol with an attached description record. Then you could easily label them in any view with a data tag that pulls the description from the record. It would take some initial time to input, but then it's fairly easy to maintain. Kevin

^ this. Ideally when adding a symbol from the library added a class VW would ask if I'd like to use the symbol's classes or assign them to my own. Kevin

This made me laugh out loud. I hate that class 😊 only because I move things out of it all the time. When something doesn't show in a sheet layer viewport, its usually in an autogenerated class and I've forgotten to move it.... Kevin

Nope. Reread the thread and you'll see why.... KM

I know the issue. I have the same problem with scaled symbols, which ungroup to unscaled symbols..... I wish there was an ungroup to current state. Kevin

That's super weird. Hopefully someone investigates it.... I don't like redoing things because VW misbehaves. Kevin

Not really helpful behaviour, is it..... Kevin

Bumping this. Still seems to be an issue in SP4 😕 Kevin

Hi Pat. The background render is shaded and the detail level is set to very high. It affects the polyline based extrude but not the oval based extrude. Kevin

Hello all, I had some weird behaviour with some geometry tonight becoming facetted. I use the same file settings and its been a long time since I've had facetting issues. I'm wondering if something changed with the most recent service pack. This is where I started noticing the problem with an extruded oval. Notice how different the background shaded render is from the foreground hidden line. When I went in and edited the oval to turn it into a polyline (cut it in half and then added the surfaces back together) the issue went away. So then I did a quick comparison in a clean file. Both started as ovals but the one on the right was converted to a polyline using the method above. The facetting is quite different. Shouldn't standard geometric shapes (ovals, circles etc.) render better, not worse? It's all very odd to me. Kevin (Its not related to either 2d or 3d conversion resolution which is where I started my troubleshooting.)

There was a wishlist item about this long ago. It would be better if they remained whatever they were before creating the EAP. Kevin

I would say some tasks are single core. There has been a lot of work in recent years to migrate the code across. There definitely are some bottlenecks but its much better. @JuanP or someone from NV may be able to provide more information as to which items are still single core. I suspect snapping, some selection highlighting, math and a few others are still single core. Kevin

Alan, it's great that you're sharing advice, but it would be more helpful if you read the original post carefully and answered the question, not just throw random partly related suggestions into the thread. The original post asks how to break up the object into individual pieces with the appropriately mitred corners to share with a joiner. Kevin

Note that you need to convert the planar (2d) surfaces to NURBS curves, not NURBS surfaces. That's why I extract the planar surfaces rather than just convert the original object to NURBS which results in surfaces. Lofting only works with NURBS curves. Kevin