there is also the V-Ray Debugging tool: Plugins->V-ray->Regenerate all V-Ray materials

you could always revert to 1.49.01 also. Although we appreciate your testing feedback, if it's impacting your workflow, by all means, revert!

there are no errors in that error log, perhaps if you can post a scene, or explicit steps on how to reproduce the error, someone can better assist you.

there's geometry being removed from the scene?... Please send us a bug report about this, and give explicit steps on how to reproduce this issue... That's an awful bug!

crashes in the observers ::begins to weep and walks off to a corner of the room to collect himself:: My suspicion is that the crash is related to setting the scene attribute dictionary

call VRayForSketchUp set_vfs_scene_attribute in C:\ProgramData/ASGVIS/VfS/Ruby/R2P.rb:ln 269
c-call Sketchup active_model in C:\ProgramData/ASGVIS/VfS/Ruby/R2P.rb:ln 271
c-call #Sketchup::Model:0x167e78ac attribute_dictionary in C:\ProgramData/ASGVIS/VfS/Ruby/R2P.rb:ln 271
c-call #Sketchup::AttributeDictionary:0x167e73fc []= in C:\ProgramData/ASGVIS/VfS/Ruby/R2P.rb:ln 272
c-call #VRayForSketchUp::VfSModelObserver:0xbbe4668 onTransactionStart in C:\ProgramData/ASGVIS/VfS/Ruby/R2P.rb:ln 272
call #VRayForSketchUp::VfSModelObserver:0xbbe4668 onTransactionCommit in C:\ProgramData/ASGVIS/VfS/Ruby/VfSObservers.rb:ln 1084
call VRayForSketchUp::CallbackWatcher busy? in C:\ProgramData/ASGVIS/VfS/Ruby/skpHelperClasses.rb:ln 41
c-call Sketchup active_model in C:\ProgramData/ASGVIS/VfS/Ruby/VfSObservers.rb:ln 1087
c-call #Sketchup::Model:0x167e78ac materials in C:\ProgramData/ASGVIS/VfS/Ruby/VfSObservers.rb:ln 1087
c-call #Sketchup::Materials:0x167e5444 current in C:\ProgramData/ASGVIS/VfS/Ruby/VfSObservers.rb:ln 1087
c-call == in C:\ProgramData/ASGVIS/VfS/Ruby/VfSObservers.rb:ln 1087
call #VRayForSketchUp::VfSEntitiesObserver:0xbbe45dc onElementModified in C:\ProgramData/ASGVIS/VfS/Ruby/VfSObservers.rb:ln 929
c-call #Sketchup::AttributeDictionary:0x167e73fc class in C:\ProgramData/ASGVIS/VfS/Ruby/VfSObservers.rb:ln 930
c-call Sketchup::FaceSketchup::ComponentInstanceSketchup::Group include? in C:\ProgramData/ASGVIS/VfS/Ruby/VfSObservers.rb:ln 930
c-call Sketchup::Face == in C:\ProgramData/ASGVIS/VfS/Ruby/VfSObservers.rb:ln 930
c-call Sketchup::ComponentInstance == in C:\ProgramData/ASGVIS/VfS/Ruby/VfSObservers.rb:ln 930
c-call Sketchup::Group == in C:\ProgramData/ASGVIS/VfS/Ruby/VfSObservers.rb:ln 930

post a scene file and a render that demonstrates the issue so others can look at your settings and how you are setting up the object that is supposed to have refraction. You need to apply the material to a group/component instance in order to have refraction work properly. SketchUp has no concept of what a mesh is, so if you just apply to faces, we have a difficult time telling what faces are related and should be considered one mesh. This can cause some really awful results, and is the main reason why people have issues with refraction. If that doesn't help, post a scene file and render.

Also... the version you are using is very old. 1.49.01 is the latest stable release, and we also are in beta for version 1.6. Both are available on the chaos group website.

you're quite welcome. I like how it was just snuck in to a minor beta release Wonder what the next one will have! Oooooh

@unknownuser said:

@dkendig said:

We now have 64bit support (...)

Wait, wait ... there's a 64-bit VfSU now?

http://www.spot3d.com/vray/help/sketchup/150PB/distributed_rendering.htm
::winks::

Blender is a fully featured 3D solution, not geared towards one particular market. Much like Max, Maya, etc. So yes, once you get past the learning curve, it's going to be capable of doing just about anything you can imagine... If you can manage to get past the learning curve

does the render finish, and then the box shows up? Are you attempting to use SketchUp while it's rendering? Do you have more than one SketchUp window open?

so the big white box... is one of our dialogs? VfB or Material Editor? I'm still not sure I understand what is happening here.

I completely agree. We do some operations during an observer event, and from what I understand, that's not safe. When are we supposed to react to what we are notified about via the observer system?... I have no idea... but I've been told that the way we do things is dangerous. I'm sure we probably make some bad assumptions during these events also. I'd love to have someone with more experience, take a look over our observers implementations, and let us know if there are any glaring issues that may be causing some of these crashes/errors to occur. I've tried doing a trace during a crash, but I don't really see anything suspicious. I have also messaged Fredo about the conflict with his plugin, in particular, because he has written a staggering number of plugins, and I believe it's fairly safe to assume that his scripts are not to blame. If anyone is interested in helping us track this down, I am open to suggestions, please send me a PM.

andyc - We're working towards matching features and workflow between V-Ray for Max and V-Ray for SketchUp, so our plugin is more consistent from one platform to the next. We are currently looking for good feedback with our 1.6 beta, from users that are migrating from other modeling apps to SketchUp, and are basically in the situation you have found yourself in. If you think you might be interested in trying V-Ray out, we'd love to hear your 2 cents.

CadFather - you are absolutely dead on, we are striving to have tighter SU integration, and a more complete feature set moving forward. We now have 64bit support, proxy support is looking better with each release, and we aren't done adding new features just yet

this is something that users have requested for a while, but there are some other big items and bugs that we are trying to deal with before venturing off on to this quest. If, for whatever reason, it doesn't make it in to this version, it will be in an update soon.

Window->Preferences->Extensions->V-Ray for SketchUp, the version number should be listed along with other plugin info below the list of extensions.

I suppose that is a more accurate description of how our animation support has traditionally been done. We aren't done adding and changing things for this release yet, so don't lose hope. The reason we currently don't support per scene changes, other than the camera, is that this requires re-parsing the scene (which in some cases can be very time consuming). In 1.49.01, the time it took to parse a scene was significantly longer in many cases, than it is in the 1.6 beta, so re-parsing for each scene was out of the question in that version. Now it's something we can consider doing. No promises, other than the fact that we will try.

never seen that before... is it easily reproducible? What steps can be taken to reproduce this? Can you please submit a bug report so we can fix this?

we currently don't process changes on a per scene basis, for anything other than the camera.

? are you asking me?