Spring RTS Engine

The CAN is fugly all on its own

!<3 can

the can needs unexisting..

ironized < can

I didnt know the can had a jetpack :O

Anyone else remember the great strife that filled the internet when the Can was released for the Ta Unit Viewer? What, the Can? That's the most retarded name I've ever heard, I'm not going to buy this game when it comes out. Damn dogs, that was like twelve, eleven years ago. Shit.

The Can is my favourite unit. It's slow and it waddles, but anything near a Can dies.

Weasel done, though there are errors in the damn model. In the first 10 seconds after spawning the first model (using CA, that is) I get a fuckton of error messages (CobError: Invalid piecenumber for get piece_xz...) from using PIECE_XZ and PIECE_Y on a certain object. Before there were three different objects broken, now it's only one - no idea why. It's either Upspring which broke the model, or scriptor broke references in the script or it's just spring being weird. No idea...

Video here.

nice!

whats with the exhaust butt? lol

Uh... well should be disabled because you can see the particles but I added it anyway.

Awsum.

Does any mod actually make use of the new models yet?
Would models such as these stop TA IP infringment?

CA and no.

Just CA so far uses them all, Xta uses a my commander and Goliath only afaik.

As far as Cavedog IP, the models are new geometry(only based on the Cavedog models as reference), all of them use UVW mapping with all hand drawn textures by me, not the Cavedog tilesets, and alot of the scripting for these units is changed,with exception to the CORE logo that I put on them they're 95% free of Cavedog IP, which is enough in my books.

The only Cavedog IP left in them is the CORE logo.

l2arm kgo

Well i don't see any reason not to just do new core and arm logos then? Simple really?

well one reason I can think off, is because they might suck.

one idea I had myself though, was a furnace for core and a winged robot thingy for arm, maybe a winged robot chalice.

Weasel done, though there are errors in the damn model. In the first 10 seconds after spawning the first model (using CA, that is) I get a fuckton of error messages (CobError: Invalid piecenumber for get piece_xz...) from using PIECE_XZ and PIECE_Y on a certain object. Before there were three different objects broken, now it's only one - no idea why. It's either Upspring which broke the model, or scriptor broke references in the script or it's just spring being weird. No idea...

That almost certainly means there's a broken reference to a piecenum somewhere. Spring often spews these, even though everything's working, and yes, it's annoying.

Maybe a piece name that was from something else, that's in the script, etc? That's the cause of these errors, most of the time. Check over your list of pieces very carefully, make sure that they match the model's actual pieces 100% exactly.

I've had these before and knew how to handle them, except that common methods as in renaming pieces twice, changing order or adding them manually again don't seem work anymore at all. Looks more like a spring issue to me because the error goes away after a few seconds.