DerRidda

Try the Intel drivers linked here and see if that helps. http://www.leadwerks.com/werkspace/page/drivers

Have you tried the specific Intel drivers linked here? http://www.leadwerks.com/werkspace/page/drivers

The constant for Key.ControlKey is 17, same as Key.RControlKey. But when I actually press the ControlKey it is 162 and the right one is 163. Which of course means that if I poll for the named constants it doesn't register when I actually press those keys. This is on Linux, so there is a chance this issue is specific to your input implementation on Linux.

This should work: http://support.amd.com/en-us/download/desktop/previous/detail?os=Windows%207%20-%2064&rev=14.9

This is a pet peeve of mine. Working with many web browser tabs of the documentation open is hard because I can't tell which tab contains which subject because all pages on leadwerks.com have "Leadwerks Game Engine" in the beginning of their title. Even at maximum tab width I can only see "Leadwerks Game En". At the very least the documentation pages should state the subject they are about first. For example the current title for the LensFlare doc page is "Leadwerks Game Engine - LensFlare - Documentation - Documentation - Leadwerks"* after this minor improvement it should read "LensFlare - Leadwerks Game Engine - Documentation - Documentation - Leadwerks" making it possible to differentiate tabs at first glance. *This is a really messy title either way if you were to clean the titling up even more I'd suggest going for something like "LensFlare - Documentation - Leadwerks Game Engine".

Also also: Forgot to say that this is the beta and I'm expecting the actual in-editor browser to pop up.

Firefox is installed and working fine. Also: You should use xdg-open for that and not expect a specific browser. http://linux.die.net/man/1/xdg-open

As in the title. Clicking the menu entry for the in-editor workshop browser does absolutely nothing.

Change that to the name of the map you actually use as your game's start map.

Almost all of these have at least three monitors where the bezel is not in the dead center of your view, on dual monitors the whole thing makes barely any sense. Of course that doesn't stop some people from using it. http://cdn.techpp.com/wp-content/uploads/2013/06/dual-screen-gaming.jpg But that isn't the issue here. How many resolutions does it find on your Linux system Guppy?

Indeed, all the games mentioned are 3D and just mimic the perspective of old 2D side-scrollers. What The Color Red is trying to do should be easy enough. It has already been done before in LW2 http://www.leadwerks.com/werkspace/page/games/_/the-last-chapter-r25

What is the Catalyst Control Center saying you are running?

As the titles suggest System:CountGraphicsModes only returns 1. While that resolution always seems to be the total resolution of the current X screen. Meaning GetGraphicsMode(0) returns 3840, 1080 for my dual screen setup and 1920, 1080 when I deactivate the second screen. Of course there are plenty of resolutions available below the native resolution of the monitor and just receiving 3840, 1080 for the dual screen setup is useless data, as nobody spreads their game across two screens, unless they like looking at the monitor edges in the middle all day.

So, it looks like full screen on Linux was implemented as a borderless, always on top window, right? That in itself is a perfectly acceptable way of doing it but it still has a few quirks that could be improved upon. 1st: At the moment the full screen flag alone doesn't resize the window to the desktop resolution. That would be nice to have because I don't think we have a way of actually figuring out the desktops current resolution, do we? It's really not wise to assume that the highest available resolution from GetGraphicsMode is the right one. I can already see that it is wrong in my case, only showing the combined resolution of my dual monitor setup. (Gonna make a bug report about that) A solution for that is needed. 2nd: Key pass through for some important combinations. X11 is absolutely aggressive when grabbing input, making sure that the rest of the system doesn't see any of it at all. That means alt-tab and alt+f4 doesn't work or the media keys on the keyboard. The former is annoying for everybody, the latter also is for some people, especially laptop gamers who need to rely on their media keys to change the system volume. There are means to pass those through I think.

Yes, this was fixed a while ago.

This was in reference to the AI and Events demo map. It seems to have been fixed in the last 3 months.

Does this work with animated models?

It's not even hidden at all. Just pick your OS and click the previous driver link to the right of it on their website. Here is the one for Windows 8.1 64bit. http://support.amd.com/en-us/download/desktop/previous?os=Windows%208.1%20-%2064 It's the same for all other platforms.

Intel integrated graphics do not support OpenGL 4.0 (yet) on Linux. You will need a system with a reasonably modern Nvidia or AMD graphics card.

Your GPU does support OpenGL 4.2, so enough for Leadwerks but I bet you are running the open source drivers which do not support OpenGL 4.0 yet on any card. Find an AUR that provides fglrx, which is AMD's official proprietary graphics driver and use that.

What GPU are you using?

Made a quick image search for 'this is how surprised I am' and this image fits perfectly.

Here's the truth of the matter: AMD and OpenGL is inferior to Nvidia on all platforms. And not just by a bit. I still hope for you guys to see a fixed driver sooner rather than later.

You can find them here, just fill out the mask with your hardware and platform config. http://support.amd.com/en-us/download

There's a driver scheduled for release next week. http://videocardz.com/54128/amd-announces-catalyst-omega-drivers-with-virtual-super-resolution let's hope this helps. PSA: Don't read the comments on that page, by GabeN, don't do it, your brain cells will melt.