PLSM3 status: ETA = When it's done.

[tuan kuranes]

PLSM3 news:

Still working on it, but honestly very slowly, plus I tried many experimentations things, and therefore tested and threw many implementations and time...

I may perhaps tend to release a less featured PLSM3 or 2.5 , without the terrain renderer plugin diversity I'm after in PLSM3. (which is the biggest problem I have here.)

Problem is I'm under load of work lately, so working on it was very hard...
So still hard to say when, but as real life work is planned (very hard), not to be released before a few month or so.

I guess I should have have announced PLSM3 once ready instead of blocking/deceiving expectations.

Sorry again.

Still PLSM2 is a viable solution, even if needing some documentations and perhaps some patches.

As I'm very busy, new maintainers/patchers, forum moderators, or documenters are and would be very welcome.

[beaugard]

Did you work on the CHC implementation (Occlusion octree scene manager...)? I have tested the existing implementation by pulling out the relevant files from plsm2, and while it does work (CHC works, pure frustrum culling doesn't) I think it could be done ... better . The obvious thing is in the todo of plsm3 - to make it a project of its own. Another thing you have mentioned in the forums is to make use of a custom renderqueue...? There are more things that I don't remember.

In short, if you have worked on the Occlusion Octree SM, it would be of great value if you released it (not only to me, I think). If you haven't I'll start working on the sources from plsm2 (I understand if you haven't - maybe not the most interesting thing to spend your time on).


EDIT:
oh, and take the time you need, release what you feel you can release, etc. plsm2 is an amazing piece of work and developing anything on the side of work&family is always going to be slow. So don't feel bad about it...

[tuan kuranes]

@beaugard: FYI: CHC released here.. As you'll see still need work into it, but I'm focusing on PLSM3.

[beaugard]

Wonderful! Thank you very much.

[Arroy]

how long for release?

[btmorex]

I'd be interested in a PLSM 2.5. I wouldn't worry too much about releasing something that's not feature complete or undocumented.

[Highway]

What is the development status on PSLM3/2.5 ? Do you still find time to work on it?

[MOROHEUZ]

Good question ...
Unfortunately, I can no longer compile .. (Vc9 + + with Vista)

I think the day will come Shoggoth, perhaps there the whole nen upswing again ...

Unfortunately, this is nothing quite so easy ....

But perhaps SPT2 the day comes out ... that's enough to plms2 ran very near ... and if there is a terrain editor would be ... OHhhhhhoooo .. then its the best tool ive ever seen

[Seregvan]

Hi all, any updates in PLSM3?

[compvis]

Hello,

When will PLSM3 be released ? I can't wait longer !!!

[Ralith]

Any news? PLSM2 seems to have fallen out of sync with Ogre SVN.

[DanielSefton]

Just to say, PLSM2 still works absolutely fine with the latest Ogre. If you're having problems, it's not because they are incompatible.

I'm sure Tuan will post an update when he feels it's ready -- he's a busy guy.

[ERSmith]

Oh really? I've been wrestling with this all week and since the compile comes out full of "bla bla is not a member of Ogre::" it seems to indicate to me that plsm2 is trying to use nonexistent members.

[tuan kuranes]

plsm3 is really near now, but still under heavy work.

Meanwhile make sure to use Ogre SDK or OGRE SVN tag 1.6 (I'm not supporting ogre SVN Trunk) AND plsm2 SVN

[DanielSefton]

Oh really? I've been wrestling with this all week and since the compile comes out full of "bla bla is not a member of Ogre::" it seems to indicate to me that plsm2 is trying to use nonexistent members.

Yes... I got it working with the latest Ogre (of which I mean the 1.6.1 branch) straight away. Something must not be right in your setup. Btw, start a fresh project, the supplied project files are a bit dodgy. But post your problem; it's no good stewing over something for a week without help.