{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
10/24/2021 6:35:29 PM
266
Known Issue: Increase in Rutabaga Errors
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 fv99: 10/31/2021 10:55:39 PMI play on a laptop with serious performance issues and very common frame freezes but i have become used to it. But now i can neither launch gambit nor crucible at all... it keeps kicking me and suspending me. As far as i remember i have never seen the glitch during my play (with an average of a complete frame freeze every time a new ability is loading on screen for the first time that is saying a lot). I also think even on slightly more powerful computers when loading you can lose frames so maybe leave the time to load in before the insta-kick (no one can realistically intentionally replicate the glitch the instant they load in) In short : loading in or loading an ability on screen causes drops (significant ones on low performance computers) and it makes the game think you are trying to make the glitch happen. Edit : and yeah this temporary fix prevents me from playing half the game pretty much so i hope a better solution is found soon.
-
Não estou conseguindo iniciar/completar partidas de Artimanha/Gambit devido ao erro: Rutabaga e
-
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.
-
I've been facing an insane number of RUTABAGA errors since Tuesday and I can't complete most of my bounties since I get kicked back to orbit by this error code while loading into any of the PvP playlists. I just got blocked from gambit with 1 last bounty before I finish the weekly set. I didn't even alt-tab for most of these errors and they are honestly driving me up the wall. I'm using a pretty good PC setup so graphics isn't really an issue. Really hope that this problem gets fixed ASAP
-
Was playing clash and my frames randomly dropped, I was taken to orbit and given error code rutabaga. Please fix soon
-
2 RepliesSince I started playing destiny again (more than a month ago) I have experienced problems with framerste but that I can assure its a problem with my pc. But less than a week ago the Rutabaga code has appeared more often than ever, sometimes I cant even start a game because it will kick me before the game even begins, this has affected my PvP, I got banned for the second time in competitive this week because of this code, and now in gambit too. My second competitive ban happened today earlier, I was about to get an orb that a teammate created and it just suddenly kicked me and it showed the same Rutabaga code.
-
THIS ERROR CODE IS BUSTED. My computer freezes and insta kick. I switch over to discord and insta kick. This exploit is not worth the fix you've put behind it. stop overcorrecting small glitches when they aren't drastically effecting the larger communities experience. These "fixes" are getting out of hand.
-
It just happened to me today 10/30/21 and previously it had never happened to me, I already changed all the parameters in the video settings to the lowest possible and it keeps appearing to me, I have the latest update on my video card, my windows and currently I don't have any other application open while destiny is running ... I was unfairly banned from osiris tests for an error that they have not been able to solve, this has happened since they put their useless "battleeye" or that anti cheat that only works to lower the fps ... I need to remove the ban that was unfairly imposed on me or I will sue them :)
-
1 ReplySo I've been encountering that common issue many others have experienced whereby alt tabbing causes the error due to low fps resulting in a temp ban. Today I encountered it when changing my video settings from fullscreen windowed to fullscreen due to the same kind of fps drop to try and relieve some stuttering I was experiencing. I normally run the game above 80 fps on average and it's a smooth performance so it's just this little quirk which is hampering my experience with the game. I understand trying to prevent exploits but this is punishing pc users for TYPICAL use on a pc. Are you looking into a way to fix this so players aren't unfairly booted and banned from matches while trying to go about normal usage?
-
Rutabaga when just switching weapons in PVP. At anytime.
-
Edited by Ghost: 10/30/2021 11:13:22 PMI have been encountering the Rutabaga error for low framerate when playing in PvP environments and it has been happening a lot to the point of not playing. I produce orbs from masterwork weapons throughout the match by just playing, between matches use DIM to move items back and forth, also switch between M/K and controller while using DIM and the Rutabaga low frame rate error is random from starting matches to the end of matches. Environment: Edition: Win 10 Home Processor: AMD Ryzen 5 3500 6-Core Processor 3.59 GHz RAM: 16.0 GB Graphics: GeForce GTX 1660 SUPER
-
Steam player here. I got rutabaga'd from trying to play Gambit. I didn't tab out, didn't touch my inventory, all I did was enter the gambit que and wait. After the intro cutscene with Drifter, I get sent back to orbit. Its gotten to the point where I get suspended from Gambit! I'm lucky to have gilded my Dredgen seal this season...
-
I've noticed that this type of error occurs when: 1. Someone's joining my fireteam (tested in multiple activities like Astral alignment, the Crucible, strikes, even orbit or the Tower)->game stutters->rutabaga appears 2. Two or more people are entering the in-game voice chat (tested in the Crucible and strikes)->game stutters->rutabaga appears My pc specs are: I7 4790, gtx 1070ti 8gb, ddr3 16gb (can't remember mhz if necessary will update), win 8.1 These stutters started to appear with the Season of The Lost beginning. Until this time they were just an annoying problem that I could handle but rutabaga ruins all my inner harmony. I'll avoid playing competitive activities until the fix comes out so Ihope that I wouldn't be permanently banned after rutabaga appears in one of the strikes. Hope this info helps.
-
Hello there! Here, things have gone haywire. Rutabaga errors have been as common as 1 per match, effectively forcing me to not play the game in the modes that I like. THis happens no matter what I do or what I don't do. Hope this issue can be fixed. 3 days consecutively and it is getting tiring to not being able to play with the community or friends there.
-
I got the code while trying to switch weapons with DIM while the trials were intro
-
Edited by Misa: 10/30/2021 8:20:00 AMi got rutabaga'd while picking up heavy during a comp match, queued up another comp match and as im checking the loadout of everyone in the lobby and as its showing the 6 guardians face each other before the match starts? i get kicked again for rutabaga then got banned XD please fix it asap or make it so we can rejoin activities if we get rutabaga'd
-
I got this error this evening by just switching HDR off as the map I was on was too dark... No alt tab, just hdr off
-
keep getting the error every time i start a gambit match says my frams are to low or something
-
So a couple buddies of mine and I just happened to get into Round 1 of Trials (widows court this week) after losing 5-4 enemy team, was going well and happened to be Last Guardian Standing when all of a sudden, black screen with Rutabaga and an incomplete match message from Shaxx. The opposing team had a titan wearing Dunemarchers (not sure if that helps or whatnot but figured some detail may help)
-
I got a Rutabega because my computer froze and kicked me out of a 4-0 trials match. This is insane
-
I was just playing comp, I didn't even alt tab just had Spotify open on my second monitor and the game kicked me and I got a 30 min suspension...
-
Crazy how I can potentially get banned for wanting to pause my music as I'm watching emotes in Trials. What's even crazier is how [b]pathetically awful[/b] a job you all are doing at handling this (A forum post? Really?). Honestly, whoever decided that alt-tabbing so players couldn't pause their media or grab weapons through one of the plethora of platforms that are lightyears ahead of the Destiny 2 app should be transferred to another ip. If you're gonna make it so players are getting kicked for alt-tabbing, take away competitive leaver penalties until you get your house in order or give us an option to surrender in game. Better yet, make an announcement saying that you are tracking the players that are being reported for abusing the exploit. If you confirm that they are doing it in game [b]hardware ban them[/b] and publicize the list like you all used to with Halo. I'm tired of a AAA title with veteran developers feeling like it's a college project because your developers cant come up with a better interim fix than an intern could come up with.
-
1 ReplyEdited by Fish: 10/25/2021 12:12:16 AMThis is not a proper response to this issue. I understand that something has to be done in the mean time but this ain't it. Seriously Bungie get your head out of your -blam!-. This change for a few malicious players are effecting players who are just trying to play the game. These are the types of scenarios that permanently alienate players. I hope you're ready to see a dip in the player base.
-
1 ReplyThis is honestly a pretty bad "fix." I spent a good two hours over the past couple days trying to figure out why my son kept getting kicked from his first Trials experiences (which he enjoyed, except for the errors, thanks). He has only one monitor, and his hardware (my old computer) is beefy enough to run D2--I know, because it was mine only 6 months ago, and I've been playing for years--but he apparently kept getting kicked (with Trials bans, thanks) simply because of alt-tabbing. How "serious" an issue is this? What are the repercussions if it goes unpatched but acknowledged? Orbs were duped in Pit of Heresy and similar dungeons for a long time, and arguably, no one was hurt. I really hope that metaphorical lives are on the line to take such drastic steps in this case.
-
poor pc that i have and stuttered in pvp
-
Quicker solution in the short term: Just disable Orb generation in pvp. Stop doing things that obviously only effect some players.
