Spring RTS Engine

Hmm, that's odd. Every time I've seen that, it's been piece names that don't exist somewhere, for example:

piece gun, turret, aimer, base, flare1, flare2;

Where flare2 doesn't actually exist. Scriptor doesn't care, and if you're not actually using that piecename anywhere in the script, it won't produce constant errors, just errors during the first time the Unit is calling stuff further down the hierarchy.

Haven't ever seen it because of name issues within the S3O itself, but maybe I've just been lucky...

No generally don't mess the piece list up because I go through them one by one and do them in the order I have in upspring when writing scripts from scratch.

Hmm, that's odd then. If you've already posted it, maybe I can take a look later, when I'm done with what I'm doing now...

Uh no I haven't because it needs a recent SVN for MIN and MAX, I was too lazy add dozen lines of code for the necessary if/else statements.
Here is it anyway...

Found yer problem. You name a piecenum "sleeve" that does not exist in the S3O.

Ugh.. ffs I double checked the list, in fact, I've had scriptor and upspring right next to each other. Thanks anyway. Now I only need to figure out a better way to calculate the gravity stuff when it does the small jumps.

Meh, I've had it happen a couple of dozen times, since I use a lot of copy-pasta

Looking over your script, meh... I think you're using far too many sensors, and it's going to run slow as hell, at that tickrate. Have you read the suspension script in P.U.R.E.? It's a lot less overhead, and does most of the same things, only I'm emulating a lot more stuff, to cheat and gain speed back.

The only thing I haven't done with it is your wheel-turning stuff, which is on my list of stuff to solve.

I think it'd be best to use Lua to get the next path-position, and do some trig... instead of checking heading constantly, which is very expensive. After all, you want to know where it's going next, not where it's been, which is the big problem with doing it all in BOS...

Actually get HEADING returns a member var stored in the unit already, thus it does no additional calculation in contrast to what I used before (get XZ_ATAN(0)).

I could get rid of the wheel sensors entirely and do fake bumps when there is a height difference but couldn't be arsed yet.

the awsomeness off this. This is greatest topic!

Noob question :

Is there a fake mod to watch your sexy models ingame ? I don't intend to play, just watching.

look, dont touch

masure u can look at all the models in game with sexy animations and firing in CA

Mr D your work is awesome but i think the gator texture seems to be fairly dull compared to your other models considering it was your first tank it could be the reason why i would say its your weakest texture..

Any chance you could do some work on the gator texture ??

A group picture ingame of all the units I've made so far.

I want weasel, thanks.

Do you plan to update the first post? It's a really cool overview..

Hot hot hot hot hot sex.

Also:

>>> remove(Can) == remove(Core.beating_steel_heart)
True
>>>

please make new con-modells, i know the honor is less compared to fighting units, but they look shitty immo

Mr.D did make a new level 1 con unit.

MelTraX wrote:Do you plan to update the first post? It's a really cool overview..

In the future, forgot about this thread. I'll host the new ones if I get the scripts.

Would be cool if the inital post would provide a downloadlink for all the remakes as it's a bit difficult to find some of them now as CA either didn't or doesn't use certain units anymore or has changed them a bit like that Raider with wheels or the Garpike with the Wolverine-style turret...

I also have two questions:
1.)
Did you create a seperate rocket model for the Diplomat?

2.)
Did you ever texture the Minelayer?
http://spring.clan-sy.com/phpbb/viewtop ... =9&t=14213