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

EngineCoder

Members
  • Content count

    67
  • Joined

  • Last visited

Community Reputation

246 Neutral

About EngineCoder

  • Rank
    Member

Personal Information

  1. [quote name='taylorsnead' timestamp='1343777183' post='4965024'] Then set the position in the shader with: gl_Position = MVP; [/quote] No, you must multiply the vertex position with that matrix: gl_Position = MVP * a_position;
  2. I have written game/rendering engines both for fun and professionally. I don't always have a use case for my engine, but when deciding on what features I'll develop, I focus on those that are needed in games like Half-Life or Deus Ex, because some day I want to be part of a team working on something like that. In the mean time, I sometimes do small indie games using my engine so I get to learn game development and not just engine development. Doing real games using your own engine is a good way to test its power. When developing an engine, I do it in the perspective of the engine's user, and try to make everything as seamless as possible for them. First I write API calls into a tech demo, then I implement them, so it's kind of a top-down process for me.
  3. [quote name='wildboar' timestamp='1341940853' post='4957668'] I dont actually use apple tools at all. I am using a crossplatform API called marmalade which lets me code in C++ I am not sure what kind of profiling tools I can use with it as I cant even use gdebugger with it. [/quote] Xcode includes a handy tool called Instruments that can be used to find bottlenecks.
  4. [quote name='LorenzoGatti' timestamp='1337068802' post='4940312'] [CODE] tangent = (deltaP1 * deltaUV2.v - deltaP2 * deltaUV1.v) / area; bitangent = (deltaP1 * deltaUV2.u - deltaP2 * deltaUV1.u) / area; [/CODE] I don't think you can trust your UV coordinates to point in the right direction: [b]deltaUV1 [/b]and [b]deltaUV2 [/b]and [b]area[/b] can have "bad" signs and any sign change determines whether your normal (implicit from the choice of [b]tangent [/b]and [b]bitangent[/b]) points towards the front or the back. Can you explain how do you relate UV coordinates to triangle facing? [/quote] Most tutorials do it that way, like: [url="http://www.terathon.com/code/tangent.html"]http://www.terathon.com/code/tangent.html[/url]
  5. Some of my triangles render as if they're pointing away from the light. I can fix them by rotating their UV map upside down. [CODE] void Mesh::generateTangents() { for (size_t v = 0; v < m_vertices.size(); ++v) { m_vertices[ v ].tangent = Vec4( 0.0f, 0.0f, 0.0f, 0.0f ); } m_tangents.resize ( m_indices.size() ); m_bitangents.resize( m_indices.size() ); bool degenerateFound = false; for (size_t f = 0; f < m_indices.size(); ++f) { const Vec3& p1 = m_vertices[ m_indices[ f ].a ].position; const Vec3& p2 = m_vertices[ m_indices[ f ].b ].position; const Vec3& p3 = m_vertices[ m_indices[ f ].c ].position; const TexCoord& uv1 = m_vertices[ m_indices[ f ].a ].texCoord; const TexCoord& uv2 = m_vertices[ m_indices[ f ].b ].texCoord; const TexCoord& uv3 = m_vertices[ m_indices[ f ].c ].texCoord; const TexCoord deltaUV1 = uv2 - uv1; const TexCoord deltaUV2 = uv3 - uv1; const float area = (deltaUV1.u * deltaUV2.v - deltaUV1.v * deltaUV2.u); Vec3 tangent; Vec3 bitangent; if (std::fabs( area ) > 0.00001f) { const Vec3 deltaP1 = p2 - p1; const Vec3 deltaP2 = p3 - p1; tangent = (deltaP1 * deltaUV2.v - deltaP2 * deltaUV1.v) / area; bitangent = (deltaP1 * deltaUV2.u - deltaP2 * deltaUV1.u) / area; } else { degenerateFound = true; } Vec4 tangent4( tangent.x, tangent.y, tangent.z, 0.0f ); m_tangents[ f ] = tangent4; m_bitangents[ f ] = bitangent; } if (degenerateFound) { std::cout << std::endl << "Warning: Degenerate UV map in " << name << ". Author needs to separate texture points in mesh's UV map." << std::endl; } m_vbitangents.resize( m_vertices.size() ); // For every vertex, check how many faces touches // it and calculate the average of their tangents. for (size_t vertInd = 0; vertInd < m_vertices.size(); ++vertInd) { Vec4 tangent( 0.0f, 0.0f, 0.0f, 0.0f ); Vec3 bitangent; for (size_t faceInd = 0; faceInd < m_indices.size(); ++faceInd) { if (m_indices[ faceInd ].a == vertInd || m_indices[ faceInd ].b == vertInd || m_indices[ faceInd ].c == vertInd) { tangent += m_tangents [ faceInd ]; bitangent += m_bitangents[ faceInd ]; } } m_vertices[ vertInd ].tangent = tangent; m_vbitangents[ vertInd ] = bitangent; } for (size_t v = 0; v < m_vertices.size(); ++v) { Vec4& tangent = m_vertices[ v ].tangent; const Vec3& normal = m_vertices[ v ].normal; const Vec4 normal4( normal.x, normal.y, normal.z, 0.0 ); // Gram-Schmidt orthonormalization. tangent -= normal4 * normal4.dot( tangent ); tangent.normalize(); // Handedness. TBN must form a right-handed coordinate system, // i.e. cross(n,t) must have the same orientation than b. const Vec3 cp = normal.cross( Vec3( tangent.x, tangent.y, tangent.z ) ); tangent.w = cp.dot( m_vbitangents[v] ) > 0.0f ? 1.0f : -1.0f; } } [/CODE] I'm calculating my bitangents in the vertex shader and multiplying them with the handedness sign. I'm transforming my camera and point light position from world space to object space by multiplying them with inverse model matrix before transforming them to tangent space. If I visualize my TBN vectors, normals are pointing away from the surface and tangents and bitangents are orthogonal. [CODE] void main() { gl_Position = u_modelViewProjectionMatrix * vec4( a_position, 1.0 ); v_texCoord = a_texCoord; vec3 bitangent = normalize( cross( a_normal, a_tangent.xyz ) ) * a_tangent.w; // .w is the handedness. mat3 toTangentSpace = mat3( a_tangent.x, bitangent.x, a_normal.x, a_tangent.y, bitangent.y, a_normal.y, a_tangent.z, bitangent.z, a_normal.z ); vec3 mDirToLight = normalize( u_lightPosition.xyz - a_position ); // Light position is in object-space. vec3 mDirToCamera = normalize( u_cameraPosition.xyz - a_position ); // Camera position is in object-space. v_dirToLight = toTangentSpace * mDirToLight; v_viewDir = toTangentSpace * mDirToCamera; } [/CODE]
  6. OpenGL

    Here's my lookat() implementation: [CODE] void Matrix::makeLookAt( const Vec3& aEye, const Vec3& aCenter, const Vec3& aUp, float* aMatrix ) { assert( aMatrix ); Vec3 forward = aCenter - aEye; forward.normalize(); Vec3 right = forward.cross( aUp ); right.normalize(); const Vec3 up = right.cross( forward ); aMatrix[ 0 ] = right.x; aMatrix[ 4 ] = right.y; aMatrix[ 8 ] = right.z; aMatrix[ 12 ] = 0; aMatrix[ 1 ] = up.x; aMatrix[ 5 ] = up.y; aMatrix[ 9 ] = up.z; aMatrix[13 ] = 0; aMatrix[ 2 ] = -forward.x; aMatrix[ 6 ] = -forward.y; aMatrix[10 ] = -forward.z; aMatrix[14 ] = 0; aMatrix[ 3 ] = aMatrix[ 7 ] = aMatrix[ 11 ] = 0.0f; aMatrix[15 ] = 1.0f; float translate[ 16 ]; Matrix::identity( translate ); translate[ 12 ] = -aEye.x; translate[ 13 ] = -aEye.y; translate[ 14 ] = -aEye.z; multiply( translate, aMatrix, aMatrix ); } [/CODE]
  7. For good up-to-date OpenGL practices try this reference: [url="http://www.arcsynthesis.org/gltut/"]http://www.arcsynthesis.org/gltut/[/url]
  8. [img]http://4.bp.blogspot.com/-WhcaGpMMYWQ/T5AcMfsOu2I/AAAAAAAAA3A/iAv_ZPwv94s/s1600/cyberjack.jpg[/img] [url="http://itunes.apple.com/us/app/cyberjack/id516673873?ls=1&mt=8"]http://itunes.apple....73873?ls=1&mt=8[/url] In Cyberjack you can shoot bots, disarm explosives, hack computers and upgrade your character with augs like stealth and shield. I made the game alone in 10 months using mostly open source tools. Any questions or feedback is appreciated!
  9. [quote name='Shashwat Rohilla' timestamp='1312536681' post='4844921'] [b][color="#ff0000"]Is XNA a game engine? [/color][color="#ff0000"]Are drivers the *.dll files which interact with the hardware?[/color][/b] [/quote] XNA is not a game engine, it's a framework. DLL files can contain many things, including drivers.
  10. [quote name='j2900' timestamp='1312487784' post='4844659'][color="#333333"] Also, as I'm new to this; is there a better format (than obj) I should be using? [/color][/quote] Production code usually uses custom file formats that are in binary and have their layout resembling the actual layout on GPU, because it's faster/easier to load. Ideally you should write exporters to popular modeling tools such as 3ds Max and Blender.
  11. How do you create your OpenGL context? You have to specify the version when creating it.
  12. In C++, there is std::map. Also, you most likely will want to do the extrusion in a vertex shader.
  13. [quote name='Palidine' timestamp='1295290683' post='4760251'] The only "trick" is that you need to name the files XXXX.mm or XXXX.cpp instead of XXX.m/XXX.c. XCode appears to easily use the file extension to figure out how to compile it [/quote] You can also configure Xcode to compile everything as Objective-C++ so you don't have to rename any files. I did this in my cross-platform engine.
  14. Integers are not automatically casted to float in shaders. You must use 1.0 instead of 1 etc.
  15. Quote:Original post by Chetanhl EDIT : regarding SDL i have been asked to use OpenGL only so GLUT & GLEW will be better i think, also i may have to work on 3D apps and SDL is 2D. SDL contains the same functionality as GLUT, and much more. It's used to set up the window, get input etc. Also, it's somewhat wrong to say that it's 2D because you can create and use an OpenGL context with it.