Is an object smaller than this value, his reflections will not be shown. I have not much experience how big the influence on the performance is. This option is supposed to prevent too small object to be rendered. Is an object smaller than this value, it will not be shown. Reducing this value can improve the performance, is it too low you can see the object spawn in front of you and you might miss traffic signs an traffic lights. Is the distance between you and an object bigger than the value (in meters), than it will not be shown. An interesting fact is that Omsi has a dynamic tile count reduction. This option has a quite big influence in performance. 1 means that 9 tiles are loaded, with 2 your get 25 tiles around you. Very big maps could fail to load because auf the 32bit limitation of RAM usage.Īmount of tiles in each direction. With this option, the loading time for new tiles is decreased, but your overall performance may also decrease a bit and big maps needs very much time to load. Only use this if your PC has problems with loading new tiles.
It decreases the performance quite heavily if you do not have problems deactivate this option. This option is more or less a leftover from the early Omsi 2 era, when the new Multithreading (means the usage of multiple CPU-cores) caused some problems.
If it annoys you, and Omsi runs quite stable you can deactivate this here, but note that you manually need to save the situation when you close Omsi, otherwise you cannot continue at this point and can only start new situations. This may cause a short freeze especially when your performance is already low. Every time you stop the bus, Omsi saves the current Situation.
0 kommentar(er)
