Doodle Post
1 Comment
Otter Updates
I just recently pushed some updates to Otter with a lot of changes to various things!
* The Controller class had some changes to allow for recording and playback of input. This is best applied to controllers used by Sessions. You can now record input to a compressed string, save it to a file, and play it back. This probably only works in fixed framerate mode.
* The performance of the game is now more accurately reported.
* Started working on an ImageBatch class that will batch rendering of a bunch of images sharing the same texture into a single draw call (or will try to minimize the amount of draw calls.) I might end up switching all of Otter's rendering to this technique at some point, but for now I'll leave it up to the user to decide what to batch.
* Various bug fixes across the board, and updates to the documentation. Note that the most recent version of the docs is in the repository and the ones online may not be the latest yet.
More updates are on the way! I'm planning on using Otter for a game jam this weekend and we'll see how it goes.
* The Controller class had some changes to allow for recording and playback of input. This is best applied to controllers used by Sessions. You can now record input to a compressed string, save it to a file, and play it back. This probably only works in fixed framerate mode.
* The performance of the game is now more accurately reported.
* Started working on an ImageBatch class that will batch rendering of a bunch of images sharing the same texture into a single draw call (or will try to minimize the amount of draw calls.) I might end up switching all of Otter's rendering to this technique at some point, but for now I'll leave it up to the user to decide what to batch.
* Various bug fixes across the board, and updates to the documentation. Note that the most recent version of the docs is in the repository and the ones online may not be the latest yet.
More updates are on the way! I'm planning on using Otter for a game jam this weekend and we'll see how it goes.
Otter Documentation
Just a quick update about Otter! If you don't know already, Otter is a 2d game making framework that I'm making using DotNet/C# and SFML 2.
I just pushed a first pass at some documentation. This should be enough to at least help some people out with basic questions, but I'm sure it all has a long way to go. It's being generated from the source using Doxygen.
I'm going to be attempting to use Otter for a game jam coming up next weekend, and I can't wait to see either what I can make with it, or what horrible bugs will reveal themselves! I've been tinkering away on two different projects in Otter and so far so good, but you never know until your deep in the trenches of a game jam...
I just pushed a first pass at some documentation. This should be enough to at least help some people out with basic questions, but I'm sure it all has a long way to go. It's being generated from the source using Doxygen.
I'm going to be attempting to use Otter for a game jam coming up next weekend, and I can't wait to see either what I can make with it, or what horrible bugs will reveal themselves! I've been tinkering away on two different projects in Otter and so far so good, but you never know until your deep in the trenches of a game jam...
Doodle Post
Quick doodle that I wanted to color but everyone is playing TowerFall now and I won't have time to finish it before Halloween is over!
Dev Log: Boring Code Stuff
With the release of Otter I got a brand new handful of bug reports and other things to fix, so I've been busy churning away at those over the past couple of days.
My collision code for AABB test was off by just one pixel (because I guess I needed to use >= and <= instead of just > and <, oops) so I got that fixed up. I also fixed some other bizarre bugs in the collision code that was mostly caused by me just using the wrong variable for some things.
I recently changed the input components around to allow for external sources of input. This is a pretty cool feature that I personally like a lot because it goes along with one of my methods for making computer controlled entities, like enemies or characters or whatever.
As an example, I like to code all of my enemies in games as potential players... meaning that they control themselves with input from a controller just like a player would. Instead of just moving left and right by changing their speeds, an enemy will push left and push right on its movement axis, and then other code will read that input and change the speed. For some reason I like doing this a lot because it feels like the enemies are operating under the same rules as the player -- and if I ever wanted to give players control over specific enemies or characters I could easily do that!
Even Dinobaus from Offspring Fling is internally controlled by a fake controller that is being fed input by his "AI."
This also allows for people to potentially record input over time, and then play it back by taking external control of the state of Buttons and Axes, a feature that is often cool for replays, or attract modes.
The one bug I'm currently stumped on is that there is a crash when you close a game in Windows 8 in Debug mode when using an Intel HD graphics card. A very specific weird thing that I have to hunt down... and I have no idea what could be causing it! The joys of programming.
My collision code for AABB test was off by just one pixel (because I guess I needed to use >= and <= instead of just > and <, oops) so I got that fixed up. I also fixed some other bizarre bugs in the collision code that was mostly caused by me just using the wrong variable for some things.
I recently changed the input components around to allow for external sources of input. This is a pretty cool feature that I personally like a lot because it goes along with one of my methods for making computer controlled entities, like enemies or characters or whatever.
As an example, I like to code all of my enemies in games as potential players... meaning that they control themselves with input from a controller just like a player would. Instead of just moving left and right by changing their speeds, an enemy will push left and push right on its movement axis, and then other code will read that input and change the speed. For some reason I like doing this a lot because it feels like the enemies are operating under the same rules as the player -- and if I ever wanted to give players control over specific enemies or characters I could easily do that!
Even Dinobaus from Offspring Fling is internally controlled by a fake controller that is being fed input by his "AI."
This also allows for people to potentially record input over time, and then play it back by taking external control of the state of Buttons and Axes, a feature that is often cool for replays, or attract modes.
The one bug I'm currently stumped on is that there is a crash when you close a game in Windows 8 in Debug mode when using an Intel HD graphics card. A very specific weird thing that I have to hunt down... and I have no idea what could be causing it! The joys of programming.
