@chrisglasier said: Thanks TIG. That is a human type thing that I think I can control; I was wondering if there were any technical if and buts. You can always turn a group into a component and if you explode a component back into a group...

I fear not... Section Planes are very badly provided for in the API - it's a miracle my SectionCutFace tool works - you do have to have manually selected the cut-plane first in that ! I have tried before but there are no work arounds I can see...

I think animation in SU, however it is achieved, is susceptible to skipping if the model is large, or vast amounts of data are being animated. Try it in a DC. DC's animate objects and you can put them on a timer. The more complex the object being animated is, the bumpier the live animation is. But if it could be exported to a video, then it wouldn't matter so much.

@tig said: @thomthom said: TIG, I think it's a native SU warning, not a ruby script warning. So I'm not sure if that can be suppressed at all... Well, in that case it can't be suppressed... it's there for a reason If the warning is sent to the console via STDERR, you may be able to suppress it by changing the setting for $VERBOSE. See this post in the Optimization thread. http://forums.sketchucation.com/viewtopic.php?f=180&t=25305#p217508 If it's a viewtip or a messagbox in a .rbs, well ...

DoubleCut makes me huddle up in a corner and cry.... My wish for SU in the future is for it to be developed further as a platform. Sorting out the bugs in the existing API and filling in the gaps.

@adamb said: FWIW This is essentially how LightUp works under the hood. I've had for some time realtime painting tools working in LightUp but I've never had time to productize them. Adam Maybe a MakeUp plugin.

thanks Jim. just before your response I solved it in another way, using the axes of the target direction and creating a transformation array. wish I had asked this question 3 days ago

i must have missed this topic, sorry saiscience83 To hide objects in there pre-active stage, you just delete that material. Let's say for example you want buildings that are going to be constructed hidden before the construction starts. Then you just have to delete the material 'Construction_pre' from the materials library.

Components/groups end up skewed if you got them nested a couple of times inside non.uniformly scaled parents.

Working now Must have missed something last time i tried it.

did everyone just give up on this ?

oh, ok.... it's simple. thx guys

I tried once to see it was possible to use the same folder for both systems. I just set each one to ignore the repos and configs of the other. It appeared to work; at least in my simple test folder. I tried and hg-git also, although it took some extra installation and setup. It also seemed to work just fine, although I had more warnings than I cared for - made me nervous.

I was drawing the matrix from memory of a screen dump the night before and thought elements [9], [10], and [11] were the component's origin. So I tried to make that fit the illustration of your matrix, and erroneously guessed at the order:-)

@martinrinehart said: Does anyone know if there is a relationship between Bug Splat reports and getting bugs fixed? Everything that has been said in previous responses is true. BugSplat tells us how often bugs occur that have the same signature. Therefore, if we set out with the aim to fix some of our most common bugs, we start at the top of the BugSplat list and work our way down. Every time we do a maintenance release or major release, we spend a fair bit of time fixing as many of the most frequently occurring issues as possible. Also, if a specific bug comes to our attention and it seems like a very big problem when it does occur, even if it doesn't occur very often, we will concentrate some effort on trying to establish how to reproduce it and whether we have any BugSplat data to help us dig deeper. Yes, there's a big correlation between BugSplat and bug fixing activities. Andrew

@jim said: This is a test piece I did last year. I post it as an example, although I think it basically works. Thanks, Jim. I DL'd, took a brief look and said, "Chapter 16". Gotta finish 15, first.

@honoluludesktop said: Martin, My apologies;-) Apologies not needed. Besides, you're the only guy here who has the correct version number on Win XP.

@jim said: The actual code that causes the BugSplat is relevant. May we see it? Not likely to get back there anytime soon. Materials have been so uncooperative that I've banned them from the Ruby portion of my tutorial. @tig said: a work around to effectively 'import a skm', is to have previously made a face with the required material and save that as a small skp file. Then in the main model use the import method to add this skp as a component, the desired material will come in with it. TIG, you have my undying affection for all the great information you provide! This, however, sounds a lot like a "you can't" answer to "I'd like to write a little Ruby..."

@cjthompson said: you might want to put: t = Timer.new( 1/fps.to_f, tt ) Matz made some brilliant decisions, and some other decisions. The decision not to coerce to float was, maybe, one of the other decisions. How many times are you really helped by 9/2 returning 4?