Ren'Py 6.99.14.2 Released

[PyTom]

I've released Ren'Py 6.99.14.2, a release that adds support for the Atom text editor to Ren'Py. Atom is a modern and approachable editor with support for a number of features, like code folding.

To try Atom, please go to the Ren'Py preferences, and select Atom as your text editor. The normal Ren'Py text editing features will then use Atom. Further customization can be done inside Atom itself, including switching between dark and light themes.

This release also includes a few new features, and a number of important fixes, so everyone should upgrade.

Special thanks to William Tumeo for the initial creation of the language-renpy Atom plugin, and then for transferring it to the Ren'Py project.

Downloads of 6.99.14.2 can be found at:

https://www.renpy.org/release/6.99.14.2

A full list of changes to Ren'Py can be found at:

https://www.renpy.org/doc/html/changelog.html

A list of changes that may require you to update your game can be found at:

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

Please also check out the credits and sponsor list.


For the record, this is version 6.99.14.2.3333, a nice easy to remember build number. Thanks to everyone who tested this release, and everyone who creates using Ren'Py.

[NocturneLight]

There's a bug with this latest version. If you make a new game and pick 1920 x 1080 for it's resolution, then start the game and go into the preferences menu, the "Window" button will show as unselected even if your game is in window mode. This problem also occurs in previously made games.

This problem doesn't seem to occur with at least the 1280 x 720 option.

The "Fullscreen" button seems to somehow be unaffected by this problem.

The color change still seems to work when you hover over the "Window" button as well.

[Imperf3kt]

There's a bug with this latest version. If you make a new game and pick 1920 x 1080 for it's resolution, then start the game and go into the preferences menu, the "Window" button will show as unselected even if your game is in window mode. This problem also occurs in previously made games.

This problem doesn't seem to occur with at least the 1280 x 720 option.

The "Fullscreen" button seems to somehow be unaffected by this problem.

The color change still seems to work when you hover over the "Window" button as well.

From what I recall, that's been present for several versions. I'll try to find some logs I remember about it.

[mitoky]

There's a bug with this latest version. If you make a new game and pick 1920 x 1080 for it's resolution, then start the game and go into the preferences menu, the "Window" button will show as unselected even if your game is in window mode. This problem also occurs in previously made games.

This problem doesn't seem to occur with at least the 1280 x 720 option.

The "Fullscreen" button seems to somehow be unaffected by this problem.

The color change still seems to work when you hover over the "Window" button as well.

I had the same problem before. Instead of

Code: Select all

action Preference('display', 'window') 

use

Code: Select all

action Preference('display', 'any window')

That fixed it for me.

[jack_norton]

I'm afraid but there's still something messed up with variables
I was debugging my screen code with shift+R and all of a suddenly I got the infamous "NameError" crash.
The variable this time is "line" which I use to display the current game line when user press a key. This has been in my games since 2014 and never had a problem. The code is also very simple:

Code: Select all

default line = False

then in the say screen I use it like:

Code: Select all

screen say(who, what, side_image=None, two_window=False):
    key "K_F1" action ToggleVariable("line")
    if line:
        text ("%s %s" % renpy.get_filename_line()) xpos 2 ypos 2 color "#FFF"

there's really no reason why suddely when I roll back, I get a NameError: name 'line' is not defined. I don't know if happens only in debug mode, or something else. But I'm sure it happens after I edited the screen code for long time (using shift+R) and I rollback. That's all I managed to discover so far, this is a much more difficult bug to reproduce than the other

Also this happens on latest release and starting a new game from scratch: so not using an old save. Thanks

[NocturneLight]

There's a bug with this latest version. If you make a new game and pick 1920 x 1080 for it's resolution, then start the game and go into the preferences menu, the "Window" button will show as unselected even if your game is in window mode. This problem also occurs in previously made games.

This problem doesn't seem to occur with at least the 1280 x 720 option.

The "Fullscreen" button seems to somehow be unaffected by this problem.

The color change still seems to work when you hover over the "Window" button as well.

I had the same problem before. Instead of

Code: Select all

action Preference('display', 'window') 

use

Code: Select all

action Preference('display', 'any window')

That fixed it for me.

Oh. That actually did fix it. Thanks. I don't think I would've ever figured out that you could change "window" to "any window".

[jack_norton]

OK now it happens regularly! Another example, I get this crash if I hit shift+R while the screen ChangeRomanceVar is showing:

Code: Select all

I'm sorry, but an uncaught exception occurred.

While running game code:
  File "game/gameflow.rpy", line 16, in script call
    call opening_barcrawl from _call_opening_barcrawl2
  File "game/Gameplay.rpy", line 1515, in script call
    call ChangeRomance("nadia","witch")
  File "game/screens.rpy", line 42, in script
    label ChangeRomance(name,var):
Exception: Required parameter name has no value.

-- Full Traceback ------------------------------------------------------------

Full traceback:
  File "game/gameflow.rpy", line 16, in script call
    call opening_barcrawl from _call_opening_barcrawl2
  File "game/Gameplay.rpy", line 1515, in script call
    call ChangeRomance("nadia","witch")
  File "game/screens.rpy", line 42, in script
    label ChangeRomance(name,var):
  File "C:\- indie dev -\games\renpy\renpy\ast.py", line 803, in execute
    values = apply_arguments(self.parameters, renpy.store._args, renpy.store._kwargs)
  File "C:\- indie dev -\games\renpy\renpy\ast.py", line 152, in apply_arguments
    return parameters.apply(args, kwargs, ignore_errors)
  File "C:\- indie dev -\games\renpy\renpy\ast.py", line 120, in apply
    raise Exception("Required parameter %s has no value." % name)
