GoW PyPRP 1.6.0 Beta 2 released

[Robert The Rebuilder]

Christian: perhaps you should highlight in your initial post that the installation method is different; it can be the first bullet on the "what's new" summary portion of your post.

I mention this not only because of Jamey's confusion but of my own as well. Luckily, after experiencing similar errors in the release, I decided to RTFM and solved the problem. So, when you announce the final release of 1.6, make it bold, underlined and super-sized text that the installation procedure has changed.

[Christian Walther]

Good idea. I've edited the first post accordingly.

[Kato]

Yeah, I can confirm that 1.6 won't complete a checkout because of that error.

-Kato

[boblishman]

I don't know if this is intentional, but my guess is that it may cause confusion for some users ...

when opening the latest zip download (from the first post) you get three "warning" messages from winzip.

winzip.jpg (193.71 KiB) Viewed 3497 times

is this intentional (or even necessary) ?

[Christian Walther]

Yeah, I can confirm that 1.6 won't complete a checkout because of that error.

Wait - you're talking about the error from Subversion because of the question marks in file names, right? Problems with a checkout would be a new thing (assuming you're checking out HEAD, not one of the troublesome revisions itself), all we had were problems with an update. Can you elaborate?

I don't know if this is intentional, but my guess is that it may cause confusion for some users ...

It's neither intentional nor necessary, and has indeed already been fixed (though no fixed release is available yet). Thanks for the report anyway! For now you can ignore these files, I'm not sure what they are used for anyway. The pages looked fine for me when I checked them on Windows - I unzipped the archive using Windows Explorer, and it just skipped the problematic files without even a warning.

[dendwaler]

Hi all, i have tried PYPRP16 in the age I am building ( Turtle Isle) and noticed the following:

If you use the "Mirror" modifier on an object the mirror is applied sucessfully , but the bounds settings for the triangle mesh is not applied on the mirrored part.
In my case i have on one object both, a mirror and an array from the mirrored object.
Only the basic object is solid, the mirror and the array not.
Pity, because i can't use PYprp16 any longer because i have lots of mirrored shapes.

[Paradox]

The collider should not be mirrored as far as I know. You need to set the collision settings for each of the copies of the object

[Christian Walther]

If you use the "Mirror" modifier on an object the mirror is applied sucessfully , but the bounds settings for the triangle mesh is not applied on the mirrored part.

Ah, good point. Obviously, we should also use the modified mesh when generating the bounds. I'll try to get a fix in for this tomorrow.

Pity, because i can't use PYprp16 any longer because i have lots of mirrored shapes.

You can just do as before and apply the modifiers before exporting.

[dendwaler]

Yes of course, you are right,
I can still apply it first.
I really like this new feature, because i always work with unapplied models.
Its easier when you want to change something, but when the age grows it can be lot of work to apply everything before exporting.
Also you get a big list of applied and unapplied versions.

In this screenshot of a little part of my age, i have an example of a mirrored and arrayed object.
The pipe i am standing on, actually is only a small segment and on one side only, extruded cylinder.

[Christian Walther]

OK, this is now fixed in http://svn.guildofwriters.com/pyprp/branches/1.6/PyPRP/prp_ObjClasses.py (you can download this and substitute it for the existing file of that name if you want to try it). Thanks for the report!

While testing this, I found some unrelated issues with bounds export - sphere bounds cause an error (some things look half-implemented there), and something seems to be wrong with the transform of box bounds. Will investigate.

Once that is done, it might be a good time to package up beta 2 with the fixes we have so far.