-
-
Notifications
You must be signed in to change notification settings - Fork 10.5k
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
end segment of circle arc scissoring #4419
Comments
Thank you for the report. With dx9 renderer strokes are always anti-aliased even if imgui anti-aliasing is disabled First question: even if it was fully the case, would you have an issue with it?
However it is possible there is something else in your app, e.g. multi-sample AA done by the app or by the GPU driver could alter that perception. About the circle missing one segment: |
@ocornut I will take a closer look at the missing circle segment. |
…ices for 12 segment case (ocornut#4419) Before introduction of adaptive arcs PathArcToFast() were operating on 12 vertices table. Now it is replaced by internal _PathArcToFastEx() doing same job but with greater granularity, PathArcToFast was left as a fallback.
@ocornut It is fixed on PR. I think this is how it should be from the begging, not patching AddCircle was my oversight. Commit and PR have an extra comment, which I hope make the change clear. |
it's not a my own app, just imgui example from latest commit, i also tried to explicitely disable multisample AA with presentParams.MultiSampleType = D3DMULTISAMPLE_NONE;
presentParams.MultiSampleQuality = 0UL; in the d3d device creation, but seems it doesnt helped, so yes could be related to gpu/drivers, but weird it happens only with dx9 |
Is AA forced in driver settings? |
you're right, found in nvidia docs about this, overriding of application antialising working only till dx10, it's so weird but ok i'm calm now |
…ices for 12 segment case (ocornut#4419) (fixup)
version: 1.82
branch: master
at first, i noticed that with dx9 renderer strokes are always anti-aliased even if imgui anti-aliasing is disabled
using following code in a fresh imgui example:
we will see this next with dx9:
and next with dx11:
i guess it could be related to bugs of dx9, because i tried to set dx9 renderstates to disable anti-aliasing but nothing changes
at second, circles (no sense filled/stroked) last segment looking scissored with magic '12' number as segments count (that will look for precached points), due to reduced segments count by 1 due to closed primitive drawing
The text was updated successfully, but these errors were encountered: