Weird Wireframes


#1

I have finished rendering a 5000-frame presentation which is my first serious rendering with Blender. I wish I can say that the enthusiasm continues, but no, … I’m terrified. I need to render some parts in wireframe and that is where I’m stuck. I have changed the materials to render wireframe. When I hit F12, blender either exits abruptly OR hangs indefinitely. Repeating the render assignment from the terminal, This is what I get:

*** glibc detected *** ./blender: malloc(): memory corruption: 0x0000000003f1c7f0 ***

Its important that I do the wireframe rendering today (urgent) and I’m very stuck. I’d appreciate some assistance ASAP.


#2

this is confusing alright, all I can say is that there’s memory corruption
while trying to allocate more memory or something,
might be that rendering the wires of the mesh together with the mesh
your using double the memory and as you run out it crashes,
either that or there’s some weird bug somewhere. :sad:

do you happen to have a machine with more memory you could try on perhaps
or multiple machines so you could move memory from one to the other perhaps?

ps. if you can, perhapsvisit the ‘#blendercoders’ channel on irc.freenode.net
or you can just simply use the freenode web irc trough pasteall.org,
perhaps the developers can give you more meaningful feedback. :slight_smile:
http://i33.tinypic.com/oh2t2.jpg

hope you get it worked out! :slight_smile:


#3

I’m afraid I can’t shed too much light on the problem itself but if time’s an issue, as a possible workaround, you could try Kernons approach:
http://blendernewbies.blogspot.com/search/label/Wireframe

I’ve used it in the past with good results.

Edit: Disregard, I just doublechecked and I’m afraid it also uses a wire material - not much use if that’s whats causing the issue!

Is the issue only with recent builds or all versions? You might be able to fall back to an early stable version such as 2.49b


#4

That was wicked adventure!

The task is done and I have learned a lot within a month. I now see why people advise against using Alpha/Beta software in a production environment. I eventually got Blender to render wireframe. The output was sufficient for the task but I wished for more. I observed some strange things while doing my crash-course in Blender.

  1. Wireframe materials loose their individuality when they’re part of a multi/sub level material. The object renders with the topmost material in the slot. I suspect this to be a bug. Returning sub-materials to ‘surface’ enables a proper sub-level rendering for the materials.

  2. Blender exits or hangs with certain wireframe material settings. Joining objects together eliminates this behaviour at the expense of uniqueness (Blender seems to ignore the rest of materials united in the merge … see above)

  3. Blender’s rendering is slow compared to MAX when using only point lights (no ambient occlusion & env. lighting)

  4. Some addons wouldn’t run … (API changes, may be)

  5. Ticking the ‘enable’ checkbox for the ‘Track to’ and ‘Follow Path’ constraints appear to be working in reverse i.e. the tick would disable them instead. This might be a bug too.

Anyway … thanks to those who came to my aid

More wicked adventures, after a wicked sleep …


#5

This thread has been automatically closed as it remained inactive for 12 months. If you wish to continue the discussion, please create a new thread in the appropriate forum.