Sketchup is broken
-
@unknownuser said:
You can load plugins on demand - simply rename them from .rb to .txt and then later use load "ruby.txt" - manually or in a 'tool' - BUT the rub is you can't 'unload' them ???
yes but the toolbars and menu's won't be there right? (and i suppose toolbar hell would happen
)i wouldn't mind it staying active per session anyway. -
And people wonder why I stick with Version 6.
-
@jgb said:
And people wonder why I stick with Version 6.
? Nothing in this thread is related to SU version...
-
@thomthom said:
@jgb said:
And people wonder why I stick with Version 6.
? Nothing in this thread is related to SU version...
I have never had any of those issues in V6.
I have read of countless new and improved problems in V7 and V7.1, and yet few of the real V6 problems have been fixed in V7.x
V7.x Free offers so little extra (notably the line crossing fix) over V6 Free that it makes no sense to me to upgrade for more problems.
-
Break Edges is a great new feature. And the speed improvement in 7.1 is significant. The Back button in the component browser came back - so even that was taken care of.
-
I'm happy to report that I've been working hard on a project all evening and since installing the update for LibFredo and the updated Tools on Surface, my Sketchup is back to normal. All of my weird quirks have disappeared. Right click menu hasn't gone gray in over 4 hours of modeling. The Esc key is working every time as well. Seems LibFredo was the culprit all along! Big thanks for Fredo for addressing it so quickly.
-
Greyout menu's in Sketchup are not just limited to Fredo's plugins from what i'm experincing. Hope this is resoslved soon.
It's become very frustrating. -
@lapx said:
Greyout menu's in Sketchup are not just limited to Fredo's plugins from what I'm experiencing. Hope this is resolved soon.
It's become very frustrating.
If you have the latest copies of all plugins it should reduce the incidence of 'gray-outs'. Some of Fredo's were implicated in the issue but they have all been updated - as have virtually all tools I can think of... However, there is a finite limit to the number of tools you can have loaded at any time that are using 'commands' - these are needed for toolbar-buttons and many context-menu items. So if you have lots of plugins loading it will increase the risk of the gray-out happening. So it's wise to disable any plugins that you rarely use - deactivate unused extensions or rename the scripts' .rb files with '.txt' on the end - then they don't auto-load... BUT they can be reloaded for one session when you find you need them by typing into the Ruby Consoleload "plugin.rb.txt"- where 'plugin' is the original name... Of course renaming so they end with .rb again will make them auto-load again.
There is also a tool to optimize 'commands'... but it will have limited efficacy in the face of zillions of plugins, so give it have a chance! [ http://forums.sketchucation.com/viewtopic.php?p=252413#p252413 ]
-
Thanks Tig, I scaled back on my plugins by unloading in the preference extentions menu. That seems to work for now. I'll have to load up the "otimizer".
-
I'll comment again probably where I have no business , but I expressed concern some time ago related to issues with plugins probably costing Google support dollars and if the the issues raised are not brought under control you may will find your self where Google will impose requirements you may not like. Dan Rathburn tried but don't think he had much success.
Secondly: When one talks about problems and SU blame that's very generic and you have to worry memory snd system also. For a 32 bit machine , that means you can only address 4GB but SU only gets 2GB9 If you have 4GB RAM) because the way the MS memory manager works. Even if you have a 64 bit machine and tons of memory SU will still only be allocated 4 GB even though 64B allows much more address than that. Some of these strange artifacts can very well be memory issues. When you have problems watch the task manager and see and understand what it is reporting. Win xp, vista etc are not all the same. See this link if you have some spare time and want to under stand virtual memory, which is what programs get to use, and physical memory. It will make your eyes glaze over?? http://blogs.technet.com/b/markrussinovich/archive/2008/11/17/3155406.aspx. and the post here in of opening a 360MB SU file with Win XP pro and 4GB Ram http://forums.sketchucation.com/viewtopic.php?f=15&t=39401
Thirdly:It is completely unreasonable to tag Google with any responsibility of running regression testing of any external plugin in the software drop. If you have had to do this you will know what I mean.
Sorry if I am totally out of line
Advertisement