Up to now I've used F3 only to tell me the signal state ahead. I'll have to try using F3 for more than that, I guess. I've never really investigated what F5 can do. I know it adds text to the screen but I've never taken a good look to see what information is there. I also tried adding a speed sign into the route where I'm having an issue and it did add the yellow HUD indicator. I'm investigating further why, on the actual path my scenario is taking, the indicator is not showing when there's a limit change
and a sign on the track. I'm thinking (bad, I know...

) that the sign is not tied to the track that I'm actually on, but an adjacent track. I made a small free-roam scenario to take a look at that. Then again, maybe I'm over-analyzing this... (But I'm learning a
TON of stuff as I go along!)
All that considered, I know there are some situations where speeds are "just known". Portland Terminal, for instance, has no signs at all. I asked G-Trax about it and they told me that it's intentional, that small switching routes like Portland typically don't have them but that speeds are known by crews.
Thanks for the suggestions!
Just drivin' trains and havin' fun!
I'm adding some AI to my scenario to break up the monotony of long solo runs. I'll publish it when I'm satisfied that it's "busy" enough. It's kind of a long run, about 1:45, going southeast from East Brunswick Yard to Potomac Yard. It's a very fun learning experience. It's actually easier than I thought it'd be.
Best,
Marc