Warning: There was an OpenGL error: #1282

Sparrow Forum » Troubleshooting

Warning: There was an OpenGL error: #1282

(39 posts) (13 voices)

Started 1 year ago by straydogstrut
Latest reply from janh

Tags:

OpenGL

12 Next »

straydogstrut
Administrator

Erm suddenly started getting this error when I run my game. It plays as normal except a tween that's meant to happen at the start doesn't happen. However, I have confirmed that method is getting called and since it happens when that scene is loaded it plays fine at other times (so presumably its a side effect of the warning message).

I wasn't even working in that class at all - i've been fiddling around re my other question - so don't know why this warning has suddenly started appearing. I've actually removed the class I was working on completely and it's still showing the error. Although Google suggested something to do with ATI Cards, the Demo project still runs fine so it seems to be something to do with my project. I would post code but nothing has been changed in the classes remaining.

Posted 1 year ago #
Durrza
Member

That is binding an invalid texture, i reckon what you are trying to animate has been released already.

Posted 1 year ago #
Daniel
Primary Feather

Hm, that's difficult to say! As far as I found out, the error is named "GL_INVALID_OPERATION", which, well, doesn't say much *g*. I agree with Durrza, it's likely that a texture that is still in use has been dealloc'ed too early.

To get closer to the root of the problem, you could copy the error-checking code in "SPRendering.m" to many more places in that file (e.g. at the end of every render method), and add a breakpoint when an error is found. Then you'll see which object is being rendered when the error first appears. It's likely that there's some problem with this object or its texture.

Posted 1 year ago #
enbr
Moderator

Hi, I am also having this issue. I am not doing anything out of the ordinary.

UPDATE: I tried to see if the same issue happened on the demo and it didn't. I think it has something to do with the Sparrow source or the sodeso.nl templates because the problem occurs with a new template. At least it's not my code.

UPDATE 2: I also found these warnings when I use the templates, maybe the two problems are related.
The 'sparrowView' outlet of 'Untitled App Delegate' is connected to 'View' but 'sparrowView' is no longer defined on AppDelegate.
The 'window' outlet of 'Untitled App Delegate' is connected to 'Window' but 'window' is no longer defined on AppDelegate.

Posted 1 year ago #
Daniel
Primary Feather

Hi Enbr,

so you're getting "OpenGL error: #1282"? Could you describe when it started appearing?

Posted 1 year ago #
Kayhan
Moderator

I've been getting this error as well. It appears even when there are no textures or images in game.m.
It hasn't affected my game (yet...) so I'm not too worried. Still it would be nice if it could go.

Posted 1 year ago #
Daniel
Primary Feather

Could someone perhaps create a small demo project for me that shows that problem? I haven't seen this issue before!

Thanks in advance!!

Posted 1 year ago #
enbr
Moderator

Hi Daniel. I'm not sure when it started, but I didn't see it until recently.
Here is a demo project. It is an unmodified project from the sodeso templates and sparrow 1.0
http://dl.dropbox.com/u/3656129/Demo.zip

Posted 1 year ago #
Daniel
Primary Feather

Thanks a lot enbr, I will have a look at it!!

Posted 1 year ago #
enbr
Moderator

Is anyone else having this problem?

Posted 1 year ago #
ronaldmathies
Moderator

I'll also have a look at the demo project this evening, (don't have a mac @ work )

Posted 1 year ago #
scorpion_hub
Member

I get that too, but only when compiling in Debug mode, it doesn't appear on the Release setting.
I don't get it on the demo project.

Posted 1 year ago #
scorpion_hub
Member

I got it reproduced to setting the framerate in the applications become active callback:

- (void)applicationDidBecomeActive:(UIApplication *)application { sparrowView.frameRate = 30; [sparrowView start]; }

that will cause the error and the demo isn't doing that - there is everything set in
applicationDidFinishLaunching.

Posted 1 year ago #

scorpion_hub
Member

Well I suppose that's the problem - setting the Framerate in the active/inactive notifications - that's introduced for some pause behavior i can't remember at the moment.
(I think it was discussed here in the forum)

So the solution is quite simple:

1. set the framerate and then start the engine like this:

- (void)applicationDidFinishLaunching:(UIApplication *)application
{
    SP_CREATE_POOL(pool);

    [SPStage setSupportHighResolutions:YES];

    Game *game = [[Game alloc] initWithWidth:320.0f height:480.0f];
    sparrowView.stage = game;
    sparrowView.frameRate = 30;
    [sparrowView start];

    [window makeKeyAndVisible];
    [game release];
    [SPAudioEngine start];

    SP_RELEASE_POOL(pool);
}

2. Ask if the engine is already running in become active notification like this:

- (void)applicationDidBecomeActive:(UIApplication *)application
{
    if(![sparrowView isStarted])
    {
        sparrowView.frameRate = 30;
        [sparrowView start];
    }
}

3. In become inactive notification, first stop the engine and then set the framerate:

- (void)applicationWillResignActive:(UIApplication *)application
{
    [sparrowView stop];
    sparrowView.frameRate = 5;
}

After implementing this changes, the games behaves as before - but without showing the error.

