Like it says, is there? I can't find anything beyond the help page which isn't great.
I realise it isn't the most complicated piece of software in the world but it would be nice to be sure that one fully understands its functinality.
I haven't made the leap yet from SW14 to 15 so I can't help but I'm curious about that bit of functionality myself.
Have you looked over here ?
Those are only the 'help' pages and as per usual they are very brief.
So if there is more available then I would love to hear about it too.
I hadn't looked there Peter but I have now and I'm not much further forward really.
I'm not quite sure I get the procedure. It seems to imply that if you export the structure it will create all the drawings and parts that are referred to but at the same time you generate these parts by loading in an assembly which implies that the parts already exist.
Yours confusedly etc...
To keep it simple, you've two options:
1. Create new parts (this just inside Treehouse). And when you export the structure new files would be created.
2. Use Existing Parts which have been already modeled in SOLIDWORKS and saved on your hard disk. So when you export the structure from Treehouse only new files would be generated in SOLIDWORKS.
If you type in solidworks treehouse in U tube you will find a few hits to help
This one looks good to get started
Yes that video was useful. Isn't it nice of 3rd parties to go to the trouble of writing tutorials for other companies for free ;-). Dassault must be very grateful.
I've just created an assembly with two subassemblies (sub assy 1 and sub assy 2) , each with two parts (part1, part2, part3 and part4) and associated drawings for parts1 & 2. See below, that went OK.
Then I saved the file and then exported it to SW. SW booted up but then crashed with a funny error message.I looked in the destination directory and found that SW had created the assembly, only one sub assy, only the two parts under that sub assy and only a drawing for part 1. See below.
For some reason both the parts are read only although the sub assy isn't.
Looks like this is still at the Beta stage.
Just used the same set up and everything went fine. What SP of 2015 you're using.
I'm on 2.0 EV
Im guessing that if tree house works fine on a demo of SW 2015, you must have an issue with something that SW dosnt like. Registry issues caused me problems with grouping folders, so it could be anything .
FYI - Although Treehouse is "new" in 2015, it has been around on the SolidWorks web site for three or four major releases as a stand alone utility.
Sadly, Treehouse works backwards to our needs.
We'd like something that produces a savable graphical version of the feature tree of a completed assembly, down to the sub-assembly level.
I don't have SW15 on this machine to check, but I thought Treehouse was able to open a SW assy & create the graphical hierachy.
It can, but it goes down to individual part level (too deep!) and isn't savable / printable as a drawing, which is what we want from it.
Are you looking to export the assembly hierarchy? If yes then you can use Assembly Visualization tool.
If you need a macro then check this one: Feature Tree to Clipboard
Thanks Deepak, I'll take a look at that.
I hadn't realised that you couldn't print a hard copy. That's a shame.
What we currently do in our (multinational) company is upload PDF copies of a manually generated family tree to a location everyone can access via a web browser. This allows them to access the released drawings from another common repository. The hard copy is really the important document.
In response to the other points everyone raised (thanks very much).
I'm on SP1.1.
I guess it might be the registry but I don't really care what the problem is, I just want it to work like it's supposed to. The way I see it, if your software is absolutely bullet proof and completely intuitive you can get away with sending it out with poor user instructions. If it's not but it still works if you know what you're doing then you need to provide a good user manual.SW have done neither, the software seems fragile and they seem to be relying on enthusiasts spending hours learning how to use it by trial and error and then telling others. This is a company with 2 million seats in the world most of whom will be paying a licence fee...you can get an idea of their annual revenue from that and then ask yourself how much they spend on quality control.
I'm aware that this piece of software has been around for a while, I was trying it out maybe 5 years ago on SWLabs. It makes it all the more difficult to understand why it doesn't work flawlessly when it's been around for so long.
I agree with the software being bullet proof, i have paid a fortune out on SW software, subscriptions, training, books, and every time we get to SP1-2 its full of little bugs which always seem to be the ones everyone is using. I noticed their was one to do with weldments taking up too much memory on creation of a structural member, that's been logged to SW as well. IT reminds me of when AutoDesk was kicking out poor versions of AutoCAD and relying on its customers to be guiypigs. I thought we had past that stage buy now. I think the pre-planning of service packs dosnt really build confidence either. Off the track a bit, sorry
There are currently 2 lessons on using treehouse available thru the my.solidworks forum
Retrieving data ...