Maxigo 2.2 beta - 1.Feb 2010

[suvakas]

You're welcome.
I just took it out of beta and you can download 2.2 stable from the main Maxigo download page too.
It's basically the same thing as the beta. The only difference is, that the version number doesn't say "beta" anymore.

To be honest the video is boring after twice the 2.2 export time... nice improvements suvakas

Thank you CTZn!

[hcpiter]

Hi,
Can you add in future update one thing in material editor ?
Basically when you make material in indigo but use max editor is hard to found materials made in indigo, because slots (balls) are not change or update.
I made easy images for better understand


Thanks

[Soup]

Those max previews are effected by some attributes, such as the diffuse colour I believe. But I agree that I have lost Indigo materials amongst max ones, perhaps made a bit more obvious?
Creating real Indigo previews of materials is not practically possible, it would slow the system too much.

[hcpiter]

Right, realtime preview material is not good idea because will be very slow, but maybe just fake like in fry ? There is just image as screen from prewiew, if you duble click in slot you got just image/bitmap not in realtime.

thanks

[dcm]

any progress in new version ?

[suvakas]

any progress in new version ?

Hey,
Yep, making some nice progress.
It's a total rewrite actually. Maxigo is a "real" render plugin now.
Scene export will be much faster. Exporting instances is already about 20 times faster than in current Maxigo version.
Also most of the render modes will be supported like region, crop, selected, blowup.
Can't say any dates though. It will be done asap.

[dcm]

woo, nice im excited!

btw would be great to have perlin noise generator like in cindigo and access to ISL.
In the new Maxigo, materials preview is supported? Like hcpited mentioned few posts before?

[suvakas]

In the new Maxigo, materials preview is supported? Like hcpited mentioned few posts before?

Probably yes, I'll look into it.

[hcpiter]

In the new Maxigo, materials preview is supported? Like hcpited mentioned few posts before?

Probably yes, I'll look into it.

WOW Great news! lovely
Some materials doesnt work in max material editor when I try import from datebase but works just in material editor from indigo not maxigo.

[dcm]

20 times faster export. Wicked !
Im working with huge scenes mostly and im waiting up to 5 minutes for export. Great news
Thanks Suv for your attention and hard work.

[suvakas]

20 times faster export. Wicked !

Only when instances are used
Don't expect to have 20 times speed increase when all your scene models are unique.

[subpixel]

Hi suvakas,

How is it going with switching to native renderer? Hope to see it soon.
Since I've completed igmesh implementation, I did some tests and it seems that imeshe files generated with Maxigo are about 3 times bigger compared to ones exported with IndigoMax. Something you might take a look with new version.

Also you might consider checking if UV data is ever needed. It's a considerable space saver since by default Max objects have at least one UV channel, and materials might never use it. Correct me, if i'm wrong but it seems that Maxigo doesn't perform such check.

Anyway, good luck and congrats on your good work.

Regards,

[suvakas]

Hi suvakas,

How is it going with switching to native renderer? Hope to see it soon.
Since I've completed igmesh implementation, I did some tests and it seems that imeshe files generated with Maxigo are about 3 times bigger compared to ones exported with IndigoMax. Something you might take a look with new version.

Also you might consider checking if UV data is ever needed. It's a considerable space saver since by default Max objects have at least one UV channel, and materials might never use it. Correct me, if i'm wrong but it seems that Maxigo doesn't perform such check.

Anyway, good luck and congrats on your good work.

Regards,

Hey subpixel,
Checking if UV's are needed would probably be a good idea.
What's your goal with this IndigoMax thing anyway? Duplicating an existing exporter seems lika a waste of man power. We have several apps that don't have exporters at all. I get that you wanted it to be a render plugin, but next Maxigo version will also act as a render plugin so... I see no point in doing this.

[subpixel]

Well, that sounded kind of discouraging. Was that your intention? I hope not

Concerning other apps: most of the apps I could help with have already exporters. Max is my preferred environment hence this choice.

The IndigoMax originates from an independent animation project, which is at the moment in preproduction. I'm responsible for rendering and i'm trying to convince some people that it might be possible with Indigo. So my main field of interest is rendering sequences, something that I failed to achieve with Maxigo (too many errors, not stable enough). I believe that an animation rendered with Indigo should become a nice advertisement of this renderer and draw some more attention to it.

I was happy to hear that Maxigo is being converted into native renderer, but since there was no roadmap nor announcements about release date, I decided to do it myself. I treat this as exercise in maxSDK, yet something other could benefit from. I believe that diversity of solutions is the best way to go. Somewhere in-between lies the perfect one. However your experienced help is more that welcome since as I see (from some past posts) your experience with C++ and MaxSDK is quite fresh.

Anyway, I'll continue to develop this plugin, hoping for some comments and feedback from you and rest of the community.

Regards and best wishes on your endeavours,

[fused]

Modo, Wings, ArchiCAD, AutoCAD, etc

You should contact nick at indigorenderer dot com if you're intrested in partnering with us and writing an exporter for a diffentent app.