f13rce

View this video Description Please consider to like, comment or even subscribe If you have any questions, please feel free to ask. I will be reading all the comments! Also please note that I'm currently on my laptop because my PC is having some troubles at the moment. The sound and graphics quality is a bit off then. In case you're interested in smaller updates, I recommend going to the Facebook page of Fallen Legion: http://www.facebook.com/FallenLegionRPG

That is a lot of good news! Got a few questions/remarks: Why 64 bit only and no more 32 bit? I know most players have a 64 bit machine, but is it hard to maintain a 32 bit version as well? Will we be able to make our own threads? Currently the Leadwerks::Thread function doesn't allow me to bind class functions. I'd like to make one for things like networking and AI. I really like the smart pointer integration. Was one of the few things that I felt missing. Plans for Leadwerks after the 5.0 release? VR optimization or also some other topics you want to tackle? Plans for the Leadwerks Game Launcher? C++ games support? Is the App.h/cpp going to be removed, where main.cpp will now be the base of your project? Leadwerks 5.0 when? I really like all of these changes. Going into the right direction. I'll be one of the early adopters!

Will wait for the vehicles patch before trying it out

Space Invaders is cool - maybe even Galaxians if you want to take it one step further. It was the first game we had to make at school.

Hi! It has been a while. Here's an update on my networking library EvayrNet which is available for C++ users of Leadwerks: While implementing it into the test project in Leadwerks, I saw that the use case had some flaws which made it really hard to debug what's going on. I figured that I should be spending some time on fixing some flaws. After a few weeks I came up with the following upgrades: Debugging class Simulation mode More debugging information available Here's some detailed explanation: Debugging class I was using a lot of "printf" before which made it hard to: Find out where it's being called Disable whenever I don't need it anymore This is when I decided to make a debugging class. I replaced the printf with a custom Print function which allows you to do the same as before - except you can disable any kind of printing whenever you want (like during release builds). I also realized that capturing data is a pretty cool feature to have, which makes it easier to visualize the data you want to debug. For that I created a SaveText function which accepts a string and a filename as arguments so you can separate data like "Pings per interval", "Bytes sent per second", etc. Here is an example what you can do with it: Simulation mode This is an interesting one that I just had to implement. A connection cannot always perfect, and it can be hard to always expect a good outcome (while you might not notice it because of your tests on localhost). This is why I introduced the manipulation of the following networking stats: Minimum latency (in ms) Random latency (in ms) Packet drop percentage Packet duplication percentage It's also very easy to activate and deactivate. All you have to do is NetworkManager::StartSimulation(...) and StopSimulation(). Here is it in the command line when you activate it: More debugging information available At last I added more ways to debug the network statistics to really see what is going on. Are you not receiving data anymore? Are you flooding the network? The following information is now ready to be displayed: Newest ping (either to the server or from a specific client) Average ping (this as well^) Incoming amount of packets per second Outgoing amount of packets per second Packets per second lost Incoming data per second (in bytes) Outgoing data per second (in bytes) Current active connections (primarily for the server) That's... quite a lot more than before! Previously you could only see if you're connected and if you're the server. I hope this information will make it easier for users to visualize traffic and debug any problems they might be having. And of course, you can mix this up with the debugging class to make cool graphs like above! Final words I'm still planning on making some extra information, like on specifics to see what kind of message is creating the amount of bytes send/received. This should help debugging even more. Other than that there are still some enhancements I'd like to put in such as encryption. These can be seen here. I hope you liked this blog post! Next time I will probably be showing how to implement EvayrNet into your C++ Leadwerks project, so you can toy around with it.

From what I still remember: Josh is really happy with the new site, thinks it really shows what Leadwerks is capable of and deflects the "unfit" users. Josh has been working on VR for a while now (Oculus and HTC Vive) using OpenVR. Almost implemented except for a few things like a skewed rendering result, which seems to be fixed when looking at today's status. Leadwerks now has a big client, which is a reason why Josh has been working on VR so much. Couldn't say who because of NDAs. Said that if Leadwerks had some more reliable income that he would hire a few people to work for him. Right now everybody just buys once and you have it forever, but if that was a $5-10 subscription per month then Leadwerks would've been in a different place right now. There weren't any plans to make subscriptions happen. Said he was worried about Steam Direct. If it takes Steam's value down then he might release Leadwerks on it own or somewhere else as well. Can't remember anything else right now, I think this was pretty much it

I like it! Especially the video in the background. Makes it a bit more alive than it previously was.

You could make it do that with Leadwerks::Thread

Thanks Gamecreator Yes, my goal with this library is to make it as compatible as possible with any kind of project. I think this use case of balls flying around and such will fully test the library's functionality. After ironing the small flaws I'll make a tutorial on how to effectively use this in Leadwerks.

Intro An interesting new project of mine. I've always wanted to become a network programmer and made many multiplayer games (like Ravage Online and SIEGE) because it really excites me to see it all work. For those games I used existing networking libraries like RakNet and ENet. Although, I found it was time to make my own for once. Not to make a new wheel, but to see how it rolls. This will make the finding of an internship easier as well. For every project you will need an end goal. I want my networking library to be fast and UDP only, as you can build the reliability layer yourself. So I started off in a blank project and made three projects: Client, Server and EvayrNet. EvayrNet is only producing a .lib file which both Client and Server are using to get their functionality from (and eventually your own project). I kept my progress hidden for a while on a private repository on GitHub until it's ready for testing, which I feel is now (although it currently has some slight issues). You can check it out here. The initial integration I now want to make a simple game to see if my networking library actually does like it is intended to. I quickly wanted to make a simple game like or something similar to a " " so I started off by making loads of ball objects and see if I can make the server run some AI for stress-testing. This is the result so far: Looking good so far. Works okay up to 64 players, but any more is killing the server right now due to too many physics calculations. I'll be looking into threading before next time. For an extended video explaining the library, check it out below:

I'd love some widescreen support for the website. And +1 for the community-driven content. Shows what's possible with the engine from a user perspective. I'd be okay with (hand-picked) top content only. Also, have you considered making the banner a short video on what Leadwerks is / stuff people made with it? I think it'd fit

I think that plugin was meant for Leadwerks 2.X. Since version 3.0 I think the .mdl format has changed a bit. Try exporting to .FBX and see if it works from there. I could be wrong though.

I think that is better than we have right now. Whenever I start a new project I have to get rid of the Start and Loop function and write it from scratch which looks similar to that. Removing the App class does make you assume that there's only one application per run, which is a perfectly fine standpoint. I don't see anyone making two games in one executable. It's also good that there's less (perhaps unnecessary) overhead now, makes it easier to understand what's going on. In case people do want multiple applications in one executable then they can create their own App class. I'd say do it.

I had this problem when using source control. On default, PropertySheet.props in the location "YourProject\Projects\Windows\" (or Linux) should be pointing towards "<installpath>\steamapps\common\Leadwerks\Include" and "<installpath>\steamapps\common\Leadwerks\Library". Make sure the file paths are correct in order to compile.

Now that the Winter Games are over, it'd seem a good time to do it (and maybe have Josh try out the games live)?

@Aggror, I'm sorry but you'll have to do it with double digits