• 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

Implicit conversion errors

3 posts in this topic



while testing my generated shaders in OpenGL-mode on my main , I noticed that there are an aweful lot of conversion errors coming from conversion completely legal in HLSL, and on another PC, only that one seems to have some issues with this. I am aware that the GLSL-compiler is a little sensitive on most machines, but is there any way to bring him to allow those implicit conversion, for example float to vec4? Example pixel shader that produces this problem:

in float indepth;
out vec4 outdepth;

void main()

       outdepth = indepth;


0(5) : error C7011: implicit cast from "float" to "vec4"

I'd hate having to rewrite all my shaders all over again (litterally every single one of them has one or more such errors), and I'd also hate having to write float4(indepth, indepth, indepth, 1.0f); everywhere for returning the single value... any ideas/suggestions?

Edited by Juliean

Share this post

Link to post
Share on other sites

Nothing legal about that, im afraid smile.png


However, you can certainly use some of the constructors of vec4:

vec4 vector(float); --> (float, float, float, float)


In your case it would turn out like this:

outdepth = vec4(indepth);


Not sure why you would spend 4 channels saving the same value, though.

I'm seeing you are expecting the value (f, f, f, 1.0)... if HLSL really does this, then they are in the wrong. Bad design decision!


I guess you're just stuck with vec4(vec3(indepth), 1.0f);


Also, admit it: It's not much work. :P

Edited by Kaptein

Share this post

Link to post
Share on other sites

In your case it would turn out like this:

outdepth = vec4(indepth);

Not sure why you would spend 4 channels saving the same value, though.

I'm seeing you are expecting the value (f, f, f, 1.0)... if HLSL really does this, then they are in the wrong. Bad design decision!


Ok, if that works I'll try it out, hopefully it compiles to float4(in.depth) correctly in HLSL to. No, HLSL doesn't convert this to (f, f, f, 1.0f), but since like this shader is being used to render to a target without an alpha channel and/or with blending disabled, it doesn't make much of a difference, or is there some disadvantage in doing so regarding shader instructions?




Also, admit it: It's not much work. tongue.png


It isn't for new shaders I'm going to write, I give you that. but for my 25 shader I currently have, it gets quite abnoxious. The hardest part actually is finding out which line belongs to the error message in my generated shaders biggrin.png




The problem is that some drivers stricly follow the spec, whereas some other drivers are relaxed and allow what should technically be erroneous code to work.


So am I right to assume that unlike the HLSL-compiler that can e.g. precompile shaders on any GPU and use it on any other, the GLSL code is specific to the GPU it was compiled on?




This is actually an extremely evil business tactic -- for example, imagine a dev who builds a game on a "relaxed" nVidia driver, unknowingly writing invalid GLSL code. They then release their game to the world, and some players with AMD cards report that the game crashes. The public is then given the perception that AMD has buggy drivers, when actually the cause of the problem was invalid nVidia drivers! They're abusing devs as pawns in a war to undermine confidence in their competitors. Just say no tongue.png


Wow, that is evil indeed. Well, in this case it was a Geforce 780 Gtx Ti that was causing problems, now if someone came to declare nVidias current flagships driver as faulty due to this reason, that would be bad for buisness for sure biggrin.png




outdepth = (indepth).xxxx;


Ah sure, I've already used stuff like that a few times in my HLSL shaders like for projecting the skysphere to the far plane with .xyzz. If it doesn't work in GLSL it's only halfway bad, before generating my shaders I'm already parsing all functions, with a bit of work I should be able to get him to recognize this pattern and convert it to vec4(indepth) too. Man, really I don't want to see the amount of stuff simply not working in the GLSL version after I got everything to compile :/


EDIT: Damn, now I've got something thats really annyoing: So HLSL has the saturate()-function, which pretty much equals out to clamp(... ,0.0f, 1.0f). In GLSL. So decided to support the saturate-function in my shader files, and parse them to clamp() in GLSL. Only problem: When I clamp a vec3 or vec4, I get the damn conversion error. I don't process or store the exact types of all variables, so there is no way for me to know whether the argument of saturate(...) actually is float, or any of the vector types. I quess I'll have to specify the type in the saturate function then, like saturate2 or saturate4, but I'm uncertain how much work it would be, and whether or not it would be better to actually store type information for all variables/functions right away...


EDIT2: Oh, nevermind, clamp seems to be more lenient, I just had to convert the result of the saturate/clamp.