Posted 1 year ago #

Mik
Member

scorpion_hub's solution worked for me, tnx for sharing!

Posted 1 year ago #
ronaldmathies
Moderator

Thanx for finding the issue scorpion_hub, i have also changed the Sparrow Templates. I'll need to do some testing to see if everything is still working fine but i hope to release it somewhere in the next few days...

Christmas is killing my inner developer

Posted 1 year ago #
Daniel
Primary Feather

Scorpion_hub, thanks a lot for your efforts, and for posting the solution! You saved me and ronald a lot of time =)

And Ronald, thanks for updating the templates!! I know what you mean, I'm extremely busy as well ... I hope it will get more calm after Christmas

Anyway, I will have a closer look at this, to see if I can prevent an error even if the code is called in that order.

Posted 1 year ago #
Daniel
Primary Feather

OK, the root of the reason was that this code (setting the frame rate) triggered rendering the stage before OpenGL was properly initialized. I fixed this now; the render method is aborted in such a case.

Posted 1 year ago #
ronaldmathies
Moderator

Nice finding, can imagine it was hard to track down.

Posted 1 year ago #
straydogstrut
Administrator

I just wanted to thank everyone for their efforts in getting to the bottom of this!

Sorry for the late response: i've had a long hiatus from my project over the Christmas break (and the stressful return to work in the new year) so it's nice to come back to a solution. Unfortunately I had started porting my code over to a completely new project after updating Sparrow to 1.1 anyway, hoping to avoid the error this time around, but it's been a good exercise in cleaning up my code and I can sleep easy, knowing what caused the error in the first place.

I hope you all had a nice Christmas and here's wishing you all the best in the new year.

Posted 1 year ago #
Daniel
Primary Feather

Thanks for reporting back on that! That bug should not pop up any more, hopefully.
I wish you all the best for the new year, too!

Posted 1 year ago #
evilliam
Member

I get this error also, but I expected it and am not worried.
The reason I get it is that due to my project's setup and the time it takes for sparrow to initialize, the game is created and the elements laid out *before* the sparrow view is added to the main window. So I get the opengl error.
If anyone else does anything similar (with their transitions etc) then maybe this will help.

On another note, how do other people handle putting a complex-ish Sparrow app into the workflow of an existing cocoa touch/uikit project? Multithreading?

Posted 1 year ago #
Daniel
Primary Feather

Hm, do you get the error with Sparrow 1.1, or are you using 1.0? Because I changed the internals of SPView a little to avoid this error. I could not reproduce it any longer with that version -- that does not mean that there might not be a way around that, though

Concerning the other question: in my games, there was always only one full screen SPView, or a full screen "basic" UIView, but never both at the same time. I have experimented a little with that, though, and it was not a problem to display other UIView objects on top of Sparrow. In theory, you should even be able to have two SPViews (+ their stages) at the screen simultaneously -- but I have not tried that yet *g*. I have not done any multithreading, though -- Sparrow itself is not thread-safe.

Posted 1 year ago #
freerunnering
Moderator

In theory, you should even be able to have two SPViews (+ their stages) at the screen simultaneously.

A SPView really represents the OpenGL/OpenAL systems, so every time you instantiate one it will set up those systems, and tear them down when you delete it. Because OpenGL can only render to a single surface and it only has one shared instance, you shouldn't (and can't) have more than one SPView at a time during the lifetime of your app.

Posted 1 year ago #
Daniel
Primary Feather

Oha, where is this text from? I cannot remember writing that! *g*

Posted 1 year ago #
Daniel
Primary Feather

Well, OpenGL can have different contexts, and you can switch between those contexts. An SPView holds such a context. However, as I have never tried that with the SPView (and I don't see a real use-case for that anyway), you will most probably be right, because nothing works at first try *ggg*.

Posted 1 year ago #
evilliam
Member

I'm using 1.0 and I'd made some changes to the source code (I know I shouldn't have been hacking around in there) so haven't tried 1.1
I'm not rendering the Sparrow view at the same time as other views. It's more the transition in my viewcontroller from the uikit menu to the sparrow view. As the Sparrow view takes a while to initialize on older phones I show a loading graphic before the crossfade of views, and this means the openGL context isn't properly initialized when I initialize Sparrow. The error is traced but it doesn't seem to affect the app performance.

Posted 1 year ago #
Daniel
Primary Feather

Ah, OK, thanks for the info!! Yes, the error should not have any negative side-effects. As soon as OpenGL is initialized correctly, everything will continue normally.

Posted 1 year ago #
evilliam
Member

I have suddenly started to have issues with this whereby openGL isn't actually ever initialized correctly. Weirdly only on iPad.
"failed to make complete framebuffer object" is called before the 1282 error runs on a loop.
Again, this is with Sparrow 1.0

Would switching to 1.1 alleviate this bug? I've hacked around it by making sure I'm not creating the sparrow elements before they are attached to the window.

Posted 1 year ago #
Daniel
Primary Feather

Liam, it would be great if you could try it with Sparrow 1.1 and report back if this removes the problem!

Posted 1 year ago #

RSS feed for this topic

12 Next »

Reply »

You must log in to post.