Spring RTS Engine

what is the maximum size i can make a texture for good compatibility?

i've heard 2048 square is a limit that once passed will be unable to be rendered on older ATI cards, but i'd like to doublecheck, because i've never myself tried to use anything larger than 1024 square.

come on experts! help me out ^^

Anything above 2048 starts to get stupidly large in filesize

aha! but if im only using on texture shared between every unit, im not too worried...

for instance, i could get 16 512x512 textures from one 2048x2048 square, right? this way i'll be getting like 150 units done within that space... so yeah, you raise a good point, but i think overall this will be very efficient (i just don't want to exclude anyone by making a needlessly huge texture)

2048 is definitely the limit for older ATi. That said, there are very few people still playing Spring on Radeon 9800s etc., and newer ATi can go 4096.

And yes, a single 4096 for everything should operate faster. However, I have to caution that I don't think that Spring checks to see if the textures match the previous Unit- that's a speedup that's possible with the Unit shader system, though.

Argh wrote:I don't think that Spring checks to see if the textures match the previous Unit- that's a speedup that's possible with the Unit shader system, though.

this seems ominous, but i dont think i understand

can you dumb it down a notch?

Argh wrote:2048 is definitely the limit for older ATi. That said, there are very few people still playing Spring on Radeon 9800s etc., and newer ATi can go 4096.

Newer ATis ones can go 16384^2
But yeah, you should always expect a maximum of 2048 for mid-range, and 4096 for high-end.

PS: You don't need more than 1024 for units at all. If you do then you are doing something wrong.

@jK - he's making his "Lego" modelling system. A set of parts that will be shared across many, many different units, and thus will have more than a single unit's worth of parts within the set, and they will all share a common texture map.

Yeah, what Pxtl said. He's building an atlas, basically.

Then it's fine to use greater texture. Still if you use the engine unit renderer for those textures you should take attention that the engine doesn't load the texture multiple times:
The engine will reuse S3O textures ONLY, AND ONLY if texture1 AND texture2 are equal.

Yes jk, they are the same. The legos all share the same uvmap (and therefore, the same texture images).

jK wrote:Then it's fine to use greater texture. Still if you use the engine unit renderer for those textures you should take attention that the engine doesn't load the texture multiple times:
The engine will reuse S3O textures ONLY, AND ONLY if texture1 AND texture2 are equal.

Does this include the case where a texture2 is not applied at all?

The filename strings have to be same not the files, so don't using a tex2 is equal to nullstring.

thx for the input jk; it set my mind at ease!

KaiserJ wrote:thx for the input jk; it set my mind at ease!

Ignore his retarded ass. You're doing it right. He just likes to be as annoying, vague and obscure as he can possibly manage. Lurker does the same thing to an extent and it pisses everyone off.

The funny thing is that the concept of what you are doing, but super smart people like jk etc can't get their minds around it. Now that's humorous.

Forboding Angel wrote:Lurker does the same thing to an extent and it pisses everyone off.

I disagree, Lurker has always been infinitely more helpful and understandable than jK.

Forboding Angel wrote:

KaiserJ wrote:thx for the input jk; it set my mind at ease!

Ignore his retarded ass. You're doing it right. He just likes to be as annoying, vague and obscure as he can possibly manage. Lurker does the same thing to an extent and it pisses everyone off.

The funny thing is that the concept of what you are doing, but super smart people like jk etc can't get their minds around it. Now that's humorous.

I love you too

Forboding Angel wrote:Ignore his retarded ass. You're doing it right. He just likes to be as annoying, vague and obscure as he can possibly manage. Lurker does the same thing to an extent and it pisses everyone off.

What's your problem? While I agree with you that those two are not usually understandable, jK was not being this way in this thread.

Forboding Angel wrote:The funny thing is that the concept of what you are doing, but super smart people like jk etc can't get their minds around it. Now that's humorous.

Pxtl wrote:@jK - he's making his "Lego" modelling system. A set of parts that will be shared across many, many different units, and thus will have more than a single unit's worth of parts within the set, and they will all share a common texture map.

jK wrote:Then it's fine to use greater texture.

jK understood it just fine. Don't bite the hands that feed you, forb.

zwzsg wrote:

Forboding Angel wrote:Lurker does the same thing to an extent and it pisses everyone off.

I disagree, Lurker has always been infinitely more helpful and understandable than jK.

jK just ignores dumb questions. Lurker actually kicks people off the server for them

woah i wasn't being sarcastic for once!

(or was i, and am i still being)

but no. all of you be nice.

zwzsg wrote:

Forboding Angel wrote:Lurker does the same thing to an extent and it pisses everyone off.

I disagree, Lurker has always been infinitely more helpful and understandable than jK.

Agreed.

jK wrote:I love you too

Back at ya lufluffykins