omsi 2 ai buses are not showing the texures

As in the SDs, the file names of the rollband gas can be read out of the *.hof file. As soon as the destination has been entered and confirmed, the conveyor belt turns automatically to the selected position. In the case of target-based conveyor control, the target can be entered either via IBIS or a separate control panel. With a tactile control, the roller conveyor stops in the current (intermediate) position after being released, whereas with a step-by-step control it continues to rotate until the next stop position. The motor rotates in the selected direction as long as the button is pressed. In the case of tactile and step-by-step control, the control unit has two buttons per motor, one for each direction of rotation. In the case of adjustment via servomotors, the control can be either tactile, step-by-step or target-based. In reality, roller conveyors are (or were) either cranked by hand or adjusted via servomotors. Depending on the direction of travel, this conveyor belt is turned into the appropriate position so that the current destination is visible from the outside. With this destination display type, all destination signs of the current yard are on a conveyor belt.

A click on the destination sign holder could then place the sign/display it again via the Visible variable. As an alternative to the implementation, a look into a driver's folder, in which one selects the next route or destination, would be a good idea. In reality, at the beginning of the shift, exactly those signs that would be needed during the service were stowed away in the bus and carried along. Theoretically it can be solved via the Alt menu, but this variant is rather unattractive. More complex is the insertion of the correct sign. A click on the sign and via a Visible-Variable the sign is hidden. Removing the sign can be realized quite easily. Operation/Suggestion for implementation:.The file name of the current destination tga can be evaluated from the *.hof file. The destination is written on a blackboard.

Probably the simplest way to display a destination indicator. The following article only deals with the script-side display, not with the creation in the 3D program or the integration in the *.cfg file. The difficulties lie in the effort of implementation and performance. In principle, all destination display systems can be displayed using scripts in OMSI. Destination indicator of the prototype in OMSI This article was originally created by Busfanat. Here is an overview of the possibilities to display and show destinations.

In OMSI, destinations can be displayed on vehicles and objects.

Omsi 2 ai buses are not showing the texures