SpedV
Changelog 22.5
↑ Google.Protobuf (3.20.1)
↑ Grpc.Tools (2.45.0)
↑ NLog (4.7.15)
↑ UnitsNet (4.128.0)
↑ TwitchLib (3.5.2)
↑ Extended.Wpf.Toolkit (4.3.0)
↑ MaterialDesignColors (2.0.6)
↑ MaterialDesignThemes (4.5.0)
↑ MaterialDesignThemes.MahApps (0.2.2)
+ Company: maximum speed split between ETS and ATS
+ Company: partnerships can now be set a bit more precisely
+ Branches/Trucks: Statistics added
+ Truck: Display for active order ID added
+ Kontor: Orders for adding to savegame can now be selected
* Design revision for company partnerships
* Bugfixes for internet connection loss
* Bugfix for display of cooldown and pause time
* General bugfixes, speed improvements and design revisions
Changelog 22.03.1
+ Truck: Use of unassigned trucks can now be set
+ Truck: KM level display also added on start page of the design
* Spare parts: Purchase only possible in companies matching the branch
* General bugfixes
Changelog 22.03
↑ Google.Protobuf (3.19.4)
+ Branch and maintenance system completely reworked
+ Kontor: Trailers now also have maintenance.
+ Kontor: Trailers outside own branches now cost parking fees
+ Kontor: Filtering by comment added in trip planning
+ purchased trucks: new random damages added
+ purchased trucks: position storage added
+ Purchased trucks: New order can only be started if route has been covered to it
+ purchased trucks: A truck can only be used in one order now
+ forwarding destination: users that are no longer in the forwarding company can now also be removed
+ Forwarding agencies can now set a maximum speed for orders
+ Twitch: Connection is automatically disconnected in case of errors
+ SCS Convoy mode: warning message regarding distances added
+ Added transfer of plus time to other users
+ Spotify: volume control added
* Achievement: fixed problem with globetrotter
* Purchased trucks: complete rework of the design
* user statistics: fuel consumption display fixed
* Bugfix for SpedV crash by displaying other drivers
* SGM: added upper limit for units
* General bugfixes
Translated with www.DeepL.com/Translator (free version)
Major overhaul of the truck, branch and maintenance system
Branches
The biggest change concerns the branches. These have now been merged with the one from Kontor, so there is no longer any coexistence between different locations here. However, since this change is not really automatically convertible, the branches will also have to be purchased again in the new update. During the update day, we will completely reverse the costs for the previous branches, so you will not incur any loss here.
The new branches have expandable parking spaces for trucks and Kontor trailers, as well as maintenance spaces. There is also storage space for spare parts, more about this under "Maintenance".
The truck parking spaces basically work the same way as before: A truck has a parent branch where it is registered. The only change here is that the branch must match the truck, so an ATS truck can no longer be parked in an ETS branch.
The trailer parking spaces play into the Kontor. This is caused by a new (small) parking fee, that will be waived for Kontor trailers that are not parked in a purchased parking space. However, these are only charged as soon as a trailer is parked on this position for at least 24 real-time hours. Kontor trailers should therefore be transferred to their own branches with enough parking spaces after the update.
Two other small changes: In one city can now exist several branches (in different companies). Also, there is now money back when a branch is sold or downsized.
Truck
There are also some changes regarding trucks. Firstly, the design has been completely changed as well and now presents itself a bit more modern.
Functionally, there are the following changes:
- Trucks can now remain unassigned in addition to being assigned to a driver. These are then freely available and can be used by any user of the company.
- Trucks, however, now have a location. This means that they can basically only be used if the task starts in the city where the truck is located. (There are exceptions to this, however, so a subsequent task can also be started in another city within a 1,000 km radius, as long as the truck actually travels the distance to that city.)
- This location can also be changed via the truck management and (depending on the rights assignment) by the "owner" of the truck, but this costs time and money.
- Trucks used in a paused job cannot be used in another job.
- A driver can now be assigned more than one truck per type.
- Damaged trucks no longer yield value when sold.
Maintenance
The maintenance system for trucks has been completely reworked. Also, there is now a maintenance system for trailers. In addition to newly added random damage types, the display of required maintenance has also been revised.
From now on, maintenance can be performed internally and externally. The former requires maintenance locations, spare parts and correct positioning of the truck/trailer, while the latter costs more time and money.
Spare parts can be purchased at some locations on the map and then have to be transferred to the branch via Kontor order. For this, however, the order can be tendered to other carriers for shipment, so there is no "Kontor constraint" either.
Maintenance jobs can also be planned in advance and get started automatically as soon as all requirements are met. For this purpose, there is a list of planned maintenance with their status (or the information, which prerequisite is not fulfilled) as well as the option to cancel them. Maintenance jobs are only booked as soon as they get started, not directly during planning.
Conclusion
Of course, the changes are very far-reaching. However, with this we hope to depict more realism and thus increase the challenges a bit. However, it is also not necessary to use everything! For example, if someone does not drive consistently, rental trucks can still be used, also the handling of spare parts can be bypassed by using the external maintenance.
Even though the system has been tested for over a month, we will of course accompany the introduction phase of the new functions and look forward to your feedback in order to find and fix problems. This, just like all questions, are welcome in our Discord!
The update is planned for the night from 15.3. to 16.3. There may be some minor downtime, which we will announce separately.
All that remains is to wish you a lot of fun and a safe journey!
Changelog 22.1
↑ STSPluginLib (1.0.9)
↑ QRCoder (1.4.3)
↑ UnitsNet (4.112.0)
+ Tasks: New status for tasks invalidated by policy.
+ Tasks: Tasks with more than 1500 l tank volume can no longer be started.
+ Telemetry: IP address is now checked for correctness
+ Telemetry: IPv6 address are now also possible
+ STS: Train numbers in Great Britain are now displayed correctly
+ STS: Tooltip for train types added
+ User statistics: Quick selection for frequently used time spans added
* Live-Convoy: Bugfixes
* Fairness: Ferry-KM are considered correctly
* Kontor: Incorrect debiting of maintenance costs fixed
* G15-Applet: Username is displayed correctly again
* Order: $/mi are now calculated correctly
* Ignored users are no longer displayed even at login/logoff
* General bugfixes
Changelog 21.12
↑ STSPluginLib (1.0.8)
↑ QRCoder (1.4.2)
↑ NLog (4.7.13)
↑ Microsoft.Xaml.Behaviors.Wpf (1.1.39)
↑ MaterialDesignThemes.MahApps (0.2.0)
↑ MaterialDesignThemes (4.3.0)
↑ MaterialDesignColors (2.0.4)
↑ Extended.Wpf.Toolkit (4.2.0)
↑ System.Linq.Async (5.1.0)
↑ Grpc.Tools (2.42.0)
↑ UnitsNet (4.110.0)
+ Added new hidden Achievement
+ Kontor: Trailer statistics and trip overview added.
+ Kontor & Orders: Added live information about tours that are currently being driven.
+ Orders: Paused orders must now be continued within 500 meters of paused location
+ Forwarding destination: added settings for OMSI and Kontor
+ STS: delay information from other users is now displayed
+ STS: rerouted trains are now displayed correctly
* STS: design revisions
* Kontor: use only tons for weights again
* Orders: Some ferry combinations lead to automatic rejection of the order
* Ranks: Fix for KM bonus
* TruckersMP flyout: Fix for collision display in servers
* General bugfixes
- Kontor MP test is now no longer required
Changelog 21.11
↑ Microsoft.Windows.SDK.Contracts (10.0.22000.196)
↑ NLog (4.7.12)
↑ TwitchLib (3.3.0)
↑ Google.Protobuf (3.19.1)
↑ FPH.SpedV.API (2021.11.01.1)
+ Refuse to start if settings cannot be saved.
+ STS: Possible errors of the control center are now displayed and do not cause SpedV to crash anymore
+ Kontor: Added display for needed time of pseudo driver
+ Orders: Added possibility to delete paused orders in the Orders tab.
+ User changelog: Added founded forwarding agencies
+ Company changelog: Pageination added
+ Statistics: weekly statistics for external orders added
+ Task fail costs are shown in the accounting
+ Telemetry: network interface name as tooltip on IP
* Ranks: sorting now works live again
* Twitch: Bugfixes for API change for authentication
* SGM: Bugfix for time zones
* Kontor: Bugfix for weight reset in TMP mode
* Notificator: bugfixes
* General bugfixes
Changelog 21.10
↑ Microsoft.Xaml.Behaviors.Wpf (1.1.37)
↑ NLog (4.7.11)
↑ Google.Protobuf (3.18.0)
↑ Grpc.Tools (2.40.0)
↑ SharpZipLib (1.3.3)
↑ UnitsNet (4.102.0)
↑ FPH.SpedV.API (2021.08.15.1)
+ OMSI: Trip recording added
+ Achievements: Added another hidden achievement
+ SaveGameManager: Added the possibility to change the trailer
* Kontor: Readiness calculation revised
* Ranks: Passing on of rights can be limited now
* Ranks: Design adjustments
* Tab orders: Design completely revised
* STS: Cut off platform names if too long
* STS: Do not show exits after 21 o'clock
* General bugfixes
OMSI for SpedV!
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.
Changelog 21.8.1
+ Kontor: trailers can now be categorized
+ Kontor: added distance indicators when dispatching
* Kontor: Import problems with some cities fixed
* Kontor: Design adjustments
* General bugfixes