out of date documentation

I've been looking around here for a couple of days at PLSM2 and I'm getting quite confused about how to get started. It's proving very difficult to read the documentation in the several wiki pages and in this forum because almost everything seems to be out of date.

Can anyone offer some tips on how to get started with PLSM2 these days (as of March 2008, using Eihort 1.4.6)? Or do I pretty much need to hack it together myself based on snippets of instructions across multiple documents, and trial and error?

Some specific problems I've encountered thus far:

- Much of the info seems to point to Dagon compatibility (not Eihort), and VC7. Hopefully this isn't a huge issue, since I'm using Eihort 1.4.6 and VC8.
- MapEditor in the vc8 SDK SLN doesn't work, and the GOOF alternative is also unsupported. I understand I will need some sort of map editor or PLSM2 is useless, is that correct?
- I've successfully built the demo application and the plugin DLL, but I can't get the demo to run because of hard-coded paths to resources that I don't have setup that way. I could hack this to work but is that necessary?

Should I even be looking at PLSM2 right now, or is this another case of "wait until PLSM3 comes out" because nobody's actually working on the older version and it's been allowed to fall apart?

Hi Arcanor


- Much of the info seems to point to Dagon compatibility (not Eihort), and VC7. Hopefully this isn't a huge issue, since I'm using Eihort 1.4.6 and VC8.

Eihort compatibility shouldn't be a big problem if you're just getting started with PLSM2, but perhapse if you're using some of it's advanced functionality.


- MapEditor in the vc8 SDK SLN doesn't work, and the GOOF alternative is also unsupported. I understand I will need some sort of map editor or PLSM2 is useless, is that correct?

Not realy. If you want to create a terrain, you can use a lot of third party terrain editors that are able to export greyscale heightmaps. The only difficulty might be editing the terrain after you splitted it up with the mapsplitter, but PLSM2 has some build in functions so you can edit the terrain in your aplication.


- I've successfully built the demo application and the plugin DLL, but I can't get the demo to run because of hard-coded paths to resources that I don't have setup that way. I could hack this to work but is that necessary?


I've never tried the demo, but normaly all resource pathes should be defined in "resources.cfg" or "resources_plsm2.cfg" and therefore easy to change.