I just purchased Viz 2006 and Vray so I am really stuck. I can’t get the older build of Vray and I only have Viz 2006.
if you email chaosgroup directly i’m sure they’ll be able to get you an older build.
they’re very helpful if you ask!
Only just found this post.
Had exactly the same problem but been wandering down the distributed render problem route…
Would have saved me hours of grief if this had been a sticky post…
Geoff
Vlado, Have you had any luck squishing the missing texture maps bug in VIZ 2006?
Thanks,
-Shane
Any news? thoughts? ways to fix?
This will be corrected for the next V-Ray release.
Best regards,
Vlado
Great to here Vlado! Thanks.
-Shane
In the mean time. I noticed that it was only happening to be during the GI clac phase. I turned off the maps, and made the diffuse color of the material to the general color of the bitmap. Calc GI only, then turn on maps using global switches.
Temp. work around, but it works.
good news from vlado about viz2006…
http://www.chaosgroup.com/forum/phpBB2/viewtopic.php?p=98627#98627
I finally got my hands on VIZ 2006 and I can reproduce the issue here; it happens with or without GI… I’m looking into it currently.
Best regards,
Vlado
Good news Vlado. Look forward to the solution. I’ll brush the dust off my copy of VIZ2006.
Chris.
yes, great news, thanks vlado.
I think I found the reason for this; it seems like the “fix” for the VFB pan/zoom crash is causing it. While it works in 3dsmax, it causes all sorts of bitmap problems in VIZ 2006. So I’m a little baffled as to what to do at this point… if worse comes to worse, I’ll restore the old VFB update code.
Best regards,
Vlado
thanks for the update, vlado!
The final answer I got from AME is that the problem is a bug in 3dsmax7/VIZ2006. I am told that in 3dsmax 8 (and perhaps the next version of VIZ) this issue is fixed.
The problem seems to be related to changes in the Bitmap pager and it can cause crashes even if the Bitmap pager is off.
It also appears that the problem is there in max7 too, but for some reason its much more apparent in VIZ 2006.
Best regards,
Vlado
Thanks for the information Vlado.
Looks like I’ll be putting Viz 2006 back on the shelf until the next release comes out.
damn. :evil:
‘perhaps’ the next version of viz…
that’s pretty annoying - doesn’t leave much option but to wait for the next viz release and keep our fingers crossed…or drop vray and use mental ray, which i’d really hate to happen.
thanks for the info and work you’ve put in trying to find a fix for this vlado.
s0real,
I’ve been using VIZ 2005 with 1.47.03 and had no problems at all. I’ll be sticking with it until the next version of viz is out. No need to drop it. ![]()
do you mean viz 2006?
I meant that I’d be sticking with Viz 2005 and 1.47.03 until they (autodesk) release a version or update that corrects this problem.
I would much rather do that than drop Vray for mental ray personally.