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

Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - Salva_R

Pages: [1]
1
General / Re: Internal OpenGL call failed in Texture.cpp
« 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.

2
General / Re: Setting SFML up in VC 2013
« on: June 13, 2014, 09:10:39 pm »
Hey, try this tutorial:
keepingupwithcode.wordpress.com/2013/11/11/getting-sfml-and-others-set-up-with-visual-studio-2013/

Please don't be posting links to tutorials unless they are actually good. Just taking a quick look through that link I can tell you already it omits information and gives false information.



Sorry, I don't mean to spread bad information; I linked it because I was having pretty much the same problems and that tutorial worked like a charm, I'll delete the comment if you find it appropiate.

3
General / Re: Internal OpenGL call failed in Texture.cpp
« 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..

5
General / 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!

Pages: [1]