Free Allegiance Forums

ICE 3.44 : http://code.google.com/p/allegice/

edit: current version is 3.44 which fixes 2 nasty bugs in 3.42/3.43

New in 3.42 (some of this was part of the pre-released 3.42)

updated to VC10 (VC++ 2010 runtime required if you don't have it already) now use registry key "Artpath" instead of "EXE Path" for artwork location minor error messages fix & sorting ship loadout UI fixes & sorting added link button from station to drone (constructor) more checks in validation: station successor and constructor & last station must be a flag pedestal major internal change: 'shared IGC source' with Allegiance. This exposed new attributes (or changing names of old ones):
factions: HUDdevel: floating icontreasures set: detailed powerups, devels addedprojectiles: directionnal & absolute speed as check boxesdrones: icon preview and path addedstations: 'scale' renamed 'radius', textureships: 'scale' renamed 'length', weapon & pack masks exposed (unused by game yet as of R5/R6)missiles: bDirectional textureName (nyi: timeToBuild & width)parts: lot of attributes renamed
As you can see most changes are cosmetic except for:

new type of treasure as devel and editable floating icon for devel. The game code should support this but plz test a lot before.Tex & bDirectional for missile: allow to render missile using a 2d sprite (a decal) instead of a 3D model. think: rapide rate of fire missiles , very small missiles or huge missile swarm... once again the game code support this but no core implemented it yet.

Nice work!
Thanks for providing this KGJV

KGJV wrote:QUOTE (KGJV @ Aug 21 2010, 06:23 AM) ICE 3.42 : http://code.google.com/p/allegice/

missiles: bDirectional textureName (nyi: timeToBuild & width)
Tex & bDirectional for missile: allow to render missile using a 2d sprite (a decal) instead of a 3D model. think: rapide rate of fire missiles , very small missiles or huge missile swarm...

Wow, a huge missile swarm would be awesome!

Outstanding, thanks KGJV.

The notion of floating GAs is very interesting.

How would 2d sprite missiles handle being shot down?

NightRychune wrote:QUOTE (NightRychune @ Aug 21 2010, 09:27 AM) How would 2d sprite missiles handle being shot down?

I've no idea, I haven't looked at the game code for this. Since the model can be null, I guess the missile collision box default to a single point ? But that's just a guess for now.

I imagine it'd use the same collision detection as bullets hitting a ship etc. You could shoot them down with something that has a model, such as a missile, but bullets would have to be in exactly the same spot. Which is nigh-impossible. Balancing that behaviour is for the core dev who decides to use it. Which is what KGJV said.

Ok then, to add something useful to the topic: Thanks KGJV! I haven't had the chance to play with this yet but I will.

As long as we don't touch the new options there's no chance or producing a jacked up core file right? I'd like to use the new version, but I don't want there to be any chance of me submitting a broken core (unless I want to break it)

I've run into an odd bug.

Seems whenever I duplicate a booster (to add a new one) none of the consumption/thrust/etc. values get copied over correctly. They all become very odd values like 3.28066. Further duplications keep randomizing the number.

Xeretov wrote:QUOTE (Xeretov @ Aug 22 2010, 11:08 PM) I've run into an odd bug.

Seems whenever I duplicate a booster (to add a new one) none of the consumption/thrust/etc. values get copied over correctly. They all become very odd values like 3.28066. Further duplications keep randomizing the number.

tx i'll look into that. Is it only for booster ?

Hmm I thought it was, but just went and confirmed and it seems to be happening for any part that gets duplicated.

Everything else looks ok: Projectiles, ships, stations, devels, etc.