Luz não atravessa vidro no Vray 1.5 rc3

Pois é! Não dava esse problema! Eu sempre usei o vidro com sub/multiobject... Agora não dá mais!!! Pelo menos na versão 1.5 rc3... Alguém tem mais alguma dica?

Tudo vale a pena se o 3d não é capenga!!!

É o seguinte o bug existe mesmo e as vezes nem precisa tar em multi/sub, existe tambem uma variável que o pessoal nao atenta que é o max deph, caso ele esteja baixo no material podera ocorrer alguns erros tanto nas luzes quanto nos reflexos, uma outra variével é quem usa o active 3d para modelar, pois o mesmo coloca dois planos para representar o vidro, sugiro que retirem um desses planos e tente novamente..... se de todo caso nao funcionar faça como fiz(reinstalei o vray)...comigo passou a funcionar...1.5 r3

Vamos que vamos....

Olá pessoal....fiz uns testes aqui e realmente o VrayBlendmtl resolve o problema. Basta colocar o material do vidro dentro do "Base Material" do VrayBlendMtl....só isso já foi suficiente....mas realmente eh um erro primário por parte do programa, como disse o André, mudaram algo que já funcionava. Mas tá valendo..valeu Hawf pela dica....resolveu um problema q aconteceu comigo tb Grande abraço a todos

Eu avistei mais longe que muitos porque fiquei de pé em ombros de gigantes.

nossa! me resolveram um problema q eu tinha já faz tempo! huhauahua vlw

"YANES" disse: É o seguinte o bug existe mesmo e as vezes nem precisa tar em multi/sub, existe tambem uma variável que o pessoal nao atenta que é o max deph, caso ele esteja baixo no material podera ocorrer alguns erros tanto nas luzes quanto nos reflexos, uma outra variével é quem usa o active 3d para modelar, pois o mesmo coloca dois planos para representar o vidro, sugiro que retirem um desses planos e tente novamente..... se de todo caso nao funcionar faça como fiz(reinstalei o vray)...comigo passou a funcionar...1.5 r3

Que eu saiba este bug só acontece se estiver dentro de um multi/sub material. O Affect Shadow não funciona. Se o max depht ficar sempre em 5 não tem problema algum, até caustic vai funcionar. Abraços a todos!

