FBO quirks (no FBO in windowed mode, black screen when resolution is different from desktop)

[dtugend]

Hi

I don't quite understand why you guys use FBO (when not using -nofbo and having OpenGL 3.x available).

Is it Frame Buffer Object?
If so why you use it?

• You don't use it in windowed mode it seems. Why?
• When using a fullscreen resolution different from the desktop resolution the screen will go black for the attached hardware setups (2 examples, one being an NVIDA card, the other being AMD):
  https://gist.github.com/ripieces/5653288
  (A resolution the same as the desktop resolution will work though it seems.)

To be honest I wouldn't mind if that FBO feature would vanish again :)

[ghost]

You don't use it in windowed mode it seems. Why?

Why do you think so?

When using a fullscreen resolution different from the desktop resolution the screen will go black for the attached

might be related with #834

[dtugend]

You don't use it in windowed mode it seems. Why?

Why do you think so?

Because atm HLAE doesn't handle Half-Life's FBO usage, which results in the buffer being cleared when the FBO is not attached yet again (upon SwapBuffers), which in turn results in distorted images (because the buffer is not cleared).
This doesn't happen in windowed mode (which most HLAE users use), so I think they are not using FBO then. If windowed mode would use FBO, then the images should have the same problems like in fullscreen with FBO.

might be related with 834

Yes, not sure if I should close my issue or not, maybe one open issue is enough.
I don't know, I'll leave it open for now, if the admins decide it's related and close it that will be fine with me.

[alfred-valve]

We use it in fullscreen to add support for a full screen anti-alias pass using optimal driver paths (i.e make it fast). It isn't in windowed mode because the backbuffer and in-game resolution match in that case and don't need the intermediate FBO for the scale and resolve step.