Making the maps: memory

[FireCrack]

I'm curious to how you guys make the texture maps for your maps, because my computer doesnt handle a 16384x16384 image (16x16 map, normal size), do you split them into multiple images and work on each of those? how do you recombine them? Any help on this?

[zwzsg]

RAM. Load of RAM.

[FireCrack]

That's it? I have 512, but maps this size should need 1 gig, owell, i guess it's time for an upgrade anyways...

[hrmph]

I'm curious what program are you using to edit your texture file?

[FireCrack]

photoshop, though mabye that sucks memory-wise...

wait, my document also had quite a few layers, that's probably why, d'oh!

[mother]

I'm curious to how you guys make the texture maps for your maps, because my computer doesnt handle a 16384x16384 image (16x16 map, normal size), do you split them into multiple images and work on each of those? how do you recombine them? Any help on this?

Whoa, one second! Thats a 32x32 (4x 'normal)... 8192x8192 is a normal 16x16.

As to how? I dunno, I wasted an hour watching an operation bring me up to 2gb of paging file only to have the script get to the end and bork because it ran out of allocatable memory

I think that to do a good job on a 16kx16k+ image you need to move to a non-windows platform (so that you can allocate >3gb).

If anyone knows of any easy command line style utilities to dice up an image into 4 quadrants, then stitch it back later... Lemme know too.

(BTW Using Gimp, and the problem is exactly what you mentioned- Layers... Doing something 'fancy' often means 5+ at any given moment, all RGBA... Nightmare.)

[FireCrack]

bah, no wonder i've been having these problems, dumb math...

[mongus]

If anyone knows of any easy command line style utilities to dice up an image into 4 quadrants, then stitch it back later... Lemme know too.

same here