• Content count

  • Joined

  • Last visited

Community Reputation

860 Good

About Fiddler

  • Rank
  1. If you use the std140 layout, the uniform structure in the shader will have the same layout as the structure in your C code. This is easier to handle, since you can just update your CPU-side struct and pass it to the shader with a single call, without querying each uniform location separately.         If this is a DX10-level GPU (AMD 2xx0-4xx0 series) there is a chance that this is supported.
  2. Uniform buffer objects are a third option that can simplify uniform management, but there is a good chance that won't be supported either on older hardware. As far as I know, explicit uniform locations or glGetUniformLocation are the only other options. The OpenGL wiki appears to support this.
  3. Raw mouse input on X11/Linux

    Yes, this can be made to work. Make sure you have the correct events selected.   A complete working example can be found here: OpenTK/Platform/X11/XI2MouseKeyboard.cs. This has been tested and is working on both and XQuartz.   The source code is in C#, but most of it should be trivial to port to C or C++. Feel free to ask if you have any questions.   Edit: raw input has been pulled from SDL2 for some reason, which is rather unfortunate. You can only use regular input events (single mouse with pointer acceleration etc.)   Edit 2: do not use WarpMouse unless you really hate your users. That was necessary back in the core X11 days, due to the lack of relative motion events, but this is no longer necessary with XInput2. Do note that some devices, such as the VMware mouse driver, do not report relative motion events. Actual mice do not have this problem.
  4. I remember someone bringing up an idea about storing code in some sort of loosely-defined database, rather than plain text files. This was in GD maybe a decade ago so good luck finding a reference to the old thread, but the idea does have some merit.   Source control could operate on individual items (add class foo, rename function bar, move that code from x to z) instead of plain non-semantic text. More complicated to implement, certainly, but it would be really interesting to what new programming capabilities could arise then.     The real challenge is that this would require very tight integration between the programming language, the IDE and the source control system. It would not work with C++, but it might just be feasible with something like Go or C# (Roslyn!)
  5. glGetError

    Or simply have a debug and a release version of your application.
  6. GDI+ support on linux

    GDI+ is available on Linux through It only makes sense to use from C# - if you are using C or C++ there are much better options available.
  7. Would you Still Play Nintendo 64-Quality Games?

    That it was ;-)   Also the music.
  8. You should handle logic updates (such as camera position) at fixed update rate, not per message. Handling updates per message will result in the issue you encountered (different update rates with/without vsync, also different update rates depending on the mouse model, CPU, operating system, etc.)   If your application is sensitive to input latency, you should move either rendering or input handling to a separate thread. The latter is quite simple: create a message-only window on a background thread and use that to capture raw input (Hint: use GetMessage instead of PeekMessage on the background window to reduce its performance impact.)
  9. Make sure you are using: while (PeekMessage(...)) { } instead of if (PeekMessage(...)) { }   /psychic debugging off
  10. OpenGL OpenGL 4.5 spec is out

    The complete list of features that were added to 4.5 core: GL_ARB_clip_control GL_ARB_cull_distance GL_ARB_ES3_1_compatibility GL_ARB_conditional_render_inverted GL_KHR_context_flush_control GL_ARB_derivative_control GL_ARB_direct_state_access GL_ARB_get_texture_sub_image GL_KHR_robustness GL_ARB_shader_texture_image_samples GL_ARB_texture_barrier
  11. OpenGL OpenGL 4.5 spec is out

    DSA, finally!   C# bindings are now WIP at
  12. OpenGL Game Development with OpenGL 3.3 on Linux

    I would advise staying with Mesa, if at all possible, for your sanity. Sometimes it works, but others it can (and will) botch your system - as you found out.   Your best bet is to switch to Debian 'testing', or a different distribution that emphasizes up-to-date software. The driver stack in Debian 'stable' is simply too old for OpenGL 3.3. I am partial to Arch for cutting edge software (GCC 4.9.1, Mesa3d 10.2.5, OpenGL 3.3).
  13. Unity Setting Up Monogame

    Which operating system is this?   Don't use a Unity version of MonoDevelop, as that is terribly out of date.   Instead, use the [url=]Xamarin Studio[/url] installer, which installs MonoDevelop with all necessary dependencies, such as gtk#. You can then install MonoGame through NuGet (right-click your project, select Add -> Add Packages, and search for "monogame").   Alternatively, MonoGame is trivial to build from github: git clone cd MonoGame git submodule init git submodule update Protobuild.Exe msbuild MonoGame.Framework.Windows.sln /p:Configuration=Release On Linux / Mac OS X, simply replace the last two lines by: mono Protobuild.exe xbuild MonoGame.Framework.Linux.sln /p:Configuration=Release # linux xbuild MonoGame.Framework.MacOS.sln /p:Configuration=Release # macos The resulting MonoGame.Framework.dll is placed under bin/Windows/Release - simply add it in your project references.   Edit: fixed link.
  14. OpenTK 3D physics engine?

    [url=]Matali Physics[/url] may be a good choice. It is free (as in beer) for non-commercial use.
  15. Want to move onto a graphics library

    In your project properties (alt-enter), under Linker / Input / Additional Dependencies