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

Author Topic: Internal OpenGL call failed in Texture.cpp  (Read 3196 times)

0 Members and 2 Guests are viewing this topic.

Salva_R

  • Newbie
  • *
  • Posts: 5
    • View Profile
Internal OpenGL call failed in Texture.cpp
« on: June 13, 2014, 06:51:35 pm »
Hi guys, I'm new around here, I've finally managed to set up SFML and Visual Studio 2013 and loaded a texture/image from a file succesfuly, but I get a weird OpenGL error message on execution, it shows the message after the texture is loaded from an image:



The application still works and the texture is loaded and drawed, but I get that error message every loop iteration.

It has something to do with the atigktxx.dll, which I have in the Debug folder, since it wasn't showing the error before copying the .dll in the debug folder.

Any idea about what can it be or how can I track it down?

Thanks!

Salva_R

  • Newbie
  • *
  • Posts: 5
    • View Profile
Re: Internal OpenGL call failed in Texture.cpp
« Reply #1 on: June 13, 2014, 07:13:18 pm »
Solved: Apparently I'm using OpenGL 1.1 due to some problems with my drivers, I guess I can't use this computer to develop games..

eXpl0it3r

  • SFML Team
  • Hero Member
  • *****
  • Posts: 11029
    • View Profile
    • development blog
    • Email
AW: Internal OpenGL call failed in Texture.cpp
« Reply #2 on: June 13, 2014, 10:51:18 pm »
Did you make sure you have a driver installed and it's up to date?
Official FAQ: https://www.sfml-dev.org/faq.php
Official Discord Server: https://discord.gg/nr4X7Fh
——————————————————————
Dev Blog: https://duerrenberger.dev/blog/

Salva_R

  • Newbie
  • *
  • Posts: 5
    • View Profile
Re: Internal OpenGL call failed in Texture.cpp
« Reply #3 on: June 14, 2014, 09:59:18 pm »
Solved: Apparently I'm using OpenGL 1.1 due to some problems with my drivers, I guess I can't use this computer to develop games..

Did you make sure you have a driver installed and it's up to date?

I thought I did that's why I posted here, but it seems it ain't so.