Changed my mind, won't post the video. But I will post my results. Note that my process is to select a scenario, whose name I provide with each route, and then click the "Start" button (there is no "Drive" buitton). I tested three routes and scenarios in my attempts. First was Suburban Glasgow. I'll come back to this one. The lowest initial load time, surprisingly, was from my second selection, Feather River Canyon, where I loaded the first of four default scenarios (Train 17 Westbound). We'll ignore the fact that this apparently has a bad instruction and there is a fixed version on the Workshop rewording it ("the original wording implied the lead locomotive was to be uncoupled from the B units and coaches"). My load time of the default original scenario was 1 minute and 16 seconds. After completing all of my tests and moving to -fastload, I dropped it down to 18 seconds in the same order as my first set of loads. Let's move to Sherman Hill. I loaded the buggiest scenario I've ever driven in Introduction to Sherman Hill. The load time is always around a minute or more, and on this occasion, it was 1 minute 41 seconds. This was a very important route for me to test as I have all of the scenarios and assets unpacked, having been messing around not only trying to work on editing scenarios, but also because I wanted to use one of the locos in other places as a substitute (and also the ES44AC has recently had applied some shiny new special paint jobs). So knowing everything was out of the AP files, I was curious. It came in at 19 seconds. So having files unpacked is not a bad thing, provided the AP file is there to load from. Let's move to the first of the three tests in each case. I nearly fell asleep on the initial load of Clydeside Direct from the Suburban Glasgow route. When I finally saw the introduction message, I clocked in at a lethargic 2 minutes 52 seconds (and I have a 1060 NVIDIA with 24 GB of RAM, that is embarrassingly slow). -fastload on this one almost had me falling out of my chair as I was shifting when the load completed. It came in exactly like FRC did, at 18 seconds. So that's a total 5 minutes and 49 seconds of loading time where I could be doing anything else reduced to a total load time of 55 seconds. I will take that any day. But here's the bonus I alluded to in an earlier post. I checked gameplay on Cajon Pass. It also loaded somewhere in the 15-20 range (I didn't write this one down). I then played Slow Climb South. Would you believe that I didn't have a moment of lag at all on that route? Good, because I did. The spot around San Bernardino was as sticky as ever. But I had previously played Arriving East on High quality and lagged constantly as I went. I was able to play Slow Climb South on High quality without any lag except for the unoptimized San Bernardino area loading when you come to W Base Line Street; it always freezes right before that bridge. It still did here. But other than that, I had no issues. It was smooth as butter. So this is a tremendous update and worth the time taken. Jamie and team should be congratulated.