15 Tips to Optimize your Tracks
I put together a list of track building optimization tips that I got from the developers at RedLynx. They are listed below, and I made a video to explain how to do everything.
https://youtu.be/K5TA6d23vOw
Video Time Codes
Tip #1 - 00:40 - PS4, objects and logic; Xbox One, effects
Tip #2 - 01:13 - Statics Overlay
Tip #3 - 01:40 - Max number of objects in view
Tip #4 - 02:25 - Screen tearing and lag
Tip #5 - 04:00 - Effects
Tip #6 - 07:11 - Interval Triggers and Curve Data Sources
Tip #7 - 11:09 - Glue Groups
Tip #8 - 12:54 - View Distances
Tip #9 - 14:18 - Physics Bubble size
Tip #10 - 15:26 - Physics Type, Decoration Only
Tip #11 - 19:56 - Shadow Positions
Tip #12 - 21:03 - Vectors and Data Sources
Tip #13 - 22:44 - Visibility
Tip #14 - 23:39 - Lights
Tip #15 - 27:15 - Area Condition
Optimization Tips
1. In general, PS4 can handle more objects and logic. Xbox One can handle more effects.
2. Use the Statistics overlay as much as possible when doing a test run. The closer any of the bars get to red, the worse your track can perform, especially on other formats.
3. Try to ensure at all times that your maximum number of objects in view does not exceed 2000.
4. If you get screen tearing or slight lag on your system, you can pretty much guarantee that it will perform worse on another format.
5. Excessive use of effects, especially overlapping one another can cause framerate issues.
6. Multiple Interval Triggers and Curve Data Sources can cause lag if there are too many active at once. Enable any animation logic when it is needed rather than at the start of your track. Disable all logic once it is out of camera view or is not seen again.
7. Multiple or complex glue groups can cause a respawn delay on any system.
8. Reduce the view distances and shadow distances if your track allows. Reducing shadow distance can sometimes help a lot without even reducing visual quality.
9. Don’t increase the physics bubble size!
10. Make water planes decoration only unless the player hits them.
11. Lots of shadows near to the driving line can cause lag at times. Alter the sun direction slightly or move objects away. Complex trees can make this issue worse.
12. Vectors and data sources changing the properties of many objects can cause heavy lag.
13. Making many objects become visible or invisible at once can cause a freeze.
14. Turn lights on and off as needed. Glue lights together and place the pivot point on the driveline to help ensure they stay on.
15. Use Area Condition to decrease the view distances whenever possible. This may help when using complex animations in smaller areas of a track.