Cool chair - very retro, thanks

That is VERY strange! Sounds like there are errors or something has corrupted. I have imported DWG files from other programs and have seen corrupted object or models. I would try downloading Sketchup 8 again and re-installing it. Also, maybe update Windows too. I have never seen that problem before. As if the snaps were not working correctly. When it pops up with "Endpoint" it always means the very end of the line. Check your snap options too under Window/Model Info/Units Maybe the "Enable Length Snapping" is set at a strange unit... I mostly work in feet so I use .01' Let us know what you figure out

And did it work?

25 or 15 GIGAbytes? Are you sure it was/is not MEGAbytes? Even if Mb, it can be quite large and I cannot imagine a 25 Gb file in SketchUp.

now when my tracks are complete and the joints are connected for sketchy physics sketchup crashes

This behavior still exists in Sketchup 2014 version 14.1.1282 It happens with ARCs and POLYGONs, but not CURVEs or EDGEs. @tig said: You don't even need to group the arc, just scale the raw arc in one axis [it becomes a curve] and its displayed length remains as it was originally NOT as it now is. Only if you explode and weld back into a new curve does the correct length get returned... This is because an Arc has some special properties - when you scale it it becomes a curve BUT it remembers it used to be an arc - therefore it displays its original arc length [confusingly]. To see this draw an arc, select it and use Entity Info to see its length, scale it in one axis x2, its displayed length doesn't change, it's 'Type' is shown as 'curve'. Now rescale it back on the same one axis x0.5 so it returns to the original scaling - the length doesn't change BUT the type changes back to 'Arc' as it somehow remembers what it used to be before it was scaled. IF you scale the arc in two axes it remains an 'arc' AND its length is reported correctly. If you explode the one-axis-scaled arc and weld it into a curve, then gets its length is displayed correctly again, the scale the curve and its displayed length adjusts to suit - so an 'arc' is a special case and if scaled in one axis it will not return its scaled length, unless you remove its 'arc-ness' by exploding it and welding back the bits into a 'true' curve, which will then behave logically... I think it's a bug that should be addressed in an update... It's been officially reported to the powers that be.

The attached-file size limit is ~4Mb - so ZIP them if necessary. Direct attachment of SKPs is allowed but if you upload a SKB it needs to be inside a ZIP anyway, as there are only certain types of files allowed for direct uploading... Zipping will optimize the file size uploaded... I know you can't purge the SKP because you can't open it , but bear that in mind for the future. A SKP can shrink considerably when purged in Model Info > Statistics...

thank you very much for the resolution!!!! I saw the other day a video from someone's presentation and it had the clock attached. It looked very nice.. hope someone knows how to.. thanks anyway!!

Before SU was working? I had also allways some crashes some time ago i could not explain... "Repair" SU was not successful but "deinstall" completely and new installation and all was fine...

thanks for the additional tip

Thanks for your replies. I updated my drivers to the latest and so far I'm not experiencing those jitters since. I just installed it over the old one without deleting anything. This is a quote from the Nvidia site- "Q: Do I need to uninstall my older driver first? A: No. It used to be the case that an uninstall was first required. Today the recommended method is to overinstall the newer driver on top of your older driver. This will allow you to maintain any current NVIDIA Control Panel settings or profiles." I did that and all seems well. So yeah, if I experience anything wrong, I can easily revert back.

In addition to what's been said already... IF you have applied a texture material directly onto a group or component-instance then that textures material is displayed for any internal faces using the default material [consistently oriented], BUT you cannot affect the material's texture placement on a face by face basis even by editing the container and selecting a face, because that face would still have the default material ! You must apply a textured material directly onto a face for you to be able to use the right-click context-menu Texture tools to modify it individually for each face... THEN you will be able to rotate the texture individually on a face as desired... Tip: once you have just two versions of the textured material adjusted as desired [let's say vertical and horizontal grain] then you need not continue to edit every texture to make it horizontal. Simply use the Material Browser's eyedropper tool to sample a horizontal version of the material - it becomes the active material - and then paint using that on all of the surfaces you want to have the horizontal version - it's a much quicker method than using the Texture tool on every one in turn...

Elegant as always Jean.

yea - a UI that's separate and doesn't lock up. That would be a big enhancement.

Thanks Rich for the explanation. Now I know what I'm looking at. I rarely see a version 8 model when I'm searching. Mostly 5,6,and 7. I usually just get the highest version on the list and so far I have no problems with any downloads.

Fololow me and keep does not rotate but in some cases it does not keep the heigt constant. 1001 Bits tools does but it's $ but does have a 30 day trial period

Happy April 1st - this is my most particular holiday!

Rather than move them back one by one you can half, and half again until you find it. E.G. Make two temporary folders Disabled and Safe. Put half of your scripts in Disabled, leave half in Plugins - if the error still happens you know which half in safe - move the contents of Disabled into Safe. Now repeat moving half of what's in Plugins into Disabled - this time lets assume the error has gone, therefore move the contents of Plugins into Safe and half of the contents of Disabled into Plugins.... repeat swapping things like that until you have the culprit file[s] and tell us what they are !! Doing if by halves is much quicker; 512 >> 256 >> 128 >> 64 >> 32 >> 16 >> 8 >> 4 >> 2 >> 1; i.e. 9 steps for 512 files, BUT doing them one by one... on average you'd need to swap ~256 files to find the problem one - at worst 512 and at best 1. BUT I think 9 steps v. ~256 is the better bet