- Thread starter Night Mirror
- Start date
Yeah I did that and it worked sorry for taking your time didn't know it was that simple
So I haven't hit the current epilogue, but I would like to know if by then the potential infinite growth of Morty's "lil" Morty due to the Devil's cursed app? I remember Morty worries about that possibility a couple time in this version of the game.
nah, there's nothing to worry about that, this game has no gameplay mechanic.
- Jun 2, 2018
- 2,023
- 12,146
- 749
No, I didn't include anything about it in the epilogue (too many other things). This concept mostly exists in this version to explain (lampshade) why his dick is inconsistent scene to scene. I think the Unity game brings it up only the once, the first time you meet the devil, then never brings it up again.
Just got a new Patreon post. To sum up - Space Beth won the vote for the next character after the currently in progress update . said update is in the writing stage, and they plan to release preview pics once they get to the art phase. And they shared an unrelated 3d animation they made (the first one they made apparently) with Emma Frost and Psylock.
- Jun 2, 2018
- 2,023
- 12,146
- 749
LuceroX
Newbie
- Jun 5, 2025
- 45
- 54
- 69
I've never seen an episode of R&M and yes. The game could probably explain a catch-up on what could be a continuity lock-out.
- Oct 28, 2019
- 2,501
- 2,219
- 498
certainly, you can play it without knowing anything of the cartoon.
it might raise some ..wtf..? moments if you happen to watch the series after, because for obvious reasons, the storyline differs.
saying more would be spoiler, for either the game or the cartoon.
Could be wrong but I think on my device there's a memory leak or something is preventing it to run for more then 10 minutes. The log just shows what it's doing and no errors. One log showed freeing memory but now it just shows the normal stuff. I don't have the best phone but the crash is very consistent and between 5-10 minutes with no common scene or action, seems to be a memory leak or memory issue even though I think I have enough memory. I have tried all versions, 32 bit, joiplay, android, etc. android crashed within 2 minutes and is slow, joiplay is 5-10 minutes and is surprisingly faster.. The log is accurate and recent but the traceback is old and was with the 32 bit patch which I undid and reinstalled PC version for joiplay. Any tips/help or edits I could do in the files, thanks?
Edit: here log file, it won't add.... 2025-11-16 23:31:24 UTC
Unknown platform.
Ren'Py 8.2.1.24030407
Manufacturer HMD Global model Nokia C300
Screen diagonal is 5.757375482716026 inches.
Version: Ren'Py 8.2.1.24030407
Mobile search paths: /storage/emulated/0/Download/RMAWH-r4.2.1-pc/RMAWH-r4.2.1-pc/game /storage/emulated/0/Download/RMAWH-r4.2.1-pc/RMAWH-r4.2.1-pc/game
Loaded 6 patches
Early init took 1.78s
Early init took 1.78s
Loading error handling took 1.12s
Loading error handling took 1.12s
Loading script took 20.82s
Loading script took 20.82s
Saving to /storage/emulated/0/Download/RMAWH-r4.2.1-pc/RMAWH-r4.2.1-pc/saves
Saving to /storage/emulated/0/Download/RMAWH-r4.2.1-pc/RMAWH-r4.2.1-pc/saves
Loading save slot metadata took 1.60s
Loading save slot metadata took 1.60s
Loading persistent took 0.07s
Loading persistent took 0.07s
- Init at 00updater.rpyc:23 took 0.27900 s.
Running init code took 5.94s
Running init code took 5.94s
Loading analysis data took 0.43s
Loading analysis data took 0.43s
Analyze and compile ATL took 1.70s
Analyze and compile ATL took 1.70s
Reloading save slot metadata took 1.01s
Reloading save slot metadata took 1.01s
Index archives took 0.00s
Index archives took 0.00s
Autosave is disabled
hw_video is enabled
Dump and make backups took 0.00s
Dump and make backups took 0.00s
Cleaning cache took 0.00s
Cleaning cache took 0.00s
Making clean stores took 0.01s
Making clean stores took 0.01s
Initial gc took 2.63s
Initial gc took 2.63s
DPI scale factor: 1.000000
Creating interface object took 0.01s
Creating interface object took 0.01s
Cleaning stores took 0.00s
Cleaning stores took 0.00s
Init translation took 2.22s
Init translation took 2.22s
Build styles took 0.02s
Build styles took 0.02s
Load screen analysis took 0.36s
Load screen analysis took 0.36s
Analyze screens took 0.01s
Analyze screens took 0.01s
Save screen analysis took 0.00s
Save screen analysis took 0.00s
Prepare screens took 0.73s
Prepare screens took 0.73s
Save pyanalysis. took 0.00s
Save pyanalysis. took 0.00s
Save bytecode. took 0.00s
Save bytecode. took 0.00s
Running _start took 0.03s
Running _start took 0.03s
Interface start took 2.95s
Interface start took 2.95s
Initializing gles2 renderer:
primary display bounds: (0, 0, 1473, 655)
swap interval: 1 frames
Fullscreen mode.
Vendor: "b'Qualcomm'"
Renderer: b'Adreno (TM) 610'
Version: b'OpenGL ES 3.2 [email protected] (GIT@47421dbee6, I139f36ad46, 1645189640) (Date:02/18/22)'
Display Info: None
Screen sizes: virtual=(1920, 1080) physical=(1557, 720) drawable=(1557, 720)
Maximum texture size: 4096x4096
Total time until interface ready: 44.32803559303284s.
Hid presplash.
- Jun 2, 2018
- 2,023
- 12,146
- 749
It certainly sounds like a memory leak, but what is causing it and how I can go about fixing it, I have no idea. No idea where to even start looking.
While not impossible I could stumble onto the cause, I'm unfortunately not going to invest time into it. I put out the android version because it's just an extra click to build it, but android has given me more problems, and wasted my time fruitlessly trying to fix them, than anything else. I honestly wish I hadn't done an android version at all.
Sorry
It's totally cool, I understand. My only guess is either the device is trying decompress and the resources in my device isn't enough or the resources in game need to restricted. I haven't done anything involving this stuff/finicking with tech and stuff in a while so my judgement is off sometimes. I actually have no idea how Android phones work, I'm a windows guy as many are. I have a few things I could try that I haven't, I'm pretty sure many of these cases are per device.It certainly sounds like a memory leak, but what is causing it and how I can go about fixing it, I have no idea. No idea where to even start looking.
While not impossible I could stumble onto the cause, I'm unfortunately not going to invest time into it. I put out the android version because it's just an extra click to build it, but android has given me more problems, and wasted my time fruitlessly trying to fix them, than anything else. I honestly wish I hadn't done an android version at all.
Sorry
- Jun 2, 2018
- 2,023
- 12,146
- 749
That is the most frustrating part about Android, is that many issues are device specific. So even if I get error logs (which I rarely do), well, I'm not going out and buying specific android devices to test on.
For this project, the majority of my testing is done on PC (really the only platform I support). But I do also test each release on two different Android devices and emulation. I do a full skip (setting AutoMenu to Full) through the game on each, so that if there is an error, or leak, it "should" come up. And I don't encounter this problem on Android 13, 16, or emulation (no idea what android version is emulated in the renpy SDK).
At the end of the day, even if there is an issue, the fix most likely is part of the renpy engine, not the game files. Again, my android deployment is mostly click a button, upload a file. There isn't really specific configuration or code for Android outside of some UI scaling.
LuceroX
Newbie
- Jun 5, 2025
- 45
- 54
- 69
If it makes you feel better, it still works for me.
- Jun 2, 2018
- 2,023
- 12,146
- 749
I mean, that is the underlying issue with Android, it works fine for me too. I can't troubleshoot issues I can't reproduce, and don't have error logs for.