Vray makes sketchup slow! (dynamic components)
-
I use a lot of dynamic components with sketchup which is normally not an issue however I notice that when I have the Vray plugin running (not rendering, just running!) that using / changing component options (in the component options dialog box) becomes extremely slow. for example if I change an option in my dynamic component and click apply, this would normally take around 4-5 seconds to update. However with vray running this same change now takes about a minute (or longer)...!
(onclick functions are also alot slower...)Is anyone having any similar problems or any ideas as to why this may be? settings etc...?
Thanks
MattI am running the latest vray update on sketchup 2015, on a new 15" macbook pro.
-
Yeah, I noted the same thing. I think it's beacause Vray is running inside SU, like a plugin. I would like to know why the creators didn't consider VRAY as a standalone software so to use just an export file like Kerkythea.
-
This is due to the fact that Vray adds observers to every group or component created. This tends to slow things down a lot.
I managed to work around this for my plugin, but maybe I can create a small script to toggle the observer creation on a targeted item.
-
You could try installing/using the SketchUcation Toolset - use its Managers, to Disable Vray [select + red-button], so its Plugin[s] [or perhaps Extension?] get moved to the right-hand column.
When you restart SketchUp Vray won't load.
But when you need Vray you can temporarily Load it from the right-hand column [select + orange button].
It remains loaded until SketchUp restarts.
If you find this way of working inconvenient, then you can always re-Enable it permanently, select it + green-button to move it back to the left-hand column...You could also use the Managers' Sets to create sets of tools that you use for specific purposes.
You probably don't want a memory intensive renderer [like Vray] or any other such application loaded every time you use SketchUp - if you don't expect to use it ? -
The slowdown could be caused by us monitoring the scene via the SketchUp Ruby API, as jiminy-billy-bob mentioned. If this is a common issue, then perhaps we should consider having an option to turn that off, rather than having to disable our entire plugin. RT wouldn't work while it's disabled... and there might be an issue with lights if it's disabled... not sure off hand what else would be impaired by not listening for component or face changes.
Archaholic - we certainly did consider exporting, like many other rendering packages out there. We decided against exporting, so that we wouldn't have to worry about syncing assets between 2 applications. We actually found that users often told us that one of the reasons they chose our product over a competitor's, is the fact that we were embedded in the host application. We just did what our users told us to do
-
it would be extremely handy if there was a way of quickly turning it on and off without quitting sketchup - this would enable me to render and then quickly make a change to the component after seeing the render (or realtime view) and then render the changed model again quickly. Rather than my current forced method of, make changes, quit sketchup, reopen with vray, render, close, open, make changes again and so on and so forth...
Why is it necessary for vray to keep a tab on all the components at all times?
thanks TIG your workaround sounds good for opening sketchup quickly but this still doesn't let you close it without quitting sketchup presumably??
-
Unfortunately you can't 'unload' a script once you 'load' it.
A SketchUp restart is needed...
Although it would be possible for a plugin's author to write it with a menu item to 'enable/disable' it: so e.g. Vray could get a menu option to 'disable' it, which would then gray-out its menu/toolbar items [they can't be 'removed dynamically'] - of course 'enable' would remain active ! - and also stop its 'obtrusive processes', like its observers etc; later clicking 'enable' would revert it to have everything working again...
But that is up to Vray's guys... -
we could enable/disable certain functionality of our plugin on the fly, sure, but SketchUp won't let us unload without restarting SketchUp, so that's on the Trimble guys...
wawmsey7 - it's necessary to keep tabs on everything in the scene at all times, because we have our own internal representation of the SketchUp scene, which allows us to update a realtime render in pretty much real time, because we don't have to crawl through the SketchUp scene to figure out what is going on. We are working with the Trimble developers to find a better solution, but so far this is the best we have. If you don't modify nested components a lot, then you will likely never see us slowing anything down. In my opinion, a rendering plugin shouldn't be hogging up system resources (like TIG said), unless it's going to be used. So if you find it too much of a bother, just temporarily disable us (you won't hurt our feelings, I promise) and turn us back on later when you're ready to light/texture/render your scene.
-
I still can't see why vray cant make an option like TIG said to enable and disable vray on the fly... Using sketchup to create complex dynamic components isn't unusual so vray should definitely work out how to cater for this. I would fully understand if this were a free plugin, but at £500 I definitely expect better support than "deal with it". Continually having to close and reopen sketchup is far from ideal and I would expect a much neater solution from such a big company.
-
@wawmsey7 said:
Using sketchup to create complex dynamic components isn't unusual so vray should definitely work out how to cater for this.
Like I said, we can probably figure out a way to turn off some functionality such as monitoring scene changes constantly. This is the first complaint I've heard about this afaik, I'll keep a lookout for any other slowdowns that are a result of our presence, perhaps there's a simple solution.
Advertisement