Ren'Py 6.13 Pre-Releases

[jack_norton]

This is really nit-picking! But... the traceback is not very accurate. For example in the code:

Code: Select all

screen topmenu:
    frame style "topmenu" at move(.9,-.25,.9,0.2,2):
        xalign 0.95 yalign 0.0 yminimum 64
        vbox ycenter .5 xcenter .5:
            textbutton "Status" action ui.callsinnewcontext("status") style "default"

I defined a non-existing label "status", and when I clicked on it, I got the obscure error below:

Code: Select all

I'm sorry, but an uncaught exception occurred.

While running game code:
  File "game/mainscript.rpy", line 272, in script
        "Clicking on the Status Icon on the screen top-right you access the Status Screen."
AttributeError: 'Context' object has no attribute 'next_node'

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

Full traceback:
  File "C:\download\renpy-6.13.0\renpy\bootstrap.py", line 276, in bootstrap
  File "C:\download\renpy-6.13.0\renpy\main.py", line 354, in main
  File "C:\download\renpy-6.13.0\renpy\main.py", line 95, in run
  File "C:\download\renpy-6.13.0\renpy\execution.py", line 269, in run
  File "C:\download\renpy-6.13.0\renpy\display\error.py", line 83, in report_exception
AttributeError: 'Context' object has no attribute 'next_node'

Windows-post2008Server-6.1.7601-SP1
Ren'Py 6.13.0.1598

since Heileen3 is very simple coding-wise was able to find the bug easily but maybe would be better a more accurate traceback ? just a suggestion of course.

[PyTom]

Spent the day working on Android - managed to get a big increase in startup time, and a big decrease in disk space usage. So that was a win-win.

I'll be out of town for the next few days, so there probably won't be another pre-release until Sunday - and that might be the last one, since the few remaining issues seem small.

Jack, that looks like a bug in the error handling code (especially the ignore code). I'll take a look at it when I get back.

[PyTom]

I posed 6.0.13.1603 to the website.

This version includes support for reading files out of an Android package, which should make initial startup much faster on Android. It will also half the disk space used by game assets.

