Changing engines in a scenario?

[Railroy19]

I have a question about changing engines in a scenario. I found out how to do it in a post on this forum but I can't find the instructions again.
My question is after changing the engine to what I want, can I delete the original scenario, to save space in my computer or does it not matter how many scenario files I now have.
I am pilling up a lot of them.
If I could find that tutorial again maybe the answer is in it.
I think the tutorial said. How to change engines in a scenario without using RW Tools?"

Thanks,
Bob

[Chacal]

It depends:
- if you clone the original scenario, then change the engine in the clone, then you can delete the original scenario.
- if you change the engine directly in the original scenario, then you shouldn't delete it.

The technique for changing the engine without RW-Tools:

1- Open the scenario in the RW scenario editor.
2- Add a new engine near the original one.
3- Drag the driver icon from the original engine to the new one.
4- Check the scenario in timetable view.

Step 4 is important. Amazingly, some engines will create pathing errors. I experienced this recently: I was trying different SD40-2s, and some of them would create unfixable pathing errors (dispatcher could not find a route to destination). I spent hours trying to fix the scenario, until I found it wasn't broken.

[OldProf]

It depends:
- if you clone the original scenario, then change the engine in the clone, then you can delete the original scenario.
- if you change the engine directly in the original scenario, then you shouldn't delete it.

The technique for changing the engine without RW-Tools:

1- Open the scenario in the RW scenario editor.
2- Add a new engine near the original one.
3- Drag the driver icon from the original engine to the new one.
4- Check the scenario in timetable view.

Step 4 is important. Amazingly, some engines will create pathing errors. I experienced this recently: I was trying different SD40-2s, and some of them would create unfixable pathing errors (dispatcher could not find a route to destination). I spent hours trying to fix the scenario, until I found it wasn't broken.

Whoops . . . there's another possible step; let's call it 3.5: in most cases, it's a good idea to delete the original engine and move the new one into its place. This is especially required when the original was coupled to other rolling stock, but also helps avoid path errors.
I'd also suggest an amendment to step 2: be sure that the replacement engine is heading in the same direction as the original, especially in a shunting scenario that is certain to contain Pick-up instructions, which are always specified as Front or Rear and are almost certain to fail if carried out incorrectly.

[Railroy19]

Thanks guys.
I'm so happy that someone came up with this method of changing the engines.
I could never accomplish this with RW tools. It has the Indian sign on me.
I'm going to do some changing on some scenarios and see if they work ok then delete the original after.
Another new challenge