Indigo Renderer Forum

Here it is. The latest Maxigo for Indigo 08.
A lot has been re-written so some stuff may be broken.
There are also some new and experimental things like converting bitmaps to jpg and rendering tiled bitmaps as procedurals and etc. They may or may not work as expected. Also the directory structure is changed a bit. Now every scene goes into it's own folder which has the same name as the scene in 3ds Max. Rendered images go to Indigo_dir/renders. Also there are no more two ini files. Now you can edit the ini that is located under Indigo dir. (like it is meant to be)
Diffuse transmitter material is added under diffuse material.

Here is the change log:


Changes in v.0.8.3:
===================
* added - Background color (Environment rollout)
* added - Glare (Camera Rollout)
* added - Hybrid mode (Advanced Setup rollout)
* added - Bih tree threshold (Advanced Setup rollout)
* added - Force Procedurals export (Advanced Setup rollout)
* added - Render Tiled bitmaps as procedurals (Advanced Setup rollout)
* added - Convert all bitmaps to *.jpg (Advanced Setup rollout)
* added - Diffuse Transmitter map (Diffuse Material)
* added - Better support for vray material (textures and refraction support added)
* added - Some support for vray blend material
* fixed - various bugs in animation mode
* fixed - Wrong error message when trying to view empty *.exr image
* fixed - Illegal *.OBJ material name export when '(' symbol in mat. name
* changed - Default procedurals resolution to 512x512
* changed - Medium/SSS material renamed to Glass/SSS
* changed - Maximum bumpMap value increased to 999
* changed - Exporter's directory structure reorganized
* changed - Indigo scene extension from *.xml to *.igs
* changed - Maxigo version numbering


Changes in v.0.8.3a:
====================
* added - Auto-Split models (Advanced Setup rollout)
* added - Dynamic memory increase when exporting large models to XML format
* fixed - Serious bug that didn't allow some users to export into OBJ format


Changes in v.0.8.3b:
====================
* fixed - A small bug in procedurals export routine
* fixed - Some parameters were not saved with the scene file



Have fun!
Suvakas

Thanks Suvakas!
Can you upload it to the download section ('exporters for 3d apps' in 'download' menu)

Sure.
I didn't know that it is possible

I think it is... It might have to be approved by an Op. tho.

I think i should wait a little before puting it to the official dl list.
Maybe it has a fatal bug or something
I'll wait for some users to test it first.

ps. what about updates? Should i upload those to there too or what's the policy?

Policy... heh....
Actually Radiance set it up so I don't know exactly what the privileges etc.. are. But If you can upload something, you should be able to remove it. So it doesn't matter too much if it has a bug.

wow! Suvakas! thanks for the cool update!
Will check it out ASAP and see if anything can be added to the VTs.

regards,
Alvaro

Thanks Suvakas....IT'S WONDEFULL WORK!!!
I test it immediatly!!
filippo

can I add the intensity of enviroment?
filippo

Thanks alot, Maxigo rulezzz!

a great and big thanks to suv!!!!Great exporter suv as well!!!!

Hi Suvakas. I was testing your exporter today with a medium complex scene and got this error:

how can I increase my scripter memory in max?
This was on the window behind:

thanks!

NM! found a couple of answers:

Customize->Preferences, there´s a "MAXScript" Panel containing a "Memory" group containing an input field. The default is 7.5 MB I think. You could try 50 MB, if your animation is rather long. If it´s really long (several hundred frames maybe) and if your skeleton/mesh is really complex, don´t be afraid to allocate hundreds of MB...

and:
http://www.turbosquid.com/Forum/Index.c ... adID/22291

let's see if it helps

Yeah..that can happen for big scenes. I'm not so sure about other formats, but it is a known issue when using xml format and models over 160k polys (or something like that..dont remember exactly)
What format did you use for export?
I recommend you to use obj for larger scenes.

[edit]
Maybe i can automate the process of increasing the scripter memory if there are models over 160k polys in the scene. I'll see if it can be done.

Hi Suvakas! Indeed I had xml as export option. Increasing the scripter memory to 150 mb helped out,though I had big focus problems, hehhehehe, have to check my camera options. Will try to post some screens soon.

But it would be great if the memory can be increased automatically.

regards,
Alvaro