Open Rails 0.8.0 is here!!!

[pworsley]

Congratulations to all involved with the latest release of Open Rails

I have installed v080 on two computers - the first running Windows XP, 32bit, SP3, and the other running Windows 7, 64bit, SP1

The former works as expected with all the advertised enhancements, but on the Win 7, 64bit machine everything loads up OK, but there is no F5 HUD display, and the Esc and other F-key boxes are present but empty of text. The Esc box works, insofar as I can guess where to click to exit.

I am probably missing something very simple - any clues would be gratefully received

Best wishes

Pete

[csantucci]

I have found another strange behaviour in cabs (also in the Dash-9 cab), that is that sometimes the speed indicator arrives almost at end of scale even if the real speed shown in the F5 HUD and in the route monitor is much lower.
But I would like to say that I am highly impressed: what has been done by the ORTS team is enormous. What we can play now is another game, with incredibly powerful and captivating features!

[hminky]

Running an switching activity on the La Salle Rockford and Central generated with Activity Generator.

Have no control of "ahead" switches in certain places, if I switch locomotives causing a locomotive direction change the same "ahead" switches will throw as "behinds".

There is no AI traffic.

Harold

EDIT: Started activity again can't change any switch "ahead" of train. All switches are manual.

[PORU333]

Personally the rail sounds could be improved. Specially representation of jointed rails. It seems like not enough is going on.

Even at 10mph there is a lot of click-clack and flange squeels taking place..



Then you got 30mph slowing to 10mph..


For those that prefer welded rail on tight curves..


Then finally 30mph and hitting a switch joint as well.


Also if you check out "nhrrman" on youtube, he has several videos of New England railroads, that include welded rail, slow freight, fast freight, passenger, jointed rail, and trains hitting switch joints.

Just some thoughts seems Otto brought up track joint sounds...

[kox]

The dispatcher ai is fairly stable, and the signals worked correctly except some strange happening, i've driven 100km+ on mostly single tracked line, with one crossing with AI in a loop, i was close to reach the dual track parts, (about 2 km), but sadly this happened: deadlock at red signals

[antuanfs]

Hello.

This is my problem in this new version.

error_route.jpg

Thanks for your work, OR team.

[scamel]

Well done OR Team!

I'm pleased to report that I'm not having the same problems here (that I've seen). The texture transfers look great! I kinda grew used to the big gaps, but now... wow!

Is the horn still on the to do list? I noticed the bell is now a "sticky", just like in real life.

Bravo!

[mdeming]

Also noticed this terrain difference and missing weeds in ORTS.

Part-1 in ORTS, part-2 in MSTS:

https://www.otto-wipfel.co.uk/video/...in-problem.wmv

O t t o

I assume the graininess has nothing to do with either simulator?

[Coonskin]

Mike:

Appears to me that the file has too much compression in order to get it down to a manageable meg size/etc.

[Claude350]

The horn loop is way too long. Can't get a short blast at all.

[jjtang]

Tried to work on Bernina route and at least got it worked (to some extend). The reason is that some signals saved into the wrong track node, thus OR cannot place them along the track. The fix is to find the proper track node and update information dynamically. This is an error of the route itself. MSTS loads it find since we all know now that MSTS can eat any data :-)

Anyway, I think this fix the signal issue (will test on other routes later). However, there is a problem with one switch on this route, may need to dig more.

[seagoon]

....This is an error of the route itself.....

So we should not expect to always lay the blame at the feet of OR.

Bruce

[csantucci]

Tried to work on Bernina route and at least got it worked (to some extend). The reason is that some signals saved into the wrong track node, thus OR cannot place them along the track. The fix is to find the proper track node and update information dynamically. This is an error of the route itself. MSTS loads it find since we all know now that MSTS can eat any data :-)

Anyway, I think this fix the signal issue (will test on other routes later). However, there is a problem with one switch on this route, may need to dig more.

Thanks jjtang,
can you tell me what signals have the problem, so I can correct them, or tell me how you identified such signals so that I can find them?

@seagoon: it's far from me to blame ORTS, I'm sure all my positive posts demonstrate this! See e.g. this pls.

https://www.trainsim.com/vbts/showthread.php?310553-Open-Rails-0-8-0-is-here!!!&p=1773466#post1773466

By the way, I have another issue: AI trains (when not shown on the simulation window) not always behave well on reverse points: At least some times I see them on the dispatcher monitor arriving to the reverse point and stopping there without reversing. Does someone other see the same?

[seagoon]

....@seagoon: it's far from me to blame ORTS, I'm sure all my positive posts demonstrate this! ....

Whoops!
Sorry....my retort wasn't directed at anyone in particular.

Bruce

[csantucci]

That's OK Bruce!

Attached the ORTS dev team can find the .zip file of a packaged small demo activity that shows an AI train that sticks at the reverse point. It uses the standard USA2 route and standard rolling stock. There is only a player train, that is of no interest, and an AI train that has as consist a Dash9. Its path is very simple. In Whitefish it proceeds forward, reaches a reverse point and runs backwards up to end point. Unfortunately by looking at the dispatcher monitor the AI train starts, reaches the reverse point and remains there, without reversing. To be more exact when arrived at the reverse point the D9 makes a zick-zack going on running a couple of meters forwards and backwards. I hope this can be useful.
Testreverse.zip