Ps 30000 px limitation

[opteryx 1562]

Hi, I'm trying to create a terrain at a size of 40960 x 40960 meters, that would mean if I'd like the terrain to have 1 px = 1 m my settings/data would be:

heightmap = 2048 x 2048 px

cell size = 20 m

Sat/mask = 40960 x 40960 px

However there's a limitation in Photoshop that hiders me from saving common formats such as png above 30000 px.

Of course I could resize my sat/mask to 20480 x 20480 px and use that, but from previous experience I've learned that 1 px = 2 meter doesn't look very pretty.

What I've tried is to use a 30000 x 30000 px sat/mask, on previously mentioned settings, ie.:

heightmap = 2048 x 2048 px

cell size = 20 m

Sat/mask = 30000 x 30000 px

This did not however work as Visitor does not seem to accept this (some warning about texels yadda yadda..)

I was under the impression that the satmap size does not matter, but apparently it does.. or have I missed something fundamental here??

So, is there anyway for me to get around this? Any plugins for PS or or any other image editors that can import PSB format and export as png above the 30000 px limit in PS?

[Nicholas Bell 0]

Quote[/b] ] was under the impression that the satmap size does not matter, but apparently it does.. or have I missed something fundamental here??

When importing the satellite image it gets chopped up into tiles sized according to your Terrain Grid Size, as set in Parameters. In your very helpful tutorial you used 512 x 512. The sat image needs to be in multiples of this size. So maybe sizing it to 29,696 would work (?).

Sorry I can't help you with the PNG size limitation. Just thinking out loud, I thought you mentioned you were using Photoshop elements. Maybe the full blown version would allow this?

[opteryx 1562]

Oh Doh, didn't think of that the segments needs to add up with the sat height/width.

Will investigate further...

-edit-

Yup, did some calc and ended up with the same number as you, it works.

However I'd still like a 1 px = 1m though.

[surpher 1]

Could you save it as a TIFF then convert it to a PNG outside of Photoshop?

[opteryx 1562]

Could you save it as a TIFF then convert it to a PNG outside of Photoshop?

Can't check right now cause I'm opening a 4.5 gb psb which takes about 20 min....

..but as far as I remember I still could save as PSB and TIFF when exceeding the 30000 limit.

Was there any particular software for conversion you had in mind?

[surpher 1]

Was there any particular software for conversion you had in mind?

Not really, you should be able to find a free TIFF>PNG convert somewhere on the net.

Anyway I think TIFF's have a limit of 4Gb

[opteryx 1562]

Anyway I think TIFF's have a limit of 4Gb

Yep.....

-edit-

I guess we can't always have our cake and eat it too, but with a 29696 px sat res, a px will be 1.379 m which isn't really that bad I guess so I guess I'll just have to go for that now.

If anyone else still has an idea how to get png's bigger than 30000 px I'd still like to hear it though.

[fasad 1]

The cause of the limit may be as simple as by the 32-bit O/S maximum file size of 4gb? Does anybody use Vista or some other 64 bit OS with a 64 bit version of Photoshop (assuming such a thing exists)? I use photoshop 6 which has a limit of 26754x26754 (maybe its older than NTFS and has 2gb filesize limit?). I'll have to buy a new version while i'm still a student.

As for overcoming it, I'm not sure... I thought of using dummy terrains and manually joining their sat/layer masks together, but since (I assume) the pew/wrp's rvmat references are created during the import process, it won't work...

~30000x30000 is big enough to keep us busy for a year or so anyway, not to mention a 1gb+ distribution file size.

[opteryx 1562]

Well, after successfully getting the map ingame there wasn't much more to yell success about..

Terrain is extremely laggy on low/normal texture settings (works on high/very high), takes a long time to load and is way to unstable to be deemed playable.

Seems like my only option now is a 20480 sat stretched out over a 40 km terrain...

[Snake Man 401]

fasad is absolutely correct, have you even estimated how big the rarred up terrain pbo package would be for download in that satellite layer size?

[opteryx 1562]

fasad is absolutely correct, have you even estimated how big the rarred up terrain pbo package would be for download in that satellite layer size?

