Page 1 of 1

Flame /sharpFlame improvements & bugs

Posted: 31 Jan 2015, 04:47
by vexed
If you found and bugs in the current Flame or sharpFlame, then post in this thread.
If you need some improvements done to either, then please be verbose on what is it you need, and how it should be done, and why it is needed.

All OT posts will be killed on site. :stare:

Re: Flame /sharpFlame improvements & bugs

Posted: 31 Jan 2015, 04:51
by vexed
A list of accepted ideas that are being worked on:
(none so far)

Re: Flame /sharpFlame improvements & bugs

Posted: 31 Jan 2015, 08:13
by NoQ
Control map format version through an extra file in tilesets and objectdata.

Map format version (which is also savegame format version) is stored in game.map in the second 32-bit word. Current version supported on -master is 39 (the constant is called CURRENT_VERSION_NUM in the game source), and the oldest supported version is 10 (hardcoded in mapLoad()). The game uses this number to detect explicit incompatibilities with maps.

Whenever new stuff is added to the game's tileset or objectdata (and later to the editor's tileset and objectdata), the new maps become incompatible with the old game. Hence, it is necessary to bump version format. Since the old tileset and objectdata can still be loaded into the editor, the editor executable is a bad place to hardcode map format. The map format version written into the map should be the maximum of the tileset format and the objectdata format version.

Such feature would allow us easily expanding tilesets and objectdata in new game releases without running into crashes or undefined behaviors.

Re: Flame /sharpFlame improvements & bugs

Posted: 26 Feb 2015, 18:42
by montetank
vexed wrote: then please be verbose on what is it you need, and how it should be done, and why it is needed.
Just now, i am making a new map in Rocky-style and i am badly missing a feature like the boulders in Arizona-maps. I know, i can use this feature in every style, but it looks very bad on snow. I need this feature to block a high-plateau near the base. I don`t want, that transporters are able to land there. I could use some tiles, changing them to cliff faces. But the map is more or less near the finish and in this case it would be necessary to prove the whole map , if there is this cliff face tile anywhere. Horrible job. We have the boulders in Arizona, why not in urban and in Rocky? This blocking feature is very important. It is a pity, that i can`t program :(

Re: Flame /sharpFlame improvements & bugs

Posted: 02 Mar 2015, 19:43
by montetank
Sometimes i use the generator for heightmap ideas. Something is going wrong there. Here is an example: I give the player No.1 for the base the y-coordinate 90 and the generator change to 64. That means-he calculate 76 (which is x in the map width) - 12 = 64. But the map has 117 as y-height. 105 would be logical. It doesn`t matter how large the base-area is defined. It is everytime the same problem.

Re: Flame /sharpFlame improvements & bugs

Posted: 18 Mar 2015, 04:05
by vexed
BTW, if people can post pics of the WYSIWYG issues (like, flame shows one thing, and the game has it as something else) that would be great as well!

Re: Flame /sharpFlame improvements & bugs

Posted: 06 Apr 2015, 01:39
by Zignaught_
Can't seem to load a map i started. Also, have to use process manager to force close.

Also I get in app error, sequence missing elements.

Re: Flame /sharpFlame improvements & bugs

Posted: 02 Mar 2018, 05:37
by Nexus Darkshade
Not sure if this counts, but I can't find a way to actually get the SharpFlame .exe file to pop up in the SharpFlame.gui.Windows folder.

Re: Flame /sharpFlame improvements & bugs

Posted: 27 Mar 2024, 11:32
by Tzeentch
This may be more the appropriate place to request;

Now I see we have both of these tools added to github:

https://github.com/Warzone2100/flaME
https://github.com/Warzone2100/SharpFlame

They contain the needed Tileset and Object Data, but lack the executable(s).
Can the latest set of zip files be added to the repo as a git tag release please?

FlaMEv1-29win-installer.zip
FlaMEv1-29win-portable.zip
FlaMEv1-29mono.zip (see FlaME on Linux)

Also it would be nice to have some docs added such as readme file and how to use FlaME.
Perhaps even a manpage added for Linux.

This will allow to more easily package those files up to provide at least Linux OOTB installer.
Seems simple enough.

Btw... what does FlaME stand for? The ME part likely implies Map Editor?