MtI 3.4

Announcements, requests and support regarding the MAYA exporter
ior
Posts: 166
Joined: Tue Aug 24, 2010 11:47 am

Re: MtI 3.4

Post by ior » Tue Jan 15, 2013 6:14 pm

I removed the the code lines from ver 3.4.17 but Iv got this error on indigo app:

Code: Select all

Scene parsing error: Found unexpected element 'rgb'.  (In element 'scattering_coefficient', around line 120, column 9)

User avatar
CTZn
Posts: 7240
Joined: Thu Nov 16, 2006 4:34 pm
Location: Paris, France

Re: MtI 3.4

Post by CTZn » Wed Jan 16, 2013 2:03 am

Ok, I'll get round this too.

Try plugging an indigoSpectrum instead of using a raw RGB. edit: no way.
obsolete asset

User avatar
CTZn
Posts: 7240
Joined: Thu Nov 16, 2006 4:34 pm
Location: Paris, France

Re: MtI 3.4

Post by CTZn » Thu Jan 17, 2013 9:01 am

ior wrote:how about spherical camera?
I'm keen to move to 3.6 once mti 3.4 is more stable.
obsolete asset

ior
Posts: 166
Joined: Tue Aug 24, 2010 11:47 am

Re: MtI 3.4

Post by ior » Thu Jan 17, 2013 8:25 pm

I reverted to mti_3.4.16 and got more problems:

PhisicalSunSky is always on and appears always in the renders even if it is turned of, and when I move the drop down Environment Type menu, respective sliders appear over maya shelf (or something like that).

At some point I saw some letters over maya menus warning me that I had to have one light source.

After using an old scene and rendering two or three times one of the objects disappears from scene as I click render and the render turns black, I had to reload the scene again and after a while it did the same again.


Maybe this is because It conflicts with older version, Ill erase all MtI files and see if it is better. Edit: no, it is not.

ior
Posts: 166
Joined: Tue Aug 24, 2010 11:47 am

Re: MtI 3.4

Post by ior » Thu Jan 17, 2013 9:55 pm

I reverted to version 3.2.12.1 and this disappearing objects also happen when I click render and the commands mti_CHK; mti_Gen_render; are run.
Any thoughts?

User avatar
CTZn
Posts: 7240
Joined: Thu Nov 16, 2006 4:34 pm
Location: Paris, France

Re: MtI 3.4

Post by CTZn » Fri Jan 18, 2013 8:03 am

Please update to mti 3.4.17b attached below, it should fix environment and spectrum related errors, including the show-stopper within 3.4.17(a).

Let me know off persisting errors, thank you.
Attachments
mti_3417b.zip
Fix for mti 3.4.17
(279.13 KiB) Downloaded 436 times
obsolete asset

ior
Posts: 166
Joined: Tue Aug 24, 2010 11:47 am

Re: MtI 3.4

Post by ior » Fri Jan 18, 2013 11:56 am

I do not Know what is happening but there is something wrong with this scene exported by maya:
teapot stall.rar
scene that stall indigo when I try to move camera
(166.19 KiB) Downloaded 336 times
It is that old scene with fog and teapot. But it is too slow and when I try to move the camera in indigo it stall indigo. the geometry also do not appear in the left top side of indigo.
Some times when I export the scene from different saved scenes it is ok but normally it makes this.


about the disappearing objects when clicking render, it seems that the center pivot of some objects gets changed and after several renders the pivot is so far that the object disappears. If I center the pivot once and a while It doesn't do that problem.

User avatar
CTZn
Posts: 7240
Joined: Thu Nov 16, 2006 4:34 pm
Location: Paris, France

Re: MtI 3.4

Post by CTZn » Fri Jan 18, 2013 12:29 pm

The rar file you linked is not a portable scene, please use the "Pack Indigo Scene..." found in Indigo 'Tools' menu to make the scene portable in the future. Then, it's probably a job for support@indigorenderer.com since the scene description doesn't seem to be in cause ?

What helps me out ior is a Maya scene causing the error you want fixed, or reports allowing the reproduction of errors in Maya.
obsolete asset

User avatar
CTZn
Posts: 7240
Joined: Thu Nov 16, 2006 4:34 pm
Location: Paris, France

Re: MtI 3.4

Post by CTZn » Fri Jan 18, 2013 12:36 pm

I'm assuming that the MLT mode is slowing real time response a lot. Test camera navigation in Indigo in bidir only.
obsolete asset

