We have compiled and answered some questions for you, so that you are up to date.
If nothing interferes, the update should be released on 9/30.
OMSI? Wasn't SpedV for ETS?
Yes, SpedV is usable for ETS and ATS and will remain so. We now additionally offer the option to record tours in OMSI as well and receive virtual money for it, so users have a wider choice of games that benefit their company.
Is the whole thing to be seen as competition to BCS?
Not in our conception, no. While in ETS/ATS or the BCS in OMSI we have a complete administration with truck or bus management, our OMSI integration is currently limited to recording the trips. Currently, not much more is planned there either.
Why are only single maps compatible?
In order for trip recording to work, SpedV needs to know about them. For this, the maps have to be imported by our admin team. In this process, the schedule (the so-called tours) as well as information about destinations, stops as well as their distance to each other and routes (the so-called trips) are read from the yard file and the map. SpedV then needs these to be able to record the tours. You can read which maps are imported hereand wish for more via our Discord as always.
Why are not all buses compatible?
To read data from the game, OMSI relies on bus- or mostly printer-specific variables. Therefore the printers have to be made compatible manually, which is a programming effort. Since some printers also don't use the normal line/circulation system, it is difficult to impossible to make these buses compatible.
Why does BCS support all buses/printers, but SpedV does not?
To record tours in OMSI certain tradeoffs are necessary due to the nature of the plugin interface. Because the BCS additionally takes access to the savegame, starts OMSI itself and uses partly undocumented functions, it can do more in OMSI itself.
We decided to use only the pure API as a basis for our implementation. This way we can't influence the weather for example, but in contrast to the BBS we can record streetcar tours for example. Furthermore we don't need to use external software to record the trip, only the telemetry has to be installed once (like with ETS/ATS).
Can I drive a tour in BBS and SpedV at the same time?
Yes.
What requirements do I need to successfully record a tour?
- Telemetry for OMSI installed
- compatible bus and compatible map at compatible time
- no timetable manipulations done on the map
- Timetable activated in OMSI
- Line and course entered correctly
- During the journey the correct station is switched to
Why does the message come up that not enough distance was covered and therefore the stop could not be recorded?
In order to prevent simply shifting on and not driving, we read the KM reading of the buses. This is then compared to the imported distances between stops. If not at least 80% of the distance between the stops has been covered, the stop operation is not registered and this stop is not compensated.
If you notice that this always does not work for some stops, please report to support.
How is the value of the tour calculated?
Partly based on the distance traveled, partly based on the stops. Each stop, depending on the delay, is valued at 100 - 300 €, each KM at 1560 € (corresponding to 78 €/km in ETS scale).
Furthermore, there are bonuses for trips that start within 30 minutes of real time️ as well as bonuses if several trips of the same round trip are completed in succession️. Country-specific taxes are then deducted from the calculated value️.
Do OMSI trips count towards the forwarding destination?
Yes️, for KM forwarding destinations with 20 times the distance to reflect the different scaling.