One of six panels for the skybox for Space Noxx II. The 256x256 texture is on the right.


Here's a closeup. Yes, that is four times the texture resolution.

Wasn't there a 512x512 limit? How'd you bypass it?

The limit is 256x256 for hardware. And I didn't bypass it...

/me wonders what the file size will be :p

Is it four quarters of that image, each one 256x256, put on the one surface and lined up?

That would result in terrible seams and is only 512x512 anyway.

Then explain so we don't think you're pulling our legs como siempre hace.

Well then I'm stumped.

Of course, but it's fun to watch you guess first.

Did you use that weird method SG_Fan was talking about a while back? Or are you running this level through the Sith2 engine by any chance? Those are my two guesses.

u hax

16 256*256 textures they are.

Space Noxx was awesome. Seriously, that level had some serious aesthetically pleasing 'stuffs' combined with some... totally swank gamplay. Worked well with a host of different mods too, which was semi-surprising.

Oh no! Somebody nuked Europe!

Acharjay...?


I like it.

i see dflt.mat

Interesting. It's not Sith2, the debug stuff at the top reveals that.

Also, he has to be using 3d acceleration, because he's using 16-bit color.

My guess (and its a sucky one):

You managed to fake out JK into thinking it was a 256x256 texture, but when it loads the texture, it is actually the full 1024x1024.

Photoshop.

16 seperate textures. First scaled down to 254 x 254 then back to 256 x 256 to prevent seam errors.

Oh, and you can't really trick JK in such a manner. JK apparently won't allocate the memory for more than 256x256 (for 16-bit at least, or was it 3d accell, I don't remember)... Something like that suggestion's been tried before, and it didn't work.

Maybe it was Russia.. or America.. or maybe Europe targeted themselves? But whatever is going on, Australias gonna be like "W.T.F., Mate?"

Emon is a filthy lying communist.

And he stole my shoes.


TELL US!!!!

if(getThingFlags(source) & 0x8){
  do her}
elseif(getThingFlags(source) & 0x4){
  do other babe}
else{
  do a dude}

So wait... you basically made an image with the detail of a 256x256 mat, and upscaled it? I'm confused.

maby it's a shot from Q3 or some other modern engine with the hud pasted in

FOR THE LAST TIME READ THE POSTS!!!

He put a bunch of low-res textures next to eachother.

He started, took the image, and cut it into 16 pieces. Each one being 256x256. He then scaled each 256x256 to 254x254. Then rescaled it back to 256x256. I imagine this widened the edges slghtly, and then helped eliminate seams.

Is it just me or does the shadow on the planet not match the position of the sun?

Hehe, I think you're right.

He is, that means it is PS'd.

Well, how much light does the moon reflect...

Anyway, is it certain that he did split it into 16 256x256 (well, stretched 254) textures? Or is everyone still guessing?

Yes, that is the case. Emon told us on Chat. LKOH_SniperWolf has the best description of how he did it:

[QUOTE=Hell Raiser]16 256*256 textures they are.[/QUOTE]

*coughcoughhackhack* :p

Ah, yes, but I said LKOH_SniperWolf had the best description. Yours was somewhat . . . simplistic. :p

Yeah yeah I'll fix that.

Here's how I did it:

Take the 1024x1024 texture and divide it up into sixteen 256x256 textures. This is done easily in Photoshop by setting the square selection tool to a fixed size of 256x256. Setting the grid to line every 8 and 1 subdivision (or any power of 2) makes snapping the selection perfectly into place very easy.

Next, shrink each 256x256 texture to 254x254. Then enlarge the canvas to 256x256, leaving a white (or black or any color which easily contrasts your texture) border around the image. The width of the border is 1 px. You can easily automate this process with a simple Photoshop macro.

Now, go into JED and cleave the surface into 16 segments. Put the appropriate textures onto each surface and scale them to fit (fit WITH the border, as if it was a normal texture).

Now you have to change the UV coordinates so that the white border isn't visible. Do this by dividing 254 by 256 (254/256) and multiply that result by your current UV values. My UV values were 2, so I changed them to 1.984375, which is 254/256*2. Then you have to shift the textures around to make sure the white border isn't visible on any of the tiles. Normally, a shift value of 1 will shift a texture 1 pixel. Change it from 1 to 254/256 (0.9921875). Then shift the textures around until all the borders are gone. You may still see a few borders in JED, and you will certainly see them ingame, but we're about to fix that.

Now go back into Photoshop. We have to remove the white border, we'll do this by copying the edge pixels of the actual texture over the white border. So each edge will have two rows of duplicate pixels. This can also be automated with a simple macro.

Since the colors of the 1px borders are so similar, the hardware texture filtering used by JK will blend them together seamlessly.

EMon, i love your balls.

if(getThingFlags(source) & 0x8){
  do her}
elseif(getThingFlags(source) & 0x4){
  do other babe}
else{
  do a dude}

Excuse this question from a non-editing person, but why would there be seams if you just cut the texture into 16 pieces?
Is this an issue only with JK or with other engines, too?

Other engines, too.

It makes seams because it blends with the pixels on the other side of the texture.