large bitmaps, and i/o error, memory use etc

[halo]

have you tried using a multi sub material, and mapping slices of your map to different polys?

i dont think max will handle a 16k map, it tends to prolapse when any type of large bitmap is involved ie shadow maps, renders, or textures....

max is a bit of a :airguitar when high memory requirements...

(and thats not ment to be an airguitarist)

[Trambott]

Hi I don't know the answer to your problems, but i am damn curious why you are using such large maps

[RealThing]

The problem is that max by default must load all bitmaps into a continuous block of memory. This becomes an issue when you're dealing with larger bitmaps especially after your memory becomes more fragmented from constant use. Of course continuous memory storage of bitmaps is ideal as it's fast. Luckily you can change the way max deals with bitmaps by turning the bitmap pager on. This essentially does 2 things. Breaks up all bitmaps into smaller buckets. Only loads the buckets when they are needed. So it will force max to work with much larger images and at the same time lower the ram usage. Of course there's a small speed hit for doing so. But if you were running into swap previously it's likely to be faster. Hope this helps.

[AJ]

In sirius' defence, he did post...

Originally posted by sirius

3. i enabled the bitmap pager, but no difference.


But I would like to know... where is the bitmap pager hiding? I've never come across it!

[gundog]

customize/preferences/rendering

[sirius]

thanks a lot folks.

it seems that max is nor really up to large bitmap textures. Realthing explained more or less why.
But several very large bitmaps seem just not to be accepted by max, even when the bitmap pager is enabled. Anyhow, what would be good settings for the pager if you have 1 gb ram in a machine? Documentation isnt too extense on this. I suppose i should buy new machines with a minimum of 3gb ram? :rolleyes:

Also i cant get the tiling when using several matl id's to be seamless. i keep seein the borders somehow.

I solved my prob by slicing the texture at different resolutions and progressively using a higher res slice for the texture part in view, determining the changing distance by looking in pshop at the texture with 100% magnification. :buttrock:

Handling of textures in max would be much better if the bitmaps in the mat editor would load by default as smaller previews.
And the definitive bitmap should only be loaded at rendertime, and only the one and part in view. It will be on my wishlist for max 6: better bitmap handling with automatic slices and preview images in the viewports and mat-editor. :shame:

I heard that the renderman renderer can handle this kind of problem much easier. is that right ? :lightbulb

sirius

[CGTalk Moderation]

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.