March 19, 20178 yr Well shit, but we won't give up until they patch this issue. We must keep fighting!
March 20, 20178 yr Obviously don't let them forget about it, but was it ever stated that's what the patch was for? I thought the patch was for 60FPS tweaks. This one is likely a lot harder to reproduce and isolate, so I imagine they're still working on it.
March 20, 20178 yr From what it looks like, they're fixing the problems in small portions. Hopefully this is at least fixed by the Western release. Obviously don't let them forget about it, but was it ever stated that's what the patch was for? I thought the patch was for 60FPS tweaks. This one is likely a lot harder to reproduce and isolate, so I imagine they're still working on it.60FPS tweaks and "various bug fixes"This obviously hasn't been fixed.
March 20, 20178 yr This should have been first priority lol It actually looks like a difficult problem to fix. I doubt they even know what's causing the problem. If that's the case, then they can't fix it until they figure out the cause. Edited March 20, 20178 yr by MythrilMagician
March 20, 20178 yr From what it looks like, they're fixing the problems in small portions. Hopefully this is at least fixed by the Western release. 60FPS tweaks and "various bug fixes" This obviously hasn't been fixed. "Various bug fixes" is usually shorthand for optimization and streamlining; if this thing is indeed a bug, it's big enough to warrant its own patch note. But yeah, hopefully we'll see a fix before the western release. If not, well... at least the unfortunate souls will provide invaluable data for a patch later on =P.
March 20, 20178 yr "Various bug fixes" is usually shorthand for optimization and streamlining; if this thing is indeed a bug, it's big enough to warrant its own patch note. But yeah, hopefully we'll see a fix before the western release. If not, well... at least the unfortunate souls will provide invaluable data for a patch later on =P. Practically the only benefit of Japan getting the game first
March 20, 20178 yr I want to emphasize the fact that clicking on report the problem sends them the code stack where the game crashed. So if users continue reporting it, there is no doubt they will understand what's the issue and where it is located. I am more concerned for non crashing issues like in 0.2 with the infinite loading screen that still happens to me from time to time.
March 20, 20178 yr I want to emphasize the fact that clicking on report the problem sends them the code stack where the game crashed. Does it really? Never heard this before, but that's actually interesting if this is the case.
March 20, 20178 yr I want to emphasize the fact that clicking on report the problem sends them the code stack where the game crashed. So if users continue reporting it, there is no doubt they will understand what's the issue and where it is located. I am more concerned for non crashing issues like in 0.2 with the infinite loading screen that still happens to me from time to time. Huh, I never knew that happened when you submited a game crash report.
March 20, 20178 yr I want to emphasize the fact that clicking on report the problem sends them the code stack where the game crashed. So if users continue reporting it, there is no doubt they will understand what's the issue and where it is located. I am more concerned for non crashing issues like in 0.2 with the infinite loading screen that still happens to me from time to time. Does it really? Never heard this before, but that's actually interesting if this is the case. Huh, I never knew that happened when you submited a game crash report.That should be in all OSesAnyway, it may be why they haven't fixed it yet Probably not enough people have reported the crash. If it's as random as they say, they'll likely need more data to find the root of the problem.