Guild of Writers

The GoW PyPRP Team is proud to release PyPRP 1.4.0 Release Candidate 1. Since this version is marked as a "release candidate," it is fairly stable; however, you may encounter some bugs. Please report any and all bugs you encounter. The next release should be the final version of 1.4.0 barring serious issues.

New Features in PyPRP 1.4

- Dynamic Environment Maps
- Wavesets
- Sitting Modifiers
- Dynamic Foot Decals (Footprints)
- Object Cast Shadows
- Dynamic Ripple Decals
- Billions of Bugs Squashed (Well, you get the idea)

Download Link: http://www.guildofwriters.com/pyprp/gow ... .0-rc1.zip

As a note to people who actively use the subversion to receive updates: PyPRP 1.4 has been tagged in the repoistory. The trunk will now be used for a rather large overhaul to make PyPRP a bit more "Plasma Friendly." So: BEWARE if you use the trunk. It's liable to become... Unstable... In the near future.

Magic, thanks guys.

Way cool! *thumbsup*
(too bad I don't know how to use half of those features yet )

Aloys wrote:Way cool! *thumbsup*
(too bad I don't know how to use half of those features yet )

I don't either
I just heard a lot of debate about flags and watched code appear in the SVN. I was doing span fixes.

Nadnerb said that a tutorial should be up by now, or within a day or so.

Paradox wrote:I don't either

That's ok, as long as I'm busy with AP I won't have the time to try the new features anyway.

So still going with, what it seems to me as, an arbitrary release number.

It great to have a new downloadable version

Any particular reason why you guys aren't using the SVN number as the postfix to the zip file?
Makes it hard to know otherwise how old it is from whats is in SVN

Grogyan wrote:So still going with, what it seems to me as, an arbitrary release number.

It great to have a new downloadable version

Any particular reason why you guys aren't using the SVN number as the postfix to the zip file?
Makes it hard to know otherwise how old it is from whats is in SVN

The version number scheme that I have been trying to use is quite easy to understand. Although, I do imagine that there are some discrepancies in releases that haven't been by me.

MAJOR . MINOR .BUGFIX

Major = Major Number, changed when massive changes to code are made.
Minor = New features added
Bugfix = Bugs are fixed. NO NEW FEATURES EVER!!!!!

I always prefer to release an "RC" before the final version (this release was an RC).

As to the SVN, if you're not interesting ino reading the SVN logs and figuring it out for yourself (which isn't hard at all... I use log messages and tag releases), then I am most certainly not interested in helping you; however, if you HAVE read the SVN log and still can't figure it out, then you have a legitimate to ask. Also, if you took time to learn a bit about SVN, then you would know that release tags are RARELY committed to, and are safe to use.

And thus ends this moment's rant. Please stay turned for more ranting. <Rainbow TV Screen: Beeeeeeeeeeeeeep>

I do read the SVN logs, its a good read.

Its just that when I am reading the logs, i'm just curious as to whats new since the previous release.

I can see now how your version numbering works, thats for that


Sorry, but i'm not an expert on SVN, i'm still going through what all the little icons mean (in the logs)

Just went through the SVN log again tonight and I see the tags now of previous releases

Since things seem to be going fast in development, how about consolidating 1.4.0 and make it a final which includes the restored footprint defaults?

Revision: 202
Author: Nadnerb
Date: 00:46:22, Monday, May 26, 2008
Message:
Restored footmgr defaults. Merged with trunk
----
Modified : /tags/1.4/src/alc_AnimClasses.py
Modified : /trunk/src/alc_AnimClasses.py