Blender2indigo 0.62beta1

[Jananton]

great, Hans and Jan!
Jan, could you upload your mod file as well?

I'll see what I can do tomorrow.

Btw, did that little piece of untested code I wipped up some five days ago work on your Linux installation? If so, we can test if it's possible to make the one script work on both OS's...
( for now my tinkering is based on WinXP pro only )

Greetings from nighttime Amsterdam,

Jan

[u3dreal]

yes we defnetly have to go with a two OS version exporter..

when i find time

cheers

u3dreal

[Hans]

Hello, Jananton.
Yours might be better than mine. Mine depends on WinNT deeply.

afecelis, thanks.

Hello, u3dreal. The exporter is quite nice. Thank you.

[u3dreal]

Hello Hans,

Hi, I'm Hans. This exporter is nice, and I know it doesn't work well with " " in the path. So I changed the code...

Yup, that's the way to go. One point though, to make it all as OS undependant as possible I've rearranged the launch function as follows:

Code: Select all

def launchIndigo(filename):
	# get blenders 'bpydata' directory
	datadir=Blender.Get("datadir")
	
	# open 'IndigoWrapper.conf' and read the first line
	f = open(os.path.join(datadir, 'IndigoWrapper.conf'), 'r+')
	ic=f.readline()
	f.close()
	
	# create 'IndigoWrapper.cmd' and write two lines of code into it
	f = open(os.path.join(datadir, 'IndigoWrapper.cmd'), 'w')
	f.write("cd /d " + ic + "\n")
	f.write("start /b /belownormal Indigo.exe "%1" -t " + str(Threads.val) + "\n")
	f.close()
	
	# call external shell script to start Indigo
	cmd = os.path.join(datadir, 'IndigoWrapper.cmd') + ' "' + filename + '"'
	print cmd
	os.system(cmd)

One little other thing I found is that when ToneMapping is set to none or in other words linear, the line in the export script for writing the exposure value should read: <scale>%.6f</scale> instead of %.3f, so it should look like:

Code: Select all

		file.write("\t<tonemapping>\n")
		file.write("\t\t<linear>\n")
		file.write("\t\t\t<scale>%.6f</scale>\n" %exposure)
		file.write("\t\t</linear>\n")
		file.write("\t</tonemapping>\n\n")

Greetings from overcast Amsterdam,

Jan

Done and added support for both OS !

cheers

u3dreal

[u3dreal]

Unchecking "def" to save the xml file to a specific location is working fine in Linux; it's only in windows that it seems to not work.

Ok I have done some rearranging of some code in the buttonEvt function and now it works it seems. Probably has to do with the way python defines true and false..

Code: Select all

def buttonEvt(evt):  # function that handles button events
	
	global Screen, EnvFile
	
	if evt == evtExport:
		if DefaultExport == 1:
			datadir=Blender.Get("datadir")
			f = open(datadir + '/IndigoWrapper.conf', 'r+')
			ic=f.readline()
			f.close()
			filename = ic + "\default.xml"
			save_still(filename)
		else:
			Blender.Window.FileSelector(save_still, "Export", newFName('xml'))
	
	if evt == evtExportAnim:
		Blender.Window.FileSelector(save_anim, "Export Animation", newFName('xml'))
	#if there was an event, redraw the window   
	if evt:
		Draw.Redraw()
		
	if evt == evtNoEvt:
		Draw.Redraw()
		update_Registry()

Now the 'def' key works at least including the running of Indigo from blender.
I have made one other addition to the code to update the registry. It seems the values of DefaultExport and ExportGeom wheren't included, so I've added them like thus

Code: Select all

## Registry
def update_Registry():
	#global EnvFile, EnvMapType
	d = {}
## lots of entries ommitted
	d['ExecuteIndigo'] = ExecuteIndigo.val
	d['DefaultExport'] = DefaultExport.val
	d['ExportGeom'] = ExportGeom.val

## and then in the rdict try except block
		ExecuteIndigo.val = rdict['ExecuteIndigo']
		DefaultExport.val = rdict['DefaultExport']
		ExportGeom.val = rdict['ExportGeom']

The only thing that doesn't work still is switching off the 'geo' button, this should ihmo result in all beeing exported to one xml file, but that is not the case it seems. Maybe I'll have a look later...

Greetings from cloudy Amsterdam,

Jan

PS Note:
These updates are for the windows version only,,
Also note that in the environment menu the choice for none will crash indigo v. 6 in windows resulting in a request to send a message to uncle Bill...

