Jump to content

Leadwerks 5 Beta Rollout

Josh

5,414 views

Today I am excited to announce plans for the release of the first Leadwerks 5 beta version.  Leadwerks 5 will roll out sooner rather than later, employing an extended beta period during which versions 4 and 5 will live side-by-side, using the same code base, with preprocessor definitions to compile each version.  This allows me to fix small problems without forking the code, while I can implement new changes in version 5.  The first features implemented will be the use of smart pointers for all shared objects, and unicode support for all strings.

A subscription model will be available for access to the Leadwerks 5 beta, at a modest price of just $4.99/month for enthusiasts who want access to the most cutting-edge game development technology as it is developed.  This will be available through the Leadwerks.com site, and will not use Steam (at least at first).  I feel it is important for the company's future to start building a recurring revenue stream, and I want to create something that does not rely on any middleman who may arbitrarily change or discontinue the terms of the service they are providing.  The Leadwerks 5 beta will implement breaking changes as it is developed, and is not meant for use in a production environment, so I do not recommend moving any commercial projects from version 4 to 5.  Leadwerks 4.x will continue to receive updates and new features until the final version 5 is released.

Leadwerks 5 is designed to be the most advanced game engine in the world, combining improved ease of use with massive performance, and a special emphasis on VR.  Thank you for supporting the next generation of game development technology.



56 Comments


Recommended Comments



Brilliant, Yue. :lol:

On topic: the pricing is very generous, thank you. There's no way the other engines can beat the $4.99 pricing, even if it's up a bit higher later in the development the pricing would still be convenient and affordable to everyone.

Share this comment


Link to comment

I would think there will be an option to pay for your subscription through PayPal. You can either get a PayPal prepaid card or a Prepaid Visa card from stores with cash. You will be able to use those online to purchase goods and services. 

Share this comment


Link to comment
1 minute ago, jen said:

I would think there will be an option to pay for your subscription through PayPal. You can either get a PayPal prepaid card or a Prepaid Visa card from stores with cash. You will be able to use those online to purchase goods and services. 

Where I live it is very difficult to access these services. Not even I buy leadwerks 4, someone bought it for me, I charge 8% commission and I send it to my steam account as a gift.

Share this comment


Link to comment
14 hours ago, jen said:

I would think there will be an option to pay for your subscription through PayPal. You can either get a PayPal prepaid card or a Prepaid Visa card from stores with cash. You will be able to use those online to purchase goods and services. 

Minecraft's early days got kind of ****ed by pay-pal. They had a cash withdraw limit.

You could do your own credit card processing and subscription through Stripe.
https://stripe.com/

It's fairly easy to implement. Fees are only like 3-5%.

Share this comment


Link to comment
55 minutes ago, martyj said:

Minecraft's early days got kind of ****ed by pay-pal. They had a cash withdraw limit.

You could do your own credit card processing and subscription through Stripe.
https://stripe.com/

It's fairly easy to implement. Fees are only like 3-5%.

I can also get a merchant account and not even deal with PayPal etc.  Paypal has had a lot of issues in the past and I would not trust them to handle any serious amounts of money.

Share this comment


Link to comment

When I did UE4 I would simply get one month to get the software and then I was able to cancel and just not get updates but still use that version. I think they eventually stopped the monthly fee and I would think for that reason. They would pump out smaller updates and fixes weekly which I think they thought would be why people would keep thier monthly they subscription, but I don't think it worked out that way. I would renew about every 6 months just for that one mo th to get caught up on all the updates/fixes. 

What is is your plan for making this subscription work? Will we not be able to use the app without an active subscription or will we not be able to get updates only without an active subscription? If we can still use the app but not get updates then I can't see people keeping an active monthly subscription. They'll just renew when they want an upgrade or a fix. This, however, means to incentivize people you have to be pumping out fixes and advancements every month to make it worth it for people.

If you make it so we can't use the app then that only refers to the editor. People could still code in LE without issue. The editor isn't really required it's just a convience thing. They could easily build most of thier levels and such in a modeling package.

I don't see how a subscription base works in today's world which is why I think you see engines dropping that idea now. Your pricing models are always about 2-3 years behind the big engine leaders. Learn from thier mistakes.

People come to Le because it's easy and it has no royalties. I think they also liked just putting up a reasonable amount of money every year or so and forgetting it. If people can still use the software and just not get updates you'll end up with probably $5-$-10 a year from a person. Probably just best to charge $25 per major update which should be yearly. You'll get more money and people won't have to screw around with the monthly game of subscribing and unsubscribing based on what and when they want to update to current. Most people probably see $25 a year for updates as very fair.

