• 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
AquaMacker

UpdateSkinnedMesh vs GPU Update

7 posts in this topic

[size=3][font=verdana,geneva,sans-serif]Hi~~~[/font][/size]

[size=3][font=verdana,geneva,sans-serif]It's a simple question...[/font][/size]

[size=3][font=verdana,geneva,sans-serif]Lock()[/font][/size]
[size=3][font=verdana,geneva,sans-serif]UpdateSkinnedMesh() vs GPU(.fx) Update Blendweigth [/font][/size]
[size=3][font=verdana,geneva,sans-serif]UnLock()[/font][/size]

[size=3][font=verdana,geneva,sans-serif]Which One is more efficient ?[/font][/size]

[size=3][font=verdana,geneva,sans-serif]So simple ? ^^a[/font][/size]
0

Share this post


Link to post
Share on other sites
The only accurate answer for questions like this is that you need to measure the performance of both options on the hardware you care about and compare the results.

Performance will vary based on details like:

- How many times per frame are you rendering the mesh?
- What GPU and CPU do you have?
- How many bones are there?
- How many vertices are there?
- Do you need to read back the results on the CPU?
- Which thread is this being calculated on?
1

Share this post


Link to post
Share on other sites
I'm going to echo Adam here and say 'depends what else you're doing.' 'Same' does not answer questions like the relative power of the GPU/CPU combination(s) installed, extra data availability requirements or additional workload.
1

Share this post


Link to post
Share on other sites
[size=3][font=verdana,geneva,sans-serif]Yes Commander ![/font][/size]

[size=3][font=verdana,geneva,sans-serif]How many times per frame are you rendering the mesh?[/font][/size]
[size=3][font=verdana,geneva,sans-serif]- 1 rendering per 1 frame[/font][/size]

[size=3][font=verdana,geneva,sans-serif]What GPU and CPU do you have?[/font][/size]
[size=3][font=verdana,geneva,sans-serif]- ATI 3870[/font][/size]
[size=3][font=verdana,geneva,sans-serif]- 2.0 core2duo[/font][/size]

[size=3][font=verdana,geneva,sans-serif]How many bones are there?[/font][/size]
[size=3][font=verdana,geneva,sans-serif]- basic biped : 30[/font][/size]

[size=3][font=verdana,geneva,sans-serif]How many vertices are there?[/font][/size]
[size=3][font=verdana,geneva,sans-serif]- 5430[/font][/size]

[size=3][font=verdana,geneva,sans-serif]Do you need to read back the results on the CPU ?[/font][/size]
[size=3][font=verdana,geneva,sans-serif]- I don't understading "read back" meaning.[/font][/size]
[size=3][font=verdana,geneva,sans-serif]- "Read back" is Loading again ?[/font][/size]
[size=3][font=verdana,geneva,sans-serif]- Answer is loading once and reuse..[/font][/size]

[size=3][font=verdana,geneva,sans-serif]Which thread is this being calculated on ?[/font][/size]
[size=3][font=verdana,geneva,sans-serif]- 1 thread[/font][/size]

[size=3][font=verdana,geneva,sans-serif]Please down answer, Sir ![/font][/size]

[size=3][font=verdana,geneva,sans-serif]I'm sorry for my veryveryvery short + rigid answer....[/font][/size]
[size=3][font=verdana,geneva,sans-serif]I wanna know just absolutely answer in common.[/font][/size]

[size=3][font=verdana,geneva,sans-serif]^^a[/font][/size]
0

Share this post


Link to post
Share on other sites
There's still no absolute answer. OK, in general terms, and everything else being equal, a GPU update is going to run much faster - maybe twice as fast or more, depending on the hardware. If however your GPU is loaded with other work and your CPU is relatively free then you'll probably want to do it on the CPU. Or if your CPU is loaded and your GPU is free then you'll want to put it on the GPU. If you can spawn an extra thread on the CPU and update in that then doing it on the CPU might get your update for free (aside from thread overhead). If you've a fast CPU but a slow GPU you might want to put it on the CPU. If you've a fast GPU but a slow CPU you'll put it on the GPU. If you're tight on constants register space or you can't do vertex texture fetches you'll consider the CPU. But drawing multiple models of the same type would mean a lot of Lock/Unlock and so on, so the GPU wins.

So like the others said, there is no right answer. You need to know what kind of environment you're running in and what the rest of the program is doing, how your GPU vs CPU usage is balancing out, where your bottlenecks are, and so on.
2

Share this post


Link to post
Share on other sites
[size=3][font=verdana,geneva,sans-serif]I just wanna know Absolutic common answer in.[/font][/size]

[size=3][font=verdana,geneva,sans-serif]My English writting skill level is very low...[/font][/size]

[size=3][font=verdana,geneva,sans-serif]I'm sorry --a[/font][/size]

[size=3][font=verdana,geneva,sans-serif]Your answer is I wanna know answer.[/font][/size]

[size=3][font=verdana,geneva,sans-serif]Thank you very much ^^a[/font][/size]

[size=3][font=verdana,geneva,sans-serif]Have a Nice DAY !!![/font][/size]
0

Share this post


Link to post
[size=3][font=verdana,geneva,sans-serif]I just wanna know Absolutic common answer.[/font][/size]

[size=3][font=verdana,geneva,sans-serif]My English writting skill level is very low...[/font][/size]

[size=3][font=verdana,geneva,sans-serif]I'm sorry --a[/font][/size]

[size=3][font=verdana,geneva,sans-serif]Your answer is I wanna know answer.[/font][/size]

[size=3][font=verdana,geneva,sans-serif]Thank you very much ^^a[/font][/size]

[size=3][font=verdana,geneva,sans-serif]Have a Nice DAY !!![/font][/size]
0

Share this post


Link to post
Share on other sites
[quote name='AquaMacker' timestamp='1328039026' post='4908133']
[size=3][font=verdana,geneva,sans-serif]I just wanna know Absolutic common answer.[/font][/size]

[size=3][font=verdana,geneva,sans-serif]My English writting skill level is very low...[/font][/size]

[size=3][font=verdana,geneva,sans-serif]I'm sorry --a[/font][/size]

[size=3][font=verdana,geneva,sans-serif]Your answer is I wanna know answer.[/font][/size]

[size=3][font=verdana,geneva,sans-serif]Thank you very much ^^a[/font][/size]

[size=3][font=verdana,geneva,sans-serif]Have a Nice DAY !!![/font][/size]
[/quote]

It's fine, we're (or at least, I'm not) not yelling at you, period, or questioning your English ability, just pointing out that you're asking for an absolute answer that doesn't exist, much like, for example, the question "How do I downsample depth?" In that case, you can get a local maximum, a local minimum or a regular, boring old mean; all are useful for different purposes and we need to know more about what else you need it for in order to give you a meaningful answer.


Since you're asking about 'readbacks,' this is simply the process of reading the skinned vertex data back onto the CPU, probably for something like physics calculations or the like. More on that in a second.

As an example of 'what else are you doing,' the use of shadow volumes is an excellent argument in favor of keeping everything CPU-side, as the actual process of getting this sort of stuff back into main memory from the GPU can be rather slow under typical game circumstances due to how the graphics driver actually goes about implementing your draw calls; generally, they're queued up into a big FIFO list behind the scenes and the GPU will need to burn through a few frames(!) worth of commands before it can be in a state where it can copy things out of VRAM. Again, the specifics of what else you're doing will influence the commands actually sent to the GPU and can in turn affect that latency. We just want some detailed information about what you plan on doing with your mesh(es) :)
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