-
-
Notifications
You must be signed in to change notification settings - Fork 156
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
NPOT causes small visual glitch in naev #11
Comments
Yes, LIBGL_NPOT=2 expose a function that is not completly supported for now. LIBGL_NPOT=1 is 100% emulated, but not 2 for now. I may work on that, but real support as not been mandatory for anything yet. |
I see, |
Limited NPOT is : can use texture not NPOT, but cannot use Repeat or Mirror on NPOT, and no Mipmap neither. Full NPOT can do whatever they wants. Emulating that on non-NPOT hardware would mean resizing a non-NPOT texture to NPOT, meaning a lot of computational power at each upload, plus some artefact du to the resizing (espcially on SubImage manipulations). |
I'll close this ticket. |
did you retry with latest changes (with added Pixmap, PBuffer and multiple glX Context, it may have just solved the issue) ? |
On Tue, 01 Nov 2016 15:25:14 -0700
I was using the latest glshim master and it's still there. Any special options to try? |
Ah no. I need to look in the code to see how that cursor is built. |
On Tue, 01 Nov 2016 15:55:25 -0700
Thanks! |
@petevine : it turned out it's not a glshim issue, but an SDL2 one. Check my github repo of SDL2, there is push about this: ptitSeb/SDL2@604d108 |
white silouette is there depending on the theme. But if you want, you can change the |
Not much can be done here. It's X11 functions, and it seems they behave differently for machine to machine. |
Update init.c
NPOT textures has to be ticked in the video settings and then:
leads to clearly visible planet tiles outlines (or whatever that is):
![naev-glitch](https://cloud.githubusercontent.com/assets/12054457/19907989/7828849e-a081-11e6-8172-894d4613b711.jpg)
The text was updated successfully, but these errors were encountered: