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

How to pass GL_BYTE to vertex shader?

5 posts in this topic

Hello,

 

If I have an array of 3 bytes per vertex - which I'm padding to 4 bytes to keep each vertex data in a 4-byte word - and pass it down to the vertex shader as a GL_UNSIGNED_BYTE data type, how does it appear in the shader? Does it get automatically converted into 4 floats? In other words, can I use the data in the shader as a vec4?

 

Also, will the float be normalize between 0. and 1., or will it be converted into a number from 0. to 255.?

 

If anybody has a link with a reference on how these non-integer, non-float data are passed down to the vertex shader I would appreciate it.

 

Thanks.

0

Share this post


Link to post
Share on other sites

Thanks. I guess all I need to do is to normalize the attributes and they will show up as 4 floats in the range [0.,1.].

0

Share this post


Link to post
Share on other sites

To answer this question, we'd have to look at glVertexAttribPointer's prototype:

void glVertexAttribPointer(GLuint index, GLint size, GLenum type, GLboolean normalized, GLsizei stride, const GLvoid * pointer);

 

The size and type parameters will tell the shader the datatype, and how many elements of that same datatype will be aligned in memory from address your provide in the pointer parameter. The normalized parameter specifies whether the datatype should be passed in using its current value if set to GL_FALSE, or whether it should be scaled down to its datatype's max constraints (yielding a value between 0.0 and 1.0) with GL_TRUE.

 

In this case, you're sending 4 "unsigned char" datatypes, and correctly specifying them as GL_UNSIGNED_BYTE. Setting normalized to GL_FALSE, they should remain as their current whole numbers (from 0 to 255). Setting normalize to GL_TRUE should scale each color component by dividing by 127.0f.

 

That's at least been my experience. I hope this helps!

Edited by Vincent_M
0

Share this post


Link to post
Share on other sites

Vincent,

 

Thanks! It does help. But I do have a few more questions:

 

If I'm passing the data as a "generic" Attribute and I will use it in the code as a normal vector, and it's being passed as GL_BYTE (i.e., as  SIGNED byte), will setting normalize to GL_TRUE divide by 127.0f or 255.0f? From what I understand, it will do the right thing if it's a SIGNED byte and divide it by 127. And if it is an attribute that will be used as a color and it's passed down as GL_UNSIGNED_BYTE, then it should be divided by 255. Right?

 

Thanks again.

0

Share this post


Link to post
Share on other sites

You are correct in both cases: GL_BYTE, should divide by 127.0f for your normal, and GL_UNSIGNED_BYTE should divide by 255.0f. Now, you may want to normalize your vertex normal once again in your shader for better accuracy if you're storing the data as an unsigned char per component if your lighting doesn't seem right. If you're doing per-fragment lighting, I have seen tutorials online suggesting that the normal should be re-normalized in the fragment shader since the normal interpolation will skew the fragment's incoming normal's magnitude.

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