dabreegster
commented
1 year ago Hi,
Thanks for reporting the bugs, and welcome to the project!
Specifically, both abort me when I was requested to press the triangle bottom to show I understand how to start and pause a simulation.
I can reproduce this on task 5 (which you can jump to quickly by running with --tutorial=5 from the command line, for debugging: https://a-b-street.github.io/docs//tech/dev/index.html#development-tips). The error is:
thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: Can't find OriginalRoad(https://www.openstreetm
ap.org/way/158782224 from https://www.openstreetmap.org/node/9167872280 to https://www.openstreetmap.org/node/53128052'
, apps/game/src/sandbox/gameplay/tutorial.rs:1057:30The tutorial is hardcoded to start some agents moving around specific streets. Every time we update the OpenStreetMap data or change some of the map importing code, these hardcoded IDs can change a bit. In the short-term, we could fix the IDs in https://github.com/a-b-street/abstreet/blob/9f6211d1b842353077b3104dc8838d92e6661f3f/apps/game/src/sandbox/gameplay/tutorial.rs#L1053, using an older version of the game to figure out what the previous behavior was.
Longer-term, I'd love to revisit how the tutorial works, because this kind of thing breaks every so often, and is a hassle to maintain. It's also tough to automate any tests to catch this kind of problem.
Another consistent abort incident is when I try to choose "trips between home and work" scenario for an imported new city OSM
Hmm, I can't reproduce this one with the latest version. Seeing the error message would be super helpful. If we can't figure out how to get that to show up on Mac, maybe you could send the coordinates from geojson.io you're pasting in?
but my output.txt seems to stop updating for a while
Really strange. So the file is partly filled out, but then the last messages before the app crashes don't show up? All of the messages the code prints should be flushed immediately to STDOUT/STDERR; there's no weird buffering going on. The 1> ../output.txt 2>&1 part of the script is just standard Unix shell magic to redirect both STDOUT and STDERR to a file. You could try running just ./game in a terminal and seeing if the stack trace and error messages show up.
Thanks for your patience working through the bugs!
xiaofanliang
Hi team,
I am a new user on A/B Street. I downloaded the software on my local Mac computer and this is my Mac setting:
MacOS Monterey Version 12.0.1 Apple M1 Memory: 16GB
I opened the sh file on my mac with this extra step indicated here: https://a-b-street.github.io/docs/user/index.html "If that just opens a text file, then instead open terminal, cd to the directory you just unzipped. Then do: cd game; RUST_BACKTRACE=1 ./game 1> ../output.txt 2>&1"
I encounter a few times that the software will abort me after I clicked something to give a command. For example, it aborts me when I was going through the Traffic Simulation Tutorial and Traffic Simulation Challenges. Specifically, both abort me when I was requested to press the triangle bottom to show I understand how to start and pause a simulation. Both tutorials abort me exactly when I finished the last click. I repeated this multiple times and get aborted every time. By abort, I mean the software window quits itself and I lost all my progress.
Another consistent abort incident is when I try to choose "trips between home and work" scenario for an imported new city OSM base map in the traffic simulation sandbox (I only import the OSM and then chose the scenario). I repeated multiple times and every time I was aborted.
Any idea why the aborts happen? Is there a way that I can get specific messages about why I am aborted? I saw from some old posts that you can see from output.txt, but my output.txt seems to stop updating for a while (based on date modified on Mac) even when I am being aborted.
Thanks!