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

Game Data Format?

9 posts in this topic

May be some thing relative to DirectX. But does a standard useful game data format consist of typical elements like the .x format?
These include

Frame Transformation
Vertex Data
Index Data
Face Data
Animation
Duplicate Vertex Data
Skin Info
Skin Weights
Material
Texture info

Can these fully "describe" a scene or even the game as a whole and it covers every aspects of 3D games like normal maps, gloss maps etc
Just in other words, is this data enough?
Thanks
Jack
0

Share this post


Link to post
Share on other sites

For the most complex games there is no such thing as “enough”.

Your list is enough for most typical games, but you really need to base your format off what you will actually need.  That part becomes obvious when you start to think about extreme cases such as realistic skin rendering.

There is also no reason you can’t add things to your format later when you do need it, so it just makes sense to start and small add things as you realize the need.

 

3D files are not typically meant to be used for whole scenes—they are meant to be individual models within the scene.

But sometimes it is easier to make cinematic sequences just using one file.

 

It also makes more sense to separate the data into multiple types of files instead of trying to make one gigantic format unless your goal is actually to make an interchange format such as COLLADA™ or Autodesk® FBX® (in which case you should say so).

It would be better to have one file format for models, one for animations, one for cameras, etc.

 

 

L. Spiro

1

Share this post


Link to post
Share on other sites
You've managed to cover a large part of the 3D graphics side.

Do you intend to include VFX and particle systems?
Do you intend to include audio? If so, how do you intend to manage all those clips?
Do you intend to combine multiple object in maps within a scene?
What about physics or collision detection/response data in a scene?

There is much more data involved than just raw graphics meshes.
1

Share this post


Link to post
Share on other sites

Because the author of the original 3D content copied and pasted an object.  This happens frequently with car wheels, shoes, gloves, eyes, etc.

You should merge them into one vertex buffer and only use that.

 

 

L. Spiro

0

Share this post


Link to post
Share on other sites
Because the author of the original 3D content copied and pasted an object.  This happens frequently with car wheels, shoes, gloves, eyes, etc.
You should merge them into one vertex buffer and only use that.
 
 
L. Spiro

Hi Spiro,
I beg your pardon, I actually meant the VertexDuplicationIndices in the x file format used in Direct3D?
I should have been more specific.
Thanks
Jack
0

Share this post


Link to post
Share on other sites
You've managed to cover a large part of the 3D graphics side.

Do you intend to include VFX and particle systems?
Do you intend to include audio? If so, how do you intend to manage all those clips?
Do you intend to combine multiple object in maps within a scene?
What about physics or collision detection/response data in a scene?

There is much more data involved than just raw graphics meshes.

Your ideas are neat. But why do we have offline particle data? We have a position and velocity etc but they are dynamic!
The idea of audio is quite good
Let me know
0

Share this post


Link to post
Share on other sites
why do we have offline particle data? We have a position and velocity etc but they are dynamic!
They are dynamic at run-time but you have to define:
  • A range of initial velocities.  Starting velocities will be chosen randomly within this range.
  • A cone of possible directions.
  • A minimum and maximum lifetime.
  • A range of colors.
  • The starting time when they should be emitted and an ending time when they should stop being emitted.
  • The image or images they will use during their lifetimes.
  • A range of fade-in and fade-out times.
  • A range of gravity values.
  • 100 other things.

L. Spiro Edited by L. Spiro
0

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