The standalone enterprise edition has been updated to the now-stable version 4.5. The new installer is available in the client area when you are logged into your Leadwerks account on our website.
My Gigabyte Brix pro lacks an audio in port and I was not able to find a USB microphone yesterday. However, I found a cheap webcam with audio support and have been using this to test voice recording, and it works great. Here is the final voice recording API:
bool Sound::StartRecording(const int frequency = 22050, const int format = Sound::Mono8, const int buffersize = 20480)
Sound* Sound::StopRecording()
bool Sound::StopRecording(Lobby* lobby)
lobby->SetVoiceFilter(const uint64 steamid, c
Previously I talked about a voice recording API done through Steamworks. However, OpenAL already has a simple recording API that handles this. The only thing the Steamworks API adds is compression (presumably OGG) to send the data.
I quickly implemented an OpenAL-based recording API, although I do not presently have any recording hardware device to test with. OGG compression can be added with the Ogg library that is already built into Leadwerks.
Here is my modified recording API:
s
Being able to communicate with a gaming headset or microphone is an important part of fast-paced multiplayer gaming. Therefore, Leadwerks 4.6 will feature easy to use voice recording features that allow you to talk to your teammates or taunt your opponents, in addition to a new peer-to-peer networking system.
The system is largely automated so that you only have to call a single command:
Voice::SetRecording(true)
Or in Leadwerks 5:
SetVoiceRecording(true)
In practical usage, y
Previously, I talked about the new peer-to-peer networking system that handles Nat punch-through and allows a sort of "floating" server that stays alive as long as at least one player is in the game.
The lobby system allows you to broadcast to other players that you have a game available to join. The name might be somewhat misleading, as it does not require players to hang out in a chatroom before starting the game. My implementation functions more like a standard game server list.
To
My latest entry for the Leadwerks Tournament "Dwarf Beard". This entry is really the product of a merge of a lot of work I have done over the many years.
The code template I used goes all the way back to my first game created in Leadwerks "Mages Alchemy". The Template has seen many iterations, updates as my skills increased or I just work out a more better way of doing things. For this tournament I've made many new improvements focusing on character controls, AI and handling animations. Mak
Leadwerks Game Engine 4.6 will feature a new peer-to-peer networking system that solves the NAT punch-through problem and provides an easy way to create a public list of game servers. Together with this and Leadwerks GUI which was released last year, we will soon have the tools to make a great deal of new types of games. Previously we have been focused on single-player games but the ability to create multiplayer games with fast reliable networking opens up a lot of new and fun possibilities.
Having a good set of tools is highly important. Just ask any mechanic. A good set of tools can save you a ton of time, just to prove this, try changing a water pump with a crescent wrench.
The back story...
There is some sort of issue with my project in GIT from the windows perspective in which it doesn't let me add source files to GIT without using the -f option. The last few months of development I haven't been creating "new" things, just working on content. This means that my new chang
A big bug fix update just came out for 4.5. Unless there are any major problems then I am going to go back to Europe for a while. I will be focusing on multiplayer features, specifically the P2P, lobby, and voice chat features in Steamworks, as well as converting lots of models to make them ready-to-use with Leadwerks Game Engine.
I am just going to bring my little Gigabyte Brix mini PC. If I need to I can have my big monster machines shipped to me overseas, but I'll start with this one and
An update for Leadwerks Game Engine 4.5 has been pushed out on Steam. The following fixes have been made:
View projection for Oculus Rift VR headset is fixed.
Added VR.AButton, VR.BButton, VR.GripAxis for improved compatibility with Oculus Touch controllers.
Fixed terrain collision bug.
Added missing Workshop toolbar icons on Linux.
Fixed script editor not opening on Linux.
Fixed LoadAnimation bug.
Fixed missing fall damage on player controller.
Welcome dear reader to my first Blog entry. In the following you will get a first impression of what I am working on. So lets not lose any more time and get started!
What is the Phodex Framework?
The Phodex Framework is created with the intention to provide common systems and mechanics to be able to create cool first person and especially role playing games within the Leadwerks Game Engine.
"Leadwerks Game Engine is the easiest way to make 3D games." and "It's everything you need
Ladies and gentlemen, come one, come all, to feast your eyes on wondrous sights and behold amazing feats! It's "Cirque des Jeux", the next Leadwerks Game Tournament!
How does it work? For one month, the Leadwerks community builds small playable games. Some people work alone and some team up with others. At the end of the month we release our projects to the public and play each other's games. The point is to release something short and sweet with a constrained timeline, which h
I recently picked up an Oculus Rift (CV1) in order to improve our support for this headset. It was easy to make my changes, but having the actual hardware on hand was invaluable in this process, and our support for the Rift is now much better because of this. I have now tried a total of five different VR headsets:
HTC Vive
Valve's duct-taped prototype that was the basis of the HTC Vive.
Oculus Rift DK1
Oculus Rift DK2
Oculus Rift CV1
At one point Leadwe
A new build is available on the beta branch on Steam. This fixes a couple of issues.
Oculus view projection is fixed.
Added VR.AButton, VR.BButton, VR.GripAxis for compatibility with Oculus Touch controllers:
https://www.leadwerks.com/community/topic/17052-vive-and-oculus-controls/
Fixed terrain collision bug:
https://www.leadwerks.com/community/topic/16985-character-controller-falls-through-terrain/
An update is available on the beta branch on Steam.
Fixed missing fall damage: https://www.leadwerks.com/community/topic/17005-i-dont-get-fall-damage/
Fixed LoadAnimation bug: https://www.leadwerks.com/community/topic/16982-modelviewer-load-animation/
May have fixed VR player script and tracking on Oculus Rift.
If you have an Oculus Rift please try creating a new project from the VR template project and tell me your results. If there is still a problem I will go buy
I have Steam peer-to-peer networking commands implemented into Leadwerks 4.6. Here are the commands. Note this complex system has been boiled down to just three simple commands:
class P2P
{
public:
#ifdef LEADWERKS_5
static bool Send(uint64 steamid, const int messageid, shared_ptr<BankStream> data, const int channel = 0, const int flags = 0);
static bool Send(uint64 steamid, const int messageid, shared_ptr<Bank> data, const int channel = 0, const int flags = 0);
static shared_
I have been working on some new features for the SplineTools package for Leadwerks. In the video below I demonstrate 2 new features
Reverse spline followers: Reverse any spline follower at any given time on the spline. Just call the Reverse() function on a spline follower and enjoy the ride.
Closest point on the spline: helper functions that can check what the closest point on a spline is based on given position.
I'm happy to announce the very first alpha release of Leadwerks 5 is now available.
What's New
String commands now accept a unicode overload. Add "L" in front of a string to create a wide string in C++.
Now using smart pointers. Simply set a variable to nullptr to delete an object. There is no Release() or AddRef() function.
Exclusively 64-bit!
Global states are gone. There is no "current" world or context. Instead, the object you want is passed into any function
Here is the second iteration of our VR robotic arm concept. This can be used for the safe planning of robotic motions and early detection of potential problems. VR gives us intuitive manual control with six degrees of freedom along with stereoscopic vision for superior spatial awareness.
I spent a few days setting up a server application and attempting to implement NAT punch through. You can read the details of my adventures here.
Here's what I think:
I can probably get it working.
There's a lot of weird hardware and configurations out there I can't realistically test.
There will always be a certain failure rate which translates into angry users who I can't help.
So I started to think about this backwards, by first asking what we want the user exp
Now that the steam updating works again, the Spline Tools 1.04 package has been uploaded on Steam.
Update 1.04
This version contains some updated maps for Leadwerks 4.5. The moving platforms map unfortunately is not working properly and will have to be sorted out.
Wire splines added.
Wire splines can be used for creating wires, cables or rope. By default, wires have no physics.
Physics can be added as static shapes by selecting the wire type
Luawerks has been updated to easily transform any game into a Seated VR compatible one. All what's needed is the application to be launched with "-vr". All what has been added is the tweak discussed here.
While Luawerks isn't really ideal for Room scale VR, seated on the other hand works better. The center tracking call gets called every time the game gets unpaused. At this time, the UI doesn't work with VR. Keep in-mind that there might be some tweaking to your game to make it 100% VR com
This is a rough timeline of events I am planning in the new year. It is not complete, and may change, but this is just what I am thinking right now.
January 15: Release Leadwerks 5 Alpha Zero subscription
February 1: Launch Kickstarter campaign for development of Leadwerks 5 Alpha One
February 1: Game Tournament
March 3: Kickstarter campaign complete
April 1: Leadwerks 4.6 released (vehicles, NAT punch-through)
June 30: Summer Games Tournament
Jun
.thumb.png.930e14f6185274fc318c83d22a72a188.png)