Oh I wasn't really planning on releasing it, was just testing something.

[fasad 1]

I asked about this topic on the Adobe photoshop forums. Amongst all the helpful "photoshop 6 is old!" and "50000x50000 is too big to print" replies, someone suggested that "Photoshop CS" (i think that's 8+) can create 300,000 by 300,000 pixel images in PSB format.

btw Opteryx, the satmask does not need to be a simple multiple of the terrain-size in meters. The main restriction is that each satmask segment can be cleanly divided into 12 texture segments. Enter the largest multiple of your terrain grid that you can make, choose a enter roughly the segment size you want. Look at the "proposed segment overlap", and manipulate the segment size and overlap until both the proposed and calculated terrain grid are equal, and suit you. I haven't thoroughly tested the performance impacts of lots of small segments vs large ones, but it seems loading time is the biggest factor in what testing I have done so far. The benefit of smaller segments is a reduction in the restrictiveness of the 4 surfaces per segment rule. The layers folder also ends up with ~60,000 files in it

[opteryx 1562]

Yeah PSB can handle huge images, but most common formats aren't supported above 30 000 px.

It's seems like satmaps that aren't using a Power of Two size are very unstable, at least that's my experience.

Also bigger segments seems to give better performance, when I made Sakakah, I initially used 512x512 segments, after changing them to 1024 I seemed to have a major boost in frame-rate.

[Nicholas Bell 0]

"Note: You can open created PNG size up to 40960x40960px in Photoshop CS and higher."

Stumbled on this on the Biki:

Making Satellite Texture and Mask

[opteryx 1562]

"Note: You can open created PNG size up to 40960x40960px in Photoshop CS and higher."

Stumbled on this on the Biki:

Making Satellite Texture and Mask

Gee I wish that was true though.

In any case, I used a 20480px and the result was surprisingly quite good, also performance is terrific!

PICTURE

[Nicholas Bell 0]

Excellent, realistic mountains. Very nice indeed.

[.kju 3240]

One question mate.

Why do you not split your sources into various smaller islands?

[fasad 1]

For what it's worth, the PNG format supports images with dimensions up to 2^31 -1 (= 2,147,483,647) pixels in each axis. Source.

[opteryx 1562]

One question mate.

Why do you not split your sources into various smaller islands?

Cause I like huge terrains.

Quote[/b] ]For what it's worth, the PNG format supports images with dimensions up to 2^31 -1 (= 2,147,483,647) pixels in each axis. Source.]

I don't doubt that for one second, but PS doesn't allow me to export above 30 000.

[.kju 3240]

Same here Opteryx.

No stuff or little less huge islands. Isn't the choice simple?

Boundaries are to be broken people say.

People are not always wise in their reasoning.

[Linker Split 0]

dunno m8, try this one:

Pixel Dragons Ltd Releases New Update For Image Genius Professionalâ„¢ V 3.1.0

[[aps]gnat 28]

Lovely look it has Opteryx

Have u considered a tool that stiches smaller sections togther to make your larger file?

I'd love one that would stitch multiple OFP terrain tiles together .....

[fasad 1]

I haven't tested it thoroughly yet, but I've found a set of command line based tools called ImageMajick that can join multiple images into one. It's just successfully combined 4x512x512 pngs -> 1x1024x1024 png. I'll push it a little harder...

- 4x6400^2 -> 1x12800^2 works (~5 mins process time)

- 4x12800^2 -> 1x25600^2 works (~50 mins process time) (this is the size I want and my photoshop can't save png's this size)

The merging doesn't use much CPU, but a lot of HDD activity. I'm not going to test anything larger now, maybe overnight...

[opteryx 1562]

I haven't tested it thoroughly yet, but I've found a set of command line based tools called ImageMajick that can join multiple images into one. It's just successfully combined 4x512x512 pngs -> 1x1024x1024 png. I'll push it a little harder...

Ohh sounds intriguing.

[[aps]gnat 28]

Its a nice tool, finally found something to make (convert) 16bit grayscale PNGs with.

..... but I don't see the commands to stitch together images ..... wheres that fasad ?