Blendigo 2.3.x test releases

[dougal2]

@dakiru
It is safe to install both 32bit and 64bit python distros at the same time.

It would be interesting to see what you get with 32bit python + 32bit blender.

I usually only run 32bit python+32bit blender for development.

I will add "do some 64bit tests" to my TODO list

[dakiru]

@dakiru
It is safe to install both 32bit and 64bit python distros at the same time.

It would be interesting to see what you get with 32bit python + 32bit blender.

I usually only run 32bit python+32bit blender for development.

I will add "do some 64bit tests" to my TODO list

Yes, 32bit Python and 32bit Blender 2.49b + Blendigo 2.3.3 run nice together

[dakiru]

One more thing that I noticed is that 32bit Blender is compiled with 2.6.2 Python and 64bit is compiled with 2.6.1 Python.

[dougal2]

One more thing that I noticed is that 32bit Blender is compiled with 2.6.2 Python and 64bit is compiled with 2.6.1 Python.

That shouldn't matter too much, 2.6.x are all compatible.

[Jambert]

Hi Dougal2, works on linux 64, I didn't test network.

could you please change max value for reinhard from 10 to 100, especially "burn" value

thx

[dougal2]

The problem using blender x64 on windows is related to the code needed for the materials database integration. I cannot see an easy solution yet, but I'm still looking.

Would there be much impact if the MatDB integration was disabled for windows+blender64 ?

[dakiru]

The problem using blender x64 on windows is related to the code needed for the materials database integration. I cannot see an easy solution yet, but I'm still looking.

Would there be much impact if the MatDB integration was disabled for windows+blender64 ?

As for me it's definitely not a problem!

[Jambert]

I've made test, network seems to be broken under linux. Autostart doesn't work with export animation. With single rendering, you need to stop render manualy, activate network and then it works. Would be nice if it could generate a file to run it with console. See this post.

http://www.indigorenderer.com/forum/vie ... =37&t=9657

thx Doug for you time

[StompinTom]

Hey dougal2, thanks for the new release!

Motion blur doesn't seem to be working with curve path animation (at least, that's the only case I've tested it in so far) and particles don't export when motion blur is enabled. I had my typical dupli-grass particle systems set up, clicked motion blur to get some blur on a moving car, and the grass disappeared in Indigo.

[dakiru]

Aperture diffraction test 2:

Windows 7 x64, Indigo 2.4.3 x64, Blender 2.49b x64, Blendigo 2.3.3, UAC is off

Image type:

Common sense tells me that image aperture diffraction will not work without aperture image and yes, it doesn't . Console shows this:

Code: Select all

INDIGO EXPORT

Traceback (most recent call last):
  File "D:\SET\blender-2.49b-x64\.blender\scripts\blendigo.py", line 4235, in buttonEvt
    exportStill(defaultFile)
  File "D:\SET\blender-2.49b-x64\.blender\scripts\blendigo.py", line 3375, in exportStill
    export(filename, False)
  File "D:\SET\blender-2.49b-x64\.blender\scripts\blendigo.py", line 3323, in export
    if exportIndigoScene(filename, objlist, meshlist, matlist):
  File "D:\SET\blender-2.49b-x64\.blender\scripts\blendigo.py", line 3011, in exportIndigoScene
    file.write("\t\t\t<path>%s</path>\n"%(relpath(file.name, IndigoUIControls.Camera.ApertureImg.val)))
  File "D:\SET\blender-2.49b-x64\.blender\scripts\blendigo.py", line 222, in relpath
    return utils.getRelativePath(base, target)
  File "D:\SET\blender-2.49b-x64\.blender\scripts\blendigopkg\utils.py", line 46, in getRelativePath
    raise ValueError("no path specified")
ValueError: no path specified

[1]
Post process: ON
Aperture type: Image
Aperture image: YES (1024x1024, .PNG)
Obstacle map: NO
Works?: YES
Result:

image_1.png (36.59 KiB) Viewed 3432 times

[2]
Post process: ON
Aperture type: Image
Aperture image: YES (1024x1024, .PNG)
Obstacle map: YES (1024x1024, .PNG)
Works?: YES
Result:

image_2.png (44.19 KiB) Viewed 3432 times

[3]
Post process: OFF
Aperture type: Image
Aperture image: YES (1024x1024, .PNG)
Obstacle map: NO
Works?: YES
Result:

image_3.png (49.75 KiB) Viewed 3432 times

[4]
Post process: OFF
Aperture type: Image
Aperture image: YES (1024x1024, .PNG)
Obstacle map: YES (1024x1024, .PNG)
Works?: YES
Result:

image_4.png (76.28 KiB) Viewed 3432 times

Generated type:

Generated settings. Works?:
Blades: YES
Offset: YES
Curvature: YES
Start angle: YES

[1]
Post process: ON
Aperture type: Generated
Obstacle map: NO
Works?: YES
Result:

generated_1.png (17.13 KiB) Viewed 3432 times

[2]
Post process: ON
Aperture type: Generated
Obstacle map: YES (1024x1024, .PNG)
Works?: YES
Result:

generated_2.png (44.29 KiB) Viewed 3432 times

[3]
Post process: OFF
Aperture type: Generated
Obstacle map: NO
Works?: YES
Result:

generated_3.png (30.88 KiB) Viewed 3432 times

[4]
Post process: OFF
Aperture type: Generated
Obstacle map: YES (1024x1024, .PNG)
Works?: YES
Result:

generated_4.png (51.84 KiB) Viewed 3432 times

Circular type:

[1]
Post process: ON
Aperture type: Circular
Obstacle map: NO
Works?: YES
Result:

circular_1.png (12.86 KiB) Viewed 3432 times

[2]
Post process: ON
Aperture type: Circular
Obstacle map: YES (1024x1024, .PNG)
Works?: YES
Result:

circular_2.png (48.97 KiB) Viewed 3432 times

[3]
Post process: OFF
Aperture type: Circular
Obstacle map: NO
Works?: YES
Result:

circular_3.png (48.96 KiB) Viewed 3432 times

[4]
Post process: OFF
Aperture type: Circular
Obstacle map: YES (1024x1024, .PNG)
Works?: YES
Result:

circular_4.png (60.76 KiB) Viewed 3432 times

Seems like everything works. Great work, dougal2!

[StompinTom]

Aperture diffraction test 2:
Seems like everything works. Great work, dougal2!

Great test, dakiru! Thanks a lot.

What image did you use for the aperature and obstacle maps?

[StompinTom]

Can't boot the script...

Code: Select all

----------------------
BLENDIGO v2.3.3
----------------------
  Windows-platform     : win32
  os.sep               : \
  matdbPreviews        : C:\Program Files (x86)\V-RayBlender-2.49.12\.blender\sc
ripts\blendigopkg\matdb\previews
  assetsPath           : C:\Program Files (x86)\V-RayBlender-2.49.12\.blender\sc
ripts\blendigopkg\assets
  matdbDownloads       : C:\Program Files (x86)\V-RayBlender-2.49.12\.blender\sc
ripts\blendigopkg\matdb

Traceback (most recent call last):
  File "<string>", line 1, in <module>
  File "C:\Program Files (x86)\V-RayBlender-2.49.12\.blender\scripts\blendigo.py
", line 4432, in <module>
    readWriteSettings(0)
  File "C:\Program Files (x86)\V-RayBlender-2.49.12\.blender\scripts\blendigo.py
", line 3404, in readWriteSettings
    readWriteValue(d, 'aperture_pproc', IndigoUIControls.Camera.AperturePProc, w
rite, 0)
AttributeError: class Camera has no attribute 'AperturePProc'

[dakiru]

Aperture diffraction test 2:
Seems like everything works. Great work, dougal2!

Great test, dakiru! Thanks a lot.

What image did you use for the aperature and obstacle maps?

Hi, Tom! Here they are:

obstacle_map_power_of_two.png (8.68 KiB) Viewed 3421 times

[StompinTom]

Shit. Installing the previous version of Blendigo doesn't help, can't revert to what I just had before.... Help!

EDIT: Ok, rebooting Blender worked. I'm gonna stay away from 2.3.3 for now... at least until I have time to play with it on a separate (non-work) version of Blender.

[dougal2]

Shit. Installing the previous version of Blendigo doesn't help, can't revert to what I just had before.... Help!

EDIT: Ok, rebooting Blender worked. I'm gonna stay away from 2.3.3 for now... at least until I have time to play with it on a separate (non-work) version of Blender.

Be aware that 2.3.x of Blendigo will soon become the 2.4.x series. The 2.3.x and 2.4.x series will not properly load scenes saved with 2.2.x series.

As ever, I would not recommend upgrading just yet if you have deadlines to meet - better is to wait until you have some time and perform a complete clean install, making sure the old exporter has been completely removed.