GoW PyPRP 1.6.0 Beta 2 released

[Christian Walther]

The GoW PyPRP Blender plugin version 1.6 is on its way and the second beta release is now available here: gow-pyprp-1.6.0b2.zip

PyPRP 1.6 installs differently than previous versions of PyPRP. READ the install section on the wiki.

Read about what's new since PyPRP 1.5 (including adjustments you may need to make in Blender) and how to install on the GoW wiki. Highlights include:

• Simplified installation - no more fiddling with a heap of loose files, just put the whole PyPRP folder into your scripts folder
• The modified mesh is exported for objects that have modifiers
• Texture scale can now be animated, and texture animation (or static offset/scale) matches the render preview in Blender
• Added support for simple GUI dialogs
• Many QuickScript additions
• Many bug fixes

Issues fixed since beta 1:

• File names containing question marks that freak out Windows
• Python error when exporting ripples/puddles/footsteps after running the Wizards script
• For objects with modifiers and bounds, modifiers were not applied to the bounds

It would be appreciated if some of you could run your ages through it and let us know if you run into any problems. Unless any issues turn up that take more time to fix (or any real life interferences or other unforeseen circumstances), the final release is planned for the weekend of September 12 (one week from now).

[Whilyam]

Just took a quick look at this and had a small suggestion:

I don't normally keep my .wav/.ogg files in the same folder level as my .blend file. Usually I have a folder like sfx under it where i pull the sound files from. Since the article doesn't say so, does anyone know if GoWPRP looks in the folder under the blend file for the sounds and, if not, could it be made to do so?

Thanks
Whilyam

[Christian Walther]

From looking at the code, that should be no problem. You have a number of options (checked in this order):

• If the sound is added to the Blender file as a sound object (which, if I understand correctly, was required up to PyPRP 1.5), you can refer to it by name or by name minus .wav extension.
• Use the full path to the sound file minus .wav or .ogg extension, either as an absolute path (not recommended), or relative to the folder that contains the Blender file by starting the path with // as usual in Blender.
• Use the name of a sound file minus .wav or .ogg extension in Blender's Sounds directory (set in the Preferences window).
• Use the name of a sound file minus .wav or .ogg extension next to the Blender file.

I haven't actually tried this, so correct me if I got something wrong. (Robert?)

So, in your case, you should be able to leave your existing sounds unmodified, and for new ones use something like

Code: Select all

MySoundEmitter:
    sound:
        file: //sfx/mysound

[Whilyam]

Okay! sounds good.

[D'Lanor]

Christian, can you remove that wiki stuff from the svn? Tortoise for Windows 1.6.4 chokes on it.

svn_error.png (39.55 KiB) Viewed 4388 times

[teedyo]

Looks like Tortoise doesn't like the space in "Wiki Excerpt"?

[Christian Walther]

No, that's just Tortoise line-breaking the error message it gets from SVN. The problem is that Windows doesn't like file names containing question marks. (I wonder what it did when I tested unzipping the release, since that seemed to work and the pages looked OK.)

Should be fixed now, thanks!

[D'Lanor]

/branches/1.6 is ok now but there are still files with question marks in /tags/1.6.0b1

[Christian Walther]

Yes. Is that a problem? Do you really need to check out the whole tree including all tags? The point of a tag is to preserve the state that was tagged, so I'm not going to modify it. I could delete it altogether, if I have to.

[D'Lanor]

Yes, it is a problem. Tortoise still chokes and stops. And of course I want to check out the whole tree.

Edit: actually I cannot get the corrected 1.6 branch either because Tortoise just stops. I can see in the log that you corrected it but it won't download.