It improves the user-defined statement support so that the statements can now take blocks. (It's still undocumented, though.)

Finally, there are a couple of bugfixes, including the one above.

My feeling is that 6.13 is very close to done - if you're having problems with the newest release, let me know immediately.

Thanks again to everyone who's helped with this release process.

[Aleema]

I've been battling a bad crash for a day now, even with the new update. It only happened when I tried to enter into the game menu (right-click or ESC), and while troubleshooting I overwrote the screens.rpy with the template one and it started crashing on launch, too. So I was scratching my head, BUT, overwriting the options.rpy completely fixed the problem so the corruption was in there. I started commenting out things, and the troublesome line of code was:

Code: Select all

layout.scrolling_load_save()

I asked Jack Norton to see if the game crashed for him, but it didn't. This layout apparently crashed specifically because of my computer, which is a year old. I've attached my log thingy. Oh, and the crash happened no matter what graphics render I selected. (I sometimes got a visual c++ "runtime error" before crashing.)

But anyway, with that line gone it seems to be working fine for me, but the load/save menu will need ... reworking.

[jack_norton]

Ahh so it's the scrolling load/save layout the problem! Here when I hit ESC the first time to go in the load/save menu, the game pauses for a few seconds, like if is doing some calculation/big texture loading, but works.
I think might be something related to that - like if tries to load a huge amount of data - before it wasn't pausing so much before entering the screen, was loading it quickly.

[PyTom]

Is the scrolling load/save crash occuring with both DX and GL, or just one of the two?

[Aleema]

Both. I tried all the options in the graphics selection screen with same results. Sorry. =\

[PyTom]

No - that's good to know, as it eliminates a bunch of things that could possibly be going wrong.

[Quilford]

Um.

Immediately after launching 6.13.0.1603, I get a typical "An exception has occurred." error, with the following traceback:

Code: Select all

I'm sorry, but an uncaught exception occurred.

While running game code:
  File "launcher/script.rpy", line 17, in script
        python:
  File "launcher/script.rpy", line 116, in python
            interact()
  File "launcher/interface.rpy", line 106, in python
            return ui.interact(suppress_overlay=True, suppress_underlay=True)
KeyError: 'test'

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

Full traceback:
  File "C:\Users\Jack\renpy-6.13.0\renpy\execution.py", line 261, in run
  File "C:\Users\Jack\renpy-6.13.0\renpy\ast.py", line 630, in execute
  File "C:\Users\Jack\renpy-6.13.0\renpy\python.py", line 977, in py_exec_bytecode
  File "launcher/script.rpy", line 116, in <module>
  File "launcher/interface.rpy", line 106, in interact
  File "C:\Users\Jack\renpy-6.13.0\renpy\ui.py", line 237, in interact
  File "C:\Users\Jack\renpy-6.13.0\renpy\display\core.py", line 1788, in interact
  File "C:\Users\Jack\renpy-6.13.0\renpy\display\core.py", line 2026, in interact_core
  File "C:\Users\Jack\renpy-6.13.0\renpy\display\core.py", line 246, in visit_all
  File "C:\Users\Jack\renpy-6.13.0\renpy\display\core.py", line 246, in visit_all
  File "C:\Users\Jack\renpy-6.13.0\renpy\display\core.py", line 246, in visit_all
  File "C:\Users\Jack\renpy-6.13.0\renpy\display\core.py", line 246, in visit_all
  File "C:\Users\Jack\renpy-6.13.0\renpy\display\core.py", line 246, in visit_all
  File "C:\Users\Jack\renpy-6.13.0\renpy\display\core.py", line 246, in visit_all
  File "C:\Users\Jack\renpy-6.13.0\renpy\display\core.py", line 246, in visit_all
  File "C:\Users\Jack\renpy-6.13.0\renpy\display\core.py", line 243, in visit_all
  File "C:\Users\Jack\renpy-6.13.0\renpy\text\text.py", line 1149, in visit
  File "C:\Users\Jack\renpy-6.13.0\renpy\text\text.py", line 1093, in update
  File "C:\Users\Jack\renpy-6.13.0\renpy\substitutions.py", line 218, in substitute
  File "string.pyo", line 549, in vformat
  File "string.pyo", line 571, in _vformat
  File "string.pyo", line 632, in get_field
  File "string.pyo", line 591, in get_value
KeyError: 'test'

Windows-post2008Server-6.1.7601-SP1
Ren'Py 6.13.0.1603

Sorry if this has already been reported/people are bugging you about it.

[PyTom]

Quilford, do you have code like:

"[test]"

anywhere? That's acquired a new meaning in 6.13.

[Quilford]

Um. Yes.

>__>

I fail at reading sometimes.


Also can I now assign slow_cps to a variable? :p

[mugenjohncel]

I still experience clipping on screen based imagemaps. In fullscreen the problem is only limited to the lower part but once you switched to windowed this happens...

Clipping on lower and right side part though the buttons still work... Same working code from 6.12, nothing to fancy, just standard screen based imagemap... only happens in 6.13 and the problem can be recreated by simply switching to windowed mode...

"POOF" (Disappears)

[DaFool]

Ren'Py 6.13 has been reported to be incompatible with many users's systems.
Please download and use 6.12.2 until we can fix these problems.

We're going to be releasing ADRIFT with 6.13, given that I have an onboard Intel graphics card and was the first to report the videocard incompatibility with angle problem, as well as manifestations of clipping. Since then the game is working flawlessly.

It's also too late to revert since all are variables are using [] and we're using the latest screen-based image galleries and menu systems.

[PyTom]

Please wait for 6.13.1. 6.13 has too many problems with too many systems - I'm trying to get 6.13.1 out ASAP.

[jack_norton]

I have an user in my forums with a really weird bug:

The text doesn't wrap properly. It goes past the box and the result is words cut off. I have to guess what the last letters are.

his system specs:

Win XP SP3 32-bit.

Acer Desktop Computer.

See http://home.comcast.net/~nekohibiki/text.png

it's Spirited Heart Girl's Love which was built using 6.12 so maybe the bug was fixed on 6.13. To be honest I've never seen this bug before and don't know how that user can have that
(To me seems almost if the resolution on the screen is too small, but I think that any PC in the last 10 years can display 1024x768!!)