To help personalize content, gather statistics and provide a safer experience, we use cookies.
By clicking or navigating the site, you agree to allow our collection of information through cookies.
Learn more about cookies in our
Cookies Policy and
Privacy Policy.
Firstly, it seemed like only the other day that Marox was made aware of this issue. Secondly, it's not just a case of hitting the 'fix' button and patching it.
They need to be able to replicate the issue, and reliably enough to properly diagnose the cause of the bug, then they need to fix it. Some bugs are quick to remedy, others are a nightmare. no bugs are created equal.
So have some fucking patience you entitled troll.
Yep, bugs are not always easy to fix, & even if they have already fixed the issue, there could be other reasons why they can't push out a new update/bugfix patch yet, such as: they were working on something else in the same project file & it isn't finished yet & if released might cause a bunch of other issues - which people would then start complaining about instead.
Game development - actually development in general - is kind of like playing with a multi-headed hydra. You fix a bug or implement a new feature & more often than not new (or even old) bugs appear in their place.
99 little bugs in the code
99 little bugs
take one down, patch it around
127 bugs in the code
haha I see what you did there.
Not fixed until today... Really annoying.
I'm having the same problem. Is there any solution yet?