Maxigo 0.8.3b (update-25 May 2007)
Maxigo 0.8.3b (update-25 May 2007)
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
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
- Attachments
-
- Maxigo_0.8.3b.zip
- Latest Maxigo for Indigo 08.
- (269.44 KiB) Downloaded 5293 times
Last edited by suvakas on Sat May 26, 2007 5:52 am, edited 2 times in total.
- Kosmokrator
- Posts: 1141
- Joined: Sat Jul 29, 2006 11:52 am
- Location: Greece-Athens
- afecelis
- Posts: 749
- Joined: Tue Aug 01, 2006 4:14 am
- Location: Colombia
- 3D Software: Blender
- Contact:
NM! found a couple of answers:
http://www.turbosquid.com/Forum/Index.c ... adID/22291
let's see if it helps
and: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...
http://www.turbosquid.com/Forum/Index.c ... adID/22291
let's see if it helps
AMD Ryzen 7 1800 @3.6ghz, 32GB ddr4 3200 mhz Ram, Nvidia RTX 3060 12GB, Win10, Blender/Sketchup/Modo/Cinema4d
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.
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.
- afecelis
- Posts: 749
- Joined: Tue Aug 01, 2006 4:14 am
- Location: Colombia
- 3D Software: Blender
- Contact:
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
But it would be great if the memory can be increased automatically.
regards,
Alvaro
AMD Ryzen 7 1800 @3.6ghz, 32GB ddr4 3200 mhz Ram, Nvidia RTX 3060 12GB, Win10, Blender/Sketchup/Modo/Cinema4d
Who is online
Users browsing this forum: No registered users and 29 guests