Compiling FlaME under mono

[NoQ]

NoQ, does this still work on linux?

Yes!

Currently, there are two more graphical troubles i didn't have before/on windows:

* Some structures (mostly towers, walls, but also some bunkers, oils, units, barbarian structures and some features) aren't displayed at all:

bug2.jpg

* A little coloring problem with water on certain medium zooms, but this is probably my script's fault (though i have no idea why only some tiles were composed wrongly) (you did use my tiles, not doing the composition yourself, right?)

bug1.jpg

[Flail13]

I used the tiles made with your script. If I went back to using the original tiles, and replacing the alpha in flaME, it would be much slower to start up, but would allow people to alter the tilesets without causing the transparency issues.

Here is the code again. It should give either message boxes or crashes with unit loading errors. Ignore the many DPVTOL message boxes for now. You could comment out the msgboxes in clsUnitType.LoadPIE if they get too annoying. Hopefully a crash with a decent error message will show you what the problem is.

[NoQ]

Fixed the trouble with PNGs; here's a correct tile archive.

[NoQ]

It should give either message boxes or crashes with unit loading errors.

Sounds like case sensitivity problems. For example, it's looking for `icdozer.PIE', while the correct filename is `icdozer.pie'.

[Flail13]

That sounds right, thanks. I had forgotten about case sensitivity in Linux.
You should be able to fix it by adding in:

Code: Select all

Path = LCase(Path)

at clsUnitType line 115, before:

Code: Select all

If Not IO.File.Exists(Path) Then
    LoadPIE.Problem = "PIE file " & path & " is missing."
    Exit Function
End If

since all the pie files are lower case

edit: oh, and if you want to comment out the message boxes for testing, they're in modData - do a search for LoadPIE

[NoQ]

Code: Select all

Path = LCase(Path)

Nope, it removes capital letters from the directory name as well.

[NoQ]

Fixed 5 entries in modData.vb instead:

Code: Select all

Result = UnitTypes(C).LoadedInfo.LoadPIE(Path & LCase(SubDirPropPIE & .Propulsion_List.Propulsions(.Template_List.Templates(A).Propulsion).PIE))

etc, everything works apart from

DPVTOL

__________

By the way, you seem to have fixed the arrows bug as well! So there are no more bug reports so far. Respect to you! (:

[Flail13]

dpvtol.pie

the lcase should only go around the last .PIE variable, not the subdir one.

edit: ....not that it really makes a difference. arrows bug? what one was that?

[NoQ]

It Works!

the lcase should only go around the last .PIE variable, not the subdir one.

Both variants work for me.

edit: ....not that it really makes a difference. arrows bug? what one was that?

viewtopic.php?f=5&t=7761&start=30#p79610

[Flail13]

yes i changed the arrows

Since we might be close to ready for a release, is an installer of any kind needed, or will a zip containing the contents of the bin\Debug\ folder do?
Have you checked to see if the settings and autosaves get saved?

[NoQ]

Since we might be close to ready for a release, is an installer of any kind needed, or will a zip containing the contents of the bin\Debug\ folder do?

A zip is enough; universal installer for all linux/mac is impossible and unnecessary; mac users might still appreciate a well-packaged application, but i have no idea how to do this; maybe someone can make linux-distribution-specific packages, but they should start with warzone2100 instead
On the other hand, it might be a good idea to include some README with the zip, saying to install mono and mono-basic (the exact package names are distribution-specific) and run the program as "mono flaME.exe".

Have you checked to see if the settings and autosaves get saved?

They are stored in ~/flaME (where "~" is something probably similar to "My documents"), which is not the best place to have them. ~/.flaME could be better. Many cross-platform applications use such dot-folders for settings even on windows (GIMP, for example, as far as i remember).

[Flail13]

If you're not tired of testing flaME already, here is another version to try to break.

I know the VTOLs still look a bit wrong, but it might be easier to use that way.

As for telling people to get Mono, is http://www.go-mono.com/mono-downloads/download.html what is needed?
There are some extra documents in the debug folder.

[NoQ]

Great, i finally see weapons on units and towers!

I know the VTOLs still look a bit wrong, but it might be easier to use that way.

This is the only way, it's good as they are, upside down ^^

One little trouble: RetreHoverFlashLight template actually looks rather like Wyvern.

[Flail13]

One little trouble: RetreHoverFlashLight template actually looks rather like Wyvern.

That problem is caused by the stats files supplied by Warzone.

edit: what do you think about the less common appearance of the red tiles?

[NoQ]

As for telling people to get Mono, is http://www.go-mono.com/mono-downloads/download.html what is needed?
There are some extra documents in the debug folder.

Here's a version of INSTALL.TXT updated according to my understanding:

Code: Select all

flaME Mono for Linux/Mac

This is a map editor for the versions of Warzone 2100 found at www.wz2100.net

Installation:

Mono runtime with Visual Basic .NET support must be installed to use this. 
MacOS users should download the package provided here: 
http://www.go-mono.com/mono-downloads/download.html 
Linux users are advised to use packages from the repositories of their distribution instead.

Extract the entire contents of the archive.
cd to the directory and run the program as "mono flaME.exe"

Usage:

See INFO.txt for more information.

As i have read, VB.NET support is included in the package from this link, but i couldn't check it.