Spring RTS Engine

@bob (edit: specifically regarding your model pack): looking at this argument objectively, when you first announced your project, it seemed clear (to me at least) that it would be pyra doing a texture, and you would do all of the models... there was never an appeal for "hey i'm looking to buil...

Behe's the BA team now, and he's doing spectacular stuff... but he's got a *lot* of ground to cover. Beherith is doing a fantastic job, yes. Infact, he's basically functioning as the person stepping up and organizing everything. The problem is, he's one person. He needs a team. Ideally a dozen or s...

And maybe a lack of proper advertising, messy and sparse introductions to the game, the lack of a single install, a vague lobby, an unfinished engine, recycled content across many games (making them all look like mods of some non-existent-mother-game), a somewhat exclusive community, no soundtrack, ...

Alright, we've handed the rights of all of our content over to Beherith personally. This way, it can be BAR content instead of Spring content.

If you have issues with the decision, please PM me personally and don't flood this thread or bother Beherith/BAR-people with subject. Thankies.

Oh, you were responding to that. I was under the impression that you were wanting to change the BAR models for BAR . Legally, you can do whatever you want with them. Personally, I'd rather you not use them all in any other game for spring. I'd rather they be somewhat exclusive to BAR to maintain a d...

On what Bob said about taking BA:R models, would it help if we edited the texture atlas somewhat? Obviously we only need to do that once and it would work on all models. They use a lot more team colour than is strictly necessary so we could probably put some other colour in some of those areas. I'm...

sniperbob121 wrote:Hi guys thanks for your reply. I am trying to create a game similar to Homeworld. Any suggestion on what kind of engine I should use?

http://udk.com/

So Unreal Engine looks nice.

While you legally have every right to do with them what you will, I'd rather they be used for a single project. Reason being; when people see the game for the first time, I'd rather not they see multiple versions of what looks (artwise) to be the exact same thing. It gets confusing and it looks wild...

People give mudbox's UI shit for being too simple. Which is weird, as that's exactly what it needs to be. I find it to be much more accessible than Zbrush's.

Now that Mudbox 2012 has better posing, vector displacement mapping, a huge supply of rendering features, integration with other autodesk applications, better baking flexibility, layers, and best of all, Ptex (so damn sexy), I still maintain that its the better app for sculpting. 5 years ago this wa...

Or I could just make it hull mounted...

Hold your ponies. I'll mess around with some stuff.

I'll fiddle around with it a bit when I get back from vacation land.

Ok, so the problem here is, using a universal texture on fairly complex models is...silly. So, despite working on it for the past 6 hours or so, it looks like shit. (The uvw that is. The meshes are fine.) But, being as I promised Christmas presents, I'll show you the commander mesh. I think at this ...

If shit goes as planned, I should release the commander, krogoth, and a few other units on Christmas day.

Cheesecan wrote:The anticipation is the best part - seeing your fps half is the worst.

Don't worry. I don't think it will be near as bad as that. Not only are they all using one material, they all have ridiculously low poly counts for today's standards.

Huzzah, I'm back.

Working on the krogoth now.

Roughly 48 hours.

bobthedinosaur wrote:Nice models mr bob. What kind of engine are those expected to run on?

Unreal Engine 3, actually. (UDK)

What's that you say? An RTS in Unreal Engine 3? THIS IS OUTRAGEOUS.

Hopefully in the coming weeks yes. Probably by the 18th or so.

*Gets his rapid fire modeling groove ready.*