Jump to content

Leadwerks Game Engine Reaches 10,000 Paid Users

Admin

2,370 views

Leadwerks Software today announced their top-selling game development system on Steam, Leadwerks Game Engine, has gained a user base of over 10,000 paid customers. Although the game development space has seen a dramatic drop in prices and the entry of many free competitors, Leadwerks Game Engine continues to gain popularity by teaching complete beginners how to make games with no previous knowledge required, and providing a pathway to publish directly to Steam Workshop.

 

Leadwerks’ ease of use is made possible by a layered development system that gradually eases beginners into game development. At its simplest, Leadwerks Editor is a drag-and-drop system with a visual interface for creating game interactions. Users can drill down to the Lua script level to modify behavior and create new game mechanics. Experts can get even more advanced and access the Leadwerks API directly in C++ with the Standard Edition DLC. This layered development system means that Leadwerks provides a smooth learning curve that grows with the user as they learn more.

 

Leadwerks Game Launcher is the company’s portal for user-made games, and is currently available for free on Steam as an early access title with over 40 free games. Developers can publish their games directly to Steam Workshop with the game launcher or as a standalone. This lets developers share their games with the entire Steam community, with no waiting period and no approval process. The Game Launcher features a variety of experimental titles, delivering fun bite-sized experiences similar to the iOS App Store, but playable on a PC or Steam Machine.

 

image001.jpg

The Borrowercan be played on Windows or SteamOS for free with Leadwerks Game Launcher.

 

With Leadwerks Game Launcher on SteamOS, games can now be built on the desktop and played in the living room. Console gaming has historically been a closed system, with expensive developer licenses and strict rules about who can publish for the living room. With support for SteamOS, Valve’s Linux-based operating system for PC-based game consoles, Leadwerks Game Launcher allows anyone to create their own games they can play in the living room with a controller. All Game Launcher titles work seamlessly on SteamOS, even if they were developed on a Windows PC. Leadwerks provides full support for the new Steam Controller and is compatible with all OpenGL 4.0 hardware for Linux.

 

Image1.jpg

Leadwerks developers can build games on the desktop and play them instantly in the living room.

 

Version 3.7

The upcoming version 3.7 update is planned to add a new vegetation system and other features. Unlike traditional vegetation systems that store each tree instance in memory, the Leadwerks 3.7 vegetation system allocates objects procedurally. This allows the user to create infinitely dense forests that consume no extra memory. The Leadwerks 3.7 vegetation system is set to be featured in a chapter in the upcoming book Game Engine Gems 3, published by A K Peters / CRC Press. Leadwerks Game Engine 3.7 is a free update scheduled for release in December 2015.

 

image003.jpg

Leadwerks Game Engine 3.7 Vegetation System, as featured in Game Engine Gems 3.

 

Leadwerks Game Engine: Indie Edition and the Standard Edition DLC can both be purchased for $99.99 on Steam. Leadwerks Game Launcher can be downloaded for free on Steam.

 

About Leadwerks Software

Leadwerks Software was founded in 2006 to make game development fun and enjoyable. The company launched Leadwerks 3, their first multiplatform product, in April at the GDC 2013 expo. In July 2013 the company conducted a successful Kickstarter campaign to bring Leadwerks to the Linux operating system, reaching over 200% of their goal in just six weeks. A concurrent Greenlight campaign for Steam was also successful, making Leadwerks the first 3D game engine approved for distribution on Steam. Leadwerks Game Launcher was released as an early access title in September 2015, enabling anyone to publish their game directly to Steam Workshop.



5 Comments


Recommended Comments

Keep adding features to leadwerks and even Møre people will prefer it over other engine's.

 

Congrats!, keep up the good work!

