Welcome, Guest. Please login or register. Did you miss your activation email?

Author Topic: Debugging a text problem - 'invisible' text  (Read 14580 times)

0 Members and 3 Guests are viewing this topic.

Qix

  • Full Member
  • ***
  • Posts: 139
  • I am Qix!
    • View Profile
    • Natoga Technologies
Re: Debugging a text problem - 'invisible' text
« Reply #30 on: November 20, 2012, 10:45:25 pm »
They are. But the context in which they are used is different. And it's enough to exhibit a strange driver bug. Don't try to understand, there's nothing to understand. Graphics driver bugs are mystical.

So should I file a bug report with ATI? I need a fix for this :P Is there any way to modify the text class to fix this? I've been sitting here twiddling my thumb for a week and a half and I'm like a crack addict on withdrawals I'm so desperate.

I don't care if I have to modify SFML itself for this project - what can I do to fix this now while waiting for a bugfix that might take months? This makes me upset seeing as how text works in every other OpenGL application I use, so it can't all be a driver bug.
« Last Edit: November 20, 2012, 10:47:23 pm by Qix »
~ Qix
Creator of Rippl Studio
Code: [Select]
<danharibo> iostream: I don't do enough drugs to think that's a good idea.

Laurent

  • Administrator
  • Hero Member
  • *****
  • Posts: 32498
    • View Profile
    • SFML's website
    • Email
Re: Debugging a text problem - 'invisible' text
« Reply #31 on: November 20, 2012, 10:55:55 pm »
All you can do is to find what makes your code so special compared to the other examples that work. Once you've found that, you'll see if a workaround can be found.

Have you tried older versions of the driver? It may be the easiest solution for you, if you can find a version which works.
Laurent Gomila - SFML developer

Qix

  • Full Member
  • ***
  • Posts: 139
  • I am Qix!
    • View Profile
    • Natoga Technologies
Re: Debugging a text problem - 'invisible' text
« Reply #32 on: November 20, 2012, 11:01:27 pm »
All you can do is to find what makes your code so special compared to the other examples that work. Once you've found that, you'll see if a workaround can be found.

Have you tried older versions of the driver? It may be the easiest solution for you, if you can find a version which works.

None of the examples work. That is the problem.

I'll try older versions of the driver.
~ Qix
Creator of Rippl Studio
Code: [Select]
<danharibo> iostream: I don't do enough drugs to think that's a good idea.

Laurent

  • Administrator
  • Hero Member
  • *****
  • Posts: 32498
    • View Profile
    • SFML's website
    • Email
Re: Debugging a text problem - 'invisible' text
« Reply #33 on: November 20, 2012, 11:04:23 pm »
You mean that sf::Text never works on your machine? So it's even simpler, just find what's different between sf::Text and sf::Sprite.
Laurent Gomila - SFML developer

Qix

  • Full Member
  • ***
  • Posts: 139
  • I am Qix!
    • View Profile
    • Natoga Technologies
Re: Debugging a text problem - 'invisible' text
« Reply #34 on: November 20, 2012, 11:13:22 pm »
You mean that sf::Text never works on your machine? So it's even simpler, just find what's different between sf::Text and sf::Sprite.

I thought sf::Text implemented sf::Sprite?
~ Qix
Creator of Rippl Studio
Code: [Select]
<danharibo> iostream: I don't do enough drugs to think that's a good idea.

Laurent

  • Administrator
  • Hero Member
  • *****
  • Posts: 32498
    • View Profile
    • SFML's website
    • Email
Re: Debugging a text problem - 'invisible' text
« Reply #35 on: November 20, 2012, 11:15:17 pm »
Quote
I thought sf::Text implemented sf::Sprite?
Nop, every high-level class directly uses a vertex array internally.
Laurent Gomila - SFML developer

Qix

  • Full Member
  • ***
  • Posts: 139
  • I am Qix!
    • View Profile
    • Natoga Technologies
Re: Debugging a text problem - 'invisible' text
« Reply #36 on: November 21, 2012, 11:30:50 pm »
Quote
I thought sf::Text implemented sf::Sprite?
Nop, every high-level class directly uses a vertex array internally.

Aha, that makes sense.
~ Qix
Creator of Rippl Studio
Code: [Select]
<danharibo> iostream: I don't do enough drugs to think that's a good idea.