<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0"><channel><title>Disqus - Latest Comments for kobykarp</title><link>http://disqus.com/people/kobykarp/</link><description></description><language>en</language><lastBuildDate>Thu, 20 Aug 2009 08:39:37 -0000</lastBuildDate><item><title>Re: Why Your SolidWorks Models Suck&amp;#8230; Memory Out of Your Computer</title><link>http://solidsmack.disqus.com/why_your_solidworks_models_suck8230_memory_out_of_your_computer_02/#comment-15123032</link><description>Rather than saving as a parasolid, if it's a part insert it into a new part, and work on the new part. It will only rebuild up to that point and its all still fully referenced and easily editable.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">narrowcurves</dc:creator><pubDate>Thu, 20 Aug 2009 08:39:37 -0000</pubDate></item><item><title>Re: Why Your SolidWorks Models Suck&amp;#8230; Memory Out of Your Computer</title><link>http://solidsmack.disqus.com/why_your_solidworks_models_suck8230_memory_out_of_your_computer_02/#comment-1059286</link><description>I used lightweight option for a while, and I realized that I don't really like it. The problem is when you do need to modify one of the lightweight components, it takes ages to load them! &lt;br&gt;Instead I'm using "shaded" view (instead of "shaded with edges"): it might be not the best to work like this 100% of the time, but I like to work like this most of the time and change view only when I need to. Also I realized SW crashes less when I'm using this option. &lt;br&gt;Another trick is to set configurations and suppress the heaviest components or features, depending on what you're working on. For example, I like to make an "envelope only" configuration to all my assemblies and I suppress everything except for the outside components, usually it's comfortable to design jigs like this.&lt;br&gt;If your model is completely stuck, you should turn it into parasolid (which deletes all its history) for it to run.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">kobykarp</dc:creator><pubDate>Thu, 31 Jul 2008 07:27:43 -0000</pubDate></item><item><title>Re: The 10+ Best SolidWorks Tips to Teach Someone Else</title><link>http://solidsmack.disqus.com/the_10_best_solidworks_tips_to_teach_someone_else_57/#comment-1048977</link><description>Yep, THE Michael Richards back in 1989 in the Movie UHF with Weird Al. That scene where he turns the firehose on is great!</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">joshmings</dc:creator><pubDate>Wed, 30 Jul 2008 07:41:15 -0000</pubDate></item><item><title>Re: The 10+ Best SolidWorks Tips to Teach Someone Else</title><link>http://solidsmack.disqus.com/the_10_best_solidworks_tips_to_teach_someone_else_57/#comment-1048957</link><description>Wow, really good list of tips Cheech. I like the idea about having a post design review, although I think it depends on getting rid of the in-context relations. Makes sense if it will be re-used, but going through that process should wait till no more changes could happen. THanks!</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">joshmings</dc:creator><pubDate>Wed, 30 Jul 2008 07:37:17 -0000</pubDate></item><item><title>Re: The 10+ Best SolidWorks Tips to Teach Someone Else</title><link>http://solidsmack.disqus.com/the_10_best_solidworks_tips_to_teach_someone_else_57/#comment-1035538</link><description>By the way, is that kramer on the picture?</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Cheech</dc:creator><pubDate>Tue, 29 Jul 2008 09:03:49 -0000</pubDate></item><item><title>Re: The 10+ Best SolidWorks Tips to Teach Someone Else</title><link>http://solidsmack.disqus.com/the_10_best_solidworks_tips_to_teach_someone_else_57/#comment-1018050</link><description>1. Tree view:&lt;br&gt;I always like to keep it neat and clean:&lt;br&gt;I start with the most relevant assemblies then the most relevant parts, then, least relevant assemblies and parts. Whenever there’s a group of parts &amp; assemblies that didn’t get their own sub-assembly, I like to open a special folder for it. Sometimes it’s also nice to save screws and bolts in a “fasteners” folder.&lt;br&gt;&lt;br&gt;2. Assemblies:&lt;br&gt;You should always minimize the number of patterns, if 2 patterns can fit into one feature, then why not? &lt;br&gt;(2b) Also, it's always better to use a feature pattern instead of linear/circular pattern, if it's possible.&lt;br&gt;&lt;br&gt;3. Sketches:&lt;br&gt;It’s impossible to suppress an entity, so instead you can use “for geometry” so that you can save a group of entities without using them physically in your model.&lt;br&gt;&lt;br&gt;4. Post design:&lt;br&gt;After you finish your design there’s a chance that your parts/assemblies will be used some place else (another project). You should remove these links (mates/relations) because they tend to brake when you use them in a different project (turning from -&amp;gt; to -&amp;gt;?). so you should go to all features that include the -&amp;gt; symbol and start replacing the mate/relation with an autonomous one. For example, instead of using an “equal” relation between an entity in your sketch and an edge in another part, you should use a dimension that “locks” the length of the entity. This way it’s possible to use you parts in other projects. This step is efficient usually in the post design step because you’re “killing” the relations between parts/assemblies in your project.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">kobykarp</dc:creator><pubDate>Mon, 28 Jul 2008 04:09:08 -0000</pubDate></item></channel></rss>