Jump to content

Leadwerks Standard Edition Brings C++ Game Development to Steam

Admin

6,242 views

blog-0972282001396890676.jpgFollowing the successful debut of Leadwerks Game Engine: Indie Edition on Steam, Leadwerks Software today announced the launch of Leadwerks Standard Edition. This DLC on Steam adds support for programming in modern C++11 with Microsoft’s Visual Studio 2013.

 

C++ is the game industry’s leading programming language, due in large part to its superior performance and flexibility. However, the language is sometimes considered to be too complicated for indie developers to take advantage of. Leadwerks solves this problem by focusing on a useful subset of the C++ language, and providing a simple command library that works the same in C++ and Lua. This makes C++ game development fast and easy to control.

 

Adding C++ support to Leadwerks Game Engine unlocks access to a massive amount of free third-party game libraries, which are typically written for C++. Indie game developers can include new libraries for physics, AI, and virtual reality into their Leadwerks projects without having to wait for the developers to add an official bridge. This lets indie developers take advantage of the newest technologies and provides a degree of control other languages can’t match.

 

Leadwerks is designed to make game development easy for Steam’s 75 million users. A new renderer built on OpenGL 4.0 provides advanced graphics at an affordable price. Built-in level design tools make map design easy for users who don’t happen to be expert artists. Game code can be written with Lua, an easy-to-learn script language, or modern C++11. Finally, the royalty-free license means game developers can publish commercial games and keep 100% of the profits, with no additional payments due, ever.

 

The Leadwerks Game Engine: Standard Edition DLC can be purchased on Steam for $99.

 

About Leadwerks Software

Leadwerks Software was founded in 2006 to build game development tools that are powerful and easy to use. The company launched Leadwerks 3, their first multiplatform product, at GDC 2013. Last summer, the company conducted a successful Kickstarter campaign to being 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.



16 Comments


Recommended Comments

I don't understand, what's the difference between this version and the standard version here on this site which cost $199. Does the steam standard edition can be used only to create games that works on steam? And does the steam standard version also include Lua like the one here on this site?

Share this comment


Link to comment

They are the same, but I think the Steam one will have the Workshop integrated into it.

Share this comment


Link to comment

Leadwerks on Steam has additional features like screenshot and video publishing, Workshop integration (in progress), and other features that may be added in the future. Games made with the Steam version can still be published anywhere you want, not just to Steam.

Share this comment


Link to comment

I still don't understand, why would anyone buy the one on the site for $199 and they could get it for $99 on steam also why would someone buy the inde version on steam for same price as the standard version on steam if the standard one had more features. Please I need a good explanation because the description does not give enough information about the versions . thanks

Share this comment


Link to comment

I still don't understand, why would anyone buy the one on the site for $199 and they could get it for $99 on steam also why would someone buy the inde version on steam for same price as the standard version on steam if the standard one had more features. Please I need a good explanation because the description does not give enough information about the versions . thanks

Well, technically it's $1 cheaper if you get indie + standard DLC on Steam. But some people prefer a standalone version.

Share this comment


Link to comment

@Oxford: Please read a little more carefully on the store page what the difference is between indie and standard edition. Indie costs 99 and standard cost 199. indie + upgrade to standard costs 198

Share this comment


Link to comment

@Oxford: The indie version is Lua only. The standard version is C++ AND Lua. So the standard on this site is $199. The standard on steam is $199. Indie on steam is $99. Standard DLC for indie is $99. It's all the same price.

Share this comment


Link to comment

Yes I understand now, the standard on steam is just an addon to the inde version on steam to make it like the one in the site. But you say that in steam description that its an addon so people don't just buy the standard one and get shocked that they need the inde one too for it to work.

Share this comment


Link to comment

Yes I understand now, the standard on steam is just an addon to the inde version on steam to make it like the one in the site. But you say that in steam description that its an addon so people don't just buy the standard one and get shocked that they need the inde one too for it to work.

It's not possible to buy the DLC without owning the base product. :)

Share this comment


Link to comment

It is this Steam Standard the version 3.1 of Leadwerks?, Im confused because it said OpenGL 4.0 support but that is Leadwerks 3.1?.

 

If thats the case how can I get this version without steam?. Or I have to continue using version 3.0 until 3.1 is ready on here?. also when 3.1, I pre ordered on March 2014.

Share this comment


Link to comment

It's not possible to buy the DLC without owning the base product. smile.png

 

As a buyer of the "pre-order", which includes both Indie and Standard edition, wonder why this last one is not already included in my Steam account (as DLC). To have both versions in Steam does not think it necessary to shell out another $ 100 for a version that is already included in my previous purchase. Correct me if I'm wrong, Josh.

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 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.
    • By Josh in Josh's Dev Blog 1
      A huge update is available for Turbo Engine Beta.
      Hardware tessellation adds geometric detail to your models and smooths out sharp corners. The new terrain system is live, with fast performance, displacement, and support for up to 255 material layers. Plugins are now working, with sample code for loading MD3 models and VTF textures. Shader families eliminate the need to specify a lot of different shaders in a material file. Support for multiple monitors and better control of DPI scaling. Notes:
      Terrain currently has cracks between LOD stages, as I have not yet decided how I want to handle this. Tessellation has some "shimmering" effects at some resolutions. Terrain may display a wire grid on parts. Directional lights are supported but cast no shadows. Tested in Nvidia and AMD, did not test on Intel. Subscribers can get the latest beta in the private forum here.

       
       
×
×
  • Create New...