The title says it all, when the full debug screen F7 is active and I move next to train-tracks the game crashes with the error msg "Wrong test path next rail logic".
We found this out on IRC because we were locking for a way to show train-track-blocks visually, which F7 does (along with a lot of other stuff, making it nearly unreadable). So this is also somehow a feature request.
Edit: Testing with always on option: The problem seems to be caused by show_train_stop_points.
[0.11.13] Debug screen F7 causes CtD while close to tracks
[0.11.13] Debug screen F7 causes CtD while close to tracks
Last edited by lpw on Mon Jan 26, 2015 2:53 pm, edited 1 time in total.
-
- Filter Inserter
- Posts: 310
- Joined: Fri Nov 07, 2014 3:46 am
- Contact:
Re: [0.11.13] Debug screen F7 causes CtD while close to trac
You can use f4 I believe too set what each debug level showes
Re: [0.11.13] Debug screen F7 causes CtD while close to trac
True, but the consensus in IRC was, that block marking should not be a debug feature, but more like some usability like the inserter arrows etc.
-
- Filter Inserter
- Posts: 310
- Joined: Fri Nov 07, 2014 3:46 am
- Contact:
Re: [0.11.13] Debug screen F7 causes CtD while close to trac
One of the categories you can set debug info to it's always
Re: [0.11.13] Debug screen F7 causes CtD while close to trac
True, but it's still a debug option. And apparently it's only available to show segments, not blocks and even this visualization is terrible, show_rail_paths or show_rail_connections has a much better visualization.LordFedora wrote:One of the categories you can set debug info to it's always
But wit this I was able to figure out, that the problem seems to be caused by show_train_stop_points. Luckily my last save wasn't with rail on screen, because turning it to always directly crashes it, when rials come into view.
Re: [0.11.13] Debug screen F7 causes CtD while close to trac
Thanks for the report, the problem is fixed for 0.11.14 now.