Ren'Py 6.13.8 Released

[PyTom]

I've released Ren'Py 6.13.8. This release focuses on improving compatibility - especially with bad graphics cards - and bug fixing. It fixes both minor bugs, and contains low-risk improvements to the design of features. (For example, it includes significantly more useful new-style side image support, and a callback that is run after each python block.) A 6.13.9 will be following shortly, improving Android support.

Testers report that this release works with hardware that failed in 6.13.7, so I recommend everyone consider upgrading.

This release can be downloaded from:

http://www.renpy.org/release/6.13

or by hitting shift+U in a 6.13 version of Ren'Py, before 6.13.9 testing begins. Updated documentation can be found at:

http://www.renpy.org/doc/html/

Please pay special attention to the incompatible change listed at:

http://www.renpy.org/doc/html/incompatible.html

A full list of changes is:

Side images can now be limited to showing a single character, or only showing
characters that are not on the screen. See config.side_image_tag and
config.side_image_only_not_showing.

Added config.python_callbacks, a list of python functions that are
called at the end of each python block.

Ren'Py now tests the video card it is running on for functionality. If it
can't draw textured rectangles to the screen, it will proceed to a different
renderer.

Old-style string interpolation is now enabled by default, alongside new-style
string interpolation.

Ren'Py is now compatible with libpng 1.5. Thanks to James Broadhead for the
patch.

Fixed the following bugs:

* A crash when dealing with certain invalid fonts.
* Pausing too long when typing out text.
* Cutting one pixel off a block of text when fractional kerning was used.
* Crashing when the time was set in the far future or past.
* Immediately exiting when rolling forward at the quit prompt.
* Crashing when a non-existing directory is added to the search path. (This
prevented Katawa Shoujo from starting in the latest version.)
* Save-file size was overly large due to screens being included in save files.

[cosmo]

Hello!
I am sorry to report the following bug to 6.13.8:

Launching a game with ren'py leads to a total freeze of the window under my Linux version. The window just goes black. No interaction with keys are possible (like: leaving the fullscreen mode). The window can't be closed and the CPU usage is extremely high.

All I could do was to switch to tty to kill the python.real process. I needed a root KILL command to do it.

I tried it so far only with two scripts. My own current WIP and the Adrift game. Both work fine while launching them with 6.13.7

log.txt is attached.

Thank you for your work once again!

[jack_norton]

I had this strange crash:

Code: Select all

I'm sorry, but an uncaught exception occurred.

While running game code:
  File "game/plot/chapter1.rpy", line 276, in script
        show i_loren confused at scale(.61),cenright with move
Exception: Parameter 'new_widget' is not known by ATL Transform.

it appears that the "with move" isn't supported anymore ? if I replace it with dissolve, works just fine.

[PyTom]

Do you have a transform named move somewhere? Transforms share the same namespace as transitions and variables.

[jack_norton]

Ahh I see! yes I have a transform called move indeed, thanks!

[GJsoft]

*CONTENT DELETED*

[PyTom]

I will look into this.

[CheeryMoya]

This was bugging me for some while already, but since a few versions ago, renpy and renpy games had weird behavior when starting a game and then clicking on the window while it's not fully started. The screen suddenly reduces its size to probably one pixel and then you need to fix it by stretching the borders. May not be a big problem, but it may be off-putting for the end-user.
(I'm using win7, not sure if the same behavior can be noticed on other versions, too.)

--GJ

I've had this same problem before as well on my Windows XP. I always thought that it was just my computer, but seeing as to how it's happened to at least one other person, I guess not.

[Viatrix]

It seems as though the 6.13.8 release has caused my projects to crash before the game ever runs, with a Visual C++ Runtime error saying the program requested the runtime to terminate it in an unusual way. This happens not only with my projects, the tutorial game does this as well. I have tested older versions, and everything up till 6.12.2 works just fine and I'm pretty sure I was able to use 6.13.7 without any problems too. I'm running Windows XP Media Center SP3 if you were wondering, and I have the newest possible redistribution of Visual C++ installed and updated. I've been searching for a while now, but I can't seem to find anything related to the issue I'm having. Any help would be greatly appreciated.

[Endorphin]

// warning: random stuff follows here

You know, I nearly switched to Novelty today as it looked really promising with the blur shader and stuff.
And then I got annoyed because there just lacked some features I already took for granted because of Ren'Py and so I decided to script something to relieve this stress.
Looking at the engine then I just noticed that Ren'Py probably is the only VN maker that can truly meet my demands.

So I just wanted to say "thank you" again. =)

Only thing I really miss now is the possibility to change hue etc. (all the graphic manipulators) dynamically ingame, but I'll wait patiently for Ren'Py 6.15 which you said would include this.
This will be such a happy day... ;_;

- R.

[cosmo]

Hello!
I am sorry to report the following bug to 6.13.8:

The crash does no longer occur with the current version 6.13.9!