Unloader Behavior Peculiarity

[fraserm]

Hi, all. Been running RW2/TS2012 since July 2011 and I'm having a ball! I prefer running freight scenarios, and there are many out there.
I first noticed this Unloader behavior when running Great Northerner's very fine Industrial Interactive Route v4. Robbit's "Gravel Loader" scenario is the first one I ran on this route. Here is what I experienced:
When centered on the unloader, clicking the mouse on the unloader begins downloading but the red "timeline" does not appear in the lower window, and the briefing does not decrement as it should. This prevents successful completion of the scenario. I contacted robbit about it and he suggested that I click a second time, so I tried that. The timeline shows after a second click, but the hopper re-loads (at the UNLOADER...) and the briefing list then decrements. Problem there is that you now have a FULL hopper again. I invested a lot of time with RW Tools and in the Scenario Editor trying in vain to figure out why this was happening.
I recently tried several other scenarios on a different route (Barstow to San Bernadino) and I have the same goofy behavior of the Unloader. My workaround is to actually click three times on the unloader - once to unload, once to re-load but decrement the Briefing list, then once more to do a final unload. Tedious, but it gets the job done and allows me to complete a scenario successfully.
My non-expert, tentative conclusion is that it is not a scenario- or route-specific glitch, but it must be the actual Unloader item and how it's programmed.
Has anyone else seen the same behavior of the Unloader, and if so, is there another, more elegant, solution to the "peculiarity"?
Any and all input gratefully accepted.

300H spent so far, and running.

AMD FX 8150 Zambezi Black Edition 3.6 GHz, 8-Core CPU
ASUS Crosshair V Formula MB
16GB Kingstion RAM HyperX PC3 12800
Dual 500GB 7,200 RPM HYBRID HDDs in RAID 0
Dual Gigabyte Radeon HD 6950 1GB GPUs in Crossfire Configuration
Corsair HX1050 PSU (1,050 Watts)
Windows 7 Home Premium 64 bit OEM

Thanks,
Marc

[Samwolf]

I found how to correct the load\unload problem. In the scenario instructions there's a box that can be checked, (just like the "Allow Reversing" box), when you select the load\unload instruction. If a transfer point can both load and unload, to make it an unload instruction the box should NOT BE checked, to make it a load instruction the box should BE checked. This also puts the correct "load", "unload" text in the instruction . I unchecked the box in all the "unload" instructions and they all work properly.

[fraserm]

Thanks, Samwolf. I thought there would be an answer out here. To be clear, it's a scenario instruction, not the unloader itself that makes the difference? That makes sense. I need to try it out on some of the scenarios I have that show the goofy behavior.

Thanks for the hints.

Regards,
Marc

[Samwolf]

Correct, it's the scenario instruction. however in your case it sounds like the gravel unloader was set up to be able to both load and unload. I've only seen this setup on the container cranes or logging cranes. Still the instruction fix should work. Just make sure the box is unchecked.

[fraserm]

Thanks again, Samwolf. I successfully modified a number of scenarios that had the same behavior for the unloader. It's really pretty easy once you know the method. I'm learning a lot every time I ask questions. I hope that someday I'll know enough to actually jump in and create my own scenarios and maybe even distribute them.

Thanks again and Happy New Year,
Marc