#877 menu and osggraph texture unit conflict

to be defined
User interface

The menu system and osggraph modules have a texture unit conflict: https://sourceforge.net/p/speed-dreams/mailman/message/32438292/

(Note: I'm not an OpenGL or OSG expert, so I may be completely wrong. :)

One possible solution reworks the menu system to be compatible with osggraph. I don't agree with approach but I investigated it anyway. The menu code is in src/libs/tgfclient. The code never calls glActiveTexture() so the texture unit is GL_TEXTURE0. The code does call glTexCoord() in lots of places, which always uses GL_TEXTURE0. This blocks simply switching the menu system to another texture unit. I stopped investigating at this point since its not obvious how to proceed

Osggraph uses at least GL_TEXTURE0-3, but those are the explicitly assigned uses that I found by guessing the functions that may be used to set texture units. Texture units are also hardcoded in lots of places which is awkward. I hope Gaëtan knows exactly which units were used and where. The next big question is: does OSG use GL_TEXTURE0 by default anywhere?


Tickets: #885


  • Tom Low-Shang

    Tom Low-Shang - 2014-06-16

    The more I look at this problem, the more it looks like osggraph is completely at fault. Ssggraph uses texture unit 0 as well and it does not confict with the menu system in any way. This suggests that osggraph is not giving up resources after it it has finished with them.

  • Tom Low-Shang

    Tom Low-Shang - 2015-05-02

    Fixed by [r5994]. Please close ticket.



    Commit: [r5994]

  • Bertaux Xavier

    Bertaux Xavier - 2015-05-02

    fixed by Brian
    Please reopened if another problem is find

  • Bertaux Xavier

    Bertaux Xavier - 2015-05-02
    • status: new --> closed
    • assigned_to: rvlander --> briangr
    • Type: Task --> defect
    • Priority: --> blocker
    • Component: Graphics/OSG --> User interface

Log in to post a comment.

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:

JavaScript is required for this form.

No, thanks