Warzone 2100 Forums

Yes, I did. It's a very nice app they offer (and for free!). weapons.mgs.ldd4.png They do look nice right next to each other, but unfortunately they're too large scale for the Viper chassis I designed yesterday. I need to either make the chassis bigger (and it's already a bit on the large side compa...

So I spent about an hour in a 'different' kind of Design Screen ... and came up with this: viper.wheels.mg.battle.png It definitely has a lot of room for improvement, but the Viper Wheels MG is nonetheless designed in a modular fashion and to minifigure scale :) I have really got to do the humble tr...

This is a widely known issue which seems to have started occuring in the 3.x series (2.x releases did not exhibit the behavior?) . The problem isn't path finding per se, it's about execution of said path, especially in a crowd. When you tell several units to travel from A to B and they cross paths w...

Well, Pie Slicer is currently having a possibly blocker-level issue in that the inclusion of the DirectX 9 library (which is built against the .Net 1.1 library) is causing VS2010's LoaderLock MDA to throw an exception. Pie Slicer itself still seems to start up and shut down properly if I simply igno...

This? However that page doesn't seem to mention anything about mesh animation, transformation matrixes or the like, only texture animations; it looks like a replacement for the PIE format but nothing else.

... wzm?

Because customizable animations would open up a whole new world of graphical improvements in WZ. Currently all the animations WZ uses are hard-wired one way or another. Specifically, they're listed in a file called "anim.cfg" that looks like this (the following was extracted from base.wz, ...

I know about the .ani format, last versions of Pie Slicer had rudimentary support for editing ANI values. WZ actually has two animation methods, there is the "frames" method (each submodel is a complete frame of animation unto itself, like an animated GIF) and the "trans" method ...

I've been seeing this error crop up quite a few times while playing the campaign. I don't really know either, I just assume it is a sign of something that went wrong on a deeper level.

Part of the problem is the whole graphical model of how cyborgs are rendered - the upper "torso" is actually part of their weapon graphic, not the chassis graphic.

Also I've not seen any flying cyborgs there. Nexus does have cyborgs with the jump backpacks (templates "NX-Cyb-Rail1-JUMP", "NX-Cyb-PulseLas-JUMP", "NX-Cyb-Miss-JUMP", graphic "cybodyjp.pie") but they do not actually fly (assigned propulsion: "CyborgLeg...

Three words describe today: Beat. The. Campaign. Nice to see no time limit on the final mission. Nexus managed to find my LZ while I was still setting up defenses, VTOLs did some damage, otherwise only harassment raids, reinforcements landed quickly enough too. Got into a Ripple vs. Archangel artill...

@Stratadrake: but only sensors/commanders can be the "eyes" for artillery. ... Which is exactly how mobile sensors/artillery works - sensor only targets 1 thing at a time it was changed, i dont see reasons for rollbacking that Really? Obviously, if you only select one target for your sens...

role of sensor units can be changed, who setted them to that role? Any unit can explore the map and discover whatever things (enemy patrols, enemy base, etc.) in the process, but only sensors/commanders can be the "eyes" for artillery. i remember games in 2.3x where you could make many ar...

Next question: Is the RD an actual sensor? As in, can you assign artillery or VTOLs to a RD unit? Can a RD issue attack orders like a standard sensor (in which case it would mostly be just a standard sensor) ?