I''m almost finished a application framework for developing distributed real-time 3D applications using DX8 and Winsock. It will allow even relative beginner programmers to build from simple chat programs to multiplyer 3D games without the knowledge of the systems underneath. It will not allow infinite control over everything, (that''s what the underlying API''s are for) but provides a more generic solution to 3D graphics, sound, input and networking for building app''s quickly. I want to release it commercially to compete as a low-budget system for indie developers to learn and use quickly. It allows model rendering with skeletal animation using x-files, a built in terrain system and integrated world builder and will ship with a complete SDK full of samples and documentation. Of course, I will need to test it thouroughly and allow people to try it out first before buying. How should I go about this process without the system spreading around like wildfire to people who did not buy it? (Presumptious as this may be) Yes. This is impossible. I know. But how can I minimize the risk and loss to me? Chris Rose-Mathew t i n y s q u i s h y d e v e l o p m e n t

Make it free for non commercial use. Make everyone register at your website by filling out a form and then letting them download.

Also for the non commercial version, you need to lock certain features which make it impossible to distribute it as a commercial game. Such as they can't compile the exe and can only run their project through your software. I'm not a programmer but this is some of the things other people use.


Make it fairly cheap to use when using your api to create a commercial shareware game. You have allot of competition already out there, such as quest3d, and the clickteam.

John

[edited by - z3lda on February 23, 2003 1:46:24 PM]

Also, don''t have an "Unlock" code within the same program to release the features... people will distribute keygens. I''d make the registered version a separate program.

Never underestimate the power of easter eggs.

You can do any of the following:

1.Have a Start up screen or popup box that says, "if this is a commerical application, please contact "me"
2.Have a command inside your library that you can either send or type to tell if this program is registrared or unregistrared, and to who. Watch port 80 for a message, then send a message back to you, or while the library is running, type "abcdefg" and a message pops up about who registered it. (LaMothe''s KeyDown /Keyup code reads keyboard presses, even if you lose focus)
3.Have the non-commerical verson communicate to your server at start up, or every 10th or so run.
4. Don''t care, because it may not be worth your time. Its better to have lots of pirates, and several happy customers, than no pirates and very angry customers.

Thanks for the tips.
Now i''ve just got to knuckle down and finish things.

Check out a company that makes a sound engine called FMod and see how they do things. If you can do something of similar quality and use their method of sales I would be very interested in using your product.

A key issue here is effort vs reward. How much effort should you put in for the reward you will get. The market you are aiming at is not a cash rich one as most of the developers your targeting are working on very small budgets. For that reason the amount of money you will make is quite small and so the effort you expend should not be too large.

1. Make it easy to register (online, instant credit card) otherwise people wont bother to go through the process.
2. Extra features in the registered version (without making the unregistered version useless).
3. Support your product and offer upgrades that are only available directly from you. That encourages people to register in order to get them
4. Accept that many people will never register.

Dan Marchant
Obscure Productions