Jump to content

Leadwerks 3.1 Pre-orders Now Available, Indie Edition coming to Steam January 6th

Josh

14,048 views

Leadwerks 3.1 is nearly ready for release! In Leadwerks 3.0, we focused on making a solid cross-platform art pipeline and editor. In 3.1 we're adding graphics that go above and beyond the capabilities of Leadwerks 2.

 

New Features in 3.1

  • OpenGL 4.0 deferred renderer with up to 32x hardware MSAA.
  • Geometry and tessellation shaders.
  • Support for the Linux operating system, for both the engine AND editor.

 

blogentry-1-0-61581200-1387224019_thumb.jpg

Leadwerks 3.1 is now available for pre-ordering in the Leadwerks store. Existing 3.0 customers can pre-order the upgrade to 3.1 for $99. New customers can pre-order Leadwerks 3.1 for $199. Order before January 6 and get the Indie Edition on Steam for free.

 

The upgrade to an OpenGL 4 deferred renderer is a big step. To make the process smoother and put Leadwerks in your hands sooner, we're rolling Leadwerks 3.1 out in stages.

 

"Leadwerks: Indie Edition" will be launched on Steam January 6th. This will be on Windows only, with support for Lua scripting. The following groups will receive a free Steam key to add this product to their Steam account:

  • Leadwerks 3.0 customers who pre-order the upgrade to version 3.1.
  • New customers who pre-order Leadwerks 3.1.
  • All Kickstarter backers who backed Leadwerks for Linux for $49 or more. (Even if you don't run Windows, hold onto this as the Linux version on Steam will have special features.)

 

Leadwerks 3.1 for Linux and Windows will be released together next, with the exact release date to be determined. Leadwerks 3.1 for Mac will follow this, with mobile add-ons for iOS and Android coming last. (There is no purchase necessary to upgrade the mobile add-ons from Leadwerks 3.0 to Leadwerks 3.1.)

 

Exemptions

  • Leadwerks 3.1 beta testers will receive the 3.1 upgrade for free.
  • Leadwerks 3.0 customers who backed the Leadwerks for Linux Kickstarter project for $99 or more will receive the 3.1 upgrade for free.

Leadwerks 3.1 is a very strong product, with great graphics and a fantastic art pipeline. I'd like to thank all the users, both old and new, who offered their input on product design and the direction of the company. I can't wait to see what the community does with Leadwerks 3.1.



50 Comments


Recommended Comments



Am I misreading this or do new customers get 3.1 for $99 less than existing customers (who already paid $199 to purchase just 3.0)? And what about water, networking and other features? If we need to pay $99 for each of those features every year then this engine will get very expensive. Or will those be added to 3.1 next year?

Share this comment


Link to comment

Our business model is to maintain a low price and charge for upgrades on a roughly annual basis. This ensures that development is inline with what the customer base wants; the upgrade rate gives me a metric that tells me how well development is meeting everyone's needs.

 

Products that take the "free upgrades for life" approach always fail because they are 100% reliant on new customers, and eventually that slows down. There are lots of software applications I own that eventually died out because they never charged for updates, when I would have been happy to pay to get more out of them.

Share this comment


Link to comment

+1 on the no mobile upgrade cost when it comes out!

 

If we need to pay $99 for each of those features every year then this engine will get very expensive.

 

We got 3 very nice features in this upgrade so I'd be shocked if each feature you listed itself will be an upgrade on it's own. As much as some people hate on 3.0 it was a good upgrade. We got pathfinding, csg, mobile support, run on wider range of hardware, and a more solid engine with the transition to C++ as it's core.

 

Honestly even if we did pay $99 for each of those features, which I don't think we will, it'll still be cheaper than some other engines. $99 /yr is cheaper than most of my other hobbies, and those don't really offer me the chance to make any money from them :)

Share this comment


Link to comment

I guess you forgot to add the not-already-customers of Leadwerks 3.0 who pledged $200+ to the section for the receivers of the 3.1 upgrade.

Share this comment


Link to comment

If one were currently developing a game for PC using a version of Leadwerks 2, would it be a good idea to switch to 3.1 now, since 3.0 was mostly for smartphone games?

Share this comment


Link to comment

I guess you forgot to add the not-already-customers of Leadwerks 3.0 who pledged $200+ to the section for the receivers of the 3.1 upgrade.

Kickstarter backers are receiving version 3.1 as was promised in the campaign. Is that what you meant?

 

If one were currently developing a game for PC using a version of Leadwerks 2, would it be a good idea to switch to 3.1 now, since 3.0 was mostly for smartphone games?

The new features in 3.1 are focused on PC development, and the renderer is more similar to the one from Leadwerks 2, so I think you will be comfortable on that.

Share this comment


Link to comment

I have no problems paying some money for yearly upgrades. Not 99$, but 199$ for yearly upgrades which bring a resonable amount of new features are 100% justifiable and will keep leadwerks a live.

Share this comment


Link to comment

Bought it. Linux support was an important reason

I hope 3.2 will have some easy to use integrated GUI .......

Share this comment


Link to comment

Kickstarter backers are receiving version 3.1 as was promised in the campaign. Is that what you meant?

Yes, thx.

Share this comment


Link to comment

I have absolutely no problem with upgrade fees in general. My confusion is with why all the costs of the upgrade go to existing customers. Why not charge less to existing customers and add some of the cost to new buyers? 3.1 costing the same as 3.0 for new purchases seems odd.

 

Or, imagine if this trend continues. Even as an existing customer, in 2 years, you'd be better off buying 3.3 from scratch instead of buying 3 upgrades. It would save you money. Seem a bit strange?

Share this comment


Link to comment

@gamecreator But then you wouldn't ever use the product because you'd always be waiting to save money. It's like cable or dish. They always give big savings to new customers to try and get them to convert. If you want the product/service, at some point you bite the bullet and make the purchase knowing that they may have bigger savings later for newer customers.

Share this comment


Link to comment

Personally, I think anywhere from $50-70 would be fair while $99 is pushing the cost/benefit analysis over the long haul. Upgrade fees themselves are not a problem. Rather, the business model should be that features are added at such a rate as to attract and retain a large user base at that lower rate. What's the attrition rate at $99/year?

 

Products die because users are not retained and there is no growth. The upgrade fee is only a part of the equation. I would suggest that this model of planning for yearly paid updates will work against an aggressive campaign to fortify the user base. The clockwork approach leaves me with a sense of something missing or that I'm being trapped.

 

That said, it remains to be seen whether the Linux port will create additional synergies and growth. If 'yes', what should the upgrade fee be under those circumstances? Optimistic planning might have resulted in an upgrade fee of $50-70. Have faith.

Share this comment


Link to comment

Products that take the "free upgrades for life" approach always fail because they are 100% reliant on new customers, and eventually that slows down. There are lots of software applications I own that eventually died out because they never charged for updates, when I would have been happy to pay to get more out of them.

 

Firstly, not all products on this model die out - one example is PureBasic.

Also, I agree with other comments that it seems upgrade prices are too high compared with the full product.

 

Also, other products that do charge for upgrades, normally charge for full version (e.g. 3.0 -> 4.0) upgrades only, and not point releases (3.0 ->3.x).

 

Finally, if I pledged for the KS and I get 3.1 when due, is there anyway to get that Steam Indie Edition as well either for free (preferably) or for a low atractive price?

Share this comment


Link to comment

I don't see how $99 a year is all that much. Save $8.33 a month and you'll be good each year. :)

 

