You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Quick mitigation is to set scene-options.env-presets.fog = 0, however that is unrealistic for new users.
Slightly better would be to disable env-presets fog behind the scenes when spe-particles are present. Hackish, but realistic for new users. We could console log this setting to at least help awareness.
aframe-environment-component has been updated recently, we could see if it helps. Unfortunately aframe-spe-particles-component has not been updated for six years, and we've modified it ourselves to work with newer THREE.js. Maybe it again needs another update for THREE.
The text was updated successfully, but these errors were encountered:
@EdwardLu2018 The best solution, aside from rewriting the spe-particles for recent THREE, is to remove the conflict from the component settings automatically for all particles by setting affectedByFog from true to false .
If any elements of https://github.com/supermedium/aframe-environment-component are set, they often enable fog behind the scenes, where
fog > 0
. In this state, adding any https://github.com/harlyq/aframe-spe-particles-component entity causes a runtime crash between the two particle emitter systems (env-presets vs. spe-particles).scene-options.env-presets.fog = 0
, however that is unrealistic for new users.spe-particles
are present. Hackish, but realistic for new users. We could console log this setting to at least help awareness.aframe-environment-component
has been updated recently, we could see if it helps. Unfortunatelyaframe-spe-particles-component
has not been updated for six years, and we've modified it ourselves to work with newer THREE.js. Maybe it again needs another update for THREE.The text was updated successfully, but these errors were encountered: