Jump to content
One of the best points of Vulkan is how shaders are loaded from precompiled Spir-V files. This means GLSL shaders either work or they don't. Unlike OpenGL, there is no different outcome on Intel, AMD, or nVidia hardware. SPIR-V files can be compiled using a couple of different utilities. I favor LunarG's compiler because it supports #include directives.
#extension GL_ARB_separate_shader_objects : enable
In Vulkan all shader uniforms are packed into a single structure declared in a GLSL shader like this:
layout(push_constant) uniform pushBlock
You can add more values, but the shaders all need to use the same structure, and it needs to be declared exactly the same inside the program.
Like everything else in Vulkan, shaders are set inside a command buffer. But these shader values are likely to be constantly changing each frame, so how do you hand
While we have Leadwerks today to make our apps, Turbo is currently in development. To make my projects more long term, I decided to take a step back from my VR project and create a wrapper class that apps can use to more easily transfer to the new engine. Keep in-mind, this doesn't cover everything and I'm used the last beta from November for testing so things can change. Regardless, as long as that bridge is made, I can always go back and edit the Turbo stuff as more things come online. The go
I am surprised at how quickly Vulkan development is coming together. The API is ridiculously verbose, but at the same time it eliminates a lot of hidden states and implicit behavior that made OpenGL difficult to work with. I have vertex buffers working now. Vertices in the new engine will always use this layout:
When a window in Vulkan resizes you have to manually delete the about a dozen objects and then recreate them with the new size. It's unbelievably complicated. They've pushed all the driver complexity onto the application, in an effort to simplify the job of writing drivers. I can see the advantage to this, because OpenGL drivers in the past were always inconsistent, but it is still shocking how many little details they expose in Vulkan. Just resizing a window and swapping the screen buffer invol
Two days and 823 lines of code later, I present to you the Vulkan triangle of awesomeness, running in our engine:
Here are my thoughts on Vulkan:
It's ridiculously verbose. You have to specify every little detail of the rasterizer, there's a million classes to create, and every little variable has to be exactly right. There's really no reason for this because 90% of the code is just something you copy and paste.
Shaders can use GLSL, which seems very weird, but it makes thin
The latest design of my OpenGL renderer using bindless textures has some problems, and although these can be resolved, I think I have hit the limit on how useful an initial OpenGL implementation will be for the new engine. I decided it was time to dive into the Vulkan API. This is sort of scary, because I feel like it sets me back quite a lot, but at the same time the work I do with this will carry forward much better. A Vulkan-based renderer can run on Windows, Linux, Mac, iOS, Android, PS4, an
A new update for Leadwerks Game Engine 4.6 is available on the default branch. This fixes a physics bug that would cause boxes to float into the air after the player stepped on them.
Subscribers can now download my current revision of the Turbo Game Engine design document in the private forum here:
Here are a few excerpts:
The document is still evolving so expect changes and updates.
File type : File.rar.
Size : 15 Megas.
Executable : Pawn.exe
Windows Operating System.
Mouse and keyboard.
Control the character : W, S keys, Space and camera rotation with the mouse. Space key to jump and with the shift key run.
Special key : E key, to interact with the boxes, wheel mouse click to establish if a box is kicked or transported.
Notes : The player starts with 10 units of energy, which is exhausted only when running and walking, spending
Luawerks has been updated to 1.2.8, making some small adjustments and fixes to the system. If you have previously purchased Luawerks, this update is available for free on the Leadwerks Marketplace.
Following changes include:
Fixed GUI code for Leadwerks Game Engine 4.6
Removed the feature "allowfullscreenfromeditor" as it was causing conflicts with fullscreen.
Added ignoreeditorwinsettings bool setting to force the game to ignore editor launch settings.
My last NASA project is complete. There's a physics bug in Leadwerks 4.6 that will get resolved this weekend. Starting Monday I am going to focus on the new engine again and move us forward so we can release in 2020. I am really looking forward to getting back in the game.
Thought I'd show off what I've been working on this weekend. I have implemented procedural grass as found here at Outerra. There is still more work to be done on it but so far it looks promising.
The stacking of boxes has been successful, this is thanks to the system that has been implemented, kicking the box, carrying a box, and releasing a box.
You could make things better, more realistic, such as when the kick and that the tip of the foot of the character to touch the box is flying, but the truth does not matter is just a simple game.
At this point everything has been a challenge, and what is done at the moment is just an immersion learning process in the set of tools that L
Despite the obstacles you continue with this, a challenge of making a video game, and on the basis of this come a number of questions. Why do you do it?, What do I get from this?, the truth is nothing, nothing matters, for some reason with the passage of time, I've noticed and I think I've already said it once, this is a hobby, that if it ends in something, it would be great, but if it doesn't, everything is fine.
The inconveniences at the moment, the ban of the steam account, I think it wa
The new game engine needs to roll out with some top-notch examples showing off what it can do. Here's what I want:
Offroad racing game
Space shoot-em-up side-scroller.
Side-scoller platformer similar to the Contra Playstation game.
Now what I can use your help with is finding good example games on YouTube or Steam that I can start designing these samples around. Post your ideas below!
Leadwerks Game Engine 4.6 is now available on Steam! This free update adds Steam peer-to-peer networking, lobbies, voice chat, and more. A new multiplayer game template makes it easy to get started with your own multiplayer games, adding new depth and interactivity to the fun.
We've also added over 100 bug fixes, making this the most stable release ever to build your game on!
New parameters for bet
This is something I typed up for some colleagues and I thought it might be useful info for C++ programmers.
To create an object:
shared_ptr<TypeID> type = make_shared<TypeID>(constructor args…)
This is pretty verbose, so I always do this:
auto type = make_shared<TypeID>(constructor args…)
When all references to the shared pointer are gone, the object is instantly deleted. There’s no garbage collection pauses, and deletion is always instant:
auto thing = m