Blendigo 1.0.5 Beta

[BbB]

In order to help me overcome this powerful humiliation, I've just exported a 300k displaced sphere and I can report that it works wonderfully.

[SmartDen]

glad to hear it

[BbB]

Sweet Jesus! This is a beautiful thing to watch. There are tears in my eyes.

[psor]

Guys, I know I repeat myself, but can someone tell me please, if there is
another way to turn 'Region Rendering' off without the need to go to 'Render'
and to press Border?



take care
psor

[zsouthboy]

Just exported a displaced plane from 32-bit blender (non LAA)
2097152 triangles

Worked great!

Thanks SmartDen! I've always loved Blendigo's UI.

EDIT:

Tried exporting again, this time with one more subsurf level, and blender crashes at Getting Matrix from <my object>.
So 2 million is a good idea of the limit for default 32-bit blender on windows.
Using the /LAA blender, it exports fine. (this is 8 million tris, btw)
However, Indigo crashes on trying to read the .igs (which is ~800 mb)!
We need an x64 build of 1.05+, Ono!

[alexmeyer]

@psor: There isn't anything new in the Blendigo GUI to enable/disable it. I don't quite see how it's that big of a problem to hit the "Border" button though...

[psor]

@alex

I thought of a short cut because SHIFT-B enables it. But as I found out
there is no way of doing it right now and that I'm not the only one who
got spoiled by it.

You see I'm a 3dsmax user, so I do almost have no clue about blender.
At least I'm able to learn which is an advantage, hehe!




take care
psor

[alexmeyer]

Ah, I see. Yeah, the thing you have to keep in mind is that Shift+B for border rendering is a blender feature, so all of the controlling of it is in blender's options. SmartDen was simply able to tap into the data for it through the python API.

[psor]

Yepp, I did understand that. I just thought that you blender heads would
know a way to turn it of through a short cut instead of pressing a button.

No worries, I'll live with this limitation without a problem.




take care
psor

[neepneep]

Muchos thankos Smartden !

Just wondering if anyone else is having problems with rendering the material previews or if its just me

[psor]

@neepnepp

You're right, it seems to be a bug.

Code: Select all

Compiled with Python version 2.5.
Checking for installed Python... got it!

----------------------
BLENDIGO v1.0.5b
----------------------
  Windows-platform: win32   os.sep: \
  indigo path: X:\Indigo\indigo_v1.0.6\indigo.exe
scene.getActiveObject() deprecated!
        use scene.objects.active instead

INDIGO MATERIAL PREVIEW EXPORT

Traceback (most recent call last):
  File "<string>", line 2977, in buttonEvt
  File "<string>", line 1252, in materialButtonEvt
  File "<string>", line 2125, in exportMatPreview
NameError: global name 'exportMaterial' is not defined

take care
psor

[Gengibre]

Is a beta, but thanks anyway...

[Kram1032]

@psor:
That will be simplified a lot, in the future
http://www.blendernation.com/2008/02/18 ... f-blender/

[Wedge]

I forgot to tell you SmartDen, we should run defaults for the Indigo values. Same as the inifile should be good idea, I think.

I'll send a copy of the exporter back, later tonight.

[alexmeyer]

Hey, just thought I'd file a bug report...

If you try to set the camera focus to "Selected" (object) when there isn't anything selected, it gives a python error and the script quits.

From the status window:

Code: Select all

----------------------
BLENDIGO v1.0.5b
----------------------
  Windows-platform: win32   os.sep: \
  indigo path: C:\bin\Blender\__Indigo\indigo_v1.0.6\indigo.exe
Traceback (most recent call last):
  File "<string>", line 2947, in buttonEvt
  File "<string>", line 2987, in setFocus
IndexError: list index out of range

Yeah, yeah, I should've made sure something was selected first, but whatever.