Rendering is different in Chrome vs Firefox
-
Andor Salga
- Tag set to anti-aliasing
- State changed from new to assigned
- Milestone set to 0.6
- Assigned user set to Andor Salga
- Milestone order changed from 29 to 0
Looks like Chrome is using anti-aliasing and Minefield isn't. I'll look into this.
Also, I wonder if this is related to the frame rate. I'll try toggling anti-aliasing on Chrome to see if there are performance differences. In any event, I know Minefield has been leading in terms of WebGL performance, but there's a chance we could file a bug for Chrome.
-
Andor Salga
I played with anti-aliasing on Chrome and found that the performance hit is ~10 fps.
On my macbook pro:
Chrome: ~42fps with AA ~51fps without AA
Minefield: ~65fps without AAWebGL spec says AA should be on by default. Currently Minefield does not have AA on my default, it actually does not support AA at all.
I think AA is something a user should be able to toggle when they create an instance of XBPS.
For now, we can disable AA making all browsers render similar point clouds, which will also fix ref testing. Later on, we can add AA support.
Thoughts, ideas?
-
Andor Salga
- State changed from assigned to resolved
I fixed the anti-aliasing in another branch so both Minefield and Chrome.
Setting this to resolved.
Please Sign in or create a free account to add a new ticket.
With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.

