[Bug]: Particles disappear after a few minutes of gameplay
thiper01 opened this issue ยท 12 comments
General Info
- I didn't added any mods
- I can reproduce this issue consistently in single-player
- I can reproduce this issue consistently in multi-player
- I have searched for this issue previously and it was either (1) not previously reported, or (2) previously fixed and I am having the same problem.
- I am crashing and can provide my crash report(s)
- I am using the latest version of the modpack
Your launcher
Curseforge
Modpack version
2.3
Describe your issue
As I'm playing, suddenly all particles stop appearing, campfire smoke, block breaking particles, it just stops appearing, I have tried every graphics setting option and reopening the save, but it only comes back to normal after I reopen my game completely, staying normal for a few minutes and then happening all over again.
I tried opening the game in different Forge versions and different Java versions, deleting the profile and creating a new one from scratch.
I'm using 8GB RAM, this issue wasn't happening on previous versions of LITV3.
Steps to reproduce the issue
Play the game normally and after a few minutes, all particles will stop appearing.
Additional Information
I didn't play in 2.2, the last version I played was 1.13 and then jumped straight up to 2.3
CPU Ryzen 1600X
GPU GTX 1070
Total RAM: 16GB
(I also love Cockatiels btw)
Forge bug not 100% sure was it like this in 2.2? also pc specs
cpu
gpu
total ram
I'll be out for a few days and when I get back I'll test it better but as far as I tested, it works!
Something even weirder happened, after a while of being with no particles, all of a sudden all the particles that weren't appearing exploded from where my head was positioned, from 40+ hours of gameplay on this version this is the first time something like that happened, after that everything continued the same, no particles.
I've seen this issue since the 1.18 versions. Can confirm that there is a burst of particles that indicates the bug has triggered, and they are usually in a line or cluster, and always block breaking particles. Usually though they spawn offscreen, meaning they just... vanish. The bug is also VERY hard to trigger manually, and it can take anywhere from 10-20 minutes to hours. A couple of times I've left the pack running for hours on end so my friend can join me over Hamachi, and I came back to particles still working fine. What has been tried so far:
Disabling all optimization mods
Disabling ItemPhysic
Disabling an assortment of other mods, such as Paxi, Traveler's Titles, Yung's mods, dynview, Farsight, and Chipped.
Nothing has worked. I have no real leads, other than one that I realized was completely wrong when I looked into the mod.
Oh, and also of note is the fact that this bug hasn't shown up in ANY other 1.18 or 1.19 pack that I've seen.
Confirmed it through testing that this works. Something about the way VTweaks challenger mob particles spawn just breaks things after some time. For now, disabling challenger mob particles (NOT the mobs themselves) will have to do until the VTweaks dev fixes this.
I had the same problem and no matter what I did, I couldn't solve the problem. That's why I stopped playing this mod pack. In mine, first of all, the particles that appeared when the grass was broken were coming out. So I think the FTB ultimine triggers this problem. Because I used the FTB ultimine mod to break the grass and create an empty space. This was the scariest bug I've ever encountered while playing Minecraft.
I had the same problem and no matter what I did, I couldn't solve the problem. That's why I stopped playing this mod pack. In mine, first of all, the particles that appeared when the grass was broken were coming out. So I think the FTB ultimine triggers this problem. Because I used the FTB ultimine mod to break the grass and create an empty space. This was the scariest bug I've ever encountered while playing Minecraft.
In my experience it's not necessarily FTB ultimine that triggers this problem but it may contribute to it happening, in my experience anything that would give the computer a bigger load to process can trigger the problem, for example, I have been able to consistently trigger the problem faster just by teleporting to unloaded chunks far away repeatedly.