Share this comment


Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Add a comment...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

  • Blog Entries

    • By Haydenmango in Snowboarding Development Blog 6
      So I've been researching snowboarding lately to get an idea of what animations and mechanics I need to create for my game.  I have learned lots of interesting things since I've only seen snow once or twice in my entire life and have never even tried snowboarding or any other board sports (skateboarding, surfing, etc.) for that matter.
       
      Snowboarding tricks are quite interesting as they are mostly derived from skateboarding.  Snowboarding tricks pay homage to their equivalent skating tricks by sharing many concepts and names.  For example basic grabs in snowboarding share the same concepts and names as skateboarding: indy, mute, method, stalefish, nosegrab, and tailgrab.  Something interesting to note is in snowboarding you can grab Tindy or Tailfish but this is considered poor form since these grabs can't be done on a skateboard (due to the board not being attached to the skaters feet) and grabbing these areas is generally something a novice snowboarder does when failing or "half-assing" a normal grab.  Check out this diagram to see how grabs work -
       
       
      So, after reading lots of text descriptions for tricks I was still confused by what all these terms meant and how they were actually applied.  So my next step was to look up these tricks actually being done and I found some really cool videos showing off how to do various tricks.  This video in particular is the best reference material I've found as it contains nearly every trick back to back with labeled names and some tweaks -
       
      Sadly my rigged model doesn't handle leg animations with the snowboard that well so I can't animate as many tricks as I want to.  Regardless there will still be around 15 total grab/air tricks in the game.  Now it's time for me to stop procrastinating and start animating!  
    • By jen in jen's Blog 3
      I thought I would share my experience on this; if you're working on Multiplayer, you will need to protect your packets. The solution is simple, let's go through how we can achieve this by implementing what Valve calls "challenge codes". (Some reading on the topic from Valve here: https://developer.valvesoftware.com/wiki/Master_Server_Query_Protocol#Challenge_response).
      Disclaimer: this doesn't cover other security techniques like authoritative server or encryption.
      So, I've worked on Border Recon last year (I think) and I needed a way to protect my server/client packets. There was no need for me to re-invent the wheel, I just had to copy what Valve has had for a  long time - challenge  codes.
      The idea behind challenge codes is similar to Captcha, but not exactly. Think of it like this: for every packet submitted to the server, it must be verified - how? By requiring the client to solve challenges our server provides.
      To implement this we need to have the following:
      A randomised formula in the server i.e.: a = b * c / d + e or a = b / c + d - e, be creative - it can be any combination of basic arithmetic or some fancy logic you like and can be however long as you want - do consider that the longer the formula, the more work your server has to do to make the computation.  Copy the same formula to the client. A random number generator.  So the idea here is:
      (Server) Generate a random number (see 3 above) of which the result would become the challenge code, (Server) run it through our formula and record the result. (Client) And then, we hand over the challenge code to the client to solve (an authentic client would have the same formula implemented in its program as we have on the server). For every packet received from the player, a new challenge code is created (and the player is notified of this change by the server in response). For every other packet, a new challenge code is created. (Client) Every packet sent to the server by the client must have a challenge code and its answer embedded.  (Server receives the packet) Run the challenge code again to our formula and compare the result to the answer embedded on the client's packet. (Server) If the answers are different, reject the packet, no changes to the player's state. The advantage(s) of this strategy in terms of achieving the protection we need to secure our server:
      - For every packet sent, new challenge code is created. Typically, game clients (especially FPS) will update its state in a matter of ms so even if a cheater is successful at sniffing the answer to a challenge code it would be invalidated almost instantaneously. 
      - Lightweight solution. No encryption needed. 
      Disadvantage(s):
      - The formula to answering the challenge code is embedded to the client, a cheater can de-compile the client and uncover the formula. Luckily, we have other anti-cheat solutions for that; you can implement another anti-cheat solution i.e. checking file checksums to verify the integrity of your game files and more (there are third-party anti cheat solutions out there that you can use to protect your game files).
       
       
       
    • By Josh in Josh's Dev Blog 4
      New commands in Turbo Engine will add better support for multiple monitors. The new Display class lets you iterate through all your monitors:
      for (int n = 0; n < CountDisplays(); ++n) { auto display = GetDisplay(n); Print(display->GetPosition()); //monitor XY coordinates Print(display->GetSize()); //monitor size Print(display->GetScale()); //DPI scaling } The CreateWindow() function now takes a parameter for the monitor to create the window on / relative to.
      auto display = GetDisplay(0); Vec2 scale = display->GetScale(); auto window = CreateWindow(display, "My Game", 0, 0, 1280.0 * scale.x, 720.0 * scale.y, WINDOW_TITLEBAR | WINDOW_RESIZABLE); The WINDOW_CENTER style can be used to center the window on one display.
      You can use GetDisplay(DISPLAY_PRIMARY) to retrieve the main display. This will be the same as GetDisplay(0) on systems with only one monitor.
×
×
  • Create New...