TRON Evolution Troubleshooting
Posted: Mon Dec 06, 2010 3:02 pm
So I managed to get the game a bit early. I'm not going to comment on the quality of it or what I think of the gameplay until I finish the Single Player game.
But what I did want to do is post a thread about troubleshooting the PC version of TRON Evolution in case anyone has any problems.
Evolution is your average console port, maybe slightly above average. At least the game gives you options to change all of your control settings for the keyboard and mouse, which a lot of console ports screw up. But it's not perfect. For example, I've discovered that you can't use more than 3 mouse buttons. Which sucks. Though perhaps I just haven't figured out the proper tweak.
Also, I'm hearing that the game won't let you set the resolution higher than 1680x1050 without again having to do some tweaking. Which is pretty idiotic.
You need to edit the GridEngine.ini file, and look for ResX and ResY entries under [SystemSettings]. Changing those will allow you to set any resolution you want. The .ini is located in My Documents > Disney Interactive Studios > Tron Evolution > UnrealEngine3 > GridGame > Config.
The game uses PhysX for its physics simulation. It's set to use the CPU for physics, by default. But if you have a powerful enough Nvidia card, you can change a setting to allow PhysX to run on the GPU. Again, the entry you need to edit is in GridEngine.ini, this time under [Engine.Engine]. Look for bDisablePhysXHardwareSupport and set it to False.
Like most Unreal engine games, it doesn't support Anti-Aliasing by default. You have to force it to work, and you'll need tools like Nvidia Inspector or RadeonPro to do it. For RadeonPro, you'll probably have to use the Force Anti-Aliasing Profile feature after setting up Evolution to work with it (GridGame.exe is the game exectuable to choose under the Triggers tab) and choose Unreal as the profile. While with Nvidia Inspector, you'll need to edit the pre-defined Evolution profile to use the executable GridGame.exe and set the Antialiasing Compatibility flag to the value 0x000100C5.
I simply haven't had enough time to do more snooping, but I'll probably come up with some more things you can tweak later.
But what I did want to do is post a thread about troubleshooting the PC version of TRON Evolution in case anyone has any problems.
Evolution is your average console port, maybe slightly above average. At least the game gives you options to change all of your control settings for the keyboard and mouse, which a lot of console ports screw up. But it's not perfect. For example, I've discovered that you can't use more than 3 mouse buttons. Which sucks. Though perhaps I just haven't figured out the proper tweak.
Also, I'm hearing that the game won't let you set the resolution higher than 1680x1050 without again having to do some tweaking. Which is pretty idiotic.
You need to edit the GridEngine.ini file, and look for ResX and ResY entries under [SystemSettings]. Changing those will allow you to set any resolution you want. The .ini is located in My Documents > Disney Interactive Studios > Tron Evolution > UnrealEngine3 > GridGame > Config.
The game uses PhysX for its physics simulation. It's set to use the CPU for physics, by default. But if you have a powerful enough Nvidia card, you can change a setting to allow PhysX to run on the GPU. Again, the entry you need to edit is in GridEngine.ini, this time under [Engine.Engine]. Look for bDisablePhysXHardwareSupport and set it to False.
Like most Unreal engine games, it doesn't support Anti-Aliasing by default. You have to force it to work, and you'll need tools like Nvidia Inspector or RadeonPro to do it. For RadeonPro, you'll probably have to use the Force Anti-Aliasing Profile feature after setting up Evolution to work with it (GridGame.exe is the game exectuable to choose under the Triggers tab) and choose Unreal as the profile. While with Nvidia Inspector, you'll need to edit the pre-defined Evolution profile to use the executable GridGame.exe and set the Antialiasing Compatibility flag to the value 0x000100C5.
I simply haven't had enough time to do more snooping, but I'll probably come up with some more things you can tweak later.