The targeted vehicles fall into three broad categories: a) those directly relying upon the \Scripts\AI_Cars\main_AI_XXX.osc and \Scripts\AI_Cars\lights_varlist.txt (and which constitute the vast majority) those which declare their own main script and/or variable list and emergency vehicles. It does, obviously, not apply to buses (even "pure" AI versions of them, as their scripts generally employ a more complex structure), trains, or whatever other special kind of vehicle you might have lying around. The modification is applicable to most cars and trucks with reduced scripts that is, vehicles which are solely destined for use by OMSI's AI. That is essentially the reason why I am posting this as a tutorial, rather than in the form of a "supported" modification. What this means is that if you decide to use it, you will absolutely be doing so at own risk, and are certainly encouraged to take backups before proceeding with the installation. one that is incomplete, poorly tested and generally sub-optimal. But before I get there I would first like to emphasize that what I am presenting here is a proof-of-concept modification, i.e. After that I will briefly explain how the modification works. In the remainder of this post I am going to provide the proposed script and configuration file modifications, as well as installation instructions. All that basically needs to be done, is to override the default condition evaluated by the vehicles' scripts in order to determine whether it is time to turn the lights on or off. Fortunately, like buses, AI-driven OMSI cars' and trucks' behavior is to a great extent scriptable. So, the intention is to add some "perceived randomness" into the way AI-controlled vehicles handle their lighting-related functionality, particularly with regard to (de-)activating their headlights. The second issue, on the other hand, can be combated in a multitude of ways, one of which I am going to present in this post. Of those two minor issues, unfortunately, no workaround that is both generic (as in that it is applicable to any map) and easy to employ is currently available for us mortal "end-users" (as in not being map or object authors) for the first of them.
Omsi 2 car drivers#
Similarly unrealistic is the fact that all AI-controlled cars and buses switch their headlights on or off at the same millisecond whereas in reality -at least for the time being and until real-world AI-driven cars become the norm- human drivers exhibit quite different behaviour in that regard: some (typically younger ones) just leave their vehicle's headlights turned on all the time some switch them on when a single cloud appears on the horizon, and some (typically older ones) only use them at night or when it actually gets really dark. Which is just unrealistic, since even in recent years -let alone in the 80's and 90's- the street lamps found in most EU cities are still controlled by plain timer switches (that are often not even properly synchronized) rather than modern light sensors. One of the subtle annoyances which I have had with OMSI all along, is that all of a map's street lights go on or off simultaneously, if it gets darker or brighter than a threshold, respectively. While the installation instructions still apply, the script replacements themselves are obsolete, and the ones given in post #2 should be used instead. Note: This post is only retained for the initial incentives behind this mod.
0 kommentar(er)
