quote:Original post by Fidelio66

quote:

quote:Renderers: I probably wouldn''t bother with software rendering. I can''t see a minimum system requirements around anywhere (yes you should have one), but it''s really not necessary for most people with the systems of today. It''s also a very time-consuming thing to write. OpenGL and Direct3D switchable renderers is good though.

One of the reasons we are making a software renderer is because it poses a good programming challenge... It can also help for the map editor, and if we have it for the map editor, might as well let the game use it.

I disagree. Now that we have 3D cards, we should use them. To fall back to software rendering like Quake I, to write a software rasterizer that constructs a frame buffer to be copied to video memory, doing stuff like texturing in software, that''s not a challenge, it''s wasting your time.

quote:Are you forgetting about your clients? Don't be so naive as to think they won't be your biggest threat. If the engine is popular enough, you will get hacked. Like superpig said, a security key, unless it is fairly complex (which is difficult to do due to resource limitations) can easily be reverse engineered (especially if the project is open-source). Look at how quickly CD key algorithms get hacked (or so I hear)

quote:Oh, it's certainly still a challenge, but yes, it's wasting time. If you're determined to include it in your project spec, Max_Payne, then I strongly recommend that you get the other two renderers done first, and then do the software renderer later when it wouldn't be blocking progress elsewhere. Consider it a perk to be added at the end.

quote:Original post by smart_idiot
You don''t need an ID. In the unlikely even they did manage to spoof their address in the packet headers, you''d end up sending their packets to the wrong address, and communication simply wouldn''t work.

quote:Original post by Max_Payne
Yeah I''m sure all racing games simulate air resistance