Josh could be naming these releases by major number if that would make people feel better, but it's about the features added not the release number.

Share this comment


Link to comment

I understand that Josh has underpriced the engine (in his eye) and he's overpricing the updates to compensate - like companies do with consoles and games. It's a rough business model but if he honestly thought 3.0 was worth $1000 originally, I guess he's making compromises too.

Share this comment


Link to comment
Finally, if I pledged for the KS and I get 3.1 when due, is there anyway to get that Steam Indie Edition as well either for free (preferably) or for a low atractive price?

All Kickstarter backers who got a reward with any version of the software will get a free Steam key for the Indie Edition before January 6th. Even if you don't run Windows, hold onto this because the Linux version on Steam will have some special features.

Share this comment


Link to comment

I don't think the updates are overpriced at all. Look at Unity Pro. It's $1,500! If you look at the feature list between them it's fairly comparable and LE is way cheaper! If you purchased 3.0 and upgrade to 3.1 you'll have paid like $300? It would take 12 more years of $99 upgrades to finally hit Unity Pro's cost. I've been more productive with LE than I was with even the indie version of Unity (that's just my experience obviously).

 

Personally, I just don't think $99/yr upgrades are overpriced when comparing it to some other popular engines.

Share this comment


Link to comment

Rick, Leadwerks competes with more than just one of the most expensive engines on the market. Saying it's cheaper than Unity doesn't say much.

 

But I'm with you in that by far Leadwerks fits me best. I'll pay this upgrade grudgingly and then continue to enjoy using the engine.

Share this comment


Link to comment

Yearly upgrade at a reasonable price is fine by me so long as there is a big/good update. You can also look at the fact that you get small updates throughout the year.

 

how do you know to which Steam user the upgrade needs to be granted?

In your profile there's a place for your Steam ID.

Share this comment


Link to comment

@gamecreator I agree, but from my experience it's one of the closest in terms of a polish editor and great API that doesn't take royalties so that's why I used it.

Share this comment


Link to comment

Again, I'm not opposed to upgrade costs and will likely (maybe) do this one but I would rather see a model of constant development and releases, with no lulls in the middle of the year. No bizarro marketing philosophies or teasers, just plain reliability. The example of Purebasic was offered earlier. Such an approach provides some confidence that the user base will grow. As noted above, this market is not captive meaning that users can simply switch, impacting the entire community. The potential for silence in the middle of the year is the perfect time to lose clients - too much ambiguity. Or, as in the case with Adobe, users often choose every second upgrade cycle. For a small operation that can prove fatal. And, again, the community suffers as a whole.

 

Just my two cents.

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 tipforeveryone in tipforeveryone's Blog 5
      II. Implement advanced actions
      Previous tutorial guided you to create your own FPS Character Controller with basic actions: Move, Look.
      This tutorial will help you add some advanced actions like Jump, Run, Crouch, and Lean
      *Note: Below steps will use code from previous tutorial (CharacterController.lua)
      1. Jump / Run / Crouch
      Firstly, build obtacle with space under it to test crouching, the space height shoud be at least 120cm (leadwerks editor will show you this height in other viewports) You can not crouch and pass space under 120cm, this was hardcoded


      Next, modify the code.
      Add new variables under --Character movement variables comment. Note that putting script variables at the top of script will allow you to modify character stat easier and faster than finding variables deep inside script's functions
      --Character movement variables Script.playerSpeed = 2 --higer = faster Script.playerRunSpeedMultipier = 2 --if this variable < 1, you can make slower movement Script.playerJumpForce = 7 --This defines how high you can jump Add new funtion to smooth movement of character components function Script:SmoothPosition(position,entity,rate) local smoothX = Math:Curve(position.x,entity:GetPosition().x,rate) local smoothY = Math:Curve(position.y,entity:GetPosition().y,rate) local smoothZ = Math:Curve(position.z,entity:GetPosition().z,rate) entity:SetPosition(smoothX,smoothY,smoothZ) end Replace code in Character_Movement() function by this code function Script:Character_Movement() local playerSpeed, playerJumpForce, playerCrouch --Press Space bar to Jump if window:KeyHit(Key.Space) then playerJumpForce = self.playerJumpForce else playerJumpForce = 0 end --Hold Ctrl key to Crouch if window:KeyDown(Key.ControlKey) then playerCrouch = true else if self.playerHeadBlocked then playerCrouch = true else playerCrouch = false end end --Hold Shift key + AWSD to Run if window:KeyDown(Key.Shift) then playerSpeed = self.playerSpeed * self.playerRunSpeedMultipier else playerSpeed = self.playerSpeed end local playerMove = ((window:KeyDown(Key.W) and 1 or 0) - (window:KeyDown(Key.S) and 1 or 0)) * playerSpeed local playerStrafe = ((window:KeyDown(Key.D)and 1 or 0) - (window:KeyDown(Key.A) and 1 or 0)) * playerSpeed --Using local playerSpeed varialbe instead of self.playerSpeed in the old code local playerTurn = self.playerNeck:GetRotation(true).y self.playerBase:SetInput(playerTurn,playerMove,playerStrafe,playerJumpForce,playerCrouch) end Replace code in Bind_Character_Components_Together() function too function Script:Bind_Character_Components_Together() --Must use this reposition process because playerBase is not playerNeck's parent, they are indipendent. local basePos = self.playerBase:GetPosition(true) local height if window:KeyDown(Key.ControlKey) then height = basePos.y + (self.playerHeight - self.neckLength) / 2 --You can adjust this variable to get desired crouch height for playerNeck (and playerEyes too) else if self.playerHeadBlocked then height = basePos.y + (self.playerHeight - self.neckLength) / 2 else height = basePos.y + self.playerHeight - self.neckLength end end self:SmoothPosition(Vec3(basePos.x,height,basePos.z),self.playerNeck,10) end Add a new function to script, this will keep player crouching if something block above character when release Ctrl key, prevent from being pushed around by obtacle when standing. function Script:Check_Head_Block() --We can use a raycast to check if something block character head when crouching local pickInfo = PickInfo() local point1 = self.playerNeck:GetPosition(true) local point2 = self.playerBase:GetPosition(true) + Vec3(0,self.playerHeight,0) if world:Pick(point1,point2,pickInfo,0.3,true) then self.playerHeadBlocked = true else self.playerHeadBlocked = false end end Update Script:UpdateWorld() function with new Check_Head_Block() function function Script:UpdateWorld() self:Bind_Character_Components_Together() self:Check_Head_Block() self:Character_Look() self:Character_Movement() end Now, you can crouch under obtacle, release Ctrl Key and you are still crouching. Continue moving for auto standing. 2. Leaning
      In Character_Movement() function, add this code after Crouching code
      --Hold Q/E to lean Left/Right local leanDistance = 0.025 --leanDistance should be < 0.025 or camera will pass through wall when you get too close if window:KeyDown(Key.Q) then self.playerEyes:Move(-leanDistance,-0.01,0) end if window:KeyDown(Key.E) then self.playerEyes:Move(leanDistance,-0.01,0) end And add this line at the bottom of Bind_Character_Components_Together() function self:SmoothPosition(Vec3(0,self.neckLength,0),self.playerEyes,10) You can lean now, so smooth. Final script file was attached to this entry. You can apply it to a pivot point (PlayerControl).
      CharacterController.lua
    • By 💎Yue💎 in The shock absorbers 2
      Coming to the end of my prototype of a 3d game, and with background music by Hanz Zimmer ( Time ). I saw my progress in many aspects, always something to learn, always something to improve, I didn't intend to make a game, that has never been the goal. 
      Rather, the effort and dedication immeasurably, was to improve on something learned. And here I was with the powerful leadwerks engine, where his greatest power lay in making everything very easy.  
      About the project
      The prototype is very simple, a third person character goes through a stage, an orbital camera that follows him with many interesting things when scripting.  A character who runs, walks, ducks, jumps, and suffers damage when he falls from different heights. 
      The interesting thing about all this is that just like when you're little and learn to write, repetition is key to learning to program, understand concepts and improve.  So as I've always said, you learn to program by programming, although I sincerely think that lua script is not programming, but the experts say it is, so I go into that elitism of those of us who think we are programmers. 
      The final part of the project consists of creating a death animation, this will be activated when the player falls from a high part and separates the legs (that is very cruel). 
      But that feeling of improvement is the same that I feel when in the mornings when I have a coffee I solve a riddle of the newspaper, but I don't know when I'm going to stop, it turns out and it happens that technology advances very fast and this continues and continues without stopping. Starting with LE 5, and the only thing that can happen is that I die or that my old computer doesn't work anymore. 
      Translated with www.DeepL.com/Translator





    • By 💎Yue💎 in The shock absorbers 1
      It's interesting that when you become an expert on something, you're not sparing any effort to see how something works, but rather you're focusing on creating something. And so everything becomes easier.
      At this point of learning there is a glimpse of a low idea of creating a game, but the secret of all this is to keep it simple and to be very clear that a game is a game, and not an exact simulation of the real world. For example anyone who has a low idea of the red planet, will understand no matter the colors of the scene that is a terrain of Mars, even if it is not very real what is transmitted, a game, that's just it.
      At this point I already have an astronaut character who runs from one place to another on a very large 4096 x 4046 terrain that would surely take a long walk. My previous prototype projects involve a vehicle, but I didn't get the best implementation prospect in that time and I always found performance problems in my machine, something that isn't happening with the character controller for a third person player. 
      As always, I think I'm a scavenger looking for game resources, that's where this community exposes links to websites with interesting hd textures, and one or another model searched on the net, but what I've greatly improved is learning to write code, I have a better workflow, writing Lua code focused on the paradigm of object programming.



      Something interesting is the system of putting rocks, all very nice from the point of implementing them. And it works very well with the character controller if you put collision in cube form.
      I've been thinking about implementing a car system, I think it would be necessary in such a large terrain, but I think it's not the time, my previous experience, involves deterioration in performance and something I think is the physics of the car with respect to the terrain and rocks that in the previous project involve deterioration in the fps. Although if you implement a car would have an option would be to remove the rocks, but I prefer not to have a car and if you have rocks. 
       
       
       
       
×
×
  • Create New...