Runtime Error

[Jarred]

Every time I export to Lux from Blender (v2.62) I get this error:

The weird thing is, the program actually renders out the image and saves it in my render folder, and it continues to render just fine as long as I don't touch anything. If I click "OK" on the error prompt it locks up and crashes Lux.

I am running Windows 7, 32-bit
4 gigs of ram
Intel Xeon 3.10 GHz
Quadro 2000 Graphics Card

Lux Version 1.0 Open CL

[Lord Crc]

Try installing this http://www.microsoft.com/en-us/download ... aspx?id=29

[Jarred]

Nope. Didn't work. Still throwing the same error. Thanks though! Any other ideas?

[Lord Crc]

If you export without running the renderer, and then run luxrender manually and open the scene, does it work then? Does rendering using "internal" work?

[Jarred]

No and no. It just crashed Blender completely if I try internal.

[Dade]

I am running Windows 7, 32-bit

The problem may be here, does it happen with any scene (i.e. simple and complex) ? And with all rendering mode (i.e. normal, hybrid) ? AS written by LordCRC, try also to run LuxRender GUI alone without any other application running (i.e. close Blender).

You are very likely to run out of address space, especially if you run multiple applications (i.e Blender + Lux + etc.) at the same time.

[Jarred]

It only happens when the scene is too complex. It does however happen with normal and hybrid modes (still only on complex models).

Like I said, it still works and renders fine if I don't touch anything. It's just really annoying that I can't view the preview window and adjust the tone mapping settings.

[yasucarine]

I have the same problem as well. -when a series of animation frames (queued) are rendered in particular.
It seems that this happens when RAM runs out.

I wonder if this is a known problem or if something is wrong/missing in my system. Does Lux release RAM usage after each frame/scene in a queue completes rendering?

(Win 7, 64bit, 4GB RAM, AMD dual core CPU, HD 6950 GPU, Lux 1.0 RC1 GUI)

[SATtva]

The problem with memory leak in LuxRays is supposed to be fixed for quite some time already. I haven't noticed anything like this.