Lemma Soft Forums

It's an issue of 6.14 not 6.15. A white tulip can't be used in other languages because it doesn't show another font.

It can be - it's just that you have to update multiple styles, rather than just style.default and style._default. For AWT, you have to update:

style.button_text
style.large_button_text
style.say_dialogue
style.say_label

In addition to the defaults.

jack_norton wrote:The message in italian means "can't find the specified file". But no clue which file refers to
However after restarting Renpy the version was the latest one (at least, checking for update didn't download anything).
Also probably just a small mistake, but if you click "about", says Renpy version 6.14.1.366

This shouldn't be possible, as the version number is just read out of Ren'Py. I don't like the error message - it looks like the update failed for you, and you have a franken-Ren'Py.

Ah I found out what happened: I downloaded 6.15 and when I click "update" it says that the PREVIOUS version is available, and if I update it downgrades it. Could be a mistake on the server-side ?

No, it looks like you might be on the "release" update channel. You need to switch that to the "prerelease" channel, in preferences.

Ah yes sorry, it's that

Is it possible to change the console text size? When I go high resolution and downsize, it shows up really small.

Also, the transform glitch still remains in 6.15. I can't do a transition without all transforms locking up.

Do you have a plan to rewrite README.html? I translated into Japanese and found it's outdated (no quick and GL menus). So I'm wondering I should do a direct translation or not.
BTW, I found a mistake: should be Alt-M.

SundownKid: You can restyle the console in your game. Check out 00console.rpy for the styles the console uses.

nyaatrap: I'll rewrite it at some point, but I'll fix the mistake soon.

Everyone - Since there haven't been any issues reported, I'll probably release 6.15 tomorrow sometime.

There likely won't be a RAPT release corresponding to 6.15.0. Updating RAPT has been taking a bit longer that I'd like, and I don't want to delay 6.15 for it. So I'll release, and then there will be a 6.15.1 with a RAPT corresponding to it.

Will you be able to fix the transform glitch? I recall you said it was fixed in this version, but it isn't.

From my investigation, at clauses in screens don't work when a new screen which is called by ui.callsinnewcontext is hidden with config.exit_transition or similar functions. To work them again, I need to use a statement which redraw the game, like say, pause and another with statement.
For example, solves this problem in the game_menu. I'm using this codes in my game, though it's nice to be fixed.

I'll note that - since these are issues present in older versions of Ren'Py - I'm probably not going to hold up 6.15 for them. Instead, I'll fix them in 6.15.1.

A curiosity: Avast! is now treating Ren'Py launcher as a "suspect program". I have added it to the exceptions of that program so it stops running inside a sandbox, but Avast! would still "suspect" of any game I build (of course I have build only for testing purposes!). Anything to do with this being a prerelease version?

Donmai wrote:A curiosity: Avast! is now treating Ren'Py launcher as a "suspect program". I have added it to the exceptions of that program so it stops running inside a sandbox, but Avast! would still "suspect" of any game I build (of course I have build only for testing purposes!). Anything to do with this being a prerelease version?

I get this problem when I work on Ren'Py stuff on my work laptop at lunchtime; I believe it's mostly because one of the metrics Avast uses to determine whether something is potentially a threat is how many Avast users run this particular application. So something like Notepad or Excel will never be flagged because a high proportion of users run them... things like Ren'Py are minority-interest, Avast has only seen a couple of people running them so it thinks they're suspicious. Particularly with a pre-release where even fewer people run it.

We also have the same problem with an in-house tool we maintain; every revision we make to the software, Avast complains about it and we have to add it to the whitelist again. I guess it's doing a hash of the executable or something which allows it to determine between different programs with the same name, so:
a) it may be that you added previous versions of Ren'Py to your whitelist before and just forgot, but now Avast doesn't recognise the new release as the same program you whitelisted
b) you may find that when 6.15 is officially released and more people start running it, Avast recognises it as being run by more people and thus less likely to be dangerous.





(Personally I'm suspicious that "how many people run this software" isn't a particularly good measure of how likely it is to be malicious. As it goes, I run NOD32 at home and I don't recall it ever flagging Ren'Py as malicious.)

Personally I'm suspicious that "how many people run this software" isn't a particularly good measure of how likely it is to be malicious.

"Wow, everybody's running MaliciousSpyWormHD3JF4L92 that's gotta be a legit program."