I'm not sure, I completely understand your problem (trying to reproduce) but with this I think can help youaudigex wrote:click set time, backspace it, ok, then hit set time again and the automatic value is set
![Pleased :]](./images/smilies/pleased.gif)
![Pleased :]](./images/smilies/pleased.gif)
Moderator: OpenTTD Developers
I'm not sure, I completely understand your problem (trying to reproduce) but with this I think can help youaudigex wrote:click set time, backspace it, ok, then hit set time again and the automatic value is set
As Rainer said, <CTRL>-click proposes a new fitting interval (without CTRL it uses the previous value and proposes an automatic one only if none was set before).audigex wrote:When adding a vehicle to a timetable which already has headway set, if you then try to set the headway you have to first clear it (click set time, backspace it, ok, then hit set time again and the automatic value is set). If you don't you get the rather unhelpful "timetable cannot be started" or something to that effect (can't check the actual message on this PC)
Reworking of manual vs. automatic modes is already on my todo list. This includes finer-grained control on what should be done automatic and what not and the possibility to change each gap length separately in manual mode. However, I can't tell when I'll implement it.audigex wrote: It would be handy if the headway could be a little more automatic (eg the "automatic" button being fully auto, if more trains get added to the shared order list, it just shortens the headway accordingly) etc.
What does happen with daylength? I'm not sure it would work out-of-the-box (especially when using days as the timetable unit, there might be conversion errors, but virtual time converts directly to ticks), but on the other hand, I don't have reports of it not working, either. That either means no one tried, or there are no substantial problems.audigex wrote:(timetables seem to get a bit pissy with daylength, I don't know if you've fixed this as I haven't played with both ITiM and Daylength)
It's in the tooltipaudigex wrote: With the first part, the CTRL+click is definately the solution I was looking for. Would it be possible for this to be a visible, rather than hidden feature though? Obviously it's no longer a problem for me, but unless people read the entire thread (wishful thinking) they wouldn't know.
Well this won't come until I implement kind of timetable stop watches, which is on my todo list, but very much at the bottom, i.e. probably far ahead.audigex wrote:Especially for headway, but if there's any possibility of a more auto- autofill, that'd be grand. Might get complicated with different speed trains though.
audigex wrote:Possible bug? Here's how I broke it...
1) Create train x between stations A and B
2) Start train x (no idea whether it has to complete any runs beforehand)
3) Create train y with shared orders with x
4) Delete train x's orders, or the train itself
Result: Stations A and B with "n passengers to A/B, no route found". Also at any stations with no direct route to A, but a route to one of B, get the same result "n passengers to A, no route found". This message remains for as long as I've been willing to sit and watch. The only solution I've found is to delete the shared orders on train y, then re-create the orders again manually. I'm assuming that if you then remove train y after creating train z, the same problem occurs.
I'm not sure if it's totally reproducable but I've definately seen it at least twice.
Patches used:
ITiM
Passenger Reduction (currently off)
Cargodest
Can supply a GRFlist if required.
Even if you had disabled all parts of ITiM, the part I suspect (the order list rewrite) can not be disabled. It would definitely help me much, if you were able to reproduce a state where it always happens, as I need to watch it happening in the debugger to find out what's wrong. I've also had cargo with stale destination from time to time, but never could pin down when it appeared, let alone under which circumstances.audigex wrote:I'm having trouble replicating it at the moment (although I wasn't using any ITiM features at the time). I'll keep trying.
I don't intend to change the autofill itself (well I already did with the non-destructive moderbn2903 wrote: I can't help it, but I always get the weirdest ideas to make this patch even betterIf a train is autofilling a timetable but somehow has to stop at a junction due to another train blocking its way, is it possible, not to record this time? Or is this impossible to do, because the train then has to accelerate again which takes longer than driving constantly?
Another thing. After a certain engine becomes available, i usually update to this (lets say: DBSet XL BR116 (max. speed 120km/h) to BR101 (max. speed 220km/h)). Would a be possible to shorten the single timetable durations with the factor 120/220 (= 6/11; of course only travelling, not waiting times), so that you don't have to autofill the timetable again?![]()
Umm, yes, at least it had a history entry on 2.30 when I just checkedrbn2903 wrote: P.P.S.: Did you update your first post when you last updated to v2.30?
Ok then, was just an idea.PhilSophus wrote:As for the second suggestion. Given that autofill is non-destructive I don't see a real need for this.
Actually I meant the sections beforePhilSophus wrote:[...] at least it had a history entry on 2.30 when I just checked [...]
Nobody's gonna be mad at you for thatPhilSophus wrote:Just a short notice: Progress in ITiM might slow-down a lot in future as my spare time might reduce significantly in future. So, don't expect so much new features either from my already long todo list or newly suggested.
Done. I should really make this a Wiki page, it would be much more maintainable then, and more important it would be maintainable by othersrbn2903 wrote:Actually I meant the sections beforefor example: 6. Non-Destructive Auto-Fill has become kind of obsolete
And C. Patch Settings should contain "Show notice when vehicle has finished timetable autofill: Off, On"
Thank you and the same backrbn2903 wrote:Greets and "Frohe Weihnachten und einen guten Rutsch ins neue Jahr!",
I think CargoDest hasn't been updated since december and so you (an me too) would miss a lot of new introduced features.MJS wrote:Does anyone perchance have a newer build with this patch
Yes, this lot of other stuff is mainly a new jobrbn2903 wrote:I think CargoDest hasn't been updated since december and so you (an me too) would miss a lot of new introduced features.MJS wrote:Does anyone perchance have a newer build with this patchbesides I didn't dare to ask. It looks so demanding, and I think Philsophus has a lot of other stuff to do
Does not really look like an ITiM- or cargodest-specific problem, IMHO. Neither of them does anything related to signal blocks. That is, I suspect that is a problem also present in trunk. You might want to search the bug tracker for a similar problem and if you don't find it, try to reproduce it with a clean Nightly (i.e. without patches). If you succeed in reproducing it you should open a bug report with a savegame (only from unpatched versions!) and steps needed to reproduce the problem.Jans wrote:Could some one Tell me what should I do with this:
Reason: Assertion failed at ..\src\signal.cpp:511: dir == INVALID_DIAGDIR || dir == GetRailDepotDirection(tile)
Users browsing this forum: No registered users and 13 guests