Openrct2: Ride list doesn't update when a ride gets deleted when game is open

[RealRexen]

Os: Windows 10
Version: 0.0.5
Build:fb456a8
If you delete a track design while in game. The list doesn't get update and shows just a blank ride. Not sure if causes a crash if chosen.

[mrtnptrs]

@RealRexen Could you test for me if choosing the deleted ride will cause a crash? As the track files get analyzed during the startup of OpenRCT2, it's logical that it can't know it isn't on your PC anymore. Maybe it just gives you an error message box when you try to build it? Testing it now myself too! :)

Edit: clicking in-game on the deleted track file/ride just does nothing (no crash, no assertion, nothing), but clicking on an other premade track does what it should do. So, this is really a non-bug, but it would be perfectly user-friendly of course to show an error like: "Track file can't be found, possibly deleted during gameplay"

[Nubbie]

I should act that way as the list gets refreshed once when you open it, if it cause a crash, then it's a problem that should be fixed (broken/missing tracks)

[RealRexen]

It doesn't cause a crash, click on it does nothing.

[mrtnptrs]

Then this issue can be closed I suppose? :) But it would may be better/more user friendly if it gives the user an error message with what's going wrong instead of doing nothing?

[marijnvdwerf]

Or monitor the filesystem for changes and update accordingly.

[Nubbie]

Is it really that necessary as you dont often remove rides while In-game, it could be useful for 'clean ups' if you have 100 rides tho :p

[mrtnptrs]

@marijnvdwerf the more advanced way, but maybe not really neccesary as.... who deletes track-files while in-game? :)

[Ryder17z]

@Nubbie considering that the original already has a lot of tracks...

There should just be a simple error message telling the file couldn't be found.

[Nubbie]

A message when about the ride not existing would be enough

[IntelOrca]

It will re-scan the tracks when you open the track list... but deleting a track when the window is already open will cause this - you can fix it just by re-opening the window.

I think this is a very rare use case to warrant a file watcher.