• Announcements

    • khawk

      Download the Game Design and Indie Game Marketing Freebook   07/19/17

      GameDev.net and CRC Press have teamed up to bring a free ebook of content curated from top titles published by CRC Press. The freebook, Practices of Game Design & Indie Game Marketing, includes chapters from The Art of Game Design: A Book of Lenses, A Practical Guide to Indie Game Marketing, and An Architectural Approach to Level Design. The GameDev.net FreeBook is relevant to game designers, developers, and those interested in learning more about the challenges in game development. We know game development can be a tough discipline and business, so we picked several chapters from CRC Press titles that we thought would be of interest to you, the GameDev.net audience, in your journey to design, develop, and market your next game. The free ebook is available through CRC Press by clicking here. The Curated Books The Art of Game Design: A Book of Lenses, Second Edition, by Jesse Schell Presents 100+ sets of questions, or different lenses, for viewing a game’s design, encompassing diverse fields such as psychology, architecture, music, film, software engineering, theme park design, mathematics, anthropology, and more. Written by one of the world's top game designers, this book describes the deepest and most fundamental principles of game design, demonstrating how tactics used in board, card, and athletic games also work in video games. It provides practical instruction on creating world-class games that will be played again and again. View it here. A Practical Guide to Indie Game Marketing, by Joel Dreskin Marketing is an essential but too frequently overlooked or minimized component of the release plan for indie games. A Practical Guide to Indie Game Marketing provides you with the tools needed to build visibility and sell your indie games. With special focus on those developers with small budgets and limited staff and resources, this book is packed with tangible recommendations and techniques that you can put to use immediately. As a seasoned professional of the indie game arena, author Joel Dreskin gives you insight into practical, real-world experiences of marketing numerous successful games and also provides stories of the failures. View it here. An Architectural Approach to Level Design This is one of the first books to integrate architectural and spatial design theory with the field of level design. The book presents architectural techniques and theories for level designers to use in their own work. It connects architecture and level design in different ways that address the practical elements of how designers construct space and the experiential elements of how and why humans interact with this space. Throughout the text, readers learn skills for spatial layout, evoking emotion through gamespaces, and creating better levels through architectural theory. View it here. Learn more and download the ebook by clicking here. Did you know? GameDev.net and CRC Press also recently teamed up to bring GDNet+ Members up to a 20% discount on all CRC Press books. Learn more about this and other benefits here.
Sign in to follow this  
Followers 0
dpadam450

Write to FBO vs CopyTexImage

3 posts in this topic

In a forward rendering approach, these are doing the same exact thing just slightly different and I'm wondering if there would be any difference in the timing. I don't know if writes to fbo vs copying screen if one is slower or faster.



Draw to FBO
Bind FBO as texture and write to screen
Use FBO as a texture for heat/refraction shader drawing particles that refract what is on the screen


Draw to screen

Copy screen to texture

Use texture for heat/refraction shader drawing particles that refract what is on the screen

0

Share this post


Link to post
Share on other sites

In this special case I would say, that when you write to multiple targets (FBO+screen buffer), that you save bandwidth by not reading from the source buffer when using the copy operation.

 

If you like to use the copy operation, remember, that a copy operation will most likely be like a single full-screen (simple)shader pass, therefor try to add more value to the copy operation by using a customized shader. E.g. instead of a simple copy operation use a shader which downscales the image to 1/4 of the original screen size which can be used to further operations like blur, heat etc.

1

Share this post


Link to post
Share on other sites

I was talking about using glCopyTexImage2D() to a rgb buffer.  As far as I know you can't apply a shader and downsample during a copy....

0

Share this post


Link to post
Share on other sites

In terms of timing, in theory using an FBO should be faster as CopyTexImage will respecify a new texture with the appropriate dimensions, format and miplevels, then transfer the data to that new texture (CopyTexSubImage should skip the respecification step). An FBO doesn't need the additional data transfer so can save on the time required to do it.

On the other hand, changing a render target can be a time-consuming operation. It may involve a CPU/GPU synchronization (see http://www.opengl.org/wiki/Synchronization#Implicit_synchronization) which may be a bigger performance impact. If you're doing it a lot of times per frame then there may be a cutoff point beyond which the bandwidth cost of CopyTexImage (or CopyTexSubImage) is the lesser evil. (And remember that an FBO means minimum two render target changes per frame, so that's two potential synchronization points.)

On the other other hand, there are things that FBOs allow you to do that CopyTex(Sub)Image doesn't. You want multiple render targets, for example? Gotta use an FBO.

So that's a lot of "maybe"s and "might"s and whatnot. By now you should be getting the idea that there is no absolute answer to this question, and that cases can exist where either is preferable to the other, and that sometimes those cases can be implementation-dependent. So in the end we need to fall back on the time-honoured answer: benchmark, find which is best for your program, and use that.

 

(Finally, and as a historical note, Doom 3 used CopyTex(Sub)Image and didn't suffer overly much from it, but FBOs didn't exist back then so maybe that's not too relevant a point...)

Edited by mhagain
1

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now
Sign in to follow this  
Followers 0