Spring RTS Engine

Looks fine to me behe, I can always add my cammo later also :)

Wombat wrote:u say it now, when first screen of his was posted 14 jun :D

Feel free to state your opinion as well,this isn't soviet russia.

Don't worry, Imo it looks very good. Though I will be missing the camo...

Anyway, I'd like to comment on that t2 consturction bot. Why the warning stripe section is so twisted and bent? Looks like it has got some damage and is in really bad shape...

It only looks twisted because my normal mapping tool picked it up as a really big groove, and that will need to be fixed on my side.

Fantastic, ETA to release?

This year.

Running out of time man.

Look forward to seeing them whenever though the normal maps are blowing my mind.

we are painting his new flat, be patient

Did you UVmap it first? Shouldnt be hard, lots of large flat surfaces.

looks great

but god do not use png my internet cracks XD

leavin this here

Here are all 15 bots, ready for Spring!

Special thanks goes to smoth for the morty and dom models and lots of help, and for Kaiser for the pyro, can and roach textures, and the valuable feedback and encouragement.



(updated first post as well)

Download link: http://beherith.eat-peet.net/stuff/Beherith_Core_T2.7z

Com unit ruins an otherwise amazing screenshot. Nice job on the models, they look great!

They look great except the sumo is very small, especially next to the commander, and the manticore looks way too big.

Whoops, realized 3 guys were missing from the screenshot :O



They can be easily resized in upspring if needed.

^ cool

resized in upspring

not quite as cool

rattle wrote:^ cool

resized in upspring

not quite as cool

No longer a problem. (Hasn't been for some time now)

Impressive effort Beherith, but where are the cookie storage facilities?

They look really really great, behe! Glad to get my hands on finished versions of these. Even better than the t1 bots, lots of nice, crisp detail.

I am wondering though why you put 4 models in each texture. It would make sense if you shared areas of texture, but in the case of the Dominator/morty/advcon/freaker textures, they all seem to have a perfect 1/4th of the uvmap to themselves. This makes it problematic to use some of the models, and not others, as in the case of Zero-K which doesnt have all these units.

Shouldnt be a problem to resize the uvmap to cover the whole area in upspring, just wondering about the motivation.

Less texture swap time, ability to kitbash. I can make two more versions of the s3o's where all are on 1 texture, and where each one has a separate tex (I made some python code to do linear transforms of s3o/obj UV space)