Minecraft: 1.21.1
Loader: NeoForge 21.1.233
Particle Core: 0.3.3+1.21+neoforge
C2ME: 0.3.0+alpha.0.93
Create: 6.0.10
Create Dragons Plus: 1.11.2b
I’m getting a threading exception shortly after joining a world/server. The log shows:
ThreadLocalRandom accessed from a different thread
owner: Render thread
current: ForkJoinPool.commonPool-worker
The stack trace goes through Particle Core’s async particle tick mixin:
particle_core.mixins.json:async_tick.ParticleManagerAsyncMixin
Then it involves Create’s airflow particle:
com.simibubi.create.content.kinetics.fan.AirFlowParticle
And also Create Dragons Plus:
com.rhseung.create_dragons_plus.mixin.create.AirFlowParticleAccessor
This looks like Particle Core async particle ticking is ticking a particle that expects render-thread-only random access. Could Create/Create Dragons Plus airflow particles be blacklisted from async ticking, or is there a config option I should disable?
I can provide the full latest.log if needed.
Minecraft: 1.21.1
Loader: NeoForge 21.1.233
Particle Core: 0.3.3+1.21+neoforge
C2ME: 0.3.0+alpha.0.93
Create: 6.0.10
Create Dragons Plus: 1.11.2b
I’m getting a threading exception shortly after joining a world/server. The log shows:
ThreadLocalRandom accessed from a different threadowner: Render thread
current: ForkJoinPool.commonPool-worker
The stack trace goes through Particle Core’s async particle tick mixin:
particle_core.mixins.json:async_tick.ParticleManagerAsyncMixinThen it involves Create’s airflow particle:
com.simibubi.create.content.kinetics.fan.AirFlowParticleAnd also Create Dragons Plus:
com.rhseung.create_dragons_plus.mixin.create.AirFlowParticleAccessorThis looks like Particle Core async particle ticking is ticking a particle that expects render-thread-only random access. Could Create/Create Dragons Plus airflow particles be blacklisted from async ticking, or is there a config option I should disable?
I can provide the full latest.log if needed.