to win the war of render engine(per vincere la battagli...)
to win the war of render engine(per vincere la battagli...)
I work with indigo very well.....and when I find Indigo I am folling in love to it......in my work I realized 6\10 render for week...so I have way to work whit some render engine a lot of time for week....I think that Indigo if want became a new point reference of render engine, it need correct the the only bug that to stop the work....THE ERROR OF THE POSITION AND SCALE OF THE OBJECT"....this bug there are in indigo 0.6 and indigo 0.7..but the bugs don't work equal in the 2 version!!!
filippo(excusame for my poor language)
p.s.
I LOVE MY GIRL
I LOVE MY CBR 900 RR
I LOVE INDIGO
IO lavoro molto bene con indigo, e da quando l'ho scoperto, me ne sono innamorato..io realizo pier lavoro dai 6 ai 10 render per settimana, lavorando con vari render engine....e posso dire che ad Indigo per divenare un punto di riferimento per i renderisti, deve risolvere l'unico bug che non ti permette di lavorare,cioe' 'ERRATA POSIZIONE E SCALTURA DI ALCUNI OGGETTI..questo bug era presente sia in Indigo 0.6che 0.7..e la cosa peggiore è che non si comporta sempre allo stesso modo...
filippo
IO AMO LA MIA RAGAZZA
IO AMO IL MOO CBR 900 RR
IO AMO INDIGO
filippo(excusame for my poor language)
p.s.
I LOVE MY GIRL
I LOVE MY CBR 900 RR
I LOVE INDIGO
IO lavoro molto bene con indigo, e da quando l'ho scoperto, me ne sono innamorato..io realizo pier lavoro dai 6 ai 10 render per settimana, lavorando con vari render engine....e posso dire che ad Indigo per divenare un punto di riferimento per i renderisti, deve risolvere l'unico bug che non ti permette di lavorare,cioe' 'ERRATA POSIZIONE E SCALTURA DI ALCUNI OGGETTI..questo bug era presente sia in Indigo 0.6che 0.7..e la cosa peggiore è che non si comporta sempre allo stesso modo...
filippo
IO AMO LA MIA RAGAZZA
IO AMO IL MOO CBR 900 RR
IO AMO INDIGO
2x Xeon quad core ghz 2.66(8 core)+4g ram+quadro fx
2 x Xeon Quad 5540 (16 core)+16GB ram+ Nvidia GTX 295 1800mb
2 x Xeon Quad 5540 (16 core)+16GB ram+ Nvidia GTX 295 1800mb
Hey,
I think it's not an Indigo bug, but more like 3ds Max related thing. I've probably written my script a bit differently than U3dreal did and that's why there are differences.
It is pain in the a** to get good coordinates out of Max.
Some tips that may help:
*[edit] I mean use Xform modifier when scaling..sry.. confused it with FFD somehow
*Use metric units.
*Use ResetXform
I also added some kind of mesh fixing feature into my exporter (sometimes it works and sometimes it doesnt
). It will be included in next release.
Suvakas
[edit] filippo, maybe you can upload some scenes that don't work? Then I would have something to test and maybe i can figure out how to make the geometry export better.
I think it's not an Indigo bug, but more like 3ds Max related thing. I've probably written my script a bit differently than U3dreal did and that's why there are differences.
It is pain in the a** to get good coordinates out of Max.
Some tips that may help:
*[edit] I mean use Xform modifier when scaling..sry.. confused it with FFD somehow

*Use metric units.
*Use ResetXform
I also added some kind of mesh fixing feature into my exporter (sometimes it works and sometimes it doesnt

Suvakas
[edit] filippo, maybe you can upload some scenes that don't work? Then I would have something to test and maybe i can figure out how to make the geometry export better.
Last edited by suvakas on Thu Mar 08, 2007 7:41 pm, edited 1 time in total.
Hey suvakas, random question, are you using the .pos or .transform of the object to get it's co-ordinates?
Website
http://www.surrient.com/
http://www.surrient.com/
I have not understood well the question..you want some of my scene to test Indigo?suvakas wrote:Hey,
I think it's not an Indigo bug, but more like 3ds Max related thing. I've probably written my script a bit differently than U3dreal did and that's why there are differences.
It is pain in the a** to get good coordinates out of Max.
Some tips that may help:
*[edit] I mean use Xform modifier when scaling..sry.. confused it with FFD somehow![]()
*Use metric units.
*Use ResetXform
I also added some kind of mesh fixing feature into my exporter (sometimes it works and sometimes it doesnt). It will be included in next release.
Suvakas
[edit] filippo, maybe you can upload some scenes that don't work? Then I would have something to test and maybe i can figure out how to make the geometry export better.
there aren't problem....I post one scene where I test a material...but I work only with interior..do you want a scene?
2x Xeon quad core ghz 2.66(8 core)+4g ram+quadro fx
2 x Xeon Quad 5540 (16 core)+16GB ram+ Nvidia GTX 295 1800mb
2 x Xeon Quad 5540 (16 core)+16GB ram+ Nvidia GTX 295 1800mb
suvakas!!!I beg you to excuse me
the problem is out!!!!
I will to a zip file for you.....when in max I broken all gruop in a scene, I export the file in 3ds I have import in rhinoceros 4 and I resave it in 3ds...after I import in max.... and start the render.......it's ok!!!!!.......so I revolve the problem...I test it in other scene 9 on 10 it,s ok....the only file that my method don't work it is in the zip file...if you resolve the problem can you tell me the solution?
http://d.turboupload.com/d/1591620/classroom_2.rar.html
so ....to resolve the problem of scale and position of object....export the scene in 3ds...open in rhino...resave the file in 3ds..import in max.......render...
filippo
excuseme for my poor language
suvakas ti prego di scusarmi..il problema è risolto.....mentre ti preparavo il file .zip, in una scena ho rotto i gruppi, esportato da max in 3ds...importato il file in rhino e riesportato in 3ds...l'ho riaperto in max...ho lanciato il ender e la scena era corretta!!!
ciao filippo
the problem is out!!!!
I will to a zip file for you.....when in max I broken all gruop in a scene, I export the file in 3ds I have import in rhinoceros 4 and I resave it in 3ds...after I import in max.... and start the render.......it's ok!!!!!.......so I revolve the problem...I test it in other scene 9 on 10 it,s ok....the only file that my method don't work it is in the zip file...if you resolve the problem can you tell me the solution?
http://d.turboupload.com/d/1591620/classroom_2.rar.html
so ....to resolve the problem of scale and position of object....export the scene in 3ds...open in rhino...resave the file in 3ds..import in max.......render...
filippo
excuseme for my poor language
suvakas ti prego di scusarmi..il problema è risolto.....mentre ti preparavo il file .zip, in una scena ho rotto i gruppi, esportato da max in 3ds...importato il file in rhino e riesportato in 3ds...l'ho riaperto in max...ho lanciato il ender e la scena era corretta!!!
ciao filippo
2x Xeon quad core ghz 2.66(8 core)+4g ram+quadro fx
2 x Xeon Quad 5540 (16 core)+16GB ram+ Nvidia GTX 295 1800mb
2 x Xeon Quad 5540 (16 core)+16GB ram+ Nvidia GTX 295 1800mb
haha just wondering because .pos can give back positions depended on what world space you're working in, but .transform will just give back the same thing no matter what. Hence why i was asking lol.
Website
http://www.surrient.com/
http://www.surrient.com/
Hey filippo,filippo wrote:....the only file that my method don't work it is in the zip file...if you resolve the problem can you tell me the solution?
That classroom scene will render fine when using the new "Fix Mesh Errors" feature that will be included in the next Maxigo release (maybe sometimes in this week..depends on how much free time i can have to work on the exporter script)
Suvakas
Here's a proof

- Attachments
-
- class2.jpg (51.03 KiB) Viewed 11124 times
Exporter supports all 3 formats (xml, 3ds and obj) and those position and scale errors are occasionally there whatever format to use. I'm 99.9% sure, that it is not an Indigo problem, but comes from Max. It mostly happens with models that are imported or linked from other apps. There is sometimes something wrong with the origin point or pivot of an imported model and the transform matrix is somehow different than with objects that are created in Max itself.
It can also happen with badly modelled objects too (messy scaling operations and etc).
The bottom line is, that it seems to be related to models and their coordinates in Max and not in Indigo. And is actually more of a mesh problem than coordinates problem. Basicly i have to reset the transform and scale of the model before exporting, but there is not a single solution for it. Sometimes one thing works and sometimes other.
Suvakas
[edit2] Here is that classroom scene when rendered without my mesh fixing feature.
It can also happen with badly modelled objects too (messy scaling operations and etc).
The bottom line is, that it seems to be related to models and their coordinates in Max and not in Indigo. And is actually more of a mesh problem than coordinates problem. Basicly i have to reset the transform and scale of the model before exporting, but there is not a single solution for it. Sometimes one thing works and sometimes other.
Suvakas
[edit2] Here is that classroom scene when rendered without my mesh fixing feature.
- Attachments
-
- class-messed_up.jpg (39.87 KiB) Viewed 11110 times
if i understood you right(well maybe not. im really tired):
i had a similar problem with rotation.
when i export to .obj(in c4d) i have to rotate the object, so that the z-axis is up. when i export to .3ds i dont need to rotate the object.
i solved this problem with an if
i had a similar problem with rotation.
when i export to .obj(in c4d) i have to rotate the object, so that the z-axis is up. when i export to .3ds i dont need to rotate the object.
i solved this problem with an if

Code: Select all
if(objExport == 1) { obj->GetMg()... /* rest of the code is not that interesting */ }
Who is online
Users browsing this forum: No registered users and 5 guests