A shuttle flying past Jupiter – spot the bugs in this scene.Ĭurrently I am working on implementing ships. The end game and scenario will be that of EV Override, but in order to test certain features I need to use Nova. I should probably point out that the engine is being developed to be compatible with EV Nova in terms of resources and data.
Now the engine is actually rendering stuff and it looks a lot more interesting. When I last posted anything there was a very basic render pipeline set up in Metal. It doesn’t look like much but it does show a lot. This represents the progress of a month of development. Once these aspects are implemented, it will be on to developing the actual game. The only missing aspect is the rendering of text, key presses and mouse interaction.
The ability to render quads, textures (sorry that the texture is just a yellow square), move objects around, etc. This may not look like much, and to an extent it is not, but this actually has much of the graphical requirements fulfilled for Kestrel. Humble beginnings for Kestrel – A test of the render pipeline using Apple’s Metal Graphics API. Well I’m currently getting the Metal rendering pipeline and functions setup for macOS, and dispatching rendering commands from the main Kestrel game library. The functionality for old Macintosh features such as ResourceForks, QuickDraw, etc will becoming from the Diamond Project and not directly replicated into Kestrel. Once again there will be a blog post about the architecture and structure of the engine in the future. There will be some overlap between these components, but in general it should be minimal. The platform specific game will setup the environment and Metal for use, and provide any hooks that the core library will use to render sprites to the screen, and receive events. The core library and main game will be linked into these to produce an actual functional game.įor example one of the macOS versions of the game will use Metal to render any graphics.
Ev nova plugins windows code#
These are the foundational code bases that are used to make an actual executable or application bundle. This library should be completely platform agnostic. This library is the main functionality of Kestrel. This library should generally be platform agnostic. This will include all of the graphics layer abstraction, basic engine functionality etc. The result of this is that there will be several components of the project. This is mostly a personal preference and that C can compile to anything. This may evolve in to C++ in the future, but for the moment I’m wanting to keep it to C. There will be a follow up post on the future of plugin compatibility in Kestrel in the coming days.Īs it stands at the moment, I am developing Kestrel in C. Further to this it will maintain backwards compatibility with all of the old plugins and data files, whilst bringing in some new features. Kestrel is being developed from the ground up in an engine dedicated to accurately representing the Escape Velocity experience. Some information about Kestrelĭisclaimer: The project is still in its very early stages, so do not take all of this information as being set in stone. The structure and format of this blog may change over time and evolve as the project develops and the community grows. Kestrel on the other hand will be much more active, with me dedicating a couple of hours a day (where possible) to it. In the past OpenNova has been an infrequent side project for me and as a result has not allowed for many posts to be made. I’m also going to try and aim for weekly/bi-weekly updates. Some of the posts will be more technical than others, but I’ll generally try and keep them understandable. I’ll discuss design decisions, structure and implementation details of Kestrel.
This blog will become the primary development blog for Kestrel. This is mainly because I may decide to make sweeping changes to the foundation of the game and I don’t want to worry about managing the project and merge conflicts whilst I’m in this initial phase. Kestrel will not be source available during the initial run of development.
For the time being these are still being considered and weighed up.
Ev nova plugins windows license#
The biggest question in deciding a license is going to be around forks pushing changes back to the main Kestrel project, commercial limitations and attribution requirements. Whilst the exact license has not yet been decided, it will be a generally permissive license as to allow people to use the main engine as a basis for their own games. Good news to everyone who has been following OpenNova for a while. Additionally the engine itself will be adopting the name Kestrel. So what does this mean for OpenNova? Well OpenNova will becoming the foundation for the new version of EV: Override. In case you are not a frequent visitor of the r/evnova subreddit (or just missed it), Peter Cartwright recently announced a project to revive and remaster Escape Velocity Override.
0 kommentar(er)
