www.kraytracing.com

AE CS6 has built in camera tracker, as well there are Boujou and Autodesk MatchMover Workflow in general is. 1. Track you footage, 2. Get camera and reference data to LW. 3. Clean up motion if necessary. 4. Move you house model, matte objects to position you need 5. Render animation 7. Composit to s...

My old 2.4 scenes with spherical lights - crash LW11+Kr2.5 BUT. Same stuff imported to the new scene (including all lights) renders just fine. Trying to figure out what is going on. UPD. These is solution. If Kray Options - Quality Tab - Light quality section - Luminosity Min/Max Rays set to 0 - Sph...

Not sure if you have the version that was removing any decimals from some of the settings, but that has been fixed.

Do you mean new version of Lightwave? or new version of Physical Sky script?

Looks like there is a bug with MB + Grid FSAA, it doesn't work in case when scene has multiple cameras and camera that has highest ID (listed last in Classic Scene Editor) doesn't have motion blur enabled. Not sure if i put it clear enough :) If it's necessary i can post a message in a bug tracking ...

Which AA modes Motion Blur supposed to work with?
Manual states MB should work with any FSAA. But so far i got it working with Random Full Screen AA only.
Grid FSAA, Quasi-Random FSAA - don't work with MB, is it correct?
(Kray 2RC5)

That´s slow!

Try it with Kray

hope this article will help to get more users, forum feels a bit abandoned nowdays

If polygons are okey (no double polygons, and so on), artifacts like one on the last image (black noise on some polygons) can be caused by some Kray bug. It's easy to check. Change "Backdrop Color" in "Backdrop" tab to any other color. If noise on yours render will change color a...

It doesn't affect "raytrace" part but it does affect how FG samples are placed. In this case "Progressive" mode produces more aligned FG sample placement which causes distinctive vertical artifacts. I guess it was only reason to make all these modes.

First, prepare yours sample scenes so it could be opened easily on remote computer. Some people wouldn't bother if they couldn't open a scene right away. In General tab change "Pixel order" say to "Scanline" instead of "Progressive" and you will get better result right ...

this means you don't create many FG sample points for your cache, that you want to have in final render in all frames of different nodes.

Upsample is AA setting. It doesn't affect FG pass at all. Just try it once.

I don't know what happens with Undersample 512 but to me it sounds like accuracy goes out the door that way, nothing for nothing. Virtually it renders just few pixels from final frame. So you are right - it renders almost nothing from final frame. It saves a lot of time if you want to create GI cac...

Off AA setting on point 1 to speed up the GI computation If you really want to minimize frame rendering time for GI pre-caching: set AA Preset to Custom, Antialiasing to None, Undersample to 512, Threshold to 1.0. This way rendering final output will take just few seconds . Maybe some day G will ad...

There is HDI stress test rendered on Core2Quad@3Ghz, render time 1-2 minutes.

nico wrote:the render time with instance is too slow or as kray instance?

HDI renders slower under Kray, but with native LW render HDI renders a way faster, and with vertex mapping trick its just unbeateable. I wish Kray instancing would be as fast as HDI in native LW render.