• Advertisement

JoshKlint_34394

Member
  • Content count

    111
  • Joined

  • Last visited

Community Reputation

1440 Excellent

About JoshKlint_34394

  • Rank
    Member

Personal Information

  1. Today we are pleased to announce the release of Leadwerks Game Engine 4.5. Version 4.5 introduces support for VR headsets including the HTC Vive, Oculus Rift, and all OSVR-based hardware, allowing developers to create both room-scale and seated VR experiences. The Leadwerks virtual reality command set is robust yet incredibly simple allowing you to easily convert your existing 3D games into VR titles. To help get you started the source code for our Asteroids3D game has been updated for VR and is now freely available in the Leadwerks Games Showcase. Leadwerks Game Engine is uniquely well-suited for VR because of its fast performance, ease of use, and the availability of C++ programming for demanding VR games. Several optimizations for VR have been made including combining the rendering of both eyes into a single culling step. The stability and accuracy of Newton Game Dynamics means we can have in-depth physics interactions in VR. A new VR game template has been added to provide common VR features including teleportation locomotion and the ability to pick up and interact with objects in the environment. Visual Studio 2017 We've also upgraded Leadwerks Professional Edition to build with Visual Studio 2017 so you can take advantage of the very latest Visual Studio features. Instructions for upgrading C++ projects from version 4.4 to 4.5 are available here. Other Improvements Added fog settings in editor and into map file format. New joint scripts and enhancements. Updated to Steamworks 1.41 You can pick up Leadwerks Game Engine with a discount during the Steam Winter Sale. About Leadwerks Software Leadwerks Software was founded in 2006 to make game development easy and fun. The company launched Leadwerks Game Engine on Steam in January 2014 and has experienced steady growth, now with over 20,000 paid users. Leadwerks Game Launcher was released as an early access title in September 2015, allowing developers to publish games to Steam Workshop with no submission fee.
  2. Today we are pleased to announce the release of Leadwerks Game Engine 4.5. Version 4.5 introduces support for VR headsets including the HTC Vive, Oculus Rift, and all OSVR-based hardware, allowing developers to create both room-scale and seated VR experiences. The Leadwerks virtual reality command set is robust yet incredibly simple allowing you to easily convert your existing 3D games into VR titles. To help get you started the source code for our Asteroids3D game has been updated for VR and is now freely available in the Leadwerks Games Showcase. Leadwerks Game Engine is uniquely well-suited for VR because of its fast performance, ease of use, and the availability of C++ programming for demanding VR games. Several optimizations for VR have been made including combining the rendering of both eyes into a single culling step. The stability and accuracy of Newton Game Dynamics means we can have in-depth physics interactions in VR. A new VR game template has been added to provide common VR features including teleportation locomotion and the ability to pick up and interact with objects in the environment. Visual Studio 2017 We've also upgraded Leadwerks Professional Edition to build with Visual Studio 2017 so you can take advantage of the very latest Visual Studio features. Instructions for upgrading C++ projects from version 4.4 to 4.5 are available here. Other Improvements Added fog settings in editor and into map file format. New joint scripts and enhancements. Updated to Steamworks 1.41 You can pick up Leadwerks Game Engine with a discount during the Steam Winter Sale. About Leadwerks Software Leadwerks Software was founded in 2006 to make game development easy and fun. The company launched Leadwerks Game Engine on Steam in January 2014 and has experienced steady growth, now with over 20,000 paid users. Leadwerks Game Launcher was released as an early access title in September 2015, allowing developers to publish games to Steam Workshop with no submission fee. View full story
  3. I'm building the VR project template for Leadwerks 4.5. Although you can enable VR in any project, this template is specifically designed to provide some of your most common room-scale VR features: Teleportation movement, which prevents motion sickness. Picking up and throwing objects. (It's actually really fun!) To start with I am creating the art assets for the teleport effect. This is basically what I want: Your controller shoots a beam which ends in an indicator when it hits an upwards-facing slope. Typically this beam will be somewhat arced. Why the curve? This allows you to climb up to areas above you: As always, I am starting with the game assets. I don't believe in using programmer art because it hurts your understanding of what you are trying to create, it's uninspiring, and you will end up writing your code twice once you get the final artwork and realize all the mistakes you made. I started with textures. I know I want a circular indicator on the floor, a misty spinning effect rising off it, and a beam. I'm going to make all my textures grayscale so that I can control the color with the entity color value and dynamically change it in the game. Here are my textures I created in about ten minutes in Paint Shop Pro: The first texture above is clamped along the X and Y axes and the second one is clamp along the Y axis. I am using uncompressed textures for all of these because they have a lot of soft gradients. I created my materials with the following settings, again leaving everything white: In 3ds Max I created my indicator model. It's just a plane with a cylinder on top, with the end caps removed: When I import it into Leadwerks and apply my materials, the model looks like this: I'll show you why I am using uncompressed textures. You can see in this shot the edge of the ring has some ugly artifacts when texture compression is used: Here's a closeup. Not something I want to see in VR: Now I am going to create an instance of the model in the editor and adjust the color. I want a bright blue glowy color. I am setting the color to RGB 128,255,255 and cranking the intensity way up to 2.0. This effectively sets the entity color to 256,512,512. This color is multiplied by the texture color at each pixel and then clamped to 0-255 (the maximum color range of the monitor). That means that the brightest spots on the material will reach a full 255,255,255 white color and look really intense, while darker parts will be tinted blue: Notice the object isn't just a flat color, but has a range of color from blue to white. To get this effect I had to increase the intensity over 1.0 to create colors brighter than RGB 255,255,255, and I had to have some red in the color. If I had set the color to RGB 0,255,255 the red channel would never increase and I would have a flat color like this. Not so good: If I had set the color to RGB 128,255,255 but left the intensity at 1.0 I would also have a solid color: Finally I added a script to the model and saved it as a prefab. The script just rotates the model around slowly on its Y axis, which I think will look pretty good. I'm going to perform the rotation in the Draw() function so it doesn't get called if the object is hidden or offscreen, and I don't think anyone will notice if the rotation doesn't update when they look away: function Script:Draw() self.entity:Turn(0, 0.1 * Time:GetSpeed(), 0) end That's it for now. The next step will be to create my teleportation mechanic in VR.
  4. Now that the Kickstarter rewards are shipped from my campaign to bring Leadwerks to Linux, I'm getting distribution channels set up. Today Leadwerks Game Engine launched in the Ubuntu Software Center. This is a big deal for two reasons: Linux users now have first-class rapid game development tools written natively for Linux. We're bringing more games to Linux, like Rogue System. You can check out a demo of Leadwerks on our site.
  5. [color=rgb(0,0,0)][font=arial]Previously, [/font][/color]I described[color=rgb(0,0,0)][font=arial] the goals and philosophy that were guiding my design of our implementation of the Leadwerks Workshop on Steam. To review, the goals were:[/font][/color] [color=rgb(0,0,0)][font=arial]1. Frictionless sharing of items within the community.[/font][/color] [color=rgb(0,0,0)][font=arial]2. Protection of intellectual property rights.[/font][/color] [color=rgb(0,0,0)][font=arial]3. Tracking of the chain-of-authorship and support for derivative works.[/font][/color] [color=rgb(0,0,0)][font=arial]In this update I will talk more specifically about how our implementation meets these goals.[/font][/color] [color=rgb(0,0,0)][font=arial]Our implementation of the Steam Workshop allows Leadwerks developers to publish game assets directly to Steam. A Workshop item is typically a pack of similar files, like a model or texture pack, rather than single files:[/font][/color] [color=rgb(0,0,0)][font=arial]To add an item to Leadwerks, simply hit the "Subscribe" button in Steam and the item will become available in a new section of the asset browser:[/font][/color] [color=rgb(0,0,0)][font=arial]You can drag Workshop files into your scene and use them, just like a regular file. However, the user never needs to worry about managing these files; All subscribed items are available in the editor, no matter what project you are working on. When a file is used in a map or applied to a model, a unique global ID for that file is saved, rather than a file path. This allows the item author to continue updating and improving the file without ever having to re-download files, extract zip archives, or any other mess. Effectively, we are bringing the convenience of Steam's updating system to our community, so that you can work together more effectively. Here's one of the tutorial maps using materials from a sci-fi texture pack from the Workshop. When the map is saved, the unique file IDs are stored so I can share the map with others.[/font][/color] [color=rgb(0,0,0)][font=arial]Publishing your own Workshop packages is easy. A built-in dialog allows you to set a title, description, and a preview image. You can add additional images and even videos to your item in Steam:[/font][/color] [color=rgb(0,0,0)][font=arial]Leadwerks even has support for derivative works. You can create a model, prefab, or map that uses another Workshop file and publish it to Steam. Since Leadwerks tracks the original ID of any Workshop items you used, they will always be pulled from the original source. This allows an entirely new level of content authors to add value to items downstream from their origin, in a way similar to how Linux distributions have grown and evolved. For example, maybe you don't have the artistic skill to make every single texture you need for a house, but you can put together a pretty nice house model and pant it with another user's textures. You can then upload that model right back to the Workshop, without "ripping off" the texture artist; their original package will still be needed to load the textures. It's perfectly fine to change the name of your Workshop package at any time, and you never need to worry about your file names conflicting with files in other packages. (If you decide you want to change a lot of file names, it's best to just create a new package so that you don't interrupt the work of users "downstream" from you,)[/font][/color] [color=rgb(0,0,0)][font=arial]Uninstalling a Workshop package just requires you to hit the "unsubscribe" button on the item's page in the Steam Workshop. No more hunting around for stray zip files! You can easily check out other users' work, use whatever you like, and unsubscribe from the packages you don't like, with no mess at all.[/font][/color] How Do I Get It? [color=rgb(0,0,0)][font=arial]The Leadwerks Workshop beta begins today. You must be a member of the [/font][/color]Leadwerks Developer group on Steam[color=rgb(0,0,0)][font=arial] to access the Workshop. A limited number of beta invites are being sent out. Once the system is completely polished, we will make it available to the entire Leadwerks community.[/font][/color]
  6. Leadwerks Software at Steam Dev Days: http://www.youtube.com/watch?v=hOCl8-_mSUA#t=07m10s #linux #steamos #steamdevdays #ubuntu
  7. [color=rgb(11,25,2)][font='Helvetica Neue'] I'm happy to say that Leadwerks now supports the entire process of making games natively on Linux. Let's take a quick tour through the process.[/font][/color][color=rgb(11,25,2)][font='Helvetica Neue'] First, we create a new project in the project wizard. The project wizard will detect project templates (you can make your own) and let you make a game based on Lua script, or on a combination of C++ and script:[/font][/color][color=rgb(11,25,2)][font='Helvetica Neue'] [/font][/color][color=rgb(11,25,2)][font='Helvetica Neue'] Step two is to make your game. Fortunately, you've got everything you need built into a single integrated editor, including script and shader debugging, automatic asset reloading, and built-in level design tools:[/font][/color][color=rgb(11,25,2)][font='Helvetica Neue'] [/font][/color][color=rgb(11,25,2)][font='Helvetica Neue'] Once you have something you want to share, the project publisher will copy all required files into an export directory. Future feature idea: Add a call to a command-line tool to pack up .deb packages. Or better yet, allow any arbitrary executable to be run at the end of the publishing process.[/font][/color][color=rgb(11,25,2)][font='Helvetica Neue'] [/font][/color][color=rgb(11,25,2)][font='Helvetica Neue'] I have some more testing to do before release, but things are looking good![/font][/color]
  8. [color=rgb(11,25,2)][font=arial]Following my previous update about correcting file path cases, I am now able to load all our maps in Leadwerks. The power of this tool running natively on Linux is starting to show, if I do say so myself:[/font][/color] [color=rgb(11,25,2)][font=arial][/font][/color] [color=rgb(11,25,2)][font=arial]The next step is to implement a file system watcher to detect file changes. Leadwerks automatically monitors the current project directory, and will reload assets whenever the file changes. This allows you to keep an image open in an image editor like GIMP, and any time you save your changes will be reflected inside Leadwerks. It's a great workflow for artists and just the kind of feature I wanted to bring to Linux with this project.[/font][/color] [color=rgb(11,25,2)][font=arial]Linux has a built-in file system watcher class called "inotify". Interestingly, this class was added to Linux in 2005, the same year the iPod was released, but there appears to be no connection. The "i" in "inotify" stands for "inode". Dennis Ritchie explains:[/font][/color] [color=rgb(11,25,2)][font=arial]In truth, I don't know either. It was just a term that we started to use. "Index" is my best guess, because of the slightly unusual file system structure that stored the access information of files as a flat array on the disk, with all the hierarchical directory information living aside from this. Thus the i-number is an index in this array, the i-node is the selected element of the array. (The "i-" notation was used in the 1st edition manual; its hyphen was gradually dropped.)[/font][/color] [color=rgb(11,25,2)][font=arial]The inotify system is pretty straightforward to implement, with a procedural C interface. One thing that tripped me up was an odd layout of the inotify_event structure. It actually has a char pointer built into the structure, so technically the structure does not have a determined length. I don't believe I have ever encountered this design before, but I also am usually dealing with std::string classes.[/font][/color] [color=rgb(11,25,2)][font=arial]One drawback of inotify is that it isn't recursive. While searching for information on the design, I came across this post by Robert Love, one of the two guys who wrote it (the other being John McCutchan). I disagree with his rational for omitting recursion; just because the performance is not as optimal as he would like does not mean the end user's tastes and preferences will change. I can't imagine a scenario when you wouldn't want the system to work recursively, or at least have the option to. In any case, implementing a recursive watch system was fairly easy. The entire file watch system from zero to finished only took about half a day. So we can mark this as one of the features where I overestimated the time and complexity of implementation.[/font][/color] [color=rgb(11,25,2)][font=arial]File creation, deletion, and modify events are now firing reliably so I am going to plug this code into the editor and start testing it out. Because the editor already works reliably on other Windows and OSX, I don't anticipate any problems. I do not have a firm release date yet, but as you can surmise, we are nearing completion of Leadwerks for Linux.[/font][/color]
  9. Linux Development Update

    With all the excitement of the Steam release and Steam Dev Days behind me, I have literally nothing else to work on but Linux and small bug fixes for the Steam users. Together with the recent solution of two long outstanding problems, the pace of development is picking up, and you can expect more frequent updates from me. I started investigating the right-hand side panel. This contains four tabbed panels filled with various tools the editor uses. I noticed the bottom of the window was being hidden behind some mystery panel I didn't recognize. I added a function that colored the entire interface random colors every frame, which led to this amusing screenshot. Yes, this is actually a real development screenshot of Leadwerks for Linux. Coloring the panels didn't reveal anything to me, but after looking through my code I soon found the culprit: a tabber widget had been created on the main window and forgotten, and it just didn't show up in front in the Windows version. So I put it out of its misery and everything was better. The asset browser allows you to view all files in your Leadwerks projects. With recursive and search options, it can be used to quickly find any file or group of files. This had some miscellaneous problems with event handling I fixed. Default fonts on Ubuntu are quite large compared to Windows and Mac, and this requires some reworking of UI elements. However, I haven't run into any places yet where this requires a significant redesign. I found that button images work best when the button is given a padding of 6 pixels. In other words, the button size minus 12 is how big the image should be. With this part of the editor working nicely, it's starting to feel like a real application. Having an advanced tool like this that can run natively in Linux is pretty intriguing because it means being free from Windows and doing the kinds of things I want to do on Linux. So we're one step closer to delivering on the promise of this campaign. Stay tuned.
  10. Leadwerks 3.1 Enters Beta; Heading to Steam Dev Days

    I would have used QT, but they don't make a library I can easily plug in; it's a whole framework that requires a certain code structure.  So that was out of the question.  Even if I were using QT for the GUI, I dislike visual GUI design tools.   QTCreator actually looks pretty nice, and I might switch over to it, just for the C++ programming not a visual designer.
  11. [color=#000000][font=arial]A new update for Leadwerks has been posted which adds new features that allow users to use Steam features.[/font][/color] [color=#000000][font=arial]S[/font][/color]teamworks Integration [color=#000000][font=arial]Leadwerks now has native support for the Steamworks SDK. You can make your game ready to publish on Steam by calling Steamworks:Initialize(). This also enables the in-game overlay so you can take screenshots, chat with friends, and access the entire Steam community in-game.[/font][/color] Screenshot Publishing [color=#000000][font=arial]The new screenshot publishing window allows you to upload rendered images directly to your online screenshots library, where it will show up on your Steam profile and the Leadwerks community hub. [/font][/color] Steam Controller [color=#000000][font=arial]We've added native support for the new SteamOS Controller. You can get input from the controller and even send haptic feedback back to the device. [/font][/color] [color=#000000][font=arial]You can learn more about these new features in the documentation [/font][/color]here[color=#000000][font=arial].[/font][/color]
  12. Leadwerks is on Steam

    I think you should try them all and choose what suits you best.
  13. Steam Launch Recap and Steam Dev Days

    Our standard edition is actually all based around C++11 and will be available on Steam soon.  I just felt it was easier to start distribution with something simpler, get the problems worked out, and then add the C++ project templates.  This allows access to the full API with the same class structure as what Lua is using.
  14. Leadwerks is on Steam

    Yes, there's a good reason the whole game industry uses C++.  That's why it's at the foundation of our engine, although I can see how you would miss that since we just have the indie edition on Steam right now: http://www.leadwerks.com/werkspace/page/programming?showbanner=0   You can access the whole API directly with modern C++11.  This has a few major benefits I'm sure you're aware of: Easy integration of third party libraries, virtually all of which are written in C++. Superior performance. Access to everything, whereas other languages always give you a subset they think is all you need.
  15. [color=rgb(18,26,13)][font='Helvetica Neue'][color=rgb(11,25,2)]On Monday, Leadwerks Game Engine: Indie Edition was finally launched on Steam. Before the Kickstarter campaign there was a Greenlight campaign to put Leadwerks on Steam, which it got through in just 27 days. Based on the success of the Kickstarter campaign, I decided to delay the Steam launch and try to get Linux done in time. However, there was one serious deadline I could not miss, and that was the Steam Dev Days conference next week. I knew we needed to have an actual product on Steam by then, and not be stuck in Greenlight limbo, so I went ahead and put what we had up, which is Windows-only. Steam keys were sent out to all Kickstarter backers who chose a software reward.[/color][/font][/color] [color=rgb(18,26,13)][font='Helvetica Neue'][color=rgb(11,25,2)]The launch went remarkably smoothly. Due to the limitations of the product (one OS, Lua-only) it made testing and updates much easier than if we tried to do a multi-platform launch all at once. There have been two patches, one to fix compatibility with Nvidia Optimus laptops, and the other to fix a few miscellaneous problems that didn't come up during beta testing.[/color][/font][/color] [color=rgb(18,26,13)][font='Helvetica Neue'][color=rgb(11,25,2)]The response from the early users, and from those of you who have tried it on Windows, has been very good. We seem to have hit the right formula with our combination of BSP brushes, navmeshes, Lua, and the flowgraph system. User engagement is high and I can tell that people "get it". We're starting to see content trickle out on Steam, and I can tell already this year is going to bring some really cool projects made by Leadwerks users. The decision to build a friendly workflow and focus on enabling user-generated content was a good one, as we are already seeing some impressive stuff come out, after only a few days, like this high-res tessellated material from "Shadmar":[/color][/font][/color] [color=rgb(18,26,13)][font='Helvetica Neue'][color=rgb(11,25,2)][/color][/font][/color] [color=rgb(18,26,13)][font='Helvetica Neue'][color=rgb(11,25,2)]Now that you have a more concrete idea of what we're building, I hope you are more excited than ever to have this running natively in Linux. I am returning my full attention to Linux development now. There's nothing else I need to work on but this, and I am determined to have Leadwerks, editor and all, running natively in Linux no matter what it takes. Steam Dev Days[/color][/font][/color] [color=rgb(18,26,13)][font='Helvetica Neue'][color=rgb(11,25,2)]Next week I head up to Seattle to attend Steam Dev Days for two days. I'm not giving any lectures or doing promotion, so it will be a relaxed trip with no prep work. This is going to be Valve's conference for the Linux-based SteamOS. SteamOS is an open console operating system. 13 hardware manufacturers showed off their "Steam Machine" consoles at the Consumer Electronics Show last week.[/color][/font][/color] [color=rgb(18,26,13)][font='Helvetica Neue'][color=rgb(11,25,2)]My personal favorite is the Scan NC10: Leadwerks (the engine) will reportedly run on these machines right now with no changes. I'll learn more next week at the conference and share what information I can with you. Can Linux Take Over the Living Room in 2014? I'm going to go ahead and call it now: Linux is going to take over the living room in 2014. Why?[/color][/font][/color] [color=rgb(18,26,13)][font='Helvetica Neue'][color=rgb(11,25,2)]Compatibility: Steam Machines are backwards-compatible. You can play your old games forever.[/color][/font][/color] [color=rgb(18,26,13)][font='Helvetica Neue'][color=rgb(11,25,2)]Market Segmentation: Steam Machines will eat the market from both ends. There will be extreme high-end models as well as inexpensive compact models.[/color][/font][/color] [color=rgb(18,26,13)][font='Helvetica Neue'][color=rgb(11,25,2)]Visibility: Traditional consoles get a big launch every seven years. Steam Machines will have continued releases, probably on an annual basis like cell phones.[/color][/font][/color] [color=rgb(18,26,13)][font='Helvetica Neue'][color=rgb(11,25,2)]You can watch the man himself, Gabe Newell, talking about it here:[/color][/font][/color] [color=rgb(18,26,13)][font='Helvetica Neue'][color=rgb(11,25,2)]Again, I would like to thank everyone who backed our Kickstarter project and had the foresight to realize Linux gaming was about to explode.[/color][/font][/color]
  • Advertisement