A group of individuals discovered and reported an issue where players can generate more orbs than intended when triggering some supers. The team has been working on a fix for this, currently targeting December for release.
To prevent exploitation of this issue, the team has deployed some changes that will force Rutabaga errors when players attempt to reproduce the bug. With this change, we are also aware that players who experience extreme sustained framerate hitching in PvP environments may encounter this error more frequently than normal.
If you encounter Rutabaga errors when playing in PvP environments for reasons other than reproducing the orb generation issue, please respond to this thread with details on what you were doing when the error occurred.
English
#Help
-
Edited by Franzo777: 10/31/2021 1:49:59 PMHi, I'm trying to run gambit matches for the born in darkness quest, but I'm encountering a specific bug: I can enter the match without problems but, when we get transported with transmat in the match arena, I get kicked because of rutabaga error; this has occured a few times, so that I got suspended from gambit. Consider that: - my PC hadn't have any fps issues since the last update, though gambit could meet some slowdowns durign transmat phase; - i run low-mid settings; - my fps stays over 30, apart some less then a second drops in some phases; - i was not alt-tabbing, just running the game normally; - no other application running (discord was closed too); - I've never used nor equipped telesto, nor tried any orb exploit. - i run in borderless fullscreen window, same resolution of my monitor (1440x900, if i remember correctly). I'll try later to run the game in fullscreen and lower resolution, hoping not to get banned because of a glitch exploitation I haven't even tried. Thanks for the help. EDIT: tried with lowest settings,: I've managed to get past the transmat but after a few secs I've got rutabaga again. Seems that, due to the changes in response to the glitch, the software has become too much sensitive to this error, making impossible to run gambit. This fix is more a bug than the glitch it should prevent.