Error - View Single Post - Converting PC Game to self contained PCB solution

**Iphone** · 29-Mar-2007, 03:09 AM

I think the short but sweet answer here is: Your options are limited. Let's just have a look at each option in order.

1.) You have written a DirectX game that runs on Windows. As far as I know (And I do know) DirectX *only* runs on Windows, and the Xbox/360. So right off the bat, if you want your game to run on another system you will need to port your code to that system.

gumstix - way small computing Sells embedded Linux systems on a device which is the size of a pack of gum with 200 or 400MHz processors and (optionally) wireless access and CF storage. CF would hold enough data and with wireless you could connect to a wireless hub to access the internet though the linux tcp/ip stack but I dont think a webservice is necessarily the best way to go. I would recommend using HTTP or even FTP for file transfer over the net - then you can avoid all the SOAP and other smeg that comes with it (Which you would need to code yourself).

2.) Have someone make a console for you. This is a bit of a black art and comparitively few people could make you a game console - even if they could they would charge you for it and those skills I'm sure dont come cheap. When the hardware is made for you, you now have a completely proprietary piece of hardware which you now need to code the entire interface for and possibly a less than average processor. Say goodbye to your compiler, and goodbye to your api's. In a worst case scenario you're going to be writing everything in asm, and without a native OS to host your game, you'll be writing an entire tcp/ip stack for the given architecture of your bit of kit just for networking support. Not easy, and by no means cheap.

3.) Use an existing console. DirectX leaves you with few options, but if you convert to OpenGL you could port to PSP (Using homebrew techniques), or the relatively powerful GP2X which would be much easier (As again you have the Linux OS, and a fairly healthy community of homebrew developers with good support from the manufacturer).

This is probably your most viable solution as the hardware is relatively cheap for what you get, and the architecture is well documented.

4.) Use electronic distribution and just assume that your niche market all have PC's.

5.) If you're serious about your game then you could try using a real game developer to develop your game and get it published. Stainless Games have been in the news quite a bit recently (Stainless Games | Home | Welcome)

29-Mar-2007, 03:09 AM	#2 (permalink)
Iphone Fixed Error! Posts: 4,202 Join Date: Mar 2007 Rep Power: 6 IM:	Re: Converting PC Game to self contained PCB solution I think the short but sweet answer here is: Your options are limited. Let's just have a look at each option in order. 1.) You have written a DirectX game that runs on Windows. As far as I know (And I do know) DirectX only runs on Windows, and the Xbox/360. So right off the bat, if you want your game to run on another system you will need to port your code to that system. gumstix - way small computing Sells embedded Linux systems on a device which is the size of a pack of gum with 200 or 400MHz processors and (optionally) wireless access and CF storage. CF would hold enough data and with wireless you could connect to a wireless hub to access the internet though the linux tcp/ip stack but I dont think a webservice is necessarily the best way to go. I would recommend using HTTP or even FTP for file transfer over the net - then you can avoid all the SOAP and other smeg that comes with it (Which you would need to code yourself). 2.) Have someone make a console for you. This is a bit of a black art and comparitively few people could make you a game console - even if they could they would charge you for it and those skills I'm sure dont come cheap. When the hardware is made for you, you now have a completely proprietary piece of hardware which you now need to code the entire interface for and possibly a less than average processor. Say goodbye to your compiler, and goodbye to your api's. In a worst case scenario you're going to be writing everything in asm, and without a native OS to host your game, you'll be writing an entire tcp/ip stack for the given architecture of your bit of kit just for networking support. Not easy, and by no means cheap. 3.) Use an existing console. DirectX leaves you with few options, but if you convert to OpenGL you could port to PSP (Using homebrew techniques), or the relatively powerful GP2X which would be much easier (As again you have the Linux OS, and a fairly healthy community of homebrew developers with good support from the manufacturer). This is probably your most viable solution as the hardware is relatively cheap for what you get, and the architecture is well documented. 4.) Use electronic distribution and just assume that your niche market all have PC's. 5.) If you're serious about your game then you could try using a real game developer to develop your game and get it published. Stainless Games have been in the news quite a bit recently (Stainless Games \| Home \| Welcome)