DerRidda

So, I'm not that well versed in matters of graphics APIs but I'm still interested to in it and what OpenGL 4.5 and all extensions that have made up all versions >4.0 could mean for Leadwerks. I think 4.0 is a fine version to target and already a ballsy enough goal seeing how many people are stuck with 3.x or are simply unaware of what OpenGL their card+driver combo supports (which isn't all that surprising seeing how OpenGL information is basically nonexistent on marketing material these days). Would support for OpenGL 4.5 (not as a baseline but rather a "cherry on top") be worthwhile for Leadwerks? Maybe not in regards to actually having a great deal of new features but in utilizing the efforts of having reduced driver overhead and giving the player better performance in return if a supported configuration is detected? "You have an awesome GPU! Here, have better performance and maybe trade it in for running the game with higher graphical settings." I'm genuinely interested, seeing how 4.5 could quite possibly be the last version of "classic" OpenGL because of OpenGL next, but I'm not well versed enough in the matter to lead this discussion.

That's on Linux, isn't it? I think it doesn't really work under Linux (yet), you have to right click it in the scene graph and add it through the menu. But you are right, it totally should work and I don't know why I didn't report it myself yet. Probably forgetinated.

This looks like me trying to iron.

Best make a desktop shortcut from one of the views where it does work until Valve figures out why Steam is being silly.

Hmm, let me see. Ubuntu has: Linux Kernel, GNU tools and X. Just like Debian and just about every other current Linux distro out there. Debian uses sysvinit and Ubuntu uses upstart while systemd is the future for both and already the standard for everything else. Ubuntu will probably be there a bit faster even than Debian. In essence, Debian is mostly just older packages for their stable releases and developers like the features the get by having newer a newer libc and other things. What if I told you that if - at least in the case of games on Steam - something runs on SteamOS it is already running on Ubuntu more than it is on Debian because of the Steam-runtime which is build with Ubuntu 12.04 libs with some of them updated here and there? I really, really dislike people coming in with this "let me tell you what's what" attitude and proclaiming a falsehood in practically every second sentence while doing so, potentially irritating and alienating Linux newbies and interested outsiders. Don't get me wrong, i'd like to see Leadwerks officially supported on SteamOS in the future. But prioritizing it over the single largest Linux distro (according to Steam's own stats) that people are actually using today is simply a pants-on-head crazy idea.

SteamOS is not a Workstation operating system, so why would anyone target the editor at JUST that? heck, it even runs Steam in another X session that doesn't really do windowing. It might be worthwhile adding it in the future because of Leadwerks being on Steam but now Ubuntu is the sane choice, though I agree it could be a heck of a lot more flexible in regards to running on anything that shares Ubuntu's base and repos.

As the title says. I've tried renaming some of the tutorial maps to see if the dash, capitalization or numbers or even length in the file name cause issues but so far it's simply the start map. I think the issue might be related to the FPS Character Controller since the 01-Introduction.map also seems to work. I found that out via the new tutorial map, I also added a button to the scene that copies the map change routine from App.lua and goes straight to a hardcoded map. No success either. Debug mode doesn't tell me anything, nor doe the other outputs have anything to offer, it almost seems like a clean termination because Output always ends on "Process Complete".

You mean not having overlay scrollbars? Open up Thunderbird in Ubuntu and you will see them missing there as well. There's plenty of apps in which they don't work (,sadly).

True, it doesn't change them but they keep working properly. I'm not sure how much entirely the editor is supposed to pick up on the theme. If I'm not mistaken it is using GTK but it is not a real GTK app but the BlitzMax based editor with GTK plugged into it. It shouldn't break with specific themes though, that much is clear. And yeah, Ubuntu doesn't offer very granular controls over themes OOTB. EDIT: Radiance just doesn't seem to change that much anyway, if you want to see it working 100% use the high contrast theme.

That seems to be a special occurrence with Mint's default GTK theme and the Steam version. For me on stock Ubuntu it looks as intended using any of the default themes.

Ubuntu 14.04 64bit and the executable is right where it should be. Same behavior after the latest update. I ran ldd on it and I have all dependencies fulfilled. EDIT: On a hunch I reinstalled Leadwerks after reading about the issues with spaces in the path name in Guppy's thread. It works now with the newly named Leadwerks directory.

The new game player in the Steam beta build doesn't work for me under Linux. Every time I try to start it, the editor just minimizes and opens right back up up again with no game launcher in sight. The log has nothing to say about that issue.

Yay! Fully featured editor is in now! Good job, klepto2. In case Josh missed this in Steam and for everybody else: Your current config for Leadwerks on Linux probably misses some editor settings and thus you won't see the new features. Rename/delete your old config in "~/.config/leadwerks" and let Leadwerks create a new default config to get the fully featured editor. (Or add the specific options manually if you know what they are.) The last thing I want to see now is the script editor options being visible in the options dialog under Linux again. They were removed shortly after the initial release because of the missing features, since that problem is solved now that reasoning has become obsolete.

If you are not seeing the fully featured editor in Leadwerks for Linux yet go to "~/.config/leadwerks" delete/rename the old config and let Leadwerks generate a new one, the defaults will enable the full editor again. Sadly the options for changing it aren't yet exposed inside the editor under Linux (again), which i'm sure will come in a future update.

Might be worth changing the offset of the second window, I have a dual monitor setup and thus am not all that concerned as to where my window spawns. And as I said, OpenGL context switching can be awful. I'm using the latest Nvidia beta drivers for Linux (343.13) and Nvidia does OpenGL best. AMD is the worst with OpenGL on every operating system there is, don't know how good Intel is.

Weeee, this is fun. Some more tinkering and the game is displaying in both windows now. You have to manually set the context you want to render each frame, which means your overall fps will be cut in half (at least, because I've heard OpenGL is awful at context switching) as its is split between windows but this is how this works. This might still be useful for something you don't want to update as fast as possible. Also, you might not need the change to FPSPlayer.lua anymore but it is still useful, as you will always have the same window as reference for input events. App.lua

Seems like you kinda can. I tinkered around a bit and at first got two windows, where nothing rendered, though the game was running in the background, then I tinkered some more and stuff now actually runs, in the second window. I tested it with the AI and Events map from the MyGame demo project. I changed App.lua to enable the second window and make it actually sync up but I also changed FPSPlayer.lua to fix the context and window that's used in there, I somehow end up on the incorrect window though but this is just the result of less than 10 minutes tinkering, so go wild and tell me how it went. Might be easier if you start and empty new project just to test. App.lua FPSPlayer.lua

It's been 3 months since I reported it and over 1 month since I last asked for news. I would love to hear some progress information. Is there anything the Linux community could help you with?

This seems to be fixed now.

Your detailed system specs would be nice to have.

That was indeed a typo.

Any news on this? It really makes Leadwerks under Linux a pain to work with at the moment. An error in your script that makes the game crash? Don't worry, there's a line number. But on Linux we don't get to see them, there's Go to but that just scrolls you to it and you still have to eyeball which line it is exactly, which is especially bad for lines at the end of the script where scrolling isn't even happening anymore. If you have some code ready, now's as good a time as any to put it into the Linux beta on Steam.

I'm seeing the same crash under Linux using the Steam beta branch.

Title says it all, I'm limited to using the mouse. Happens in the stand-alone and Steam beta builds both.

Ubuntu 14.04 64bit. Steam download region is Germany - Berlin.