Really looking forward to see this renderer integrated into Blender.
And…
One of the most important thing is to get the material menus to
cohere with the Toxic renderer…in other words…what you see
is what you should also get in the renderer…
Like Yafray is now…it’s nearly impossible to use procedureals because
they turn out differently than the material-previews shows, it should
be possible to “activate”
Yafray Materials (in the f5 shader/texture menues)
really the number one thing is to get more people to test it.
really people, I’m telling you, it is not one of those complex ones like beast, blODEd or yablex, it can be run without any options changed.
Hmmm. I tried it on the standard startup scene and it crashed.
Here’s what I get in the console:
Made scene directory
exporting:
camera: Camera
lamp: Lamp
Traceback (most recent call last):
File "(string)", line 541, in Action
File "(string"), line 183, in Render
NameError: Lamp "Lamp" not found
I followed your installation instructions. I thought I did things right, but maybe I missed something?
that means the render did not complete correctly, it can’t find the output image.
try openning a console window and navigating to c: oxic\blender_export\run.bat and use that.
When toxic is finished check to see what it says. It most likey can’t read the scene export.xml file, even though it validates with the schema, so i think there may be a bug in the toxic xml parser, although it is the apache xerces, which I don’t think would have and error like that.
exporting:
camera: Camera.001
Traceback (most recent call last):
File "toxicx.py", line 567, in Action
File "toxicx.py", line 188, in Render
NameError: Camera "Camera.001" not found
exporting:
camera: Camera.001
Traceback (most recent call last):
File "toxicx.py", line 567, in Action
File "toxicx.py", line 188, in Render
NameError: Camera "Camera.001" not found
skip: 40, x: 640 y: 640, depth: 24 (18)
I had to delete the new python variable setting that you mentioned it messed up the Fiber Script. I will have to try this out later . I’ll make much use of this when I can get it up and going on my machine.
that data not found thing is strange.
i don’t know why it can’t find the data for it, I am looking right at the camera/lamp.
I will have an updated version with reflections and image textures soon.
Material conversion (or would it be light conversion?) needs some adjustments.
Knife rendererd in Blender internal:
Same scene rendered in Toxic using ToxicX:
On second thoughts… if area lights are not supported by Toxic or ToxicX, then that might be the cause of the problem. I had to use indirect lighting, because the area light would not export. Maybe that is why the Toxic render looks so… bright?
It’s still very young, so there are some important features still missing (eg. transparency), but when rendering using supported features, it looks extremely realistic.
area lights are fully supported, simply, well, add an area light. It will be exported as a light emitting sphere. (squares seem to have an export problem, I will fix this soon)
you need to change the light multiplier setting to get the right light amount. This is due to the fact that toxic is real unit based, and blender is not. (is one blender unit a meter or an inch?)
