It's easy, use full screen mode. You can't play 2560x1440 window mode on a 2560x1440 monitor, since the window takes space too. It wouldn't fit.I'm sorry if this was already asked but how do I enable 1440p?
I have the required monitor, but the only mention of 2560 x 1440p is from last year and the attached file no longer works
I also have no idea how manual config works, if that is even what I want
There is a quick fix on my patreon page.Well I was getting an error message during the Jessica Photoshoot and I've tried with and without the 2 files and I keep getting the same error message.
So far Dark no Issues on my Android ...Again nice jobThere is a quick fix on my patreon page.
There won't be any additional quick fixes now, since there were too many bugs to stick with version 0.2.3.1 for several weeks/months.
I will release another update to 0.2.3.2 soon to fix the know bugs, but this time with no other fancy stuff that could create new bugs will be added. Almost alll of the stuff coming up now wasn't from 0.2.3.1, but was already in 0.2.3.0.
Bottom line - 0.2.3.1 was released too early, I should have waited a little longer.
You can expect 0.2.3.2 tomorrow. Depending on what I hear from the android users, there might also be a new full android version. I haven't decided it yet.
You're completely right. As how it is with current hardware, you have the optiona for really good image quality using images and animations rendered in apps like daz studio, where one render (or one animation frame) takes between 3 minute and 30 minutes to complete, even with really fast hardware.You realize this is not a fully animated game and this would require every woman to have multiple renders for every possible combination of physical change plus outfit?
Maybe if a AAA game dev was doing this and using a real yime 3D engine it would work, not like this however. Right now you get to 'tolerate' the woman the size/shape the dev envisioned.
Thanks, and basically you will also have on android:So far Dark no Issues on my Android ...Again nice job
You are using a different (standard) renpy version. The one I use has some changes to it's base code to support handling some errors differently, that's why you get the errorsjust a question please see below. I am trying to run PC version completely updated thru the emulator JoiPlay on an Android Samsung s6 tablet. In short after you see this message can the game be played in Ren py environment aka access to console in Android environment.
trackback message below.
I'm sorry, but an uncaught exception occurred.
While running game code:
File "renpy/common/000namespaces.rpy", line 9, in set
Exception: config.developer_show_all_exceptions is not a known configuration variable.
-- Full Traceback ------------------------------------------------------------
Full traceback:
File "/storage/emulated/0/Download/HolidayIsland-0.2.3.0-pc/game/options.rpyc", line 13, in script
��� mhHi�*p5,v�� �:�R�h�������������*���k) n�ʛ�b�(Uo�Mn�2���0��Vv+'��؆�d�fXm���
File "renpy/ast.py", line 2117, in execute
File "renpy/common/000namespaces.rpy", line 9, in set
File "renpy/defaultstore.py", line 99, in __setattr__
Exception: config.developer_show_all_exceptions is not a known configuration variable.
It won't help, I have modified the renpy base code. What you can do is to remove the variable "developer_show_all_exceptions" from the options file.Ty ya sir I'll see if an add to the emulator matches your version. Many thanks.
It seems you have to repeat your question many times...I have the GUIDE, but I can't understand how to get this HEARTS and unlock scenes. How many times I have to repeat myself...
As it says... You need to have at least 50 company favour and then you can buy the smart watch from the doctor.How do I complete this quest?
it tells you get 50 Hi credits buy a smart watchHow do I complete this quest?
Don't push yourself too hard. You're doing a fantastic job, and I think everyone would understand if you took an extra day or so to iron out everything.There is a quick fix on my patreon page.
There won't be any additional quick fixes now, since there were too many bugs to stick with version 0.2.3.1 for several weeks/months.
I will release another update to 0.2.3.2 soon to fix the know bugs, but this time with no other fancy stuff that could create new bugs will be added. Almost alll of the stuff coming up now wasn't from 0.2.3.1, but was already in 0.2.3.0.
Bottom line - 0.2.3.1 was released too early, I should have waited a little longer.
You can expect 0.2.3.2 tomorrow. Depending on what I hear from the android users, there might also be a new full android version. I haven't decided it yet.
Should be between pages 26 and 28.
You're welcome.
It seems you have to repeat your question many times...
So to try to help you more click on the spoiler below..
You don't have permission to view the spoiler content. Log in or register now.