Well, I'm heading for Pasadena in less than three months, so that burden would need to fall on someone else's shoulders. I think it's definitely feasible, though, as there always seem to be a good number of people at our VAR whenever someone from SolidWorks comes to demo the latest and greatest.
I don't know what you're using, but on SW 2007 under the dimension property manager, under primary value select "Override Value" and type in L. At this time, you can also select the desired tolerances.
From what I read in the API notes, the \ returns an integer value, which is what I wanted, i.e. 100 \ 3 = 33. And that formula works correctly to give me the number of holes on the sheet.
Yes, that's the conversion into inches. My problem is that for some reason, those lines aren't running when I have the formula in there, but they will if I have a simple numeric value. I used the Width value a couple lines previous to it, and it worked just fine. Here's the complete code, in...
I'm attempting to make a macro (not something that I'm very good at) that given a width and height of a plate, will create a centered array of holes at 2" on center. I can get it to create the right number of holes, but I can't get them to center, so that I often end up .75" from one side and...
I second the usage of the set center point. I have that mapped to one of my two buttons, and zoom fit mapped to the other. It took a while to get used to the device, but I've become firmly attached to it. Not so firmly that I wouldn't mind an upgrade to a SpacePilot or SpaceExplorer, though.
I would say yes, but probably with the usage of dummy parts. Use distance mates to expand the cylinder, which will need to be modeled as at least two parts to show the expansion. Use an angle mate combined with a distance mate to make the ball roll. Solidworks often has difficulties traveling...
Also, does the Windows Task Manager give any helpful information about what's going on? I'm animating right now and it lists Solidwork's memory usage at around 200MB. It has the CPU usage at 100%, though. And what about breaking it up into multiple animations and splicing them together?
It's definitely a memory intensive job, so I set it to run overnight, but wouldn't it just crash if it ran out of RAM, instead of rendering a bugged video? That's just what my intuition says, but obviously you've had experiences to the contrary.
I've been working on some animations that would loop on a display at a trade show, so I'm trying to make them as large as possible, with no regards to file size. However, I've found that once I get to certain size (a width of between 2000 and 2500 pixels at screen ratio) it all goes to hell...
Related to this, I've run into some issues with a very large animation (small assembly, but large image size and fps) and noticed that my driver is not the one listed by Solidworks for my card (6.14.10.7756) but 9.1.3.6, one with a slightly later release date. Should I roll it back to the older...
