OpenRails ver 0.6.1.677

[jeff9595]

The OpenRails team is very proud to announce that a “maintenance release” with a number of important fixes is now available on the Release page of the OR website, http://www.openrails.org/release.html. Based on the incredible feedback that the community has provided, a number of significant improvements have been made, including the following:

1. Key combo problems caused by the wide variety of keyboards in use around the world have been fixed with a complete update.

2. “No texture” or “No definition” defined for signals causing "failure to load" has been patched so routes load with "warnings".

3. Invalid path nomenclature discovered as routes load their elements has been trapped and bypassed, preventing loading failure.

4. A new Dynamic Shadow solution complete with significant framerate performance improvements has been implemented.

5. Reported bugs relating to car spawning and level crossing have been fixed, and the efficiency of level crossing code has been improved.


We are instituting a new naming system for the OpenRails Train Sim product with this release. We call this OR ver 0.6.1.677 and in most future announcements and discussions simply ver 0.6.1. “677” is what programmers call the “build number”, and the complete version number, including the build number, will always be available using the F5 HUD display.

[BjarneL]

Are you planning to update the manuals as well? I miss a way to print a list of keyboard commands.

Bjarne

[antuanfs]

Bravo. Keyboard users of other languages had many problems in previous version. Keep it up.

Congratulations.

[kox]

5. Reported bugs relating to car spawning and level crossing have been fixed, and the efficiency of level crossing code has been improved.

The level crossings are still act as signals, and on one route those are still red stopping the train.

I also noticed micro stuttering in game, in 1-10 sec intervals, most frequently when i'm moving the camera, but the loader process isn't working those times.

I don't see any performance improvement since the last release with shadows on.

But the keys work correctly.

PS: i don't know if it's a bug or not, but the 2000 Series MU on tokyo-hakone needs about 4 min to release emergency brake. (emergency brake means 82 psi cylinder pressure, but the reservoir pressure is rising very slowly after 60 psi, and the brake is released then the reservoir reaches the same pressure as in the cylinder).

[csantucci]

Dear ORTS Dev Team,
a BIG thank you for your goodwill in developing this maintenance release! With my Italian notebook keyboard now I get the good old MSTS command layout, with even dynamic brake keys correctly reversed with respect to preceding versions. So I expect this improvement is there for all people with a non-US keyboard. And moreover in Bernina electrics now the panto rise to the correct height. Missing level crossings also appear, and I too expect that carspawner problems have been solved (to test them I have to revert to some original files in the route).
With this release moreover you have shown efficiency, reaction speed as well as willingness to hear to the user's wishes.
Those are the best credentials to ensure a development of the most successful train simulator.
Keep on the good work and thank you again!

Carlo

[csantucci]

