Official v645 Thread

[twpol]

I saw it, but doesn't change anything. Control brakes with altgr keyboard combinations? No thanks. The problem is the keyboard layout set to symbols, and not to hardware keys. On msts and railworks, the game uses the same buttons for controls on each language keyboards, no matter what is the symbol on it, so was v360 did.

It will be 'fixed' for the next release; there simply wasn't enough time to get the change in for this release and properly test it (we rewrote the input code to enable a variety of other improvements).

[longiron]

Tried again, apparently I must wait for the "BC" number to hit 0 before pulling.

The Train brake HUD line now has two brake pipe pressure numbers. The first is at the lead engine and the second is at the last car. The F5 HUD display includes up to 11 lines worth of brake pressures down the length of the train. The values are: brake cylinder pressure (BC), brake pipe pressure (BP), aux. reservoir pressure, emergency reservoir pressure and brake valve state.

Brake Cylinder pressure (BC) determines the amount of braking applied, it should be zero or close to zero before the brakes are fully released - as in real life.

[PORU333]

The Train brake HUD line now has two brake pipe pressure numbers. The first is at the lead engine and the second is at the last car. The F5 HUD display includes up to 11 lines worth of brake pressures down the length of the train. The values are: brake cylinder pressure (BC), brake pipe pressure (BP), aux. reservoir pressure, emergency reservoir pressure and brake valve state.

Brake Cylinder pressure (BC) determines the amount of braking applied, it should be zero or close to zero before the brakes are fully released - as in real life.

Ah okay, that works. Thanks.

[kox]

ok then.
I read in documentation pdf, that the irkklang sound engine is replaced with openal. But i still see irklang things on console at loading. Or this is a future thing?

Browsing the source code i see there will be two seperate physics code, an msts compatible one, and a new one. The new one will be based on msts physics, so we only needed to extend the current msts rolling stock configs, or it well be a completely new physics, so we need to rewrite the msts configs to use the improvements of orts?

[longiron]

ok then.
I read in documentation pdf, that the irkklang sound engine is replaced with openal. But i still see irklang things on console at loading. Or this is a future thing?

Very near future thing.

Browsing the source code i see there will be two seperate physics code, an msts compatible one, and a new one. The new one will be based on msts physics, so we only needed to extend the current msts rolling stock configs, or it well be a completely new physics, so we need to rewrite the msts configs to use the improvements of orts?

There will be new parameters that will need to be added to ENG files to take advantage of the new OR physics. Since MSTS ignores parameters it doesn't recognize, there's no impact on running MSTS. If the ENG doesn't have these new parameters, OR physics will default to MSTS-based physics.

[twpol]

I read in documentation pdf, that the irkklang sound engine is replaced with openal. But i still see irklang things on console at loading. Or this is a future thing?

The documentation is flat-out wrong. We're still using irkklang for this release.

Browsing the source code i see there will be two seperate physics code, an msts compatible one, and a new one. The new one will be based on msts physics, so we only needed to extend the current msts rolling stock configs, or it well be a completely new physics, so we need to rewrite the msts configs to use the improvements of orts?

Where possible, existing data and values in MSTS files will be used in the new physics, but there will be some additions to take full advantage of the improvements in future releases.

[2slow4u]

As already reported, the current keyboard mapping, with not english keyboard layout, make very difficult the train brakes use.
With italian keyboards, i have to press a combination of two keys (shift + ,) to release train brake!
I also have problems with sounds, depending by loco, sometime i have not engine sound in cab view.
Horn and bell, doesn't work with many locos, pantograph doesn't work if i press the "p" key in "1" (cab) view, all is fine if i press the key in "2" (external) view...
Compatibility with msts activities, seem worse then in 0.360.

[twpol]

Compatibility with msts activities, seem worse then in 0.360.

That's a pretty sweeping statement that I am going to ask you to back up strongly. When you do, please be sure to include the OR log file with every reported issue.

[longiron]

ok then.
I read in documentation pdf, that the irkklang sound engine is replaced with openal.

Shawn,
What you are referring to is a section that discusses the FUTURE roadmap, not what's available in v645. The docs don't say it's available now.

[Redcoat_1812]

Jeff & longiron,

to reiterate guys, my comments were not meant as critisism.

But how many people of the thousands who use MSTS and threfore probably OR, actually own a RailDriver.

I would say a very small percentage.

Compared to vacuum brakes, which was the initial braking system when railways were in their infancy.

I am talking about road map priorities ( not "it's the end of the world because they are not in this release" ).

This version is a very worthwhile step forward from the last release, i fully agree.

Many thanks for the replies and explanations.

cheers,
Mike.

[kox]

Compared to vacuum brakes, which was the initial braking system when railways were in their infancy.

In their infancy there was just full manual handbrakes on loco or reverse throttle

[twpol]

But how many people of the thousands who use MSTS and threfore probably OR, actually own a RailDriver.

I would say a very small percentage.

It was also remarkably simple to add, thanks to the RailDriver SDK being rather good, and for those that own one it is a pretty major improvement.

Compared to vacuum brakes, which was the initial braking system when railways were in their infancy.

I am talking about road map priorities ( not "it's the end of the world because they are not in this release" ).

Specific priority items like "vacuum brakes" are hard to set in a volunteer project because we still need someone willing to actually take on the work. We are focusing on realistic physics, though, with a lot of knowlege and time currently going in to locomotive traction physics. Hopefully we can do something with the brakes too.

[BLR-IIC]

Framerate drops significantly when dynamic shadows are enabled. OS is Windows 7, 2 GHz AMD dual-core processor, NVidia 8400M GS with 256 MB onboard RAM.

Framerate with dynamic shadows enabled never goes above 7 FPS. Framerate without dynamic shadows is consistantly over 25 FPS.

[Redcoat_1812]

Thanks James, i realise you cannot do everyone's bidding and all in 5 minutes.

It is like the semaphores, they don't animate at the moment.

So i am more than happy to use them as they are, untill they get "fixed".

cheers,
Mike.

[OTTODAD]

OpenRails - V.645 - Feedback

First the good !

The MSTS Swiss Bernina route is one of the routes which will benefit most from ORTS when it is finished and is looking terrific except for it's distant mountains and not using the environments listed in it's *.TRK file.

Now the not so good !

The ORTS distant mountains looking like those in Railworks I ran the route in MSTS to take some screenshots to compare the scenery between ORTS and MSTS as shown below.

Having shut down MSTS after doing that I then tried to run another mountainous MSTS route in ORTS to check it's distant mountains and ORTS would not launch.

Had to shut down my WIN-XP SP2 AMD Phenom-II X2 / ATI HD 4870 computer and then ORTS would load again.

But trying to run any route in the MSTS Main folder none would load into ORTS as shown below !

Over to you, team !

O t t o