Android bug after update version 48.0.0

Device: Samsung galaxy S21 Fe
Operating system: Android 12
In game name: Cosmicruler~1
Game mode: plat 3 war and all general game modes

The above issue happened in war. This occurred only fighting spider ham. Fights on node 3, 12 30 and 37 all no problems with void.

This same issue occurs in practice and quest mode.

Only visible frame is during spider hams heavy attack

Hopefully this gets fixed asap, it was very annoying to give up a death in war.

Comments

Cosmicruler

@Kabam Miike @Kabam Lyra @Kabam Zibiit @Kabam Vydious @Kabam Porthos
Sorry I didn't know who was the right person to tag.

Anarchy_Reigns20

Spider ham and Nimrod seem to be the problem.
Device Google pixel 8 pro

kidanine

Same issue with Google Pixel 8.

Khetalord

Same issue on Google Pixel 7.

Happened during Spider-Ham fight in event quest Chapter 1.2

tznyc

This has been widely reported across the community

It has also been widely ignored by Kabam

AngelSvytoi

Now they've done downgrade graphics, enjoy the game without special effects on Google Pixel

damianohm

Similar issue S24 Ultra

Dromar_13

Multiple times this has happened to me in war, aq and battlegrounds
Lost resources to this and lost wars because of this

Unforgvn

I had the same issue in AQ, Samsung Galaxy s21ultra. It seems like the Fire/Skull background gets massively oversaturated and becomes a whiteout.

Unforgvn

KoiBoy18

Same. Note that all screenshot in this thread are against Spider-Man Ham defender

CelticSamurai

Fighting Longshot, this is his SP3. What's going on?! Has Kabam addressed this and I missed it?

Nimrod, SpiderHam, Air Walker, now Longshot, and I'm sure more have visual glitches totally ruining gameplay.

Asher1_1

This has been widely reported across the community

It has also been widely ignored by Kabam

Reported means kabam knows about it. If they don't have a solution yet doesn't mean they are ignoring it. They will say after it's fixed .

Reproduce & see what causing the problem first to solve it.

unknown

This content has been removed.

Unforgvn

Has this bug even been acknowledged by Kabam yet? The image I posted just started with this weeks hotfix/update, not with the December update.