Ren'Py 6.14 Released

[PyTom]

Juny - are you saving the file as UTF-8, or in some national encoding?

[Juny]

I used Jedit while working with 6.13 and never picked any enconding myself. Switched to Editra for 6.14.1 and again, simply clicked File -> Save.
I just tried going back to Jedit and it does in fact send an error about wrong encodings (Editra instead doesn't). Should I try make new .rpy files and copy over the text in case something went wrong when switching editors?

[Jake]

I just tried going back to Jedit and it does in fact send an error about wrong encodings (Editra instead doesn't). Should I try make new .rpy files and copy over the text in case something went wrong when switching editors?

I had a few different encodings (and combinations of newline characters) from JEdit over the years, I think largely depending on the computer I was using it on.

One thing you may find useful would be to go into Editra and open the 'Edit' menu, choose 'Preferences', then with 'General' clicked at the top choose the 'Files' tab just below that. Just next to 'Preferred Encoding', drop the list down and choose 'utf_8'.

For some reason when I first downloaded 6.14 and installed Editra, it was defaulting to one of the cpXXXX choices near the top of that list (I guess probably it was whatever the default Windows codepage is for the US or the UK, since I'm running on English-language Windows with UK regional settings?) and it kept complaining when I opened files that the file encoding was 'wrong'.

[Juny]

One thing you may find useful would be to go into Editra and open the 'Edit' menu, choose 'Preferences', then with 'General' clicked at the top choose the 'Files' tab just below that. Just next to 'Preferred Encoding', drop the list down and choose 'utf_8'.

For some reason when I first downloaded 6.14 and installed Editra, it was defaulting to one of the cpXXXX choices near the top of that list (I guess probably it was whatever the default Windows codepage is for the US or the UK, since I'm running on English-language Windows with UK regional settings?) and it kept complaining when I opened files that the file encoding was 'wrong'.

I tried that, now it keeps asking me to choose an encoding when opening the files, and no matter how many times I choose 'utf_8' it still keep asking without opening them (it went on for over 30 times before I gave up).
I went back to jEdit and after saving everything forcing the 'utf_8' encoding now everything works. I guess I'll stick around with it and forget Editra for the time being.

Thank you very much for all the help!

[Jake]

I tried that, now it keeps asking me to choose an encoding when opening the files, and no matter how many times I choose 'utf_8' it still keep asking without opening them (it went on for over 30 times before I gave up).

For what it's worth: this suggests that your files were previously saved in some peculiar encoding which can't be interpreted as UTF8. Now you've saved them all as UTF8, you should find that Editra opens them fine without any complaints. (And if it doesn't, that is a bug. Either with Editra or JEdit's UTF8-saving.)

Of course, if you're happy with JEdit and don't particularly want any of the features in Editra, then there's really no reason to use anything but JEdit!

[nyaatrap]

I tried that, now it keeps asking me to choose an encoding when opening the files, and no matter how many times I choose 'utf_8' it still keep asking without opening them (it went on for over 30 times before I gave up).

Yes it occurs for me too. I always set default encodings of all editors I downloaded as UTF-8 before using them, so I thought It shoudn't occur, but not. It was pain to reset all encoding one by one

[hugolino]

Thanks for the update. I just downloaded it and I like what little I've seen of the changes thus far.

[WispoWill]

I'm having the exact same problem as Blane Doyle. I cannot get Editra to launch from within RenPy. A crash box comes up for about 3 seconds (barely enough time to mentally register that it's there and to read the message) then disappears again. From this point on Editra remains locked in memory and needs to be killed via Task Manager. This problem occurs whether I install the download package from the RenPy site or use the new launcher to install. I deleted the Renpy folder altogether and redownloaded the package altogether and it still does the same thing. I was finally fast enough to hit the bug report button and the message it tries to send is complaining that one of the toolbar BMP is invalid.

I'm running Windows XP SP3 on a laptop.

Also, with the new launcher... Although it looks nice visually, it was just a bit easier for me to work with when the Launch Project could be chosen from the left side of the screen. My laptop screen isn't but so large and usually my windows are overlapping. The Jedit now covers the two options I use most during a debugging run, requiring extra clicks.

I know that this is a very minor matter, and probably only affects those of us with small screens, but that is my actual first thought about the new launcher.

[Bombermans]

I also have Blane Doyle and WispoWill problem. Back in 6.14.0 I couldn't download editra from the launcher. Now in 6.14.1 it's fixed, but editra keeps not working, showing the error during 3 seconds, then closing and staying in memory. I also use Windows XP.

[Blane Doyle]

I also have Blane Doyle and WispoWill problem. Back in 6.14.0 I couldn't download editra from the launcher. Now in 6.14.1 it's fixed, but editra keeps not working, showing the error during 3 seconds, then closing and staying in memory. I also use Windows XP.

If you have Service Pack 3 it might just be our Operating Systems then. So glad I am buying a laptop.

[Code Monkey]

The new version of 6.14 is great! The bugs I reported before are fixed ^_^

Except now I get one issue.... When trying to archive and build T_T

Has anyone else gotten this? Not even sure where to debug, only shows Renpy source in traceback.

[PyTom]

Is there a chance that you're running out of memory, by trying to pack a truly huge .rpa file?

[Code Monkey]

The rpa is 1GB actually... But it worked in 6.13 just fine. I tried breaking it up into multiple rpas but still got the same error.

[Code Monkey]

Fixed. For anyone else getting that issue, if you break down the rpas to be sufficiently small, you wont get a MemoryError.

I'm not sure if this is intentional for 6.14 or I'm missing something but you can no longer pass args to the game. I get the following error

Code: Select all

I'm sorry, but an uncaught exception occurred.

Before loading the script.
WindowsError: [Error 3] The system cannot find the path specified: u'C:\\Users\\My Name\\Desktop\\DandelionFull\\CodeMonkey\\*.*'

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

Full traceback:
  File "C:\Users\My Name\Desktop\DandelionFull\dandelion\renpy\bootstrap.py", line 228, in bootstrap
  File "C:\Users\My Name\Desktop\DandelionFull\dandelion\renpy\main.py", line 185, in main
WindowsError: [Error 3] The system cannot find the path specified: u'C:\\Users\\My Name\\Desktop\\DandelionFull\\CodeMonkey\\*.*'

Windows-7-6.1.7601-SP1
Ren'Py 6.14.1.366
 

It was painful but I did some minor modification to some of Renpy's source to get it to work. The arguments were not being parsed and instead used directly as a path. The changes are minimal for PyTom but is it possible to include these? I don't really want to have a different version of Renpy that is not "standard". Our game needs the args passed to it and it's already finished and live. It's currently running on 6.13 and we want to use 6.14 because it's more stable with Intel Graphics Cards. We've had a lot of users complain about video issues.

[PyTom]

What are you using arguments for? 6.14 now lets you register commands that can process arguments as necessary.