ior
Posts: 166
Joined: Tue Aug 24, 2010 11:47 am

Re: MtI 3.4

Post by ior » Fri Jan 18, 2013 8:18 pm

I found out that when I put a sss with vatue of 200 it slows down the render (the higher the sss value higher the render times) and if use post process diffraction it slows down more, and adding to this if I render with MLT it is to slow for anything to be done. Maybe a bug, Ill post this in the req bug forum tomorrow after knowing your opinion.

About objects disappearing, I have a scene that if after opening I click render the->Indigo camera a sphere goes up in maya and goes down left in indigo, also in indigo, the plane that divides the scene is not there.
Please test if you get the same result:
sphere going up at render time 01.rar
(163.23 KiB) Downloaded 336 times

User avatar
CTZn
Posts: 7240
Joined: Thu Nov 16, 2006 4:34 pm
Location: Paris, France

Re: MtI 3.4

Post by CTZn » Sat Jan 19, 2013 3:39 am

Thanks a lot about the scene ior, that's something sound I can work on.

About the responsiveness of Indigo camera navigation during rendering, that does not qualify as a bug on my behalf. Bidir alone is expected to be the most responsive rendering method, MLT to be the slowest, period. MLT builds on top of PT or bidir, so it has to be slower than either. Keep in mind that the max depth is around 10000 and other costly operations are happening with specular materials (ray rejections), and that sss is slowing light down by definition.

If you are using the post pro AD, well, yes it's slow. I would tick it on from times to times to check on the result, but then it's best to set it when the render is converged because of this. The same goes for navigation: if I want responsiveness I switch to bidir alone for editing.

So you can request better performances for this or that, call it a counter-performance if you will but "bug" is not appropriate I believe.

Thanks again for the debugging material !
obsolete asset

User avatar
CTZn
Posts: 7240
Joined: Thu Nov 16, 2006 4:34 pm
Location: Paris, France

Re: MtI 3.4

Post by CTZn » Sat Jan 19, 2013 6:37 am

Interestingly enough when I try to render your scene there is this error popping up in Indigo:

Error while loading phong material 'indigoShader4SG': ComplexIORExcep: Could not find file 'c:\3d\Indigo\3.6.4\nkData/Ag.nk.nk'.

Wether using a native Phong or an indigoShader node, the ".nk" extension bit is never showing up in the dropdown nk list, even after I loaded the scene back in Maya. But in the case of your scene the extension is showing up in the dropdown list.

Is it always the case for you ior ? Did you happen to modify some Indigo application folder or data ? Is this on a Windows OS ?

I can easily fix this, but why the extension is happening in the attribute in the first place is of great interest for me.

It might be helpfull to have a couple Maya scenes from different users using nk data for checking. Dang :)
obsolete asset

ior
Posts: 166
Joined: Tue Aug 24, 2010 11:47 am

Re: MtI 3.4

Post by ior » Sat Jan 19, 2013 5:05 pm

That error always happen to me so I changed my nk file to ag.nk.nk in order to work. I never spoked about this error because I didn't find it a hight priority. Fix it please.

After fixing this did you had that moving sphere problem?

User avatar
CTZn
Posts: 7240
Joined: Thu Nov 16, 2006 4:34 pm
Location: Paris, France

Re: MtI 3.4

Post by CTZn » Sat Jan 19, 2013 5:30 pm

I mean to fix both issues but the nk one is important because it is potentially broken for everyone but me.

Well, both are importnat ant the nk one should be easy to fix.
obsolete asset

User avatar
CTZn
Posts: 7240
Joined: Thu Nov 16, 2006 4:34 pm
Location: Paris, France

Re: MtI 3.4

Post by CTZn » Sun Jan 20, 2013 3:36 am

ior, I don't think I can fix the issue with moving objects on the mti side at the moment, given the data provided in your scene. There's something fishy and it happened already if I remember correctly.

While the world translate pivot of the sphere is at:

-72.2313
-21.6754
15.3918

its world scale pivot is at:

-156773578785762720.0000
-47525737818225736.0000
33401930875317116.0000 <- 334 and so billions kilometers from the teapot. About 2232 astronomic units. But only 0.03530598251220007 light years, it's all relative ;)

It's too much of an inconsistency. Given how little the sphere is moving (10-20 cm) it might be a precision issue. I'll dig deeper on the issue this week.

I know for sure that rigged objects may be found misplaced.
obsolete asset

Post Reply
49 posts

Who is online

Users browsing this forum: No registered users and 16 guests