Quote from: prissi on January 14, 2026, 12:41:14 PMIn in r11871. Maybe there shoudl be also a method to make windows sticky, since I have closed tutorial and scenario windows countless times by accident.Now that you mention it, I've been thinking that it would be good if the scenario information window remembered the last selected tab, so when you open the window again, it would be displayed in the tab where it was previously closed.
Quote from: Yona-TYT on January 13, 2026, 10:38:04 PM...
I can trace the problem so far, the construction of the schedule is wrong, "get_waiting_halt(3)" is 0, but the value of that condition is required to be the total size of the list (len - 1), since the stop to which the values ��are applied is the last stop of the list.
...
Quote from: Yona-TYT on January 13, 2026, 10:27:10 PMI realized that using the automated script, the last vehicle in chapter 2 is created correctly, but for some reason it doesn't start from the depot, so the problem is in chapter 2, not chapter 3.That's why the script advances when starting vehicles are done using conditionals like this
Edit.
Confirmed, creating and starting the vehicle manually works fine, the problem is in the automated script logic for the vehicle in chapter 2, step G.
if (cov_valid && current_cov == ch2_cov_lim1.b){ pot2=1 } for(local j=0;j<sch_siz;j++){
if (j==get_waiting_halt(3))
sched.entries.append(schedule_entry_x(my_tile(c_list[j]), load, wait))
else
sched.entries.append(schedule_entry_x(my_tile(c_list[j]), 0, 0))
}Quote from: Andarix on January 13, 2026, 10:22:39 PMThen, apparently, the wrong depot is queried in Chapter 3.
In the post before her post.
Quote from: Yona-TYT on January 13, 2026, 10:14:46 PMThis relates to the logic used to determine the number of vehicles and whether their IDs are valid. If you look at the garage, there's a vehicle that was probably created too many and never started.
...
Quote...
I need to investigate this further. Tell me, what exactly did you modify in CH2?.
...