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

Vector anti-aliasing issue #3124

Open
2 of 11 tasks
tslocum opened this issue Oct 5, 2024 · 2 comments
Open
2 of 11 tasks

Vector anti-aliasing issue #3124

tslocum opened this issue Oct 5, 2024 · 2 comments

Comments

@tslocum
Copy link
Contributor

tslocum commented Oct 5, 2024

Ebitengine Version

v2.8.0

Operating System

  • Windows
  • macOS
  • Linux
  • FreeBSD
  • OpenBSD
  • Android
  • iOS
  • Nintendo Switch
  • PlayStation 5
  • Xbox
  • Web Browsers

Go Version (go version)

1.23.1

What steps will reproduce the problem?

Run Boxcars using the vector branch, which adds this commit using Ebitengine's vector package instead of draw2d. For comparison, the previous commit is this one. The only change between the two is which package is used to draw the vector graphics.

What is the expected result?

Anti-aliased triangles. This is the result when using draw2d with anti-aliasing enabled:

vector_draw2d

What happens instead?

Rough triangles. This is the result when using Ebitengine's vector package with anti-aliasing enabled:

vector_ebitengine

Anything else you feel useful to add?

I tried different fill rules, but that did not seem to have any effect.

@hajimehoshi
Copy link
Owner

We might need a special shader to resolve this issue. As utilities, we might introduce some functions. See #3150

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

No branches or pull requests

3 participants
@tslocum @hajimehoshi and others