01-19-2018, 01:12 PM
(This post was last modified: 02-07-2018, 06:02 PM by Brian Beuken.)
The forum now seems to be stable and happy but a bit empty and in need of a bit of colour, I'll work on that but need to focus on cleaning up demo code for the main site.
However if you've just arrived, hello, and welcome, please take a few moments to register and say hello.
Over the coming weeks I will add as much content on here as I can, hints, tips and occasional rants about using SBC's for graphic programming which is my main area of interest.
Why? You are probably asking yourself, and with good reasons, almost nobody buys an SBC to write games on.
Well, my reasons are really simple, I'm a console programmer, but I am not allowed tell people how to write games on Xbox, PlayStation or Nintendo consoles.. So I wanted to try to simulate both the experience of working on a console as a target system, and working at a fairly low level to get the hardware to work. That's possible on PC's of course, but there's just too much variety of system and speed. Having a system with fixed constraints forces you as a coder to consider how to get the best out of it and that in itself is also a lot of fun. There's a fantastic sense of achievement in getting a Raspberry to do Shadows and post processing effects fast enough to be useful in a game, and that's the kind of dogged determination that console games coders need to develop.
And, if you like SBC's generally, they really are a lot of fun to work with. You are not going to make any money writing games for SBC's but you will learn a lot about HOW to write games, by using SBC's
If you are experienced with SBC's and are aware of some of the common pitfalls beginners have getting them set up to be useful in a coding situation, please register and post your experience, the more people we can attract with a little knowledge the more we can help those seeking knowledge.
One very important point that will become apparent when people start reading the book, is that I did NO (zero) optimizing of any of the graphic code in the books. That was to avoid confusing new coders and also to present challenges for them to find and resolve. We can discuss optimization of things here as any game with a decent GPU load is going to need some considerable thought about optimizing.
Log in, say hi, and lets see if we can get a nice community of SBC game coders started
However if you've just arrived, hello, and welcome, please take a few moments to register and say hello.
Over the coming weeks I will add as much content on here as I can, hints, tips and occasional rants about using SBC's for graphic programming which is my main area of interest.
Why? You are probably asking yourself, and with good reasons, almost nobody buys an SBC to write games on.
Well, my reasons are really simple, I'm a console programmer, but I am not allowed tell people how to write games on Xbox, PlayStation or Nintendo consoles.. So I wanted to try to simulate both the experience of working on a console as a target system, and working at a fairly low level to get the hardware to work. That's possible on PC's of course, but there's just too much variety of system and speed. Having a system with fixed constraints forces you as a coder to consider how to get the best out of it and that in itself is also a lot of fun. There's a fantastic sense of achievement in getting a Raspberry to do Shadows and post processing effects fast enough to be useful in a game, and that's the kind of dogged determination that console games coders need to develop.
And, if you like SBC's generally, they really are a lot of fun to work with. You are not going to make any money writing games for SBC's but you will learn a lot about HOW to write games, by using SBC's
If you are experienced with SBC's and are aware of some of the common pitfalls beginners have getting them set up to be useful in a coding situation, please register and post your experience, the more people we can attract with a little knowledge the more we can help those seeking knowledge.
One very important point that will become apparent when people start reading the book, is that I did NO (zero) optimizing of any of the graphic code in the books. That was to avoid confusing new coders and also to present challenges for them to find and resolve. We can discuss optimization of things here as any game with a decent GPU load is going to need some considerable thought about optimizing.
Log in, say hi, and lets see if we can get a nice community of SBC game coders started