Hmmm..... interesting one that Rod.
I haven't got it to work either yet - SBI887 was showing as I tried. This is what I did:
- I manually added SBS887 UUDD EIDW to the routes section of the database
- I shut down RB and started it up again, however, no route. When I checked the database again, SBI887 wasn't there - must be finger trouble I thought.
- I went through the same process again, and blow me, SBI887 wasn't there again after the shutdown and startup.
- So I added SBI887 using SQLite Database Browser with RB shut down.
- Ran RB and SBI887 was there in the database OK, but still not showing the route in the list, on the map, or in the data window to the tright of the photo.
- Added a fictional third destination to the route using RB Database Explorer (EGLL just to see what happened)
- Shut down RB and started it again, and my third destination wasn't showing in Database Explorer - most odd!
I also noticed that when I first looked at SBI887 (VP-BTO) the aircraft details weren't populated, but were populated by the time I shut down RB to restart it. At the restart, the aircraft details were no longer populated, but did autopopulate after a few seconds.
I'm wondering if there is some sort of time lag between manually populating the route using Database Explorer, and the data becoming available to RB. Is this why my manual edits disappeared when I restarted RB?
I think the thing to do to test this is to look out for SBI887 next time it gets airborne, and see if the route shows this time. I've added loads of routes in the past using SQL Maestro, but I've never checked to see if they become available immediately.