Exception: Required parameter name has no value.

Windows-7-6.1.7601-SP1
Ren'Py 6.99.14.2.3333
Love Bites 0.7
Wed Mar 28 10:57:03 2018

problem is that name HAS a value the call stack is:
call ChangeRomance("nadia","witch")
label ChangeRomance(name,var):
call screen ChangeRomanceVar(name,var,"%s_%s_romance" % (name.lower(),var.lower()))
and screen is defined as:

Code: Select all

screen ChangeRomanceVar(name,var,i):
    modal True
    add Solid("#0009")
    timer 5.0 action (SetVariable("P%s" % i,evalFixed(i)),Hide("ChangeRomanceVar",transition=dissolve))
    frame background Frame("images/frame_small.png",100,110,tile=True) xsize 400 xpadding 35 ypadding 25 xcenter .5 ycenter .5 at tfade(.0):
        vbox xcenter .5 spacing 5:
            text [name] xcenter .5 style "tip2" size 28
            fixed xsize 100 ysize 100 xcenter .5 :
                add "gfx/%s.jpg" % var.lower()
                text "%s" % evalFixed("P%s" % i) xcenter .5 ycenter .5 style "big_numbers" size 45 at tfade2(.1,.5)
                text "%s" % evalFixed(i) xcenter .5 ycenter .5 style "big_numbers" size 45 at tfade2(1.2,2.5)
            text "%s Alignment" % var xcenter .5 style "tip2" size 22

I can always reproduce this loading a save just before that event, and pressing shift+R while the screen ChangeRomanceVar is showing.

[jack_norton]

And now I got a crash never seen before. Posting it here in case can give you a clue about the other variable bug:

Code: Select all

I'm sorry, but an uncaught exception occurred.

While running game code:
  File "game/gameflow.rpy", line 16, in script call
    call opening_barcrawl from _call_opening_barcrawl2
  File "game/Gameplay.rpy", line 1511, in script call
    menu:
  File "renpy/common/00start.rpy", line 94, in script
    python hide:
  File "renpy/common/00start.rpy", line 94, in <module>
    python hide:
  File "renpy/common/00start.rpy", line 97, in _execute_python_hide
    i()
  File "renpy/common/00console.rpy", line 600, in watch_after_load
    if config.developer and traced_expressions:
NameError: global name 'traced_expressions' is not defined

-- Full Traceback ------------------------------------------------------------

Full traceback:
  File "game/gameflow.rpy", line 16, in script call
    call opening_barcrawl from _call_opening_barcrawl2
  File "game/Gameplay.rpy", line 1511, in script call
    menu:
  File "renpy/common/00start.rpy", line 94, in script
    python hide:
  File "C:\- indie dev -\games\renpy\renpy\ast.py", line 862, in execute
    renpy.python.py_exec_bytecode(self.code.bytecode, self.hide, store=self.store)
  File "C:\- indie dev -\games\renpy\renpy\python.py", line 1839, in py_exec_bytecode
    exec bytecode in globals, locals
  File "renpy/common/00start.rpy", line 94, in <module>
    python hide:
  File "renpy/common/00start.rpy", line 97, in _execute_python_hide
    i()
  File "renpy/common/00console.rpy", line 600, in watch_after_load
    if config.developer and traced_expressions:
NameError: global name 'traced_expressions' is not defined

Windows-7-6.1.7601-SP1
Ren'Py 6.99.14.2.3333
Love Bites 0.7
Wed Mar 28 11:03:43 2018

[ISAWHIM]

Fullscreen on 4K, is still horribly choppy. Impossible to navigate and play. (Just trying to change settings back to "Windowed" is a nightmare.)
Windowed on 4K, is still fine. So the issue revolves around something to do with the "borderless window" state, AKA: Fullscreen.

I am getting the "store.quick_menu is being given a default a second time" error again, in rollbacks. It shows just after "STARTING" a new game. (Going past three dialogue-interactions and rolling back to the start-point, will throw the error. This is past the splash-screen and menu.)

It seems to be reloading "screens.rpy" again, for some reason. (That is where it is defined, once, and only once. The other place it is defined, is in the core-defaults function.)

[NocturneLight]

Was the text on the second row rightmost save slot not being highlighted with the same color as the other save slot texts already a known issue?

[ISAWHIM]

This issue may be present in other versions... Just noticed it now.

"Questions" asked by the "narrator" (menu text without a character ID), do not get recorded in "HISTORY".

Code: Select all

define Y = Character("You:")

menu:
    Y "I am you. Do you agree?"
    "YES":
        $answer = "YES"
    "NO":
        $answer = "NO"

menu:
    "I am the narrator. Do you agree?"
    "YES":
        $answer = "YES"
    "NO":
        $answer = "NO"

The history will show as...

Code: Select all

You: "I am you. Do you agree?"

          NO

          YES

Expected results, similar to the narrator speaking...

Code: Select all

You: "I am you. Do you agree?"

          NO

     "I am the narrator. Do you agree?"

          YES