my bug list

[plastic_]

all in one i'm having great fun with VrayRT, especially DR works like a charm (once it's set up).
here are some issues:


INSTALLER
----------

-) installer doesn't warn if a license server service is running.

-) vraylicense webserver isn't found with hostname, only with ip (vista 64, sp1)

VRAY RT
--------

important bugs/unacceptable behaviour:

-) vrayRT doesn't pause when a ordinary vray render is started. vray.exe and 3dsmax.exe fight for cpu power as a result, when "low thread priority" is active. same behaviour with DR servers.


bugs/missing features:

-) DR servers are not found with hostname, only with ip. with standard vray DR, hostname lookup is working.

-) resizing the max window, or the active viewport results in a black window, until activeshade is restarted

-) activeshade window doesn't crop to safe frames (important for composition tweaking)

-) secondary ray bias is ignored (for fixing coplanar faces...important for archviz)

-) something fishy with smoothing groups and reflections...smoothing groups completely ignored for glossy reflections?

-) different/wrong gamma with hdri bitmaps from the max map (not vray hdri), compared to vray render.

-) updating any vray render setting results in activeshade restart, even if setting has no affect on vrayRT.

[vlado]

-) installer doesn't warn if a license server service is running.

Hm, it does that here (check is the same as for the normal V-Ray installer). The only case where it can't detect the running instance is if the installer is 32-bit, but the running vrlservice is 64-bit.

vraylicense webserver isn't found with hostname, only with ip (vista 64, sp1)

If you mean through a web browser, this is not a problem of the service, I'm afraid; the name lookup is performed by Windows before it even attempts to connect.

vrayRT doesn't pause when a ordinary vray render is started. vray.exe and 3dsmax.exe fight for cpu power as a result, when "low thread priority" is active.

Yep, it was mentioned before; I'll see what can be done about that.

DR servers are not found with hostname, only with ip. with standard vray DR, hostname lookup is working.

Yep, someone reported that; should be easy enough to fix.

resizing the max window, or the active viewport results in a black window, until activeshade is restarted

Yep; I think it worked if you make it larger, but if it was smaller we got crashes on the 3ds Max side, so this is intentionally disabled for the time being.

activeshade window doesn't crop to safe frames (important for composition tweaking)

If the viewport had the "Show safe frames" option before you start ActiveShade in it, then the preview will only be drawn in the safe frame region.

secondary ray bias is ignored (for fixing coplanar faces...important for archviz)

Yep, made a note of that, will be done.

something fishy with smoothing groups and reflections...smoothing groups completely ignored for glossy reflections?

Not sure about that one, I'll probably need an example. It cannot happen that smoothing groups are ignored just for glossy reflections - if there was an issue it would affect all shading.

different/wrong gamma with hdri bitmaps from the max map (not vray hdri), compared to vray render.

If you adjusted the settings of the HDRI reader when selecting the file (e.g. black/white points etc), we have no way to find this out for the time being.

updating any vray render setting results in activeshade restart, even if setting has no affect on vrayRT.

Yep, I've noticed this too, will see if it can be corrected.

Best regards,
Vlado

[simmsimaging]

Quote:
different/wrong gamma with hdri bitmaps from the max map (not vray hdri), compared to vray render.
If you adjusted the settings of the HDRI reader when selecting the file (e.g. black/white points etc), we have no way to find this out for the time being.

If you load an HDRI with the max bitmap loader try manually setting the gamma in the loader at 1.0. This matches VRay and RT outputs for me. Using the VrayHDRI map works fine, but I'm guessing that is because it overrides the gamma there to 1.0 by default.

b

[rajdarge]

more spiders

vray sphere doesnt show up in window at all

[rajdarge]

the renderslave dialogue box doesnt allow you to resolve servers
plus the servers dont actually seem to work .They are all in workstation installs, but I turned on the vrayRT renderserver thingy and it didn't seem to do anything on the other machines.

Can this be combined into one service?
Raj


I like how if you keep the window open and fiddle around with the main settings of vray the RT window keeps updating - nice

[vlado]

vray sphere doesnt show up in window at all

Anything not explicitly listed in the "supported features" page is not guaranteed to be supported: http://www.spot3d.com/vray/help/rt10...d_features.htm

Best regards,
Vlado

[vlado]

plus the servers dont actually seem to work .They are all in workstation installs, but I turned on the vrayRT renderserver thingy and it didn't seem to do anything on the other machines.

You need to use IPs for that it seems. Working on fixing that.

Best regards,
Vlado

[zoobadoo]

important bugs/unacceptable behaviour:

-) vrayRT doesn't pause when a ordinary vray render is started. vray.exe and 3dsmax.exe fight for cpu power as a result, when "low thread priority" is active. same behaviour with DR servers.

in addition i was wondering, what would happen if a few RT renderslaves would be adressed from two or more workstations at the same time? will only one job per node be allowed, so it will only be available for the other workstations when this job has finished? or could it be possible to manage this so the available servers would evenly be divided among the workstations, so calculation power is distributed evenly, instead of giving the first workstation all?

we have 18 max/vray dedicated rendernodes, and three workstations at which we would like to use RT simultaniously.

[vlado]

Currently it works pretty much like the regular V-Ray RT. If a server is already busy with an RT render, it will refuse to take part in other RT render requests, until the current render completes (e.g. the user closes the ActiveShade window).

Best regards,
Vlado