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.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |