My Rudy fatal error is no more which is great. You guys are absolutely incompetent in game testing process! I think you have a very small crew – that is your main problem…Ĭompletely restarted to test all the things I saw before the patches. Yes, I’m REALLY angry because I was waiting for SEVEN months and I can’t proceed in game because of that bug. I know I am not alone with this problem so DO SOMETHING WITH IT!!! But I can’t start the new game either – sevepoint system is completely broken!!! When I try to load from them inserting the “save1.ini” file manually – all MOGIs are disappeared! So each time the new beta comes out I should start from very beginning because old savepoints are bugged (no MOGIs in game at all). Old savefiles from previous beta versions are useless as well. When I press the C button in correct save area the “save1.ini” file DOES NOT APPEAR in C:\Users\Александр\AppData\Local\MogiOrigins directory!!! Yes, I have a Cyrillic user folder – so this might be the source of this issue! I’ve already told you several months ago but you did NOTHING with it!!! Didn't know about that until I had long passed Oak and died later on. So I have to purposely get hit in order to fix my OCD and completely the gallery. Beat Oak so many times already that she is easy mode and I don't even get hit once. I don't remember if this was in the older versions but I'm a little disappointed that you HAVE to trigger an h-scene for it to be in the gallery. But dang, the later areas where you start seeing slime girl black are tough. *Then there's that squirrel glitch that was already mentioned above. Point_distance argument 3 incorrect type (5) expecting a Number (YYGF)Ĭalled from - gml_Object_obj_rudy_Step_0 (line 393) Otherwise she runs, jumps, and shoots while in the air just fine. This only happens when I'm standing still and hit the Z key to attack. *Switched to Rudy didn't move at all and when I went to attack I got this fatal error. This is right after defeating Oak, unlocking the door to the far right and then left from that entrance. Next, Voms tries to call for help, but can he actually defeat. But now all these problems are probably gone for good. The memory issues had, unbeknownst to me, affected old files too however so things. A few more days happened, and since the ball was in my court, I thought I'd be done immediately. They helped me isolate the problem areas in the game and I began to fix them. Parts of the game's memory got corrupted with the #1 theory being a memory mismanagement incident that could be traced to my PC limiting the amount of RAM I could use when my charger got unplugged. The direct cause of the problem was never really found. I could not see how it was my fault, meanwhile, conversations are slow since it's support. Time went on, and I was making no progress on my end. I didn't make the previous mistake of not contacting GM's dev team though. Therefore, I assumed the problem was on my end, and I began working surreptitiously thinking the problem would be solved before long. Previously we got to 25 texture pages before facing such errors. Ever since moving the adult animations to be external videos, we were using much less memory. This time around though, the situation was different. If you've been following our blog for a while, an unwarranted memory problem has happened before and it wasn't a pretty sight.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |