Indigo 0.9 test 7

Macrob · Post by **Macrob** » Mon Sep 24, 2007 12:10 am

sent

Ups:
Gentoo linux 64 bit
indigo_v09_test7.2 32bit(wine)
blendigo 0.9beta4s

delic · Post by **delic** » Mon Sep 24, 2007 10:47 pm

Nice !

Not only faster, but also better for me !

I tried to render some high res (A4 300dpi) files, and I always have a "runtime error" message and crash of indigo, sometimes during the build of the scene, usually during or at end of the warmup.
I tried it with different files and it always happens, but I should not be out of ram, since the windows monitor always showed a memory usage lower than the ram I have.

It seem to begin crashing at approx 1.6k-2k wide renders.
And perhaps it has to do with highly uv mapped scenes or huge textures files since I should remove some uv mapping and reduce some textures size to get a render pass the runtime error.

Big Fan · Post by **Big Fan** » Tue Sep 25, 2007 12:56 am

most likely you are in fact out of memory
32 bit will allow only use of about 1.6gb
I see there is a blender build at graphical.org with the 3gb flag enabled
It would be nice if ono would add one to indigo as well

Zom-B · Post by **Zom-B** » Tue Sep 25, 2007 12:59 am

delic wrote:I tried to render some high res (A4 300dpi) files, and I always have a "runtime error" message and crash of indigo, sometimes during the build of the scene, usually during or at end of the warmup.
I tried it with different files and it always happens, but I should not be out of ram, since the windows monitor always showed a memory usage lower than the ram I have.

Its still an out of RAM issue dude! Indigo crash if all your base are belong to us. Indigo doesn't like to use your swapfile, and windows isn't that generously giving RAM away (by default) so it gave Indigo some of the Swapfile cake even if there was some MB of the tasty RAM cake left...

Kram1032 · Post by **Kram1032** » Tue Sep 25, 2007 1:43 am

ZomB wrote:(by default)

What's to change?

delic · Post by **delic** » Tue Sep 25, 2007 1:59 am

Ok, is there a workaround ?
Is it better using Wine ?

Is it possible to tell XP not to swap ?

For the 1.6gigs allocatted by XP you talkin about ZomB, I guess this is without the /3GB switch in the boot.ini.
Since I have 4gigs of ram I had to add this so XP sees at least 3 of them .

Big Fan · Post by **Big Fan** » Tue Sep 25, 2007 2:10 am

indigo needs itself to be built to use the 3gb switch though as far as I see

Post by **OnoSendai** » Tue Sep 25, 2007 2:17 am

I suggest getting a 64-bit OS if you want to use all your 4 Gigs

delic · Post by **delic** » Tue Sep 25, 2007 2:29 am

Linux 32bits does, but not more !

I would like to render up to 3gb ram with xp without runtime error.

I'll try with Wine on ubuntu32bits to see if goes better.

With ubuntu64 bits too, but not sure wine does handle the 64 bits build of indigo. Does it ? "EDIT" it doesn't !

and the problem seems to be the swap of XP, not the onboard memory.

Anthony · Post by **Anthony** » Tue Sep 25, 2007 9:35 pm

:O

The render speed is WRONG!!!!!! ONO, YOU FAIL!
When you resume renders Indigo is all like "omg its done 200 samples like 5 seconds after warming up" and then its all like "woah 999999999999 samples / second"

Ya know....
I haven't installed this version yet (am waiting for stable) but its on beta two and older versions and I just remembered and I think its on this one too but dunno

manitwo · Post by **manitwo** » Tue Sep 25, 2007 11:52 pm

this isn't anything new nor are you the first one who noticed this anthony

Heavily Tessellated · Post by **Heavily Tessellated** » Wed Sep 26, 2007 5:11 am

delic -

Uhm, it's got nothing to do with linux or Windows or ANY 32-bit OS, this is analogous to a plane being over-booked; regardless of it's size, there's just no more seats. Err, address space. Especially if you have a modern high-RAM gfx card. This RAM needs to be addressable along with every other hardware device, and gets precedence. Getting 3.1G usable system RAM on a 32-bit OS w/o PAE is quite impressive, actually!

Enabling the 36-bit PAE extension adds a bit to try and work around this (/PAE kernel boot flag) which will let you map like 64G of memory addresses, but no app is going to get assigned more than 2G (or /3GB), ever. Unless it's specifically coded to, using the AWE API. There's also a performance hit for doing this; you are cheating, making the CPU count those extra 4 bits on it's fingers and toes, adding a bit of overhead. Depending on the app it can be harsh, -10% or so. What sucks is that it's globally slower, not just when using said monster memory app.

Just switch. And welcome to the 64-bit Early Adopters Club.

At the present it means Windows x64, because there's no x64 wine support as you've discovered, and nik hasn't been badgered enough to release native linux builds. (in lieu of badgering, I suppose paypal donations would work.)

Big Fan · Post by **Big Fan** » Wed Sep 26, 2007 9:48 am

>just switch

Well hold on there some of us are using 32bit for commercial reasons
I havent heard before of any significant performance hit using the 3gb switch - and besides its the memory space we want to get the job done.
With the 3gb switch you actually only get about 2.6 gb to use but hey thats a whole extra gb.
Rather than volunteering everyone to use 64 bit how about you give the 32bit users a break and let us have the switch if we need it

I have a 3gb switch set in my boot file for running Solidworks and an optimised Blender build if projects require it and if Indigo could run it as well I would be very happy indeed

however I can make 'includes' so I can get around it to some extent

Anthony · Post by **Anthony** » Wed Sep 26, 2007 10:14 am

How come no fix for ages? :O

Big Fan · Post by **Big Fan** » Wed Sep 26, 2007 2:57 pm

well ono only released t7 2 weeks ago

Indigo 0.9 test 7

Who is online