Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

GPURenderer particle #235

Open
QuisMagni opened this issue Oct 6, 2022 · 4 comments
Open

GPURenderer particle #235

QuisMagni opened this issue Oct 6, 2022 · 4 comments

Comments

@QuisMagni
Copy link

Version: 10.0.3

I'm trying to use the GPURenderer for performance reasons and the results performance wise are very good. The problem is that the particles are not fully rendered (i dont use multiple emitters just a simple smoke system).

image

It seems that only one quarter is being rendered and the rest of the texture is missing out. I also tried the GPURenderer particle systems from the examples getting a very similar result.

This is the code i use for initializing;

Nebula.fromJSONAsync(this.getParticleSystem(name), THREE).then((loaded) => { const nebula = loaded.addRenderer(this.gpuRenderer) for (let e in nebula.emitters) { const emitter = nebula.emitters[e] emitter.setPosition(position) } ... })

@QuisMagni
Copy link
Author

QuisMagni commented Oct 6, 2022

The problem is gone if i add only a single system to the scene. But if i add another one the uv coordinates of the particles are messing up.

@samyH
Copy link

samyH commented Oct 6, 2022

nebula-render-issues

Yes I'm also encountering this issue

Looks like it's already been reported and fixed according to this though? #90

@samyH
Copy link

samyH commented Oct 6, 2022

@butzemannbiber did you try adding alpha to the WebGLRenderer?

renderer = new WebGLRenderer({alpha: true});

I pulled the GPURenderer example particle system (data.js) and was having the same issue as above until I added that.

When I tried that fix on my own fireball though the issue still persists :(

@jmschrack
Copy link

@butzemannbiber @samyH are you using NPM for the module or did you build the library yourself? The npm library hasn't been updated in over a year. There are some new fixes that are in the github that might help.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants