Areas that need research

[Paradox]

Just an update for everyone. I'm working on a test plViewFaceModifier.

If UruExplorer survives the test, I'll let you know the results.

List:
[s]1. plLayerAnimation[/s] --documentation complete
[s]2. plViewFaceModifier[/s] --implemented in plugin
[s]3. plATCAnim[/s] --documentation complete
[s]4. plOccluder[/s] --Tahgtahv says that he has it finished. Not in plugin
5. CSV code and Hard/Soft Volume Regions
6. pl --Being worked on my AdamJohnso and Tahgtahv
[s]7. plCameraModifier[/s] --Trylon added to plugin, documentation not finished
8. Other Modifiers and Responders --Messages doc'ed when needed
9. pfGUI___
10. plSharedMesh

But I'd start with Layer Animations before we get a riot going on here :ph34r:

[Tahgtahv]

One other thing, if I document a class and it relies on other classes, feel free to put the new classes back at the top of the list as I may not complete them at the same time as the original class. Make sense?

[Paradox]

yeah. I'll bug you if you leave something out

[Aloys]

I can't wait to hear more about that plViewFaceModifier test. B)

Beside this.. Hmm.. How should I say that?.. The four classes you just mentionned are of course the most needed right now. But err.. in a near future I know of an Age project that would deeply need occluders.. *cough*ahrapahts*cough*..
That's all.. :rolleyes:
[/shameless plug]

[Robert The Rebuilder]

My personal lists...

Higher priority classes - Needed info for new features

plVolumeIsect, plConvexIsect (used by plSoftVolumeSimple)
UEGClassesS (used by plSound)
UEGClassesH (used by plEAXListenerMod)
plCameraModifier1

Lower priority classes - Needed info for refactoring

plMessage, plRefMsg, plLayRefMsg (for plLayer)
plCameraMsg (for plResponderModifier)
plTimerCallbackMsg (")
plEnableMsg (")
plSoundMsg (")
plLinkToAgeMsg (")
plResponderEnableMsg (")
plOneShotMsg (")
plExcludeRegionMsg (")
plSubWorldMsg (")
plSimSuppressMsg (")
UEGClassesO (")
plController, plPosController (for plLayerLinkAnimation)
plSwimRegionInterface (self)
plSwimCircularCurrentRegion (self)
plSwimStraightCurrentRegion (self)

[Paradox]

From my understanding, most of the message classes are just documented as they are needed, so once we start implementing those classes they will be documented.

Tahgtahv tells me that he has finished plLayerAnimationBase and all of the classes associated with it; But he hasn't given me any documentation :rolleyes: So I've crossed it off the list, I just need him to put the docs somewhere.

plViewFaceModifier, preliminary test: I have the plugin reading them, but it's encountering errors in a few spots that I need to fix. I will add a VFM to the test Age as soon as I figure out what the variables mean.

[Robert The Rebuilder]

plViewFaceModifier, preliminary test: I have the plugin reading them, but it's encountering errors in a few spots that I need to fix. I will add a VFM to the test Age as soon as I figure out what the variables mean.

This link may or may not be useful.

http://wiki.cobbs.ca/index.php/Uru_PRP_ ... ceModifier

[Tsar Hoikas]

COBBS is frightfully innaccurate, and anything found there should be discarded and burned in the deepest depths of hell. No disrespect intented, but the info is just wrong sometimes.

[Branan]

I'm sure they get it right occasionally...

Or not. Who knows, really?

[Paradox]

How can I say this...

The COBBS data is from the time when we were taking apart the PRP Objects by hand. That info is over 2 years old.

A prime example of inaccuracy is the plDrawableSpans code. COBBS has it all wrong, because it relies on a whole whack of other classes which were all compressed into one on COBBS.

Anyways,

I've successfully imported plViewFaceModifiers, but the aren't positioned properly because the matricies don't seem to affect it. So I'm waiting for Tahgtahv to finish documenting the class and then I'll see how things should look.

EDIT: No such luck :angry: I have a plane that is visible from one side, but it doesn't rotate. I'll have to wait for Tahgtahv to finish documenting it. <_<