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


  • Content count

  • Joined

  • Last visited

Community Reputation

123 Neutral

About Squidshire

  • Rank
  1. OpenGL

    Thanks for the suggestion. I went back to take another look. The issue seems to be that if I move the shadows back, then they will vanish entirely (the particles won't shadow themselves, but won't shadow anything else either). [url="http://i.imgur.com/NfHx7.png"]http://i.imgur.com/NfHx7.png[/url] (screenshot - ignore the "particle" text, which is part of the HUD). I suppose I could use two separate shadow maps - one for particles where the depth is offset slightly, and one for meshes where the depth remains the same.
  2. OpenGL

    I managed to fix the problem, but I have another issue. The solution: the shadows weren't being drawn as I had enabled front face culling for the rendering of shadows. Changing the order of the vertices in the geometry shader fixed it. New issue: Because the depth of the shadow is essentially the same as the depth of the particle itself, every particle will be affected by its own shadow. [url="http://i.imgur.com/UPcgl.png"]Image[/url] (ignore the "particle transparency" bit - it's part of the HUD) I've tried applying a polygon offset through glPolygonOffset (for lines, points and fill) but it only seems to affect the shadows cast by the mesh objects (not built in a geometry shader). I've also tried messing about with the gl_FragDepth (so the particle fragments would be treated as closer to the camera, and the particle shadows would be treated as being further away), but that gave no change other than the particle or its shadow completely disappearing when the depth was outside of the 0 to 1 range. I also tried changing the screen-space depth of the shadow vertices themselves. Lower offsets removed the self shadow but also displaced the positions of the shadows on other objects. [url="http://i.imgur.com/YRapE.png"]Image[/url] I then tried to draw the particles closer to the screen so that their screen-space depths would be lower than that of the shadows. Applying the offset before the projection transformation (but after applying the modelview matrix) displaced the particles according to the camera position but otherwise did not affect the shadows. Applying it after projection seemed to change the distance at which the particle could be seen but didn't change the shadow at all. What am I doing wrong? Is this issue actually possible to solve? Thanks
  3. Hi Are there any special rules regarding rendering to an FBO when there's a geometry shader involved? Context: I'm trying to implement shadow mapping in a scene which includes different types of objects being rendered in different ways: Meshes, rendered in the standard way through VBOs and shaders Point sprite particles, rendered with a vertex and fragment shader Quad particles, sent in as points but expanded to quads in a geometry shader I'm doing shadow mapping in the standard way, which involves creating a depth FBO and rendering to it the object's depths from the light's point of view. The meshes and point sprites work fine, but the depths of the geometry shader quad particles aren't being rendered to the FBO. [url="http://i.imgur.com/hxpVE.png"]Here[/url]'s the standard (non-FBO) depth buffer. Note the large circular-shaped particles in the foreground. [url="http://i.imgur.com/IJlXp.png"]Here[/url]'s the same view rendered to the FBO. Note that only the depths of the meshes and point sprite particles are drawn. My FBO is set up as follows (it's based on Chapter 7 from the [i]OpenGL 4 Shading Language Cookbook[/i]): [CODE]const bool Renderer::generateShadowMap(FBO & f, string & error) { uint depthTexID; uint width = f.getWidth(); uint height = f.getHeight(); glGenTextures(1, &depthTexID); glBindTexture(GL_TEXTURE_2D, depthTexID); glTexImage2D( GL_TEXTURE_2D, 0, GL_DEPTH_COMPONENT, width, height, 0, GL_DEPTH_COMPONENT, GL_FLOAT, NULL); float border[] = {1.0, 0.0, 0.0, 0.0}; glTexParameteri(GL_TEXTURE_2D, GL_TEXTURE_MAG_FILTER, GL_LINEAR); glTexParameteri(GL_TEXTURE_2D, GL_TEXTURE_MIN_FILTER, GL_LINEAR); glTexParameteri(GL_TEXTURE_2D, GL_TEXTURE_WRAP_S, GL_CLAMP_TO_BORDER); glTexParameteri(GL_TEXTURE_2D, GL_TEXTURE_WRAP_T, GL_CLAMP_TO_BORDER); glTexParameterfv(GL_TEXTURE_2D, GL_TEXTURE_BORDER_COLOR, border); glTexParameteri(GL_TEXTURE_2D, GL_TEXTURE_COMPARE_MODE, GL_COMPARE_REF_TO_TEXTURE); glTexParameteri(GL_TEXTURE_2D, GL_TEXTURE_COMPARE_FUNC, GL_LESS); glActiveTexture(GL_TEXTURE1); glBindTexture(GL_TEXTURE_2D, depthTexID); uint fID; glGenFramebuffers(1, &fID); glBindFramebuffer(GL_FRAMEBUFFER, fID); glFramebufferTexture2D(GL_FRAMEBUFFER, GL_DEPTH_ATTACHMENT, GL_TEXTURE_2D, depthTexID, 0); glDrawBuffer(GL_NONE); if(!checkFBOstatus(error)) { cerr << error << endl; return false; } glClearDepth(1.0); glClear(GL_DEPTH_BUFFER_BIT); glBindFramebuffer(GL_FRAMEBUFFER, 0); glActiveTexture(GL_TEXTURE0); f.setFBOID(fID); f.setTexID(depthTexID); return true; }[/CODE] The shaders that should render the depths of the quad particles are: [CODE] //VERTEX SHADER #version 400 in vec3 aPosition; in float aSize; out float gSize; uniform mat4 vWorldView; void main() { gSize = aSize; vec4 v4Vertex = vec4(aPosition.xyz, 1.0); vec4 transformedVertex = vWorldView * v4Vertex; gl_Position = transformedVertex; } //GEOMETRY SHADER #version 400 layout (points) in; layout (triangle_strip, max_vertices = 4) out; in float gSize[1]; uniform mat4 vgProjection; void main() { vec4 oPosition; float halfSize = gSize[0] * 0.5; oPosition = (vec4(-halfSize, -halfSize, 0.0, 0.0) + gl_in[0].gl_Position); gl_Position = vgProjection * oPosition; EmitVertex(); oPosition = (vec4(halfSize, -halfSize, 0.0, 0.0) + gl_in[0].gl_Position); gl_Position = vgProjection * oPosition; EmitVertex(); oPosition = (vec4(-halfSize, halfSize, 0.0, 0.0) + gl_in[0].gl_Position); gl_Position = vgProjection * oPosition; EmitVertex(); oPosition = (vec4(halfSize, halfSize, 0.0, 0.0) + gl_in[0].gl_Position); gl_Position = vgProjection * oPosition; EmitVertex(); EndPrimitive(); } //FRAGMENT SHADER - empty as depth should be written automatically #version 400 void main() { } [/CODE] Depth testing is enabled, of course. I've also tried telling the fragment shader to try to draw something to see if that makes a difference. I've run this through gDebugger which can't detect any errors at all. I've tried telling the fragment shader to actually draw things but that doesn't make a difference either. The only difference between the point sprite particles and the quad particles is the use of the geometry shader. I'm rendering both at the same time and with the same uniform values (and I've run gDebugger to make sure). I've tested this on a computer with a nVidia GTX 560 Ti with driver version (the latest, I believe, at the time of writing) and another with a Radeon Mobility HD 5650. I get the same result on both. Am I making any obvious mistakes or are there some specific things I should know about? Thanks