That might save us wading through many lines. If you have an in-game time, feel free to mention it. Just send us that text file along with your description of the problem. When in doubt, sort them by modification date. Older ones are typically marked with a timestamp in the name. The latest one is called "trace.txt" unless rFactor 2 crashed during the latest run. Trace logs end up in the UserData\Log folder of your rFactor 2 install. +trace=2 +traceFlush to enable logging, flushing any new lines to disk immediately, which is needed if you are reporting rFactor 2 crashing.+trace=2 to enable logging to disk (see "what to send?" below for the location of the logs).In the "general" tab there is a button called "set launch options." which shows you a text field where you can enter: You right click on rFactor 2 in your "library" and choose the "Properties." option from the context menu. Command line arguments are set in your Steam client before you launch. Trace logging is enabled via a command line argument. They are typically not useful for performance related issues. They are useful in situations where the simulation does not do what you expect it to or even crashes. Typically they can help us figure out if anything out of the ordinary happened in the game code as they typically also record error conditions or other problems we can detect. They tell us about series, cars and tracks that load, settings that get applied or saved and many other details. The trace log contains a step by step overview of events that happen inside the code of rFactor 2. If the bar behaves erratic, or somehow your graphics don't appear to be smooth, go to graphics logging. This bar indicates how much time is spent rendering graphics (mostly done on your GPU). A green bar, representing graphics, that (unless you cap your framerate) should be close to 100%.If that bar behaves erratic and shoots up to 100%, go to the section on performance logging and try to capture the issue with that enabled. This bar indicates how much time is spent doing physics calculations (which are done on your CPU). A purple bar, representing physics, that should never be close to 100%.If it is performance related, a good first step is to enable a little graph with Ctrl-C that shows two horizontal bars: This page gives a brief overview of each, its purpose and how to enable and send them.Īs a starting point, if your issue is not performance related, take a look at trace logging below. Apart from describing such steps, there are various different types of logs you can enable that help us diagnose problems in more detail.
If you have someone else that can validate those steps, that's even better. A step by step explanation would be very helpful. If you are experiencing any problems when running rFactor 2 on your system, it's obviously important to describe your problem as accurately as possible so we can try to reproduce it internally.