Ren'Py 6.9.2 Released

[PyTom]

I've released Ren'Py 6.9.2 "Roadside Attraction". This release focuses on fixing bugs that have been found in 6.9.1. The largest bug fixed was one that made Ren'Py not run when sound playback was enabled on a computer with Data Execution Protection enabled, as it is in 64-bit Windows Vista. There was also a change to the play and queue statements to make them match the documented semantics. Please see the changelog for a list of other bugs that have been fixed.

Downloads of 6.9.2 and a full release announcement can be found at:

http://www.renpy.org/wiki/renpy/releases/6.9.2

Since this release is a bugfix-only release, I'm going to release it without the usual pre-release rigamarole. I'm also going to systematize Ren'Py's version numbering from here on out:

- The first digit is the "marketing version". It will be incremented when a collection of improvements is such that Ren'Py programming is greatly improved.
- The second digit is the "feature version". It will go up whenever new features are added, especially if those features may affect the core of Ren'Py.
- The third digit is the "bugfix version". If will go up when bugfixes occur. The only new features in a bugfix release will be minor features that do not affect the core.

The idea is that 6.9.2 will be strictly better than 6.9.1. Ideally, 6.10.0 will be better than 6.9.2, but it's possible that new features may create new bugs. Hopefully not.

[Adorya]

What about the letters (a,b,c...)...are they hotifx?

[PyTom]

Letters are now only for pre-releases. Anything that requires more than a file patch will trigger the bugfix version to increment.

[Satoh]

So this means the {w=#} thing coupled with ctc_pause is fixed now right?

EDIT: downloaded the new one... I still have the ctc_pause/{w=#} error...

[PyTom]

It should be fixed, yes. Not sure what code was failing for you, since it works for me.

[usul]

Does the movein/moveout work with a ConditionSwitch image now?

[PyTom]

Hm... not sure. That wasn't in the bug tracker, so I'm not sure if I remembered to address it.

[Satoh]

I did some much, much more sophisticated tests...

I discovered the ctc_pause/wait tag issue has another factor... anim.Filmstrip.

That is my exact character setup,

Code: Select all

    $ n = NVLCharacter(None, ctc=anim.Filmstrip("arc/icon/cursor0.png", (24, 24), (3, 1), .20), ctc_pause=anim.Filmstrip("arc/icon/cursor0.png", (24, 24), (3, 1), .20))

and when coupled with this text...

Code: Select all

"\n\nWith a loud BANG and a sickening thud,{w=.5} the vampire finally collapsed."

I get a full click-to-continue wait tag effect, rather than a wait .5 seconds wait tag effect.

I'm sorry I didn't realize the connection the first time, but without the anim.Filmstrip in the setup, I don't get the error...

My guess is the .20 in the 'delay' property for the filmstrip timing...

If you still fail to produce the error I can send my entire folder (sans the 150mb+ images)

[PyTom]

I'm using the code:

Code: Select all

init python:
    eomega = NVLCharacter("Eileen",
                       ctc=anim.Filmstrip("sakura.png", (20, 20), (2, 1), .30),
                       ctc_pause=anim.Filmstrip("sakura.png", (20, 20), (2, 1), .30))

label start:
    eomega "This is a {w=2}test."

And it's working for me. This is using the assets from the demo game.

[Satoh]

ugh... well... I tried using 2, like you did, for my wait tag... 2 should mean two seconds, correct? Well... it works with 2, except that it works like .5 seconds...

I am thoroughly confused by this whole ordeal, but since no one else seems to be having the issue....I suppose I'll just continue to work around it...

EDIT: Even no it was set for .2 by accident... but that created one more test for me... apparently the interval of the filmstrip delay, must be larger than the amount of time wait uses for the wait tag to work...

This is obviously not a program breaking so I don't want to go overboard... though I do find it fascinating...

[PyTom]

EDIT: Even no it was set for .2 by accident... but that created one more test for me... apparently the interval of the filmstrip delay, must be larger than the amount of time wait uses for the wait tag to work...

This is obviously not a program breaking so I don't want to go overboard... though I do find it fascinating...

I'm a little confused. I have the filmstrip delay at .3, and it's working with {w=.1}, {w=.3}, and {w=5}.

[Satoh]

I don't get it either... if I did I'd most likely have fixed it myself XD;

I've concluded Ren'Py just doesn't like me much... ahh... unrequited love is painful. Maybe I should try a whip...

[georgmay]

PyTom,
how we (easy mortals) can upgrade old version of Ren'Py?
I didn't want download new version with 70% similar files.
Laziness will control the world =)
Please.... =)

sorry for my bad english...

[Satoh]

I don't get it either... if I did I'd most likely have fixed it myself XD;

I've concluded Ren'Py just doesn't like me much... ahh... unrequited love is painful. Maybe I should try a whip...

BAH!! DUMBASS, ME!! Somehow I managed to run 6.9.1 and thought I was running 6.9.2...

*sigh* the ctc things IS fixed... I don't know HOW I managed to screw that up so hard...

[AlphaProspector]

I don't get it either... if I did I'd most likely have fixed it myself XD;

I've concluded Ren'Py just doesn't like me much... ahh... unrequited love is painful. Maybe I should try a whip...

BAH!! DUMBASS, ME!! Somehow I managed to run 6.9.1 and thought I was running 6.9.2...

*sigh* the ctc things IS fixed... I don't know HOW I managed to screw that up so hard...

I wouldn't worry so much, considering I downloaded an xml file instead of the py file that fixed the transitions... All because I thought it was a direct download link, heh.

So, I'm upgrading to 6.9.2. The same tricks to run Scite still apply to this version, right?