automatic shunting yard

[Anonymous]

Thanks.

Yeah, that is another instance of improper uncoupling. There should have been only one ’empty’ ore car.

Chris

[Anonymous]

Chris on version 4 I have had the same as the governor when the twins are pushing the constence up to the back tracks and I have also had it at the beginning of the run with the other twins uploading screenshots for you to see the issue. I do not think it is the timing of the decoupler I think it maybe in the drift of the engines

Don

[Anonymous]

Don,

If we were dealing with a mechanical layout I could understand your position of engine drift. But in a computer simulation I would expect it to occur every time or none of the time.

As a note, I’ve had the timing even tighter than it is now to make the uncoupling operation as smooth as possible – occuring at/near the end of engine drift forward/backward. I’ve respaced the control-device distance just in case the actuation sensitivity of the control to triggering engine varies thereby causing the anomaly.

I have had the back mine operation run perfectly at times while at others I’ve encountered the same error both of you have witnessed.

So, I’m puzzled to say the least and that’s why I referred the matter to Brainbom.

Thanks to both for taking the time to look at it. It’s appreciated.

Regards, Chris

[Anonymous]

[img]http://www.freewebs.com/biazer9/rtr_104110.jpg[/img][p]

[img]http://www.freewebs.com/biazer9/rtr_105250.jpg[/img][p]

[img]http://www.freewebs.com/biazer9/rtr_105814.jpg[/img]

[Anonymous]

Now that I think of it, I don’t remember this type of problem in the previous version. V1.21 introduced a new feature in which tenders would not be uncoupled from their locos when passing over an open decoupler. I wonder if that might have anything to do with this behaviour? Just a thought.

Chris

[Anonymous]

Chris it is possible that there is something in the code that is causing this issue

[img]http://www.freewebs.com/biazer9/rtr_105908.jpg[/img][p]

[img]http://www.freewebs.com/biazer9/rtr_105919.jpg[/img][p]

[Anonymous]

Blazer9,

your terrain looks more than strange… 😯

brainbom

[Anonymous]

Brainbom I quess this is chris’ strip mining operation

not my landscape

[Anonymous]

Don,

Your screenshots are bizarre. They show a number of texture grids in white (unlike those the Gov took).

Chris

[Anonymous]

HMM I see what you mean…updating my video card drivers ….should not be causing this it is 128meg vodoo with directx 9c ….AMD processor 1.6….1 gig ddr ram……will let you know

[Anonymous]

Definitely something amiss there Don. Is it the same at all zoom levels?

[Anonymous]

Don, have you played about with the texture file? ‘objectsbitmapsterrain.jpg’

[Anonymous]

Governor,

I have not edited the terrain.jpg but thanks for the info{creating a curved section for the road}

and it shows on all zoom levels so i think it might be my video card drivers downloading the updated drivers now

[Anonymous]

Blazer9 wrote:

Governor,

I have not edited the terrain.jpg but thanks for the info{creating a curved section for the road}

That’s what I was thinking. If you make a curved road section on that graphic, someone else running your saved game would not see the road section you created but what was in the same position on their graphic, perhaps snow.

That would then give a simlar effect you have there.

As you say, that isn’t the case here but worth bearing in mind for anybody that is thinking of altering the original.

[Anonymous]

Governor and Brainbom

I think it was a bad memory stick

Downloaded the updated drivers 2 months out of date did not fix the issue

downloaded directx once again did not fix the issue

reinstalled the complete program upgrade and exp packs did not fix the issue

replaced the ddr stick fixed the issue

works fine now

[Author]

Posts