What changed
0 fixes1 addition1 change0 removals
addedI have been tracking an issue that on some systems the timing codes fails, and the game runs at uncontrollable speed. Throughout the last few builds I have tested different techniques and have not had any success solving the problem. With this update I have modified the timed codes again and it now includes frame rate clamping (among other changes). In the Menu Setup\Display you will be able to select the maximum framerate the game will run at. This will let your system (CPU and GPU) run at less load and should avoid any math errors that might occur on new system due to very high frame rates.
changedAlso, I have included a time test function that will output debug information to a file. While in game, hold 'Shift' and press 'Backspace' to start the time test. While the test if being performed, extra information will display on the screen (should take about 10 seconds with framerates clamped at 500 fps). Once that information is gone the test is done and a file called 'time_test_500.txt' will have been created in you [users][user_name]\Saved Games\Atomic Hick Software\BlocAge\ directory. If you are having the above problem, and you have time please email this file to our Support address.
Bloc-Age: Path of the Oracle changes
addedI have been tracking an issue that on some systems the timing codes fails, and the game runs at uncontrollable speed. Throughout the last few builds I have tested different techniques and have not had any success solving the problem. With this update I have modified the timed codes again and it now includes frame rate clamping (among other changes). In the Menu Setup\Display you will be able to select the maximum framerate the game will run at. This will let your system (CPU and GPU) run at less load and should avoid any math errors that might occur on new system due to very high frame rates.
changedAlso, I have included a time test function that will output debug information to a file. While in game, hold 'Shift' and press 'Backspace' to start the time test. While the test if being performed, extra information will display on the screen (should take about 10 seconds with framerates clamped at 500 fps). Once that information is gone the test is done and a file called 'time_test_500.txt' will have been created in you [users][user_name]\Saved Games\Atomic Hick Software\BlocAge\ directory. If you are having the above problem, and you have time please email this file to our Support address.
I have been tracking an issue that on some systems the timing codes fails, and the game runs at uncontrollable speed. Throughout the last few builds I have tested different techniques and have not had any success solving the problem. With this update I have modified the timed codes again and it now includes frame rate clamping (among other changes). In the Menu Setup\Display you will be able to select the maximum framerate the game will run at. This will let your system (CPU and GPU) run at less load and should avoid any math errors that might occur on new system due to very high frame rates.
Also, I have included a time test function that will output debug information to a file. While in game, hold 'Shift' and press 'Backspace' to start the time test. While the test if being performed, extra information will display on the screen (should take about 10 seconds with framerates clamped at 500 fps). Once that information is gone the test is done and a file called 'time_test_500.txt' will have been created in you [users][user_name]\Saved Games\Atomic Hick Software\BlocAge\ directory. If you are having the above problem, and you have time please email this file to our Support address.