Sure they are maybe more 5 000 plugins so...and we don't know Chiness, Indian etc... The SU4 above is very powerful and interesting if you want make some repetitive Fractale or Grebble Components volumes...following your imagination! [image: suforyou.jpg] [image: simili1.jpg]

Got an answer on the other forum to the import/file format questions. Still interested in hearing from anyone whose found a good source for standard AEC material patterns. For anybody looking for the same: https://forums.sketchup.com/t/how-to-import-pattern-fills-into-layout/64448

Thanks for the suggestions Moujiik. I downloaded Rhino 5 evaluation version this morning and it handled the conversion perfectly. ...Plus now I get to play with Rhino for the next 3 months!

You need to add some extra code, e.g. read the scene name then split it at the space etc etc name="Scene 2 1;00pm" splitname=name.split(" ") ###>>> ["Scene", "2", "1;00pm"] timestring = splitname[2] ###>>> "1;00pm" ###delete the ; timestring.gsub!(/[;]/, "") ###>>> "100pm" ###now check if pm if timestring=~/pm$/ timestring.gsub!(/pm$/, "") time_num=timestring.to_i + 1200 ###>>> 100 >>> 1300 timestring=time_num.to_s ### elsif timestring=~/am$/ timestring.gsub!(/am$/, "") ###>>> 100 end name=splitname[0]+" "+splitname[1]+" "+timestring ### modify name >>> "Scene 2 1300" ### ### now rename that scene with the modified name etc... ### To strip off the entire 'Scene N ' part just use: name=timestring ### modify name >>> "Scene 2 1;00pm" >>> "1300"

You can set the shadow settings (in all scenes) such that it does not display cast shadows on the ground plane. In the Shadows window (expanded pane). Then you probably would want a script that can do that.

If this is happening after unlinking and embedding --could be a bug. but maybe it's too late and you are embedding the altered version of the SU file. So you've lost the old version?

What I left out of the mix is Apple's 'auto restore window' functionality... I think this can come into play if switching between models in the same session... I have no hard evidence of when or if this occurs, but it would explain some of the seemingly odd folders that pop up... Like many, I no longer use 'AutoSave' or 'Save Backup' and prefer 'Save Copy As' over 'Save As' and religiously use S... even with this I get caught out... john

@driven said: the whole point of any maintenance update is to deal quickly with reported splats... each release has an overview of the changes, do they reflect a possible correction of your issues? Well I just updated so we'll see. Many of mine were outliner-related: often when trying to change nesting order directly in the outliner. Didn't see anything in a quick scan of the release notes re the outliner, so don't know if this release will prove to be more stable in my case. (Although I have gone back to cutting and pasting in place in the model instead of shuffling groups/components in the outliner. Slower by far, but I got fed up with the splats. Kind of defeats the value of the outliner if you can't trust it for the purpose.) @driven said: After a considerable amount of bug chasing on mac's, I find recurring issues being related to 'plugin observers' and 'Auto Save', so I avoid both whenever possible... To do this I disable many plugins until I actually want to use them, including the SU ones, and any 'renderers'... I normally try to keep the number of enabled plugins in any given session to a minimum, but I realized that I had installed several new ones of late and left them all enabled, so a good reminder to pare it back down. As for the autosave, that's a tough one... and a bit ironic that the feature meant to ameliorate the results of a crash can be responsible for those very splats. I've tried to get in the habit of manual saves, but the more engrossed I am in modelling the less likely I am to remember. I would have lost an awful lot of work this last week if it weren't for the autosave file whittling it down to 5 or 10 minutes of lost work per crash. Thanks for your thoughts and 'best practices'. Doug

Glad to help, Doug. Sometimes it's just asking the right question that gets it all sorted.

@oceanembers said: I can't help you with the code, I don't know Sketchup's API very well at all, but as for a starting point for learning... http://learnrubythehardway.org/book/ I used this to learn the basics of ruby, and I thoroughly reccomend it. Starting to learn Ruby is on the to-do list once I'm through my current set of deadlines. Thanks for the link and the recommendation. I'll check it out.

No problem! At least you now know two ways to do it

Maybe I'll turn off auto-save in LayOut to avoid such a clash. Thanks for the idea.