Unfortunately I got a case where OR 645 runs, whereas OR 677 fails.
It is in the Bernina Route, activity 452 Tirano-St.Moritz new, and I get at activity startup following fatal error:
runactivity.exe : Error : 0 : System.NullReferenceException: Riferimento a un oggetto non impostato su un'istanza di oggetto.
in ORTS.MSTSElectricLocomotiveViewer..ctor(Viewer3D viewer, MSTSElectricLocomotive car)
in ORTS.MSTSElectricLocomotive.GetViewer(Viewer3D viewer)
in ORTS.TrainDrawer.Load(RenderProcess renderProcess)
in ORTS.Viewer3D.Load(RenderProcess renderProcess)
in ORTS.RenderProcess.Initialize()
in Microsoft.Xna.Framework.Game.Run()
in ORTS.Viewer3D.Run()
in ORTS.Program.<>c__DisplayClass8.<Start>b__7()
in ORTS.Program.Start(IEnumerable`1 options, String[] args)

Attached you find the complete log file.

OpenRailsLog_677.zip

Carlo

[OTTODAD]

Making progress !

However, exhaust smoke is still intermittent.

The Combined Throttle / Train Brakes does not work as it should and train brakes have to be applied separately.

My Santa-Fe-Express is selectable in Explore Route mode but is UNKNOWN to ORTS when used in activities.

Driving it is does not accelerate as it should, this one being capable of speeds up to 500mph.

The team can download it with my improved for MSTSBin set of MSTS rolling stock:
https://www.otto-wipfel.co.uk/msts-d...s/mp3kcons.zip



No SHIFT-1 camera yet.

Could camera options requiring the use of the Numbers Pad with the Num-Lock OFF be changed to work with it ON ?

The MSTS / ORTS default number functions numbers use those on the QWERTY part of the keyboard.

Could the F5 Hud display be re-arranged into more parts, so that the opening display shows only information relevant to driving locos ?

I too am having the same problems in the BERNINA with some of it's activities.

Minor cosmetics below.

O t t o

[csantucci]

Hi Otto, your last picture showing a tree amidst of the track is due to the fact that the random positioning of trees within a forest is a bit different between MSTS and ORTS. This can be hardly solved within ORTS itself. Only solution is reducing a bit the area of the forest within the RE.

Carlo

[OTTODAD]

Hi Otto, your last picture showing a tree amidst of the track is due to the fact that the random positioning of trees within a forest is a bit different between MSTS and ORTS. This can be hardly solved within ORTS itself. Only solution is reducing a bit the area of the forest within the RE.

Yes, Carlo, I am aware of that, this having been mentioned at the start of ORTS.

Had a look at that one and moved one of forest borders a bit and hope that after ORTS has matured I can run routes like mine, your's and the PRR better than in MSTSBin and that there are not many more trees and other objects like it !

O t t o

[kox]

The Combined Throttle / Train Brakes does not work as it should and train brakes have to be applied separately.

My Santa-Fe-Express is selectable in Explore Route mode but is UNKNOWN to ORTS when used in activities.

Driving it is does not accelerate as it should, this one being capable of speeds up to 500mph.

Combined controls haven't implemented yet.
The non steam physics aren't implemented too, so the game doesn't even reads that max speed, as you can see from source code, it's a TODO.

[apco25]

So this version now loads every route I have, payware and freeware. When will the microtex ace actually be used? Ground textures are blurry and too smooth looking to be natural. In reading the posts am I assuming correctly that non steam physics arent use yet? Train handling is quite slow and unresponsive with US diesels and freight cars.

[twpol]

We can't promise anything, but I would like to get microtex working for the next release. Loco physics, across all types, are getting some improvements right now.

[nicober]

OR "677" & Douce France 2010 - Problems:

Impossible to run a train on this french route, OR close rapidly and return to the desk immediatly after opening at 3 departures and for one departure the engin run about few undred meters before to close at Arleuf. I used a french steam locomotive 242A with the tender 34A. I tested this loco on the 6 MSTS default routes without problem and on de DF-X I tried also the original GP38 with the same errors result. I received 2 diffferents error messages in relation with the signalisation depanding the departures.

Arleuf:
runactivity.exe : Error : 0 : Signal type rm_bmvu_gam has invalid light texture .

We find this at Skip 7 of the sigcfg.dat file
_Skip ( 7 )
SignalType ( "RM_BMVU_GAM"

Vandenessy:
runactivity.exe : Error : 0 : Signal type mr_carre_c has invalid light texture .

We find this at Skip 18 of the sigcfg.dat file
_Skip ( 18 )
SignalType ( "MR_Carre_C"

RM_BMVU_GAM and MR_Carre_C, I saw this at other places and also an other close Signal type MR_Carre_CP, I don't know if this last work correctly with OR.

Clamecy:
runactivity.exe : Error : 0 : System.IO.InvalidDataException: {TileX:-5797 TileZ:14852 X:-809.354 Y:95.669 Z:872.504} signal 63299 unit 0 has invalid sub-object node-name SIGNAL.
runactivity.exe : Error : 0 : System.IO.InvalidDataException: {TileX:-5797 TileZ:14852 X:-820.173 Y:95.9163 Z:901.673} signal 63300 unit 0 has invalid sub-object node-name SIGNAL.

Chagny:
runactivity.exe : Error : 0 : System.IO.InvalidDataException: {TileX:-5787 TileZ:14842 X:-718.918 Y:225.32 Z:544.402} signal 53169 unit 0 has invalid sub-object node-name SIGNAL.
runactivity.exe : Error : 0 : System.IO.InvalidDataException: {TileX:-5787 TileZ:14842 X:-711.587 Y:225.459 Z:527.483} signal 53168 unit 0 has invalid sub-object node-name SIGNAL.

For Clamecy and Chagny:
If you go on the tiles write by OR above, the UId 623299, 63299, 53169 and 53168 correspond in the sigcfg.dat file to Signalshape Info_2.s and Info_1.s and you can see 3 other files (3-4-5) similar.

I include the 4 OpenRailsLog.txt renamed with the departures location in the zip file plus the sigcfg.dat file of the route DF_X.

If you need the route you can find it at: http://doucefrance.apsfi.org/DF_Page010.htm

Thanks in advance for your attention

[Hotwheels2009]

Hi ORTS Dev's

First and formost EXCELLENT work on Open Rails !! I had put off OR till version v645 , After seeing some Youtube video's , thought
ill need to see and try this for myself , again great work ! ..

Though one thing has bugged me, is the not implemented Speed Limits , Siding Names , Work Order ....

Ide love to run up and down the Feather River route , BNSF Scenic Sub for hours on end .. yet having no speed limits and or proper known path
this is very difficult .. Saying this as otherwise OR is a fully working functional Train sim.

Long story short is there any date or idea of when these IMPORTANT features shall be added ?

[twpol]

Long story short is there any date or idea of when these IMPORTANT features shall be added ?

Everyone has their own idea of which features are important, of course; those you mention are all due to be added but providing a timescale at this point is not easy - we're working out what to focus on for the next release. I would say speed limits are pretty likely as they tie in to signalling and we're doing a major update there currently.