Oi André! Realmente, dessa vez os caras abusaram com esse bug do affect shadow. Li no forum dos usuários que o erro foi causado por várias alterações no codigo por causa do max9. O que eu não entendo é como eles soltaram uma release com um bug tão ridiculo como este. Os usuários estão reclamando direto e pedindo uma nova release, mas como falei pra vc, só vai sair na siggraph e estão prometendo que vem cheio de novidades e com um ganho de velocidade enorme pra compensar essa demora de uma nova "release candidate". Ja está disponível uma versão demo da versao RC4, mas disseram que nao é a final. Aqui tem uma lista dos bugs corrigidos, fora os que ainda estão corrigindo + as novas funções: [code:1:b01166bcbb] New features: (*) New render elements: VRayMatteShadow, VRayTotalLighting, VRayRawTotalLighting. Modified features: (*) Updated WIBU-key drivers for 32- and 64-bit Windows* (including Windows* Vista*) are included with the installation; (*) VRaySun is now compatible with the 3dsmax Daylight system and can be selected as a sun type; (*) VRayDisplacementMod now supports high-dynamic range textures for displacement in "2d landscape" mode; (*) VRayPhysicalCamera supports horizon line in the viewports, clipping and environment near and far ranges; (*) Distributed rendering can now be started as a BackBurner job; (*) VRayColor texture has an option to apply gamma correction to the displayed color in the UI; (*) "Don't affect colors" option for color mapping; useful if you only need the sampling adaptation to be performed; (*) "Cutoff" threshold parameter for VRayLight's allows to reduce render times in scenes with many weak lights; (*) "Envrionment priority" option added to VRayMtl to control environment override behaviour between different materials; (*) Options for directly controlling the render mode (region, crop etc) of the V-Ray VFB; (*) "No GI on other mattes" and "GI surface ID" parameters added to VRayMtlWrapper; (*) Matte objects with the "Shadows" option checked will now generate VRayRawLighting, VRayRawShadow and VRayMatteShadow elements; (*) If "Check for missing files" option is checked, DR will now fail on the render slaves if some maps cannot be found, instead or rendering wrong buckets; (*) If there are several VRaySun nodes in the scene, VRaySky will now pick the first one that is enabled (rather than the first one at all); (*) V-Ray will now force multithreading when 3dsmax is in slave mode, regardless of the 3dsmax multithreading option; (*) When rendering to texture (RTT) the 3dsmax VFB is now always generated, regardless of whether the V-Ray VFB is on or off; (*) VRayFur can now generate motion blur with more than 2 geometry samples; (*) The irradiance map viewer will print out the progress of merging irradiance maps; (*) The autosave file names for irradiance/light cache/photon/caustics maps are now updated at each frame, rather than only at the render start; (*) The irradiance/light cache/photon/caustics maps are auto-saved as soon as they are computed, rather than at the end of the frame/rendering; (*) The "Save maps per frame" option has been removed from the GI rollout; (*) VRayProxy will now re-link the .vrmesh file at each frame, rather than only at the render start; Known issues: (*) When rendering a 3dsmax Raytrace material applied on VRayProxy objects, V-Ray will crash; Bug fixes: (*) "Affect shadows" and "Affect alpha" options did not work for VRayMtls inside a Multi/subobject material (RC3 bug); (*) Moving VRayPhysicalCamera caused spurious MacroRecorder events about the target distance changing; (*) Problems with 2D displacement (RC3 bug); (*) Automatically created VRaySky did not have a name; (*) Horizontal scrolling problems with the V-Ray messages window; (*) VRayOverrideMtl could cause 3dsmax to crash; (*) Multi/subobject material inside a VRayBlendMtl etc. did not render; (*) 64-bit V-Ray could fall into an infinite cycle when rendering 2d displacement; (*) Some rare raycaster precision errors were fixed; (*) Starting/finishing rendering could be extremely slow in 3dsmax R9; (*) VRayHDRI always took at least 10 MB of memory, regardless of actual image size (RC3 bug); (*) Incorrect irradiance map density and texture sharpness when using camera clipping planes; (*) Missing files (textures/VRayProxies etc) were not always detected correctly; (*) Distributed rendering between mixed 32/64-bit V-Ray versions did not work properly; (*) Standard materials with transparency did not render properly (RC3 bug); (*) No motion blur for ParticleFlow on 64-bit 3dsmax; (*) Color corrections from the V-Ray VFB were applied to the alpha channel when splitting the render channels to files; (*) Crash with the "Show map in viewport" option for VRayMtl when using Direct3D (RC3 bug); (*) Textures with mapping channels greater than 1 are now correctly shown in the Material Editor; (*) The "Global light level" options from the Environment dialog now affect the color of VRayLights and standard 3dsmax lights; (*) VRayBlendMtl did not list the blend textures as sub-anims; (*) If "Render to raw image file" option for the V-Ray VFB was ON, but the file name is empty, V-Ray would freeze while rendering; (*) The parameters of VRayMtlWrapper did not have proper names in Track View; (*) If the primary GI engine was light cache or photon map but GI is turned off, standard materials would render black; (*) VRayMtl materials with low glossiness inside a VRayBlendMtl could produce polygonal artifacts on shadow/light boundaries; (*) The pixel aspect ratio from the Render Scene dialog was ignored when rendering with DR to the 3dsmax VFB; (*) A low-dynamic range 3dsmax frame buffer was used even when saving to a high-dynamic range file format (.exr, .hdr etc); (*) Problems when rendering animations in DR mode with light cache as both primary and secondary engine; (*) Small rectangle area lights could produce artifacts for points lying close to the light plane; (*) Somewhat better memory management for proxies and dynamic meshes; (*) Crashes with VRayFur on animated objects when using motion blur; (*) Incorrect environment color with several VRayLights in "dome" mode; (*) "Crop" render mode with the V-Ray VFB did not work for animations; (*) Sporadic crashes when using the "Camera Map Per Pixel" texture inside V-Ray materials (VRayMtl, VRayLightMtl etc); (*) VRayBmpFilter did not always display its bitmap texture successfully; (*) VRayBmpFilter could produce invalid colors; (*) Photon mapping could produce wrong GI on transparent surfaces; (*) Crashes with interpolated glossy reflections/refractions if there is only 1 sample in the interpolation map; (*) Irradiance map produced incorrect results when used with VRayLight in "Light portal" mode; (*) Faceting on low-poly geometry when using anisotropic reflections with UV-channel mapping; (*) Incorrect sampling with gamma color correction when some of the pixel RGB components is zero;[/code:1:b01166bcbb] Abração!

Ai pessoal, descobrir mais um bug no vray, quase fiquei doido, ate achar onde estava o erro, 'e o seguinte qdo aparecem uns erros de faces sobrepostas existe uma variavel "ray bias", se aumenta la um pouco ela da uma melhorada nas manchas pretas....mas ai que ta o grande problema, se retirar essa variavel do valor "0", todos os mapas de opacidade daram uns erros mais loucos....depois de uma semana que descobrir isso...tomem cuidado ao usar esse recurso.....

Vamos que vamos....