Hi Tom,
I thought it over again and I think you should stay with the dot NET 
Framework for some additional reasons.
`. Since it is a new and evolving language, the features you miss may be 
created by someone else and could be used by you.
 I thought DirectX controls the force feedback to some extent so a search 
for DirectX FF code could be helpful.

One example for not finishing a game is my work with the GMA game engine 
which I have been using for the past five years.
Every few months, David adds new features and capabilities to it.
And I have learned to do things better.
A few times I have stopped developing Sarah to add these capabilities but 
although the game is better, this delayed the release of the game by months.
I think it is better to stop making changes and say the project is over and 
go on to a new one.
Of course I have been working on Sarah for three years so I should have 
taken my own advice.
An important lesson is to know when a project is finished for you can always 
tweak it a bit to improve it but at the cost of people not being able to 
enjoy the game.
For example I could wait until book seven comes out and make changes in the 
castle to match things in that book, but then it would be Christmas 2007 
before my Sarah game is finished!

Smiles,
Phil 


_______________________________________________
Gamers mailing list .. [email protected]
To unsubscribe send E-mail to [EMAIL PROTECTED] You can visit
http://audyssey.org/mailman/listinfo/gamers_audyssey.org to make
any subscription changes via the web.

Reply via email to