Hello.
Le Duc a la Flambe is correct. Unfortunately, despite the ideal that computers should present equal behaviours (however scaled) in all circumstances, the plethora of combinations of processors, ram-modules, motherboards, etc, means that you cannot categorically say one method is better than another, or at least not until you've tried all the combinations.
However, providing two executables for this one area seems a little excessive. If this is the final, last possible, ultimate optimisation you can provide then ok, but I'm sure there are other areas you can pull some cycles back from.
Include both methods in your game and let the user decide. That normally solves the problem for you, as most people will accept the default anyway, especially if they can't distinguish between ms in a frame.
Oh, and always make sure all media is available in a puki-rippable format.
Goodbye.
Le Duc a la Flambe is correct. Unfortunately, despite the ideal that computers should present equal behaviours (however scaled) in all circumstances, the plethora of combinations of processors, ram-modules, motherboards, etc, means that you cannot categorically say one method is better than another, or at least not until you've tried all the combinations.
However, providing two executables for this one area seems a little excessive. If this is the final, last possible, ultimate optimisation you can provide then ok, but I'm sure there are other areas you can pull some cycles back from.
Include both methods in your game and let the user decide. That normally solves the problem for you, as most people will accept the default anyway, especially if they can't distinguish between ms in a frame.
Oh, and always make sure all media is available in a puki-rippable format.
Goodbye.