when unchecking def NO geometry will be exporter this comes very handy as
you can change materials,camera and so on withou reexporting !!!

added and fixed..

[afecelis]

awwwwwwwhhhh! U3dreal, you've just made my sleepy 12:04 am a better and happier instant!

Same link as in the 1st post or not published yet?

[Jananton]

when unchecking def NO geometry will be exporter this comes very handy as you can change materials,camera and so on without reexporting !!!

added and fixed..

Ok, I can understand that thought, but mayby the user should have a choice when unchecking the geo button to either ommit or include the geometric data in the exported file.

I noticed I've introduced a bug in the export event, the correct code should read including independancy fixes:

Code: Select all

	if evt == evtExport:
		if DefaultExport.val == 1:
			datadir=Blender.Get("datadir")
			f = open(os.path.join(datadir, 'IndigoWrapper.conf'), 'r+')
			ic=f.readline()
			f.close()
			filename = os.path.join(ic, 'default.xml')
			save_still(filename)
		else:
			Blender.Window.FileSelector(save_still, "Export", newFName('xml'))

Well, that's it for now, I'll see if I can put up a link to what I have now later today...

Greetings from cloudy Amsterdam,

Jan

[Jananton]

Hello All,

As asked by afecelis, the following link should help you at the current state of my revised version of the export script for indigo v. 6

revised export script v. 63beta1

Read the readme.txt file included for installation instructions and if you want to try this on Linux, note that the file Indigowrapper.conf is not nescessairy.

Greetings from overcast Amsterdam,

Jan

[Phil]

0.63beta1



Regards, Phil

[u3dreal]

Cool Jananton.

do me a favour and update the old version until i have 0.7 ready...

thats cool ... thanks for helping me fixing bugs thats great so i can
concentrate on implementing the new stuff...

cheers

u3dreal

[u3dreal]

0.63beta1



Regards, Phil

That seems to be a nasty bug... somehow i got that working
with the radium exporter .. so i'll have a look once again.

cheers

u3dreal

[Jananton]

0.63beta1



Regards, Phil

Hmm, so exporting the file does happen, it's the launch again....

I can only think of two solutions now.

The first is to change the content of the created cmd file, if this doesn't help at least we know which part is the culprit. So go to launchWinIndigo() and change to the following:

Code: Select all

	# create 'IndigoWrapper.cmd' and write two lines of code into it
	f = open(os.path.join(datadir, 'IndigoWrapper.cmd'), 'w')
	f.write("echo 'Change to indigo root folder'\n")
	f.write("cd /d "" + ic + ""\n")
	f.write("echo 'Now start indigo with file on commandline'\n")
	f.write("start /b /belownormal Indigo.exe %1 -t " + str(Threads.val) + "\n")
	f.close()

When an error occurs and no echoed text is visible then the error is in calling this cmd file itself. If this is the case try the following, otherwise take another screenshot to see which line is faulty

Code: Select all

	# call external shell script to start Indigo
	os.chdir(datadir)
	cmd = 'IndigoWrapper.cmd "' + filename + """
	print cmd
	os.system(cmd)

As said in the readme.txt file it's very hard for me to test this since blender is installed on another partition than the default windows c: one. I did however put indigo there, since installing is just unzipping to a folder, and that's probably why exporting the file is no problem..

Please try the above and let me know the results so I can update the script accordingly.

As for the missing function makename, this is the animation part, as with rendering times of 24 hours and up for good results I haven't looked at that part of the script at all...

Greetings from overcast Amsterdam,

Jan

[drBouvierLeduc]

Problem with UV textures :

My projects are located in "c:\program files\indigo\scenes\xxx\...", with .blend files and textures.
But the exporter looks for the textures in "c:\program files\indigo\...", so it can't find them.

Is there a way to make it look in the directory where the .blend file is ?

[afecelis]

I agree with drBouvierLeduc, relative paths are much better than hard-coded absolute paths

Jan, can you please look into it?

[afecelis]

SIDE NOTE: well, I just remembered that U3dreal recommended me to use a blender version installed (unzipped) at C:\
This way the path wouldn't get lost in "Program Files" (long name-spaces), so I tried Jan's beta3 exporter in this one instead, and it works great!!!
@Jan: One question though: U3dreal's exporter has a "none" option among the environment options to choose; yours uses the usual 3 (texture map, physical sky, background color). Is "none" interpreted as bkg color? Hence getting rid of it your version?

regards, and thanks for all the help.