D
Deleted member 2482011
Guest
Guest
Let's just say there are impossible "possibilities" xDWhat I want to "complain" about is the possibility to change the age of the MCs, the default is 25 ... I raised that, but if you have a daughter (and she must be 18+), you had to father her at 7, and even if she is only 14 or something like that, it doesn't work.
And considering the story so far there could be some weird shit behind that, but everyone reacts as if this could be a possibility. Currently I think that there is "just" some parallel World stuff going on - so no time travel or stuff like that. Because even if the MC is "his own (maybe younger) brother" - that does not work because the mom or sis never say that his age does not fit.
So to make sense, the min. age of the MC has to be more around 33-36 ...
---
It is a fun game, but not really an erotic/porn game. All the lewd stuff is quite tame and rushed without much detail. I like that there are several small animations here and there and quite a huge number of renders for most scenes - some games are way to static, but the little lewd stuff we had was short and feels more like added stuff and not as a main part of the game.
What kind of changes do you do for the 1080p version? Why not just use the same code and only change the media files? You can scale images and video within renpy. IE. "Movie(size=(1920,1080), play="name of video.mkv")" would scale any video to 1920x1080 virtual pixels(what you set with gui.init in GUI.rpy). Virtual pixels aren't real pixels, if someone plays a 4k video on a 4k screen it will still be 4k, even if scaled to "1080p".You should have seen the first version xD
The version you played was probably the one I fucked up before the upload.
When I work on the game, I work on the 4k version and then copy the files over to the 1080p version, so after editing and testing was done, I just did a small fix right before the first upload and must've somehow fucked up while copying over the files (no idea how that could happen). So yeah, the version that's online now should be a lot better.
Don't say that, there's always an error left somewhere... always xD
The "Hotfix" only fixed an error btw, only the re-upped version has the grammar fixes.
The problem is that 1. the 4k version runs shitty on almost all medium/low hardware which makes most of the players here. Renpy is just bad at handling hq videos or rendering hq stuff in general, scaling everything down instead of using native 1080p images/videos would only make it worse.What kind of changes do you do for the 1080p version? Why not just use the same code and only change the media files? You can scale images and video within renpy. IE. "Movie(size=(1920,1080), play="name of video.mkv")" would scale any video to 1920x1080 virtual pixels(what you set with gui.init in GUI.rpy). Virtual pixels aren't real pixels, if someone plays a 4k video on a 4k screen it will still be 4k, even if scaled to "1080p".
If you did that, you wouldn't have to maintain two branches of code and double test... You could standardize on the 1080p version and improve performance while maintaining image quality. More virtual pixels = more work on CPU.
thx, added to the op.Weird Shit Is Going to Happen [v0.3] [recreation] - Original size 845MB(1080p)
Compressed Android(178MB): MEGA
Compressed Windows/Linux(167MB): MEGA
Compressed MAC(161MB): MEGA
Weird Shit Is Going to Happen [v0.3] [recreation] - Original size 6.38GB(4k)
*working on it*
*This unofficial port/version is not released by the original developer, download at your own risk*
These files were compressed using YAC, my own cruncher script! Check it out!
I am sorry but I have got to say that personally I can't see the point, 1080 download of 900 MB or download 4K of 6.43 GB, I will go for 900 MB I may be a heathen but I can see no real difference in quality ( maybe my machinery or eye sight) but the time and problem of downloading 6.43 GB is definitely not worth the extra effort for a debatable gain ( Mega over limit and Nopy just gave up ) and its still a GREAT GAME even at 1080. CheersBecause I don't want to be asked to do it later. ¯\_(ツ)_/¯
It might still look better than 1080p, too. Won't know 'till it's out.
What do you think? Compressed 4k video sample attached.
It looks good on my Android, I'll have a look at it tomorrow on my py.Because I don't want to be asked to do it later. ¯\_(ツ)_/¯
It might still look better than 1080p, too. Won't know 'till it's out.
What do you think? Compressed 4k video sample attached.
This is because of the textbook option I included right before release. The script has its own text size defined.define mc = Character("[mc_name]", who_color="#bbb")
define mcthink = Character("[mc_name]", who_color="#bbb", what_italic=True, what_size=35)
## The size of normal dialogue text.
define gui.text_size = 45
weird ... really
I got this ... thinking and talking
View attachment 712220 View attachment 712221
and i really don't understand why
She has her own amulet, but she's not wearing it, she didn't ever wear it, and she won't ever wear itOne thing I am waiting for the MC to notice is that there is only ONE of the Amulet! Interesting thing I was thinking about, and that's how his "Mother" saw him with the Amulet on and took it from him, then he got it back, but I am waiting for him to realize, and she is from a parallel earth than his, why doesn't She have her own?! I think that, like the Hotel, there is only 1 Amulet. The Hotel is a Nexus point of Realities, with the Amulet being the obvious Key, and as we have seen, the Holder of the key can move between realities by opening a door, and I think with practice, and focus, might have some control, but has to realize the truth of said Amulet! I don't think it matters WHO is holding it, as his Mother held it and ended up in another Reality, and he was only able to save her because she dropped it. Like I said, Loving it, because it is a mind-fuck, and mind-opener!
Did you mean 'textbox'? And isn't this the text_size bug which got fixed in 0.3?This is because of the textbook option I included right before release. The script has its own text size defined.
mc
and mcthink
are defined as follows:define mc = Character("[mc_name]", who_color="#bbb")
define mcthink = Character("[mc_name]", who_color="#bbb", what_italic=True, what_style="thinking_dialogue")
test_size
is only used on the 4k-version. See the following lines of gui.rpy:init python:
if fourk is None:
gui.text_size = 30
gui.name_text_size = 50
gui.interface_text_size = 40
gui.textbox_height = 278
...
no she hasntHmmm....Now it has me wondering if she has it with her....that would be amusing....seeing how the 2 resonate.....
Yes textbox xDDid you mean 'textbox'? And isn't this the text_size bug which got fixed in 0.3?
tk99, as far as the current script.rpy is concernedmc
andmcthink
are defined as follows:
The defaultPython:define mc = Character("[mc_name]", who_color="#bbb") define mcthink = Character("[mc_name]", who_color="#bbb", what_italic=True, what_style="thinking_dialogue")
test_size
is only used on the 4k-version. See the following lines of gui.rpy:
Hope this helps!Python:init python: if fourk is None: gui.text_size = 30 gui.name_text_size = 50 gui.interface_text_size = 40 gui.textbox_height = 278 ...
Interesting. So the size difference between 45 and 35 isn't as noticeable at 4k than the difference between 35 and 24 at 1080p, yes? The way I see it the problem wasn't theno she hasnt
Yes textbox xD
the "text-size bug" wasn't a bug, it was just me sitting in front of a 4k screen not knowing which text size looks good in 1080p^^ For me it looked good and readable in the first version already, so it's a bit of guesswork and asking testers.
the "thinking-dialogue" text size comes from the textbox, not sure why I left it in there since it's actually not necessary in WS.
also, looks like tk99 uses the first 1080p version of 0.3, the mc/think lines changed with the fixed version.
text_size
but rather the size difference between text_size
and mcthink
. The former can easily be solved on the player's end by adjusting the font scaling as detailed here while in case of the latter the very same approach just exaggerates the problem. At least on 1080p-screens.