dxf file layers imported into Vectric vCarve Pro|Forum|WOOD DESIGNER

Avatar
Search
Forum Scope


Match



Forum Options



Minimum search word length is 3 characters - maximum search word length is 84 characters
sp_Feed sp_TopicIcon
dxf file layers imported into Vectric vCarve Pro
Avatar
Stefan

Forum Posts: 918
Subscriber Since:
November 8, 2013
sp_UserOfflineSmall Offline
2
January 15, 2021 - 5:36 pm
sp_Permalink sp_Print

Hi Randal, thanks for downloading and testing StairDesigner, and also for this detailed query. There’s a good integration between StairDesigner and VCarve, we can name the DXF layered output within StairDesigner’s post processor settings and once templates are set up in VCarve, the process is well automated.

One of our technicians would need to discuss these issues with you in an online demo of the software. They are familiar with VCarve, we sell this ourselves. I’ll email you now to see if you would like to proceed with that.

Thanks

Avatar
Guest
1
January 15, 2021 - 4:52 pm
sp_Permalink sp_Print

Hi,

I’m trying out the Stairdesigner software and am using the Stairdesigner Sample files – SD file – quarter turn stair with winders.stair

I have imported stringers and treads so far, and cut the stringers at 60% actual size just to get a feel for what work needs to be done in order to cut on CNC once the stair design is in .dxf format.

The one hitch I’ve found so far is that when I imported the .dxf for the newel posts, only the stringer and handrail slots came into vCarve. The mortise for the treads was missing. The reason is that vCarve recognizes when an incoming vector layer has the same name as an already existing layer, and won’t import that new layer.

i.e.: When I imported the stringers, a layer came in called – “step_housing_30x15”. So when I tried to import the newel posts, it stripped off that layer because there was already a layer with the same name. Once I realized what was happening, I renamed the layer for the stringers and was then able to import correctly.
So naming conventions for post processed files would be better if referenced to a specific part layer. (stringer_step_housing_30x15, post_step_housing_30x15)

Note:
This wouldn’t be an issue if different files were created in vCarve for each component such as Stringers.crv, Treads.crv, Posts.crv, etc. But I’ve found it’s much more convenient to put a complete job into one file and separate components into different layers. It could be avoided in vCarve by using the “merge visible layers” command each time a new component was imported. However, then you lose the ability to show/hide different aspects (layers) of the imported file.

Forum Timezone: Europe/London
Most Users Ever Online: 256
Currently Online:
Guest(s) 31
Currently Browsing this Page:
1 Guest(s)
Top Posters:
Ness: 1939
Tom Cleaver: 162
mark nichols: 160
brendan kavanagh: 136
Conor Devoy: 135
Duayne Naugle: 130
Stu Robertson: 104
Zaheer Abbas: 89
Patrick Maylor: 63
Robert Coxhead: 63
Newest Members:
Dov Bolel
David Bragg
wstenholt@gmail.com
Michael Hofer
Chris Jackson
Anthony Penn
almys111
Keith Shelley
Kate Polak
zorsim
Forum Stats:
Groups: 2
Forums: 7
Topics: 2119
Posts: 11587

 

Member Stats:
Guest Posters: 4
Members: 267
Moderators: 0
Admins: 11
Administrators: Stefan, Michel, Carole, Alex, admin, Laly, ipatrick, Crystal, Fatima, Darren, Isaac