Star Wolves 3: Ashes of Victory in Development

[Goblin Wizard]

Yesss. At last. Added bloom/hdr? Textures resolution looks the same.
I'd like to see new GUI too.

While better graphics is always a nice thing, imo that's just icing on the cake. Putting more stuff as FILETYPE STANDART instead of DYNAMIC would be nice Also, I still don't know enough of LUA to suggest script improvements, but I'm sure guys like Nanaki and Goblin Wizard may have something to say about that.

[Rastix]

Think some more screenshots http://www.strategyinformer.com/pc/s...reenshots.html

[Rastix]

Originally Posted by Trucidation

Putting more stuff as FILETYPE STANDART instead of DYNAMIC would be nice

Explain please

@Rastix:
DYNAMIC type seems to be some sort of encoding, for example look at the text in \Data\LocData\English\Locations\Aurora\text.loc. Line 8 is something like "#L_nav_Alex=<some numbers>".

But in STANDART type files like \Data\LocData\English\ui_windows.loc, definitions like those are in plaintext, e.g. line 11 "#UI_TradeStationWndCaption = Trade station".

I'm sure the devs have their reasons for using different types, but perhaps they can be persuaded to explain how to understand DYNAMIC type files?

[Goblin Wizard]

Originally Posted by Trucidation

While better graphics is always a nice thing, imo that's just icing on the cake. Putting more stuff as FILETYPE STANDART instead of DYNAMIC would be nice Also, I still don't know enough of LUA to suggest script improvements, but I'm sure guys like Nanaki and Goblin Wizard may have something to say about that.

I can give only one suggestion: Release as much part of the code as you can (form the exe) and put it into editable script files. We'll take care of the rest.

I like the new light effects.

[Rastix]

Originally Posted by Goblin Wizard

I can give only one suggestion: Release as much part of the code as you can (form the exe) and put it into editable script files. We'll take care of the rest.

The great decrease of perfomance would be as a result

Originally Posted by Trucidation

I'm sure the devs have their reasons for using different types, but perhaps they can be persuaded to explain how to understand DYNAMIC type files?

They have copyrighted decoding tools

We don't need their decoding tools if they used STANDART (because the text wouldn't be encoded...). Or did you mean something else?

Btw thanks for the update, nice pictures

[Goblin Wizard]

Originally Posted by Trucidation

We don't need their decoding tools if they used STANDART (because the text wouldn't be encoded...).

Exactly! What is the reason of encoding the dialogs? Why don't put them in plain text (like some others loc files)?

Destructible modules, or item durability. E.g. "full health", "light damage", "heavy damage", "broken". We could set items to perform less optimally at different stages of damage or even be totally inoperable if they get broken.

Set flags to allow which weapons can have a %chance of causing this damage. This also opens the possibility of repair modules that fix items instead of shield / armor. In other words, more variety.

Edit:
This can also create more perks for repair; right now we have shield repair rate and armor repair rate. This can add item repair rate.

Another idea, firmware + pilot slot. Firmwares for fighters as well, not just mothership. Nothing major of course but even modest improvements (5%-20%) can help.