Two things I noticed though (I suppose the development is just not at that step at the moment): frogs are not generated/shown...
Both are as expected: Switch points and tunnels are currently not displayed/loaded.
Two things I noticed though (I suppose the development is just not at that step at the moment): frogs are not generated/shown...
Both are as expected: Switch points and tunnels are currently not displayed/loaded.
Patch 1.EA.111
Basis for train protection built: Now significantly expanded communication of vehicles with triggers possible!
Simulation: If passengers want a ticket to a specific destination, then a special ticket is no longer requested (day ticket, short distance, ...)
Simulation: No two passengers can order a ticket at the same time.
Simulation: Door jamming grumbling should really only happen when it does. However, it is a prerequisite that the number of doors is correctly entered for the respective vehicle!
Simulation: Weighting of the individual tickets was defective
Simulation: No ticket request while there is still money on the payment table.
Simulation: AI vehicles have not yet set the system variable "RC_DirLeaver".
Simulation: If there are closed passenger path chains in the vehicle, passengers should search for the shorter path in each case anyway. However, it is not the length of the chain that counts, but the number of path segments (previously, the "next best" path leading to the destination was simply taken).
Simulation: With the centre of gravity of the bus shifted in the Y-direction, the curve pivot point was no longer correct.
Simulation: When light sources illuminated several tunnel light source levels at the same time and these were also close together, flickering occurred.
Simulation: If "Realistic Year"/"Date"/"Time" is now set, these should also be selected in this way.
MapEditor/ContentTool: Missing language entries added
MapEditor: Auto-block signals possible: Create /no/ activation paths for this, but set the auto-block priority for the corresponding route to >= 1. If there are several self-block terms at the signal (e.g. Hp2 for reduced slip path and Hp1 for normal), then these are set different priorities: Hp1 gets priority 2, Hp2 gets 1. So if Hp2 is already active, but then the conditions for the higher priority are fulfilled (because the previous train left the Hp1-slide-through path), then the signal changes directly from Hp2 to Hp1.
MapEditor: Switch ties no longer disappear
MapEditor: Fixed problems with toolbars getting wider (top)
MapEditor: Window "Available tickets" widened
MapEditor: Additional rail quality level "dirty"
MapEditor: Fixed copy-paste function for selecting valid tickets in station window
MapEditor: Remaining problems with overlong reference lines removed
MapEditor: Crash when reopening the route window
ContentTool: Paths for passengers in vehicles for one direction only
ContentTool: Tickets can be given an (internal) free name to make them easier to recognise in special cases. However, this has no influence on what passengers say when ordering tickets
ContentTool: Start parameter "-noCatCheck" so that the ContentTool no longer checks whether the object is classified in the wrong category (1, 2 or 3).
ContentTool: If the order of coupling of broadcast buses (CoupleBroadcastBus) was not in ascending order by bus name, these connections were sometimes not recognised.
ContentTool - Interlocking tool: Block signals (without push-buttons) and "smarter" list at top right
ContentTool - Interlocking tool: Track occupancies were no longer visible when a route from the list was switched to active.
ContentTool: Delete button for tariff zones only worked for the last tariff zone
Content: Switch ties for wooden ties
Content: I have added two polys to the wooden sleepers so that they appear more three-dimensional (even without parallax occlusion). Attention: These only take effect on existing tracks when the properties of those tracks are called up once, confirmed and the terrain is regenerated at the end. ( is enough)
Content: Running surface of the S49 rails of higher quality
Thank you for the log file! The nightly build version is rather inconvenient for multiplayer games.
We currently have (known) problems with multiplayer. The next patch does not revolve around this topic, but it is of course on the "agenda" for further patches.
Hi!
Usually, you should have terrain polys which cut into terrain and "move" it in the correct height.. Why don't you have any?
OK, I understand. I will note this bus on my check list.
Hello!
What does happen after restarting the ContentTool? What does happen, if you do not save and pack, but only save?
Is it only possible if i make my own light and i can set it in the content tool?
Unfortunately yes, but we plan to create "light object helper" which you can place in the MapEditor and adjust the light parameters by start parameters.
So am i need to wait until this feature will be available
No, you have not to wait, just make your own experiments!
Hello!
The problem is that each point of the scenery can be illuminated by a maximum of as many light sources as specified in the settings. For this reason, LOTUS reduces the radius of the light sources to such an extent that they no longer overlap. Many light sources that are close together therefore do not work as desired.
We are still working on a concept ourselves for how underground stations should ideally be lit. In any case, long bar light sources will play a central role, because they can illuminate a large area with only one light source. In addition, the ambient component of an underground station light source should be set high.
Hello!
Again nice ideas, some are already noted, the others I will note!
These are all very good ideas! The idea with the simulation of the energy supply we already have in mind, the other two points we will remember when it comes to the further optimization of the functions!
I will check that.
Of course, many features are conceivable, as well as the ones you suggested. But which ones will be implemented in the end (and especially when), we can't say yet.
Hi!
Well, at the left colomn, you decide where to start your tour, e.g. Hackescher Markt. For that purpose, you should select one of the fitting entry points.
Otherwise it is possible, that you will find entrypoints, which are not part of a route, e.g. Alexanderplatz (Tram). But in this special case, you are able to enter into the "roundabout" of the Hackescher Markt, where you can start the line M1.
However - in general, there may exist entrypoints, where you cannot start any route.
Sorry, but we won't give you any release dates, that includes subway trains in base content. Yes, we need to create "round" tunnel splines for the U7, but I have no idea, when we will do this.
Unfortunately, this means that the map files seem to be broken... Please show us the map directory and the subordinate export directory.
You do mean "control center", right?
Well, the basic design won't change, it's just the normal Windows look. It is not just very much easier to add new and complex components fast, but the look fits to the design of a real control center software: No software developer of real control center software will hinder himself by creating an own GUI.
But please tell us, if you would like to have a new function you are missing!
Although the AI will get better in future, the easiest way is to give the bus an own lane without car traffic.
Hi!
It would be very helpful, if you would show us screenshots of your described situations.
The problem could be the " ' " in the comment line, too...