@slbaumgartner said: I mean this as discussion, not argument That's the way I understood it too, so I hope I didn't sound like I was arguing back... just agreeing that for board layout there's too many variables for it to be useful, but that mightn't be the case with (some) sheet goods. @slbaumgartner said: Even for sheet goods, the layout facilities in CutList don't take orientation of the figure into account. That would make it fairly useless for veneered sheet goods (or the laminated bamboo we often use) I wasn't sure whether it allowed you to specify grain direction in layout. @slbaumgartner said: To your second point, I have never been impressed with the layout algorithms in CutList. I've seen them propose a layout that called for a second sheet when those pieces could be fit into the first sheet by a bit of rearrangement and reorientation. That's disappointing, and by your overall account it would seem layout in its current incarnation has limited value — or least limited use cases where it might be of value. @dave r said: I know that Steve had been working on improving the layout section of the plugin shortly before his death. He and I had been discussing it only the week before. It's unfortunate that we won't see his improvements now. Maybe someone else will be able to take it further, though. That's too bad that he didn't have the chance to finish his work. Much worse that he passed too soon and without much forewarning (if I understood well from your earlier post) @dave r said: He was a good friend and I for one miss him. I never had the opportunity to interact with him, but I appreciate his contributions and I'm sorry for the loss of your friend.

@db11 said: @jim said: It's an easy fix. It has to do with changes to the String class. ... I sent an update to Martin via his email. Thanks for identifying the needed fix Jim. I hope that Martin posts an updated version to the SCF plugin store. It seems to me that if more people knew how useful / time-saving this plugin is for any model with more than a few scenes, it would find a lot of users. I so could have used it over the past couple of days to clean up a walkthrough animation. And thanks again to Jsteacy for following up on the original post with Martin. Thanks db11, I was also wondering the same thing about the vismap2 until I found this post. was the fix done by martin? and where can I find it?

@jean lemire said: On Mac: Cmd-A won't work because the window isn't focused, you can however 'drag the selection' then click a checkbox to apply to all... john

@db11 said: ...Next up on the migration odyssey: Yosemite. I'm certainly happy with Yosemite and SUv15... depends what else you use... john

Thanks for the quick response, ThomThom. It may well be coincidence as you suggest. It seemed related as I hadn't had a CleanUp crash or console error until applying the Library update. @unknownuser said: But whenever I've tried to track that down it has disappeared, either by itself, a reboot, or reinstallation. After disabling all plugins but CleanUp/TT Lib, I have tracked down a possible telltale behaviour -- it seems to work on the first run (after SU launch) without error -- regardless of model. It then throws an error on the second run in the same session. (with any other model). So from the fully initialized state it runs fine, then it seems to spit out errors. Should also mention that for the first model run in a session (than cleaned successfully), subsequent runs of the plugin works fine on that model. But the same model opened in a subsequent session --and after CleanUp has started throwing errors -- generates the same error. So from the fully initialized state it runs fine, then it seems to spit out errors. Is it possible that some variable/method is not being properly reinitialized/declared? The other weird thing (which I don't remember from before) is that after running CleanUp the cursor becomes the paint tool?? @unknownuser said: The crash, when you did get a BugSplat, did you submit it? Did you enter your email or any other message? I can then look it up and see where it crashes. Without I cannot do much. No I didn't, but when I have time I will try rolling back to the previous TT Lib version and see if it clears the issue... and if the behavior persists I will send you the bugsplat report. Don't want you to waste time chasing it down -- mostly wanted to let you know in case others were experiencing the same issue, and/or if it was easily identified. @unknownuser said: Mind you, SketchUp 8 is nearing four years old this year. Many bugs has been fixed since then. The issue you experience might very well be fixed already. You're right about SU8 -- I'm still using it because of license restrictions on SU13 Make. Hoping to finally be able to upgrade to Pro sometime this year (at this point I might as well wait till SU14 is released... at BaseCamp maybe ). Oh, and many thanks for all your fantastic plugins! Doug

@tmwoodcrafters said: Hi, I think it would be great if you posted them. Thanks! When I posted this, I wanted to see if there was any interest. I probably need to clean up the models a bit before posting them to the 3D Warehouse. I don't have time at the moment to do so, but will do when I have a chance. In the meantime here are a couple of them as jpeg's. [image: y2Rk_Hettich_BlueMax.jpg] [image: E0cS_Cascadei_KS-3.jpg]

@caronte01 said: ...Apple has moved away from discrete graphics for all entry level hardware, and only offers it on 15" macbooks, and some imacs, but not on their line of macbook air, or mac minis, or even on their 13" retina macbook. Intel graphics are imo inferior to even entry level nvidia cards, esp. for sketchup work. It's shame indeed... Honestly, if machine needs to be good with CUDA, maybe macbook pro is not the ideal choice as they GPU's have fairly limited RAM (512MB to 1GB). Not sure what's with next Mac Pro, looks like it will have state-of-the-art AMD FirePro GPU cards, so no CUDA there too (from published images it looks like one simple cannot swaps those to nvidia cards).