MC-1319261.12.2 version's cube darking Graphical spawnning
1.12.2's vulnerability is 61.55% of my satisfaction, but I released this cube vulnerability. It's the black one.It's a lot of loopholes
What I hope to happen is...
No black holes and no lowfps
What actually happened is...
At the end of the lowfps (at least <15fps), there appeared a black cube vulnerability, which was continuously generated.
**Steps to Reproduce:**
1. how to trigger a mistake here step by step
2. to a certain place
3. there is a bit of lowfps, FPS low
4. there is a black hole, the cube of the vulnerability generation
5. cubic loopholes are constantly emerging
This vulnerability has been detected since 12:30 in May 20, 2018, but I haven't entered the Bug Tracker yet, and I landed today.
This is too frightening!
The following screenshot can prove this point
Attachments1
Created Issue:
1.12.2 version's cube darking Graphical spawnning
1.12.2's vulnerability is 61.55% of my satisfaction, but I released this cube vulnerability. It's the black one.What I hope to happen is...
No black holes and no cards
What actually happened is...
At the end of the card (at least <15 FPS), there appeared a black cube vulnerability, which was continuously generated.
**Steps to Reproduce:**
1. how to trigger a mistake here step by step
2. to a certain place
3. there is a bit of card, FPS low
4. there is a black hole, the cube of the vulnerability generation
5. cubic loopholes are constantly emergingThis vulnerability has been detected since 12:30 in May 20, 2018, but I haven't entered the Bug Tracker yet, and I landed today.
This is too frightening!
The following screenshot can prove this point
Attachments1
1.12.2's vulnerability is 61.55% of my satisfaction, but I released this cube vulnerability. It's the black one.What I hope to happen is...
No black holes and no cards
What actually happened is...
At the end of the card (at least <15 FPS), there appeared a black cube vulnerability, which was continuously generated.
**Steps to Reproduce:**
1. how to trigger a mistake here step by step
2. to a certain place
3. there is a bit of card, FPS low
4. there is a black hole, the cube of the vulnerability generation
5. cubic loopholes are constantly emergingThis vulnerability has been detected since 12:30 in May 20, 2018, but I haven't entered the Bug Tracker yet, and I landed today.
This is too frightening!
The following screenshot can prove this point
1.12.2's vulnerability is 61.55% of my satisfaction, but I released this cube vulnerability. It's the black one.
What I hope to happen is...
No black holes and no cards
What actually happened is...
At the end of the card (at least <15 FPS), there appeared a black cube vulnerability, which was continuously generated.
**Steps to Reproduce:**
1. how to trigger a mistake here step by step
2. to a certain place
3. there is a bit of card, FPS low
4. there is a black hole, the cube of the vulnerability generation
5. cubic loopholes are constantly emergingThis vulnerability has been detected since 12:30 in May 20, 2018, but I haven't entered the Bug Tracker yet, and I landed today.
This is too frightening!
The following screenshot can prove this point
1.12.2's vulnerability is 61.55% of my satisfaction, but I released this cube vulnerability. It's the black one.
What I hope to happen is...
No black holes and nocards
What actually happened is...At the end of the card (at least <15 FPS),there appeared a black cube vulnerability, which was continuously generated.
**Steps to Reproduce:**
1. how to trigger a mistake here step by step
2. to a certain place
3. there is a bit ofcard, FPS low
4. there is a black hole, thecube of the vulnerability generation
5. cubic loopholes are constantly emergingThis vulnerability has been detected since 12:30 in May 20, 2018, but I haven't entered the Bug Tracker yet, and I landed today.
This is too frightening!
The following screenshot can prove this point
1.12.2's vulnerability is 61.55% of my satisfaction, but I released this cube vulnerability. It's the black one.It's a lot of loopholes
What I hope to happen is...
No black holes and no lowfps
What actually happened is...
At the end of the lowfps (at least <15fps), there appeared a black cube vulnerability, which was continuously generated.
**Steps to Reproduce:**
1. how to trigger a mistake here step by step
2. to a certain place
3. there is a bit of lowfps, FPS low
4. there is a black hole, the cube of the vulnerability generation
5. cubic loopholes are constantly emergingThis vulnerability has been detected since 12:30 in May 20, 2018, but I haven't entered the Bug Tracker yet, and I landed today.
This is too frightening!
The following screenshot can prove this point
![[Mod] Neko](../../../data/avatars/users/92901.png){kind=small}
When the rowing saw the temple of the seabed
; Cubing bug MC-131926 what.
The bug
Put the summary of the bug you're having here
When I went to the temple of the sea, I was going to explore here, and suddenly there appeared a hole in the black cube. What's the matter? Please fix it for me
What I hope to happen is...
It's normal to explore (I don't have diamond armor, funny).
What actually happened is...
There are less than 20 of FPS and black cube vulnerabilities, which he has been loading constantly (see MC-131926).
Steps to Reproduce:
1.Go to a distant place (more than >800 Block)
2.This flaw is happening (50% is found)
*3.Sometimes it often crashes, even FPS is low to <10, sometimes generates >20 cubes (black cube caves copy brightness)
I have two graphs that are the loopholes that are produced as an attachment*(MC-131926 is more accurate, not your own view)*
go to MC-131926.
This bug is sure to be found in MC-131926
Thank you for your report!
However, this issue has been closed as Invalid.
This ticket is very difficult to comprehend, please use the Bug Report Guidelines here when posting issues.
Quick Links:
📓 Issue Guidelines – 💬 Community Support – 📧 Customer Support – 📖 Game Wiki
I was the one before yesterday