try contacting support@chaosgroup.com

please contact our support department support@chaosgroup.com. I was under the impression that this bug had been fixed.

I thought we had fixed that...

when you import a vrmesh, it should be faster than going through the whole export/import process, however the vrmesh does not contain detailed material information. When you import a vrmesh, it will be assigned default materials in place of whatever materials were previously applied to the object prior to exporting the vrmesh. The recommended workflow at this point, is to create the proxy in-place, in order to preserve material information, and then export the component to a separate .skp file. All of the preview geometry and material info should be preserved in the skp, so when you import that file as a component, you won't have to wait for us to read the vrmesh file, create the preview geometry, and create or hook up materials.

we had a faster export method previously, but we had an issue when someone would try to export a model that had been mirrored. The normals would be inverted, and we were unable to easily remedy this without changing how we exported to utilize SketchUp's explode command... which as we have been told, and you can see... is slow. We will continue to try to optimize this process, but for this release, we opted for correct but slow, over fast and incorrect.

The beta period is over, your demo license has expired. When you upgrade to 2.0 you will receive a dongle that plugs in via USB and your watermark issue should disappear.

I really don't recommend messing with the power parameter, if you want physically accurate results. The power overrides the IES file's information. It should be left to 0, unless you really know what you're doing. Plugging in random numbers isn't going to result in something accurate, because the IES file already contains the correct information for that particular light. Get a different IES file, and ensure that you are working in the proper units.

you tried upping the light subdivs?

http://help.chaosgroup.com/vray/help/rhino/150R1/rectangularlight_params.htm

try upping the subdivs:
Subdivs - this value controls the number of samples V-Ray takes to compute lighting. Lower values mean more noisy results, but will render faster. Higher values produce smoother results but take more time. Note that the actual number of samples also depends on the DMC Sampler settings.

no, it's the same speed regardless of pro/make/free status. We track changes in real time while we are loaded, so that we can process RT renders quickly. If you have any response time issues, or any models that are failing to even load, please let us know about them. Submit a bug report to vfswip@chaosgroup.com.

$820!

he has been beta testing through the entire development process, so I would assume it's a 2.0 render.

you'll have to check with your local reseller for an accurate answer. For example: http://vray.com/vray_for_sketchup/buy_vray_2_for_sketchup_upgrade.shtml

yes, it's how we license now. Even on one computer, our old licensing system was terrible. A hardware change, major OS change, or a few other somewhat random factors, could cause your existing software based license to become invalid. With the dongle, it's hassle free. The only downside is that you need to plug it in to a usb port either on your machine, or a machine on your local network.

We don't respond to all bug reports necessarily. Only if we need additional information, much like sending a bugsplat off to Trimble, or a crash report off to Apple or Microsoft. Due to the volume of reports, and the level of technical knowledge required to give a productive response, we just can't respond to reports very frequently. We thank you for your feedback, and I can assure you it was not lost in the system. We link related cases together, and your report was likely closed with the other cases related to it.

The dome light editing issue was addressed in this release, as were the other issues mentioned in this thread. If you check the changelog of our current 2.0 public release (it's out of beta now) you should see those issues noted as being resolved.

I agree that dongles have been around longer than software licensing, but the current dongle tech isn't too bad, and it's certainly less of a headache than the software licensing we have traditionally used in V-Ray for SketchUp. One thing in particular to keep in mind, is that you can share the license across the network, just as you could with the software licensing. Just set the dongle up on a machine on your network, and point your client installation at the machine that has the dongle plugged in.

no, that's fryrender

2.0 was released today, I think we may have already addressed this issue

yay!

we use the same control for all external file controls. So in some cases it's handy, in others, it's not.