Edited by Juliean

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

  • Similar Content

    • By Toastmastern
      So it's been a while since I took a break from my whole creating a planet in DX11. Last time around I got stuck on fixing a nice LOD.
      A week back or so I got help to find this:
      In general this is what I'm trying to recreate in DX11, he that made that planet LOD uses OpenGL but that is a minor issue and something I can solve. But I have a question regarding the code
      He gets the position using this row
      vec4d pos = b.var.vec4d["position"]; Which is then used further down when he sends the variable "center" into the drawing function:
      if (pos.len() < 1) pos.norm(); world::draw(vec3d(pos.x, pos.y, pos.z));  
      Inside the draw function this happens:
      draw_recursive(p3[0], p3[1], p3[2], center); Basically the 3 vertices of the triangle and the center of details that he sent as a parameter earlier: vec3d(pos.x, pos.y, pos.z)
      Now onto my real question, he does vec3d edge_center[3] = { (p1 + p2) / 2, (p2 + p3) / 2, (p3 + p1) / 2 }; to get the edge center of each edge, nothing weird there.
      But this is used later on with:
      vec3d d = center + edge_center[i]; edge_test[i] = d.len() > ratio_size; edge_test is then used to evaluate if there should be a triangle drawn or if it should be split up into 3 new triangles instead. Why is it working for him? shouldn't it be like center - edge_center or something like that? Why adding them togheter? I asume here that the center is the center of details for the LOD. the position of the camera if stood on the ground of the planet and not up int he air like it is now.

      Full code can be seen here:
      If anyone would like to take a look and try to help me understand this code I would love this person. I'm running out of ideas on how to solve this in my own head, most likely twisted it one time to many up in my head
      Thanks in advance
    • By fllwr0491
      I googled around but are unable to find source code or details of implementation.
      What keywords should I search for this topic?
      Things I would like to know:
      A. How to ensure that partially covered pixels are rasterized?
         Apparently by expanding each triangle by 1 pixel or so, rasterization problem is almost solved.
         But it will result in an unindexable triangle list without tons of overlaps. Will it incur a large performance penalty?
      B. A-buffer like bitmask needs a read-modiry-write operation.
         How to ensure proper synchronizations in GLSL?
         GLSL seems to only allow int32 atomics on image.
      C. Is there some simple ways to estimate coverage on-the-fly?
         In case I am to draw 2D shapes onto an exisitng target:
         1. A multi-pass whatever-buffer seems overkill.
         2. Multisampling could cost a lot memory though all I need is better coverage.
            Besides, I have to blit twice, if draw target is not multisampled.
    • By mapra99

      I am working on a recent project and I have been learning how to code in C# using OpenGL libraries for some graphics. I have achieved some quite interesting things using TAO Framework writing in Console Applications, creating a GLUT Window. But my problem now is that I need to incorporate the Graphics in a Windows Form so I can relate the objects that I render with some .NET Controls.

      To deal with this problem, I have seen in some forums that it's better to use OpenTK instead of TAO Framework, so I can use the glControl that OpenTK libraries offer. However, I haven't found complete articles, tutorials or source codes that help using the glControl or that may insert me into de OpenTK functions. Would somebody please share in this forum some links or files where I can find good documentation about this topic? Or may I use another library different of OpenTK?

    • By Solid_Spy
      Hello, I have been working on SH Irradiance map rendering, and I have been using a GLSL pixel shader to render SH irradiance to 2D irradiance maps for my static objects. I already have it working with 9 3D textures so far for the first 9 SH functions.
      In my GLSL shader, I have to send in 9 SH Coefficient 3D Texures that use RGBA8 as a pixel format. RGB being used for the coefficients for red, green, and blue, and the A for checking if the voxel is in use (for the 3D texture solidification shader to prevent bleeding).
      My problem is, I want to knock this number of textures down to something like 4 or 5. Getting even lower would be a godsend. This is because I eventually plan on adding more SH Coefficient 3D Textures for other parts of the game map (such as inside rooms, as opposed to the outside), to circumvent irradiance probe bleeding between rooms separated by walls. I don't want to reach the 32 texture limit too soon. Also, I figure that it would be a LOT faster.
      Is there a way I could, say, store 2 sets of SH Coefficients for 2 SH functions inside a texture with RGBA16 pixels? If so, how would I extract them from inside GLSL? Let me know if you have any suggestions ^^.
    • By KarimIO
      EDIT: I thought this was restricted to Attribute-Created GL contexts, but it isn't, so I rewrote the post.
      Hey guys, whenever I call SwapBuffers(hDC), I get a crash, and I get a "Too many posts were made to a semaphore." from Windows as I call SwapBuffers. What could be the cause of this?
      Update: No crash occurs if I don't draw, just clear and swap.
      static PIXELFORMATDESCRIPTOR pfd = // pfd Tells Windows How We Want Things To Be { sizeof(PIXELFORMATDESCRIPTOR), // Size Of This Pixel Format Descriptor 1, // Version Number PFD_DRAW_TO_WINDOW | // Format Must Support Window PFD_SUPPORT_OPENGL | // Format Must Support OpenGL PFD_DOUBLEBUFFER, // Must Support Double Buffering PFD_TYPE_RGBA, // Request An RGBA Format 32, // Select Our Color Depth 0, 0, 0, 0, 0, 0, // Color Bits Ignored 0, // No Alpha Buffer 0, // Shift Bit Ignored 0, // No Accumulation Buffer 0, 0, 0, 0, // Accumulation Bits Ignored 24, // 24Bit Z-Buffer (Depth Buffer) 0, // No Stencil Buffer 0, // No Auxiliary Buffer PFD_MAIN_PLANE, // Main Drawing Layer 0, // Reserved 0, 0, 0 // Layer Masks Ignored }; if (!(hDC = GetDC(windowHandle))) return false; unsigned int PixelFormat; if (!(PixelFormat = ChoosePixelFormat(hDC, &pfd))) return false; if (!SetPixelFormat(hDC, PixelFormat, &pfd)) return false; hRC = wglCreateContext(hDC); if (!hRC) { std::cout << "wglCreateContext Failed!\n"; return false; } if (wglMakeCurrent(hDC, hRC) == NULL) { std::cout << "Make Context Current Second Failed!\n"; return false; } ... // OGL Buffer Initialization glClear(GL_DEPTH_BUFFER_BIT | GL_COLOR_BUFFER_BIT); glBindVertexArray(vao); glUseProgram(myprogram); glDrawElements(GL_TRIANGLES, indexCount, GL_UNSIGNED_SHORT, (void *)indexStart); SwapBuffers(GetDC(window_handle));  
  • Popular Now