FOnline SDK - Question

[Grey]

Awesome! thank you. How can it be there?? is just the global map info. Anyway, im sure this will be helpful for many others

[Gob]

How can I disable the opacity thingy for the roof? So people can't see through it.

[Surf]

setting the RoofAlpha to 255 in the config.fos file should do the trick.

Code: [Select]

/// Client specific definitions
#ifdef __CLIENT
__RoofAlpha             = 255;


[Gob]

Thank you. It worked.

[Gob]

How can I resize the mapper window ? It's difficult to make maps with a 800 x 600 window.....

[Wipe]

Mapper uses client configuration, so just change it via FOConfig or manually in FOnline.cfg

[Gob]

Mapper uses client configuration, so just change it via FOConfig or manually in FOnline.cfg

Yes, I noticed after I chage resolution to client. It's pretty dumb IMO.

[JovankaB]

Whole mapper is... let's just say, suboptimal

Feel free to create better mapping application

[Wipe]

Yes, I noticed after I chage resolution to client. It's pretty dumb IMO.

Well, not really. Mapper share pretty much code with client, like drawing functions, so fixes in there affect both applications. But hey, nothing stops you from using command line switches (another shared part ) for different resolution in mapper; these are checked after reading values from config, so...

Code: (Mapper1024.bat) [Select]

Mapper.exe -ScreenWidth 1024 -ScreenHeight 768


[Gob]

Feel free to create better mapping application

I'm not such a good programmer.

[Wipe]

I'm not such a good programmer.

Since FOnline maps are enforced to be in text format, it doesn't require to be a pr0 to read them. In fact, simple parser can be done just for practice, without deep knowledge about chosen language. Displaying given object graphic isn't much of a problem too (many .frm loaders around, (including this one ;p)), so all you has to do is stick to the current format.

Biggest challenges in creating new mapper would be - imho - creating more user-friendly GUI, probably sorting objects in right order (last one is wild guess, someone more experienced should correct me if needed - i didn't messed with .fomap files for more advanced stuff than reading them, so... :>) and make it working with scripts. First two can be done even now, last thing can wait until you/someone make at least half-usuable application. If stuff will be good enough, i guess it would be much easier to get support from cvet

Due to compatibility reasons, i would recommend C++ here - should be easier for everyone if program find its way into standard SDK tools. (but if someone make it perl+gtk, i'll give my whole "+1" limit for given month ;p)

[Kilgore]

I completely don't understand why one would give a shit about making "a new, better" mapper.. for teh lulz?

The mapper is a very convenient tool after you just get used to it, which should take time of making few maps. Also, at least basic knowledge about SDK is handy, but not necessary. The only thing that I imagine missing there is "Undo" but it seriously doesn't matter if you know what you're doing. Also, I've seen some solution for it somewhere scripted by someone, I would post a link but I don't have it and don't use it.

The real problem is that there is almost no tutorials for mapper or good how-to-make-a-map guides.

[Lexx]

The mapper is a very convenient tool after you just get used to it,

You probably haven't used many mapping tools yet.

[Surf]

To me the mapper works allright aswell, the only thing I am really missing is some "undo" function.

E: was so lazy and didn't read the full post of kilgore, he got it already pointed out.

[Kilgore]

You probably haven't used many mapping tools yet.

The outcome of your work is the thing that counts, not the tools you use, my master.