Share this comment


Link to comment

Are there any plans for Console and Mobile export? I think those would bring in a lot of money if sold as separate modules.

Share this comment


Link to comment
41 minutes ago, jen said:

Are there any plans for Console and Mobile export? I think those would bring in a lot of money if sold as separate modules.

No one I know of has a console developer license.  If one company wanted to use it I would be willing to develop it if they were willing to pay.  It would probably cost about $150,000 because I need to hire one additional full-time programmer.

Mobile would involve too many compromises to the renderer and would hold back the engine.  We are going in the direction of VR which means hyperrealism and performance, performance, performance.

Share this comment


Link to comment
1 hour ago, Rick said:

What is is your plan for making this subscription work? Will we not be able to use the app without an active subscription or will we not be able to get updates only without an active subscription? If we can still use the app but not get updates then I can't see people keeping an active monthly subscription. They'll just renew when they want an upgrade or a fix. This, however, means to incentivize people you have to be pumping out fixes and advancements every month to make it worth it for people.

I don't see how a subscription base works in today's world which is why I think you see engines dropping that idea now. Your pricing models are always about 2-3 years behind the big engine leaders. Learn from thier mistakes.

People come to Le because it's easy and it has no royalties. I think they also liked just putting up a reasonable amount of money every year or so and forgetting it. If people can still use the software and just not get updates you'll end up with probably $5-$-10 a year from a person. Probably just best to charge $25 per major update which should be yearly. You'll get more money and people won't have to screw around with the monthly game of subscribing and unsubscribing based on what and when they want to update to current. Most people probably see $25 a year for updates as very fair.

Other engines do not make their money from consumer sales at all.  They have thrown in the towel and just give their product away for free (even their source code, lol!).  Leadwerks is the leader in the consumer space, and the only company that does well in this market.  Our nearest competitor CryEngine only got one third the number of customers Leadwerks has on Steam.  Therefore Crytek, Unreal, and Unity should be taking notes from me, since I have humiliated them so badly in this arena.

The LE5 beta is the first time I have done a subscription so I'm sure there will be a lot to learn.  Initially, updates will be frequent, the beta subscription is only targeted at enthusiasts who want to support the development of LE5 and get there hands on the tech early, and there will initially be no editor (use Leadwerks Editor 4).

If I continue offering a subscription model, it is not a problem to make the editor stop working when the subscription becomes inactive.  I imagine I will probably want to offer both options like Microsoft does for Office.  I think once a subscription is in place, it tends to just keep going because it's only a small amount, like a gym membership.

Share this comment


Link to comment
55 minutes ago, Josh said:

Other engines do not make their money from consumer sales at all.  They have thrown in the towel and just give their product away for free (even their source code, lol!).

They have a different business model than yours.  I imagine they make a lot of their money from asset sales on their stores.  As such, it makes sense for them to send as many people to the stores as possible by giving away their engine for free.

Share this comment


Link to comment
9 minutes ago, gamecreator said:

They have a different business model than yours.  I imagine they make a lot of their money from asset sales on their stores.  As such, it makes sense for them to send as many people to the stores as possible by giving away their engine for free.

You can do the math yourself.  The money Unity makes on asset sales is pitiful given their amount of funding.  It doesn't even come close to what their investors want.  And they are on like their 11th year of venture capital funding, whereas most other startups would have an exit by now (6-7 years is typical).  Now they only hold back game development technology.  Leadwerks is fine, but other good engines can't compete against free Silicon Valley money.  On top of that, their engine sucks and everyone knows it.  Pathetic!

Share this comment


Link to comment

 

What I think is that there are different business models, and within each one there are potential customers. Something I would like to see is an expansion of Leadwerks, to the Latin market, forums, communities, channels of tutorials in Spanish. And a reseller system to earn a percentage.

Share this comment


Link to comment
14 minutes ago, DoomSlayer said:

When LE5 is released on Steam it will also use the Steam Workshop?

That depends on whether I am satisfied with Valve's commitment to supporting this feature.  In any case, some type of in-app store will be included.

Share this comment


Link to comment
42 minutes ago, Josh said:

Leadwerks is fine, but other good engines can't compete against free Silicon Valley money.  On top of that, their engine sucks and everyone knows it.  Pathetic!

EU has made you frisky lol.

Share this comment


Link to comment

You guys forgetting about open source and free game engines. I think Godot 3.1 is going to be a killer engine(with updated 2D and 3D). There is also banshee game engine, atomic , lumix and etc. When leadwerks 5 is released I'm seriously going to compare which is better and I honestly kinda hate subscription based pricing. I'm not going to have any loyalty to any product or brand. I will switch and use which product that is suitable for me in terms of cost, features wise and etc.

 

Share this comment


Link to comment
59 minutes ago, tumira said:

You guys forgetting about open source and free game engines. I think Godot 3.1 is going to be a killer engine(with updated 2D and 3D). There is also banshee game engine, atomic , lumix and etc. When leadwerks 5 is released I'm seriously going to compare which is better and I honestly kinda hate subscription based pricing. I'm not going to have any loyalty to any product or brand. I will switch and use which product that is suitable for me in terms of cost, features wise and etc.

 

It ends up being more about your time. Eventually your time is limited due to other commitments and you want to be as productive as you can. Switching engines all the time limits your productivity while increasing your knowledge. It's a trade-off.

Share this comment


Link to comment
5 hours ago, tumira said:

You guys forgetting about open source and free game engines. I think Godot 3.1 is going to be a killer engine(with updated 2D and 3D). There is also banshee game engine, atomic , lumix and etc. When leadwerks 5 is released I'm seriously going to compare which is better and I honestly kinda hate subscription based pricing. I'm not going to have any loyalty to any product or brand. I will switch and use which product that is suitable for me in terms of cost, features wise and etc.

 

I am not forgetting.  I have seen a million of these come with huge fanfare and big announcements and then they quietly disappear into the night after that.  If it was good, they would charge money for it.  Leadwerks 5 will cost money because you can't get anything like it anywhere else.  The architecture I have designed will make your games run faster than anything else possible.  In fact, nothing else can possibly be faster because Leadwerks 5 is like a space-time warp of the fabric of the universe.  At least, it will seem that way when you are using it.

Combine that with our ease of use (smart pointers and a new editor will make it even better) and new Leadwerks hyperrealism for VR, and Leadwerks 5 will be like using an advanced alien civilization's game development tools.

Share this comment


Link to comment
2 hours ago, Josh said:

I am not forgetting.  I have seen a million of these come with huge fanfare and big announcements and then they quietly disappear into the night after that.  If it was good, they would charge money for it.  Leadwerks 5 will cost money because you can't get anything like it anywhere else.  The architecture I have designed will make your games run faster than anything else possible.  In fact, nothing else can possibly be faster because Leadwerks 5 is like a space-time warp of the fabric of the universe.  At least, it will seem that way when you are using it.

Combine that with our ease of use (smart pointers and a new editor will make it even better) and new Leadwerks hyperrealism for VR, and Leadwerks 5 will be like using an advanced alien civilization's game development tools.

Are you watching too much scifi movies or series :lol: ? Anyway I would wait for Leadwerks 5 to be released first then I will decide which is better for me to proceeds. I think that is a fair thing to do.

Share this comment


Link to comment

Of course, but once you see it you will never want to use anything else.  Leadwerks 5 is going to be the best game development tool ever created.

Share this comment


Link to comment

@tumira I've used many game engines including those on your list, and they did not compare well against Leadwerks. I have 10 years of experience going back and forth using different engines and I ended up settling with Leadwerks. I have been using it for little over a year now. I have reached the farthest in my game development hobby with Leadwerks than any of the other engines I've used in the past, and I've used them thoroughly. I can say with confidence, Leadwerks has something the other engines do not have, and that's a combination of many things including flexibility, accessibility, simplicity, intuitiveness, and power. It currently lacks a few things but those features aren't far from reach, in many cases you can even implement the features yourself. 

I do look forward to welcoming you back once you realize the amount of frustration dealing with the other engines in the future.

 

Share this comment


Link to comment
14 hours ago, tumira said:

... Godot 3.1 is going to be a killer engine(with updated 2D and 3D). ...

This is the first time I have heard of this engine and now checking it out. Thanks for mentioning this game engine. :)

I always come back to Leadwerks. :D

Share this comment


Link to comment

@SpEcIeS It doesn't have a CSG editor as with all the other engines mentioned. Good luck on the level design. That's what sets Leadwerks apart from those other engines, it actually has its own level editor which primarily supports CSG brushes. Even Unity doesn't support CSG by default, at the start people were clueless until someone came out with a mod that allowed them to create CSG brushes.

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 Chris Vossen in Chris Vossen's Development Blog 6
      There are two types of days here at Leadwerks; days that we work and those that we werk. On werk days we hunker down at our desks, cups of caffeine in hand, and code (Unless you’re thinking… or pretending to think). Then there are work days, on these days we focus on business development: researching, planning, and occasionally field trips. So to kick off our intern hunt members of Leadwerks grabbed their sack lunches, kissed their monitors farewell, and ventured over to the Sacramento State University for some high octane presentations!
       



       
      These action packed presentations were given to students in both a game architecture course and a 3D modeling class, focusing on highlighting our four new internship openings:
       

      Programming Internship


      Assist the development team with core engine design
      Work with game development team to create a sample Leadwerks3D game
      Gain experience working in a professional software development environment
      C++ and Lua experience are a plus but not required

       

      3D Art internship


      Become proficient with the Leadwerks3D design tools
      Provide feedback to the development team to improve the art pipeline
      Assist game development team by producing 3D models, textures, animations, and game levels

       

      Web Development Internship


      Work with marketing to enhance our online identity
      Develop social features for our online community of game developers
      Foster online community relations

       

      Marketing Internship


      Author promotional materials for website, press releases, and newsletters
      Interact with the development team to communicate technical information to the public
      Enhance and promote our unique company brand

       
      We had a wonderful reception and have received an outpour of interest. The trip was well worth leaving our keyboards neglected for one day. A special thanks to everyone at Sac State and with any luck the Leadwerks intern family may be growing in the future!
    • By Josh in Josh's Dev Blog 2
      DPI scaling and the 2D drawing and GUI system were an issue I was a bit concerned about, but I think I have it worked out. This all goes back to the multi-monitor support that I designed back in September. Part of that system allows you to retrieve the DPI scale for each display. This gives you another piece of information in addition to the raw screen resolution. The display scale gives you a percentage value the user expects to see vector graphics at, with 100% being what you would expect with a regular HD monitor. If we scale our GUI elements and font sizes by the display scale we can adjust for screens with any pixel density.
      This shot shows 1920x1080 fullscreen with DPI scaling set to 100%:

      Here we see the same resolution, with scaling set to 125%:

      And this is with scaling set to 150%:

      The effect of this is that if the player is using a 4K, 8K, or any other type of monitor, your game can display finely detailed text at the correct size the user expects to see. It also means that user interfaces can be rendered at any resolution for VR.
      Rather than trying to automatically scale GUI elements I am giving you full control over the raw pixels. That means you have to decide how your widgets will be scaled yourself, and program it into the game interface, but there is nothing hidden from the developer. Here is my code I am working with now to create a simple game menu. Also notice there is no CreatePanel(), CreateButton(), etc. anymore, there is just one widget you create and set the script for. I might add an option for C++ actors as well, but since these are operating on the main logic thread there's not really a downside to running the code in Lua.
      local window = ActiveWindow() if window == nullptr then return end local framebuffer = window:GetFramebuffer() if framebuffer == nil then return end self.gui = CreateGUI(self.guispritelayer) --Main background panel self.mainpanel = CreateWidget(self.gui,"",0,0,framebuffer.size.x,framebuffer.size.y) self.mainpanel:SetScript("Scripts/GUI/Panel.lua", true) local scale = window.display.scale.y local w = 120 local h = 24 local sep = 36 local x = framebuffer.size.x / 6 local y = framebuffer.size.y / 2 - sep * 3 self.resumebutton = CreateWidget(self.mainpanel,"RESUME GAME",x,y,w,h) self.resumebutton:SetScript("Scripts/GUI/Hyperlink.lua", true) self.resumebutton:SetFontSize(14 * window.display.scale.y) y=y+sep*2 self.label2 = CreateWidget(self.mainpanel,"OPTIONS",x,y,w,h) self.label2:SetScript("Scripts/GUI/Hyperlink.lua", true) self.label2:SetFontSize(14 * window.display.scale.y) y=y+sep*2 self.quitbutton = CreateWidget(self.mainpanel,"QUIT", x,y, w,h) self.quitbutton:SetScript("Scripts/GUI/Hyperlink.lua", true) self.quitbutton:SetFontSize(14 * window.display.scale.y) w = 400 * scale h = 550 * scale self.optionspanel = CreateWidget(self.mainpanel,"QUIT", (framebuffer.size.x- w) * 0.5, (framebuffer.size.y - h) * 0.5, w, h) self.optionspanel:SetScript("Scripts/GUI/Panel.lua", true) self.optionspanel.color = Vec4(0.2,0.2,0.2,1) self.optionspanel.border = true self.optionspanel.radius = 8 * scale self.optionspanel.hidden = true  
    • By Josh in Josh's Dev Blog 2
      Previously I talked about the technical details of hardware tessellation and what it took to make it truly useful. In this article I will talk about some of the implications of this feature and the more advanced ramifications of baking tessellation into Turbo Game Engine as a first-class feature in the 
      Although hardware tessellation has been around for a few years, we don't see it used in games that often. There are two big problems that need to be overcome.
      We need a way to prevent cracks from appearing along edges. We need to display a consistent density of triangles on the screen. Too many polygons is a big problem. I think these issues are the reason you don't really see much use of tessellation in games, even today. However, I think my research this week has created new technology that will allow us to make use of tessellation as an every-day feature in our new Vulkan renderer.
      Per-Vertex Displacement Scale
      Because tessellation displaces vertices, any discrepancy in the distance or direction of the displacement, or any difference in the way neighboring polygons are subdivided, will result in cracks appearing in the mesh.

      To prevent unwanted cracks in mesh geometry I added a per-vertex displacement scale value. I packed this value into the w component of the vertex position, which was not being used. When the displacement strength is set to zero along the edges the cracks disappear:

      Segmented Primitives
      With the ability to control displacement on a per-vertex level, I set about implementing more advanced model primitives. The basic idea is to split up faces so that the edge vertices can have their displacement scale set to zero to eliminate cracks. I started with a segmented plane. This is a patch of triangles with a user-defined size and resolution. The outer-most vertices have a displacement value of 0 and the inner vertices have a displacement of 1. When tessellation is applied to the plane the effect fades out as it reaches the edges of the primitive:

      I then used this formula to create a more advanced box primitive. Along the seam where the edges of each face meet, the displacement smoothly fades out to prevent cracks from appearing.

      The same idea was applied to make segmented cylinders and cones, with displacement disabled along the seams.


      Finally, a new QuadSphere primitive was created using the box formula, and then normalizing each vertex position. This warps the vertices into a round shape, creating a sphere without the texture warping that spherical mapping creates.

      It's amazing how tessellation and displacement can make these simple shapes look amazing. Here is the full list of available commands:
      shared_ptr<Model> CreateBox(shared_ptr<World> world, const float width = 1.0); shared_ptr<Model> CreateBox(shared_ptr<World> world, const float width, const float height, const float depth, const int xsegs = 1, const int ysegs = 1); shared_ptr<Model> CreateSphere(shared_ptr<World> world, const float radius = 0.5, const int segments = 16); shared_ptr<Model> CreateCone(shared_ptr<World> world, const float radius = 0.5, const float height = 1.0, const int segments = 16, const int heightsegs = 1, const int capsegs = 1); shared_ptr<Model> CreateCylinder(shared_ptr<World> world, const float radius = 0.5, const float height=1.0, const int sides = 16, const int heightsegs = 1, const int capsegs = 1); shared_ptr<Model> CreatePlane(shared_ptr<World> world, cnst float width=1, const float height=1, const int xsegs = 1, const int ysegs = 1); shared_ptr<Model> CreateQuadSphere(shared_ptr<World> world, const float radius = 0.5, const int segments = 8); Edge Normals
      I experimented a bit with edges and got some interesting results. If you round the corner by setting the vertex normal to point diagonally, a rounded edge appears.

      If you extend the displacement scale beyond 1.0 you can get a harder extended edge.

      This is something I will experiment with more. I think CSG brush smooth groups could be used to make some really nice level geometry.
      Screen-space Tessellation LOD
      I created an LOD calculation formula that attempts to segment polygons into a target size in screen space. This provides a more uniform distribution of tessellated polygons, regardless of the original geometry. Below are two cylinders created with different segmentation settings, with tessellation disabled:

      And now here are the same meshes with tessellation applied. Although the less-segmented cylinder has more stretched triangles, they both are made up of triangles about the same size.

      Because the calculation works with screen-space coordinates, objects will automatically adjust resolution with distance. Here are two identical cylinders at different distances.

      You can see they have roughly the same distribution of polygons, which is what we want. The same amount of detail will be used to show off displaced edges at any distance.

      We can even set a threshold for the minimum vertex displacement in screen space and use that to eliminate tessellation inside an object and only display extra triangles along the edges.

      This allows you to simply set a target polygon size in screen space without adjusting any per-mesh properties. This method could have prevented the problems Crysis 2 had with polygon density. This also solves the problem that prevented me from using tessellation for terrain. The per-mesh tessellation settings I worked on a couple days ago will be removed since it is not needed.
      Parallax Mapping Fallback
      Finally, I added a simple parallax mapping fallback that gets used when tessellation is disabled. This makes an inexpensive option for low-end machines that still conveys displacement.

      Next I am going to try processing some models that were not designed for tessellation and see if I can use tessellation to add geometric detail to low-poly models without any cracks or artifacts.
×
×
  • Create New...