Part of the Khronos Group
OpenGL.org

The Industry's Foundation for High Performance Graphics

from games to virtual reality, mobile phones to supercomputers

Results 1 to 4 of 4

Thread: Rendering problems with release configuration [C++] [VS2010] [GLFW]

  1. #1
    Junior Member Newbie
    Join Date
    Dec 2012
    Posts
    9

    Question Rendering problems with release configuration [C++] [VS2010] [GLFW]

    I'm using GLFW and everything has been working fine, as long as I'm using the debug configuration in VS2010.
    When switching to release, everything's still fine in the debugger. However, when I try to run the program directly using the executable I'm suddenly getting some weird rendering issues.

    This is what it's supposed to look like:


    This is what it looks like running the .exe from the release configuration (Debug is fine):


    The rendering issues are the same every time I run the program.
    It's not an issue with the textures, as it's doing the same if I use the same texture for everything.

    Does anyone have an idea what could be causing this? It only happens with the release configuration and even then only when running the .exe directly.
    I'd post some code, but I really don't know what could be relevant here. It's an awfully specific problem.
    I've never encountered a problem like this before.

  2. #2
    Senior Member OpenGL Guru Dark Photon's Avatar
    Join Date
    Oct 2004
    Location
    Druidia
    Posts
    3,124
    Looks like shadow acne. Doing shadow mapping? Add some bias.

  3. #3
    Junior Member Newbie
    Join Date
    Dec 2012
    Posts
    9
    Well, that's embarrassing...
    I found the source, it was due to a uninitialized variable.
    Thread can be closed.

  4. #4
    Junior Member Newbie
    Join Date
    Oct 2011
    Posts
    3
    Quote Originally Posted by Silverlan View Post
    Well, that's embarrassing...
    I found the source, it was due to a uninitialized variable.
    Thread can be closed.
    Yeah, I found the hard way that when results of GL app differ when you launch app in Release/Debug under MSVC and then standalone executable, its often some garbage in memory that causes it, uninitialized value being the most common reason

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •