Announcements, requests and support regarding the Blender Indigo export script
-
ViennaLinux
- Posts: 191
- Joined: Thu Jul 26, 2007 9:26 am
- Location: Vienna/Austria
-
Contact:
Post
by ViennaLinux » Thu Jan 24, 2008 9:19 am
I think I now know what the problem is.
You are exporting the mesh with python and usings strings to stream the information into the RAM ...
maybe big meshes are too big for the datatyp string in python. Maybe you should overthink your exporting procedure and either split strings or use a better datatyp/algorithm.
Code: Select all
exporting mesh "sandbank"
Traceback (most recent call last):
File "<string>", line 2710, in buttonEvt
File "<string>", line 2058, in exportStill
File "<string>", line 2030, in export
File "<string>", line 1540, in exportMeshs
MemoryError
Core2duo e6600 @ 3.1GHz watercooled at default VCore ^^
-
Big Fan
- Posts: 745
- Joined: Tue Oct 17, 2006 9:37 am
- Location: Nelson NZ
Post
by Big Fan » Fri Jan 25, 2008 7:34 pm
ok in general talk to ono in chat it was mentioned smartden may like an idea for making render region for the official blendigo.
I offer an idea I used making use of blenders border tool - unfortunately I could not see a way to use the shift b rectangle to draw a region for the script to read directly but conversely you can set up the script so that it will draw the border via slider changes to the cameras window realtime for visualising the output - which is all you need really
see pic attach
its not very clear here but I have sliders for left , right , top , bottom position
possibly that works for him too
-
Attachments
-
- regions.jpg (121.05 KiB) Viewed 4211 times
-
SmartDen
- Posts: 999
- Joined: Fri Oct 13, 2006 10:58 pm
- Location: Canary Islands
-
Contact:
Post
by SmartDen » Fri Feb 01, 2008 10:01 pm
i got the region render with shift-b and fixed the memory bug with big scenes. but i have still to fix some minor bugs and then i publish the new version. be patient a little bit longer...
-
Vanessa07
- Posts: 312
- Joined: Mon Sep 24, 2007 11:17 pm
- Location: Suisse
Post
by Vanessa07 » Fri Feb 01, 2008 10:14 pm
SmartDen
Take your time, everybody knows that you work for free
Thank you very much for it
-
Pinko5
- Posts: 497
- Joined: Mon Feb 19, 2007 8:15 pm
- Location: Italy
Post
by Pinko5 » Fri Feb 01, 2008 10:20 pm
Tnx Smart... quote Vanessa07
Luca.
-
drBouvierLeduc
- Posts: 412
- Joined: Wed Oct 11, 2006 2:32 am
- Location: france
Post
by drBouvierLeduc » Fri Feb 01, 2008 11:35 pm
SmartDen wrote:fixed the memory bug with big scenes
Mmmmmh that sounds good !
-
SmartDen
- Posts: 999
- Joined: Fri Oct 13, 2006 10:58 pm
- Location: Canary Islands
-
Contact:
Post
by SmartDen » Sat Feb 02, 2008 12:00 am
drBouvierLeduc wrote:SmartDen wrote:fixed the memory bug with big scenes
Mmmmmh that sounds good !
yea, but i need a big scene(that crashes now) for test. or sombody who wants to play with my buggy blendigo
-
drBouvierLeduc
- Posts: 412
- Joined: Wed Oct 11, 2006 2:32 am
- Location: france
Post
by drBouvierLeduc » Sat Feb 02, 2008 1:06 am
Try that one, it will crash for sure. It is a displaced wooden plank with 2 subsurf modifiers applied, increase the "render levels" of the 2nd one if that's not enought.
-
Attachments
-
- bigscene.zip
- big crashing scene
- (267.53 KiB) Downloaded 210 times
-
zuegs
- Posts: 380
- Joined: Tue Jun 27, 2006 5:46 pm
- Location: switzerland
Post
by zuegs » Mon Feb 04, 2008 4:57 am
Hi all, nice to see the success of blendigo! Thx a lot to SmartDen!
Here a code i used to get the right materials from OB and ME at same time (if compress=False then list indexes matches indexes used inside mesh.faces):
Code: Select all
#-------------------------------------------------
# getMaterials(obj)
# helper function to get the material list of an object in respect of obj.colbits
#-------------------------------------------------
def getMaterials(obj, compress=False):
mats = [None]*16
colbits = obj.colbits
objMats = obj.getMaterials(1)
data = obj.getData()
try:
dataMats = data.materials
except:
try:
dataMats = data.getMaterials(1)
except:
dataMats = []
colbits = 0xffff
m = max(len(objMats), len(dataMats))
if m>0:
objMats.extend([None]*16)
dataMats.extend([None]*16)
for i in range(m):
if (colbits & (1<<i) > 0):
mats[i] = objMats[i]
else:
mats[i] = dataMats[i]
if compress:
mats = [m for m in mats if m]
else:
print "Warning: object %s has no material assigned"%(obj.getName())
mats = []
return mats
rgds Zuegs
-
Wedge
- Posts: 441
- Joined: Sun Jan 14, 2007 11:33 am
- Location: East Coast, USA
Post
by Wedge » Mon Feb 04, 2008 12:50 pm
Off topic: Zuegs! Long time no see. How are you? Send me a PM if you want.
Sorry for my OT.
Content contained in my posts is for informational purposes only and is used at your own risk.
-
Leaf
- Posts: 3
- Joined: Sat Dec 15, 2007 9:17 am
Post
by Leaf » Tue Feb 05, 2008 3:52 pm
I'm a little confused on how to install Blendigo. Do I run the installation steps then the Blednigo Installer? Or just pick one of these ways?
Thanks.
SmartDen wrote:Requirements:
-
Blender 2.45
-
Python 2.5
-
Indigo v1.0.1
Installation:
- Place Blendigo in ./blender/scripts
- Dont forget to edit Indigowrapper.conf to specify your indigo location and put it in ./blender/scripts/bpydata
- put preview in the indigo directory
Download, install, run and post your experience
Have fun!
Note
- For Photometric lights(IES) use small planes(i suggest 3.5cm x 3.5cm)
Blendigo v104 installer
*added aperture diffraction
- supported types: circular and generated. image comes soon
*watermark default is off
Blendigo v101 installer
-
Vanessa07
- Posts: 312
- Joined: Mon Sep 24, 2007 11:17 pm
- Location: Suisse
Post
by Vanessa07 » Tue Feb 05, 2008 6:48 pm
It depends of your OS, use blendigo v104 installer if you use XP, try manualy with other OS
-
GNUdo
- Posts: 40
- Joined: Sat Feb 10, 2007 10:05 am
-
Contact:
Post
by GNUdo » Tue Feb 05, 2008 9:43 pm
Setting up a blended material in Blendigo 1.0.4 I forgot to select the "Material B" and so previewing the material or exporting the scene results in Blendigo crashing with this Python script error:
Code: Select all
Traceback (most recent call last):
File "<string>", line 2803, in buttonEvt
File "<string>", line 1231, in materialButtonEvt
File "<string>", line 1945, in exportMatPreview
File "<string>", line 673, in exportMaterial
File "<string>", line 677, in exportMaterial
NameError: Material "" not found
I think it could be useful to insert a check warning the user and so avoiding Blendigo to quit.
Thank you!
-
Woodie
- Posts: 188
- Joined: Thu Oct 11, 2007 2:25 am
Post
by Woodie » Wed Feb 06, 2008 2:11 am
BigFan,
How you get that blendigo interface? Is this some sort of your cooking? Could you share?
-
Big Fan
- Posts: 745
- Joined: Tue Oct 17, 2006 9:37 am
- Location: Nelson NZ
Post
by Big Fan » Wed Feb 06, 2008 6:00 pm
hi Woodie,
its a variant based on an older version of blendigo I keep reheating for use with Solidworks and for Indigo tasting evenings
its somewhat different now in appearance and slightly different in function from the blendigo available here
I would really rather you use the official blendigo that Smartden posts cos I dont want to maintain it for public use or have a number of versions in circulation causing confusion
I think he will post an update quite soon
Who is online
Users browsing this forum: No registered users and 14 guests