CodeComparison

This plugin is a modder\'s resource aimed specifically at scripters, which allows the efficiency of various segments of code to be compared. If you don\'t know how to install mods or FOSE, or how to use the console, I leave it up to you to find out. In order to use this plugin, you\'ll need to edit the script that it uses (CodeComparisonQuestScript) so that it contains the code that you want to test. See the script for how to do this - the places in which you should insert your code have been marked off for you. Once you have done this, you can initiate your test by calling StartQuest (the quest\'s editorID is CodeComparisonQuest) in the console. The script will automatically close the console when you do this. In order to gain the best results, I recommend that you find a secluded spot so that you don\'t need to worry so much about the effects of the rendering engine, AI processing etc. For example, I use the TestQAItems cell for my tests. You can call CenterOnCell from the console without loading a game to get there as soon as you start Fallout 3, and many vanilla items are readily available for you there. In order to capture results, I recommend using the SetConsoleOuputFile console command (not the missing \"t\" in \"ouput\"), which will allow you to write all console input and output into an external file. The parameters of the test are controlled by two or three global variables, so that they may easily be altered via the console: - IterationsPerFrame An integer. It represents the number of times each segment of code should be executed per frame. Default is 1, but most simple code segments require values greater than 1 000 in order to have a noticeable effect on frame rate. - MaxFrameCount An integer. It represents the number of frames for which each segment of code should be tested. Default is 50, which I\'ve found to be a good value for each test that I\'ve performed. - CachedChecks An integer. It represents the number of times a value should be checked per iteration when the CodeComparisonQuest is set up to specifically check the effect of caching a function\'s return value in a variable. If this is not what you\'re testing, you can safely ignore this global, and you might want to alter the PrintToConsole call to omit it. If you find any bugs or have any suggestions, you can contact me via PM on the Bethesda Games Studio Forums or the Nexus Forums, where I use the username Cipscis. Alternately, you can email me at mark (at) cipscis (dot) com.