vray 1.9 è c4d r16 compatibile?

Forum dedicato a tutti i motori di rendering come Vray, Corona, Octane, RedShift, inserite i vostri rendering e postate le vostre problematiche.

Moderators: Arkimed, natas, visualtricks, cappellaiomatto

Post Reply
  • Advertising
walterfog
Posts: 574
Joined: Tue Feb 01, 2011 8:44 am
Location: treviso

vray 1.9 è c4d r16 compatibile?

Post by walterfog »

ciao ragazzi.. ho da poco fatto l'aggiornamento alla R16 di c4d studio.
volevo sapere se vray 1.9 funziona tranquillamente o se bisogna fare attenzione a qualcosa.
che mi dite?
grazie a tutti
62VAMPIRO
Posts: 3807
Joined: Mon Mar 14, 2005 6:46 pm

Re: vray 1.9 è c4d r16 compatibile?

Post by 62VAMPIRO »

Certo, funziona senza problemi: dovrebbe averne? :) :) :) . La stabilità o meno di Vray non dipende dalla versione di Cinema, ma dal lavoro fatto o non fatto dal team di Laub e stavolta, contrariamente alla sgangherata uscita dell 1.8, hanno fatto le cose per bene..........
walterfog
Posts: 574
Joined: Tue Feb 01, 2011 8:44 am
Location: treviso

Re: vray 1.9 è c4d r16 compatibile?

Post by walterfog »

62VAMPIRO wrote:Certo, funziona senza problemi: dovrebbe averne? :) :) :) . La stabilità o meno di Vray non dipende dalla versione di Cinema, ma dal lavoro fatto o non fatto dal team di Laub e stavolta, contrariamente alla sgangherata uscita dell 1.8, hanno fatto le cose per bene..........

ottimo... buono a sapersi.... grazie e buon lavoro!!!
User avatar
nexzac
Posts: 4888
Joined: Wed Dec 03, 2008 4:08 pm
Location: Milano

Re: vray 1.9 è c4d r16 compatibile?

Post by nexzac »

La r16 crasha quando si utilizzano gli shader disturbo di cinema4d nei materiali vray (su Mac).
Dear Users,

the reported problem of the freeze with the OSX c4d noise in v16 is now, after 3 hard weeks of work, clear where it comes from:

it is a c4d threading bug inside cinema4d v16 which in special is visible on osx in the noise shader, but also can affect v16 overall with vray (win and osx), but maybe also some other engines or plugins.

- the good is one Maxon dev was very helpful in this indeed searching the reason, and he found it also and also fixed it last Friday - thanks a lot!
- the not yet so good is that it is yet unclear when Maxon will/can release the bugfix to public, as they just released a SP last week (16.027 without the fix yet in).
we very much hope that Maxon will be able to provide the fixed version as fast to you as possible, as kind of hotfix. we know many of you on v16 wait for this (it seem to affect all v16 usage and stability on both OS),and we also tried to make that clear to them.

so lets hope they decide to make a fasft hot fix for that possible, to give the already existing fix to all of you all (of course some testing etc needs to be done from their side in any case before releasing a new SP). On this first also big thank you to Maxon devs for the very responsive help and reaction!

i keep you updated with info in this thread

best greetings
Stefan
Image
"if you can't explain it simply, you don't understand it well enough"
  • Advertising
Post Reply