Maxigo 0.9.4a

[suvakas]

Suvakas, please, make an option for Maxigo to include .igs files in exported scenes. This would keep me from copy-pasting stuff monkey-job, thanks in advance!

Sry, but I don't understand what you are talking about. Can you explain in a bit more detail?

[vansan]

Ok, I've done a script, that generates IES lights XML code, and I need it to be included in exported scene. Just a string value like a pre-render script in max, you know...

[suvakas]

Do you mean like an extra option to include any custom user defined igs file?

[vansan]

Yes, that's it!
Sorry for my poor language.

[suvakas]

Gotcha!
Interesting idea.
But i'm wondering if there will be any use for it in the future too?
I don't want to add too many "extra options". Things can get confusing (i think there already is too many settings )

[vansan]

I think it's a must-have function for testing personal-written modules.
Here is the code for IES-Lights. Hope this helps.

Code: Select all

--scenescale = 
format"<include><pathname>C:\Indigo\scenes\meshlight_IES.igs</pathname></include>\n\n"

for iL in lights do
	(
	try (if iL.distribution == 3 then 
			(
			--ies_xposition = iL.pos[1] --/ scenescale
			--ies_yposition = iL.pos[2] --/ scenescale
			--ies_zposition = iL.pos[3] --/ scenescale
			format "<meshlight>\n<pos>% % %</pos>\n" iL.pos[1] iL.pos[2] iL.pos[3] --ies_xposition ies_yposition ies_zposition
			format "<scale>1.0</scale>\n<mesh_name>lightmesh</mesh_name>\n\n<spectrum>\n<blackbody>\n<temperature>%</temperature>\n<gain>1.0</gain>\n</blackbody>\n</spectrum>\n\n<ies_profile>\n<path>%</path>\n</ies_profile>\n</meshlight>\n\n" iL.kelvin iL.webFile
			)
		else())
		catch()
	)

And this is Meshlight_IES.igm file code:

Code: Select all

<mesh>	
<name>lightmesh</name>
<normal_smoothing>false</normal_smoothing>
	<embedded>
		<expose_uv_set>
			<index>0</index>
			<name>albedo</name>
			</expose_uv_set>

			<vertex pos="-0.02 -0.02 0" normal="0 0 -1" uv0="0 0" />
			<vertex pos="-0.02 0.02 0.02" normal="0 0 -1" uv0="0 10000" />
			<vertex pos="0.02 0.02 0.02" normal="0 0 -1" uv0="10000 10000" />
			<vertex pos="0.02 -0.02 0" normal="0 0 -1" uv0="10000 0" />

			<triangle_set>
				<material_name>white</material_name>
				<tri>0 1 2</tri>
				<tri>0 2 3</tri>
			</triangle_set>
		</embedded>
	</mesh>

[suvakas]

You're missing the rotation matrix.

[raster]

suvakas,
i dont know why when i export an interior scene it took me 6min to export to xml and is this normal?
6min is unacceptable cos the interior has only 150k polys and other applications could do that under 1 min.

Export to 3ds = crashes(mesh error)
Export to obj = long "Doing initial warmup" (around 2 min)
Export to xml = long export + error

in the end i get frustrated cos didnt render anything

EDIT: When i export to obj format it only process something like 400 samples/s .. now when using xml, increased to 44ksample/s

thanks

[suvakas]

XML export is slow cause it's done via maxscript. 3ds and obj formats are using 3ds Max native exporter and are much faster. If you get long warmup times, then there might be something wrong with your scene scale. Try increasing it.

[surreal]

Thanks for this Suvakas! I haven't been around in ages (to busy with work) but great to see this stuff still going on!

[suvakas]

You're welcome
Yep, haven't seen you around for a while.
How have you been?

[surreal]

Excellent! Working in a Game studio in Vancouver now, which takes up a lot of my time (well with my 2 hour each way commute it does!) What about yourself?

[suvakas]

Nah, not much. Doing regular archi viz stuff mostly.
Probably not as fun as working in game studio .