Railworks America

When trying to go back and edit a scenario I've created with the FEF3, I am unable to free-fly around in the editor any further than I would be able to if I was actually playing the scenario (i.e. I can't move to a location down the route to add AI Traffic). During the initial creation of the scenario everything works fine and I'm able to navigate anywhere I want. However, when trying to go back and make additional modifications, I am limited in where I can travel.

Don't know if this has anything to do with it, but when I open the editor I am getting the pop up about the expert fireman like at the beginning of a scenario; could this be a clue to the problem?

The pop-up doesn't have anything to do with it, but here's an easy way to get rid of it - just press F2 and save the scenario. The pop-up will vanish and then you can carry on editing it.

I can close the pop up no problem....I just can't navigate more than about a mile or so away from the locomotive when editing a scenario.

In the game its self, when you press the 8 key and go into roaming view you cannot go any further than about a mile from your train, so what is happening in the editor is probably normal I would think as I don't use the editor.

trev123 wrote:In the game its self, when you press the 8 key and go into roaming view you cannot go any further than about a mile from your train, so what is happening in the editor is probably normal I would think as I don't use the editor.

Yes, I think it's normal. You can go further using the fly-out at the top to select another named place along the route.

No that's just it: its acting as if I'm running the scenario instead of editing it. Even if I use the fly out, I can not navigate more that a mile or so away. In the editor you should be able to move about the route freely.

For example: In the scenario I'm creating, it begins with the locomotive near the engine shop in Cheyenne. Now that I have the player route working the way I want, I want to add AI traffic. However, if I choose Laramie from the fly out window, I only navigate to a point just west of the BNSF sub bridge in Cheyenne and can advance no further west.

mikeg1250 wrote:No that's just it: its acting as if I'm running the scenario instead of editing it. Even if I use the fly out, I can not navigate more that a mile or so away. In the editor you should be able to move about the route freely.

For example: In the scenario I'm creating, it begins with the locomotive near the engine shop in Cheyenne. Now that I have the player route working the way I want, I want to add AI traffic. However, if I choose Laramie from the fly out window, I only navigate to a point just west of the BNSF sub bridge in Cheyenne and can advance no further west.

That's odd. As an experiment, try putting some other loco (not the FEF-3) as the player loco and see if you still get the same problem. I really can't see how one particular locomotive could cause the editor to behave so strangely.

Test Complete. If the player loco in a Standard Scenario is the FEF3 you are unable to navigate in the scenario editor more the the 1+ mile away from the locomotive. However, if it is a Free Roam Scenario or a Standard Scenario that includes the FEF3 as a AI train, you can navigate freely throughout the route. I also took the original scenario and changed the player loco from the FEF3 to one of the locos original designated as AI and once I exited and reopened the scenario, I was able to move about freely.

As note: I have only been using the advanced version of the FEF3 not the HUD version....don't know if that makes a difference.

Well then, simple solution: When in the process of creating a scenario with the intention of using the FEF-3 as the player loco, designate the FEF-3 as the player loco in the timetable menu only for test runs (like after setting up the initial route for the run, then another one to test how the AI interacts with the player train, another one to test out any custom scripting, etc.). It's as easy as one click of a box.

I've just tried it with a new free roam scenario and I could fly any distance from the FEF-3, including from one end of the NEC to the other.

Right, free roam is not the problem though. Try doing it creating a standard scenario.

mikeg1250 wrote:Right, free roam is not the problem though. Try doing it creating a standard scenario.

Tried it just now and it worked fine. I created a new standard scenario for the Sherman Hill route, placed an FEF-3 (HD) at Laramie, put a driver icon on it, clicked on the timetable button, used that view to make service1 the player train, gave it a destination in Cheyenne, used the destinations flyout (from the compass thing at the top of the screen) to select Cheyenne and teleported over to Cheyenne, placed an SD40-2 near the roundhouse, pressed play, and there I was near the FEF-3 in Laramie ready to jump into the cab.

I also tried editing the scenario after saving it and exiting the game. Worked fine. I was still able to fly all over the place and teleport to any destination on the list.

Well then, guess we'll just chalk this up to one of the many mysteries of TS2015! I've tried verifying the game cache, re-installing, changing routes and settings....I'll just go with the work around suggested for now.

mikeg1250 wrote:Well then, guess we'll just chalk this up to one of the many mysteries of TS2015! I've tried verifying the game cache, re-installing, changing routes and settings....I'll just go with the work around suggested for now.

Aye and what a mystery indeed.