VIZ 2006 - maps not rendering [updated - bug in max/viz]

[vlado]

Well, like I said, I can try to roll back the part of the code that I *suspect* caused the bug in VIZ to become apparent. This would be a temporary fix though, since it will cause other problems (crashes while panning/zooming in the 3dsmax VFB). I'm very frustrated by this issue, but it looks like we don't have much of choice - got to choose the lesser evil

Best regards,
Vlado

[timmatron]

Well, like I said, I can try to roll back the part of the code that I *suspect* caused the bug in VIZ to become apparent. This would be a temporary fix though, since it will cause other problems (crashes while panning/zooming in the 3dsmax VFB). I'm very frustrated by this issue, but it looks like we don't have much of choice - got to choose the lesser evil

Best regards,
Vlado

I would take the crashes from the vfb any day if it will fix the maps problem. I will just use Vray's vfb when I need to zoom & pan during rendering.

[percydaman]

Well, like I said, I can try to roll back the part of the code that I *suspect* caused the bug in VIZ to become apparent. This would be a temporary fix though, since it will cause other problems (crashes while panning/zooming in the 3dsmax VFB). I'm very frustrated by this issue, but it looks like we don't have much of choice - got to choose the lesser evil

Best regards,
Vlado

I would take the crashes from the vfb any day if it will fix the maps problem. I will just use Vray's vfb when I need to zoom & pan during rendering.

maybe you should get a whole list of problems before you say that. the zoom and pan might just be one of several.

[vlado]

personally I recently purchased vray to use with viz 2006. If I had been warned that there was a problem that would not be fixed I would not have bought it. Vlado you previously mentioned a potential workaround - any chance that could be implemented ?

Well, the bug is there in VIZ anyway; V-Ray just made it more apparent. There is no knowing if/when you might run into problems even if you don't use V-Ray. The work-around might make things better, but I don't know if the problem won't appear in some other form.

Best regards,
Vlado

[leotchest]

Is it safe to say that this bitmap problem is not present in Max 7.5 ?
I am wondering about migrating from Viz to Max, & therefore wondered if there were any known problems (like the known problem between Viz 2006 & latest Vray) Autodesk have released a Service Pack for Viz 2006 but it has not fixed the problem.

[vlado]

Is it safe to say that this bitmap problem is not present in Max 7.5 ?

I am not sure. People have not reported this problem in Max 7.x and I have not noticed it either. However, the problem might still be there in the 3dsmax core, even though it may not be evident in many cases.

Best regards,
Vlado

[leotchest]

Are Vray doing anything about warning potential customers about this problem? As a Viz 2006 user I would not have bought Vray if I had known that this problem was going to be left in limbo. I have not noticed any serious rendering problems in the last year of using Viz without Vray, so even if there is some kind of bug, it does not affect my productivity. At the level of the customer, the latest Vray seems to have a serious incompatibility with Viz 2006 (which works fine on its own & which has recently been issued a service pack) and I dont think its satisfactory to tell prospective customers that they should not use the 'up-to-date' software. I dont see how anyone can buy Vray with confidence when there is no guarantee that it will work. I wonder why in the world of software providers like Chaos there is no real empathy with their clients? (im thinking of typical customer support solutions like "refund" or providing assurance of a "fix").

[vlado]

I do not see how a bug in VIZ becomes an incompatibility with V-Ray, but if you are not satisfied with your V-Ray purchase, you can always ask for a refund by sending an email to vray@chaosgroup.com

Best regards,
Vlado

[Morbid Angel]

Are Vray doing anything about warning potential customers about this problem? As a Viz 2006 user I would not have bought Vray if I had known that this problem was going to be left in limbo. I have not noticed any serious rendering problems in the last year of using Viz without Vray, so even if there is some kind of bug, it does not affect my productivity. At the level of the customer, the latest Vray seems to have a serious incompatibility with Viz 2006 (which works fine on its own & which has recently been issued a service pack) and I dont think its satisfactory to tell prospective customers that they should not use the 'up-to-date' software. I dont see how anyone can buy Vray with confidence when there is no guarantee that it will work. I wonder why in the world of software providers like Chaos there is no real empathy with their clients? (im thinking of typical customer support solutions like "refund" or providing assurance of a "fix").

I think people are forgetting that vray is still in beta, and betas bound to have problems, so those who purchaise beta have to come into terms with bugs and issues that it might carry with it.
When we moved to vray, I have already known that there would be problems on many fronts. But I was prepared to search for workarounds and other mesures because vray imo is still a great product.

[leotchest]

Being a Beta would certainly make a difference - but I dont think its adequately marked as "Beta". The download section states 1.47.03 is a stable build - no mention of beta there. Anyway, as Vray have offered a refund then all is forgiven.

[Da_elf]

actually it should be marked its a stable build for max if memory serves me right it just so happens that it works in viz as an added bonus for the viz people. so if viz has a problem you cant fault vray now can you? as far . just read through chaos's site and yup... seems its being marketed as a plugin for max.

[leotchest]

When you install Vray in VIZ, the installer specifically states "V-Ray for 3dsmax and Autodesk VIZ". That seems pretty clear to me. Of course what it should say is "Vray for 3dsmax and Viz so long as your not using the latest version of Viz - in which case, dear customer, you are screwed". Chaos should provide a warning to their Viz 2006 customers.
Anyway, despite all this I would like to be a Vray user because it is a cool, even if somewhat embattled, product. From the threads I have read though, even Max 7.5 looks like its has more than its fair share of problems with Vray.

[vizage]

VIZ 2006 problem

Hello everybody,
I use Autodesk VIZ 2006 and V-Ray 1.47.03 and I have the same problem with non-rendered maps, like the others. Now I´m doing some tests, because here are some strange things. At first: it seems, that V-Ray 1.47.03 works correctly with only with Quasi-Monte Carlo as secondary bounces GI engine. But, if you switch the secondary bounces to the Light Cache- you will be frustrated, because the maps will disappear. Well, it´s really incalculable when the renderer will miss the maps, but with Quasi-Monte Carlo you can be sure ( i hope) you´ll be succesfull.
At second: we tried out another way. If we got the error with maps, we switched off all programs, log-out workstation, then log-in again and run only Autodesk VIZ 2006, we opened the last file with our work and started renderer without doing any action (like zooming, dragging etc.) and the problem disappeared.
So, perhaps this is some pure solutions to use it ... We hope it could help to developers of V Ray plugin.
bye

[vizage]

what a hell?

Oh oh...we are sorry - the first render from the 153th test pictures...oh damn, is without maps (using Monte-Carlo). It doesn´t work....
Maybe, next time...

[Da_elf]

ah sorry. my bad. ive installed vray so many times in the last...hmmm. 4 years? or is it 5? that i dont pay attention to whats written there anymore. (hey. vray should do something special for its 5th aniversary hehe)