v360 thread

[csantucci]

That green object stretching skywards is a terrain point with a wrong height value. I have sometimes seen such things working with the route editor. That value should be corrected with the RE.

Carlo

[Redcoat_1812]

Hi guys, no the same effect is not present when running that part of the route in MSTS.

Mike.

[csantucci]

At that particular location MSTS probably displays terrain points with lower density, so that the wrong point is not shown. This of course are my 10 cents.

[Redcoat_1812]

I am actually more interested in a possible explanation in regards my earlier points about scenery and buildings etc not being present.

When a route is run from within OR, compared to how it looks in MSTS.

Surely objects can't just disappear, even taking in to account OR is still at a very early development phase.

cheers,
Mike.

[twpol]

The logs your provided earlier include the following error:

runactivity.exe : Error : 0 : System.IO.DirectoryNotFoundException: Could not find a part of the path 'c:\ts\routes\cnbala\textures\spring\'.

My guess is that the there are missing seasonal texture folders and OR doesn't know what to do about that.

[Redcoat_1812]

Weird James the folder exists within the route's directory tree.

Mike.

[twpol]

Have you seen the "missing scenery" on any freeware routes I could download and try?

[Redcoat_1812]

Hi James,

no sorry i am only using payware in MSTS, ready made activities and less hassle.

I would not have re-installed MSTS to run stand alone and only did due to the new version of OR being released.

I had been using it along side Trainz since june 2001 ( Trainz from dec 2001 ) and it had all become a bit stale and dated for me.

RW is just a waste of time in my opinion, so TS2010 and OR are my prefered sims.

regards,
Mike.

[voxland]

Referring to the "beanstalk" and photos posted earlier:

This is almost certainly *not* a video card artifact or driver side effect. Notice that the "beanstalk" casts a wonderful shadow. I would say its a terrain data base anomaly. That is, there is a single elevation point (perhaps corresponding to a 10 meter square area) which is displayed with stunning height. It could be that the data truly is bad or that OR has become confused, but if the data is bad then I wonder why MSTS presumably does not show the same curiosity. The data looks to have come from a downloadable geographic data base, and I have seen in MSTS some abrupt canyons where the elevation data is zeroed. Sometimes this is data that is "missing" at the edge of a geographic grid of elevations, though I have also seen holes in the middle of such a grid.

-- Phil

[conrail1]

I am actually more interested in a possible explanation in regards my earlier points about scenery and buildings etc not being present.

When a route is run from within OR, compared to how it looks in MSTS.

Surely objects can't just disappear, even taking in to account OR is still at a very early development phase.

cheers,
Mike.

I've experienced the same issue, with the Feather River Route also with v360 which did not occur with v128 -

[antuanfs]

Hello.

My problem is the poor framerate, since the v.022 his decreased a lot. This is the content of my Open Rails Log.txt:

SVN V = 360
BUILD = 0.0.3911.24215 2010.09.16. 14:27

Starting Explore = C:\Program Files\Microsoft Games\Train Simulator\ROUTES\VALLARIZASORIA\paths\Pola de Lena-Leon.pat C:\Program Files\Microsoft Games\Train Simulator\trains\consists\Renfe 598 Regionales.con

------------ ---------- ------------ ----------
Loading TRK TRP TDB DAT ACT CON


runactivity.exe : Warning : 0 : Ignoring extra world_water_layer in C:\Program Files\Microsoft Games\Train Simulator\ROUTES\VALLARIZASORIA\ENVFILES\springcle ar.env:line 302
en ORTS.ORTraceListener.TraceEvent(TraceEventCache eventCache, String source, TraceEventType eventType, Int32 id, String format, Object[] args)
en System.Diagnostics.TraceInternal.TraceEvent(TraceE ventType eventType, Int32 id, String format, Object[] args)
en System.Diagnostics.Trace.TraceWarning(String format, Object[] args)
en MSTS.ENVFile..ctor(String filePath)
en ORTS.Viewer3D.ReadENVFile()
en ORTS.Viewer3D.Initialize()
en ORTS.Program.Start(IEnumerable`1 settings, String[] args)
en ORTS.Program.Main(String[] args)

CSS

runactivity.exe : Error : 0 : Unexpected Variable_Trigger in C:\Program Files\Microsoft Games\Train Simulator\trains\trainset\RENFE598\sound\598Meng.s ms:line 475
en ORTS.ORTraceListener.TraceEvent(TraceEventCache eventCache, String source, TraceEventType eventType, Int32 id, String format, Object[] args)
en System.Diagnostics.TraceInternal.TraceEvent(TraceE ventType eventType, Int32 id, String format, Object[] args)
en System.Diagnostics.Trace.TraceError(String format, Object[] args)
en MSTS.STFException.ReportError(STFReader reader, String message)
en MSTS.STFReader.SkipUnknownBlock(String token)
en MSTS.PlayOneShot..ctor(STFReader f)
en MSTS.Trigger.ParsePlayCommand(STFReader f, String token)
en MSTS.Variable_Trigger..ctor(STFReader f)
en MSTS.Triggers..ctor(STFReader f)
en MSTS.SMSStream..ctor(STFReader f)
en MSTS.SMSStreams..ctor(STFReader f)
en MSTS.ScalabiltyGroup..ctor(STFReader f)
en MSTS.Tr_SMS..ctor(STFReader f)
en MSTS.SMSFile.ReadFile(String filePath)
en MSTS.SMSFile..ctor(String filePath)
en MSTS.SharedSMSFileManager.Get(String path)
en ORTS.SoundSource.Initialize(Viewer3D viewer, WorldLocation worldLocation, String smsFilePath)
en ORTS.SoundSource..ctor(Viewer3D viewer, MSTSWagon car, String smsFilePath)
en ORTS.MSTSWagonViewer.LoadCarSound(String wagonFolderSlash, String filename)
en ORTS.MSTSWagonViewer.LoadCarSounds(String wagonFolderSlash)
en ORTS.MSTSWagonViewer..ctor(Viewer3D viewer, MSTSWagon car)
en ORTS.MSTSLocomotiveViewer..ctor(Viewer3D viewer, MSTSLocomotive car)
en ORTS.MSTSDieselLocomotiveViewer..ctor(Viewer3D viewer, MSTSDieselLocomotive car)
en ORTS.MSTSDieselLocomotive.GetViewer(Viewer3D viewer)
en ORTS.TrainDrawer.GetViewer(TrainCar car)
en ORTS.Viewer3D.GetPlayerLocomotiveViewer()
en ORTS.Viewer3D.Initialize(RenderProcess renderProcess)
en ORTS.RenderProcess.Initialize()
en Microsoft.Xna.Framework.Game.Run()
en ORTS.Viewer3D.Run()
en ORTS.Program.Start(IEnumerable`1 settings, String[] args)
en ORTS.Program.Main(String[] args)

TTTTTTTTTWWWWW S(repeats) S(repeats) S(repeats) SSSSSSSSSSSSSSSSSSSSSSSc:\program files\microsoft games\train simulator\routes\vallarizasoria\textures\spring\


runactivity.exe : Error : 0 : System.IO.DirectoryNotFoundException: No se puede encontrar una parte de la ruta de acceso 'c:\program files\microsoft games\train simulator\routes\vallarizasoria\textures\spring\'.
en System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
en System.IO.FileStream.Init(String path, FileMode mode, FileAccess access, Int32 rights, Boolean useRights, FileShare share, Int32 bufferSize, FileOptions options, SECURITY_ATTRIBUTES secAttrs, String msgPath, Boolean bFromProxy)
en System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access)
en MSTS.ACEFile.Texture2DFromFile(GraphicsDevice GraphicsDevice, String filename)
en ORTS.SharedTextureManager.Get(GraphicsDevice device, String path)

S(repeats) S(repeats) S(repeats) S(repeats) SSSSSSSSSSS$WWSW S(repeats) S(repeats) SSSS$WCSS

runactivity.exe : Error : 0 : Stream count mismatch in C:\Program Files\Microsoft Games\Train Simulator\trains\trainset\RENFE598\sound\598Mwag.s ms:line 314
en ORTS.ORTraceListener.TraceEvent(TraceEventCache eventCache, String source, TraceEventType eventType, Int32 id, String format, Object[] args)
en System.Diagnostics.TraceInternal.TraceEvent(TraceE ventType eventType, Int32 id, String format, Object[] args)
en System.Diagnostics.Trace.TraceError(String format, Object[] args)
en MSTS.STFException.ReportError(STFReader reader, String message)
en MSTS.SMSStreams..ctor(STFReader f)
en MSTS.ScalabiltyGroup..ctor(STFReader f)
en MSTS.Tr_SMS..ctor(STFReader f)
en MSTS.SMSFile.ReadFile(String filePath)
en MSTS.SMSFile..ctor(String filePath)
en MSTS.SharedSMSFileManager.Get(String path)
en ORTS.SoundSource.Initialize(Viewer3D viewer, WorldLocation worldLocation, String smsFilePath)
en ORTS.SoundSource..ctor(Viewer3D viewer, MSTSWagon car, String smsFilePath)
en ORTS.MSTSWagonViewer.LoadCarSound(String wagonFolderSlash, String filename)
en ORTS.MSTSWagonViewer.LoadCarSounds(String wagonFolderSlash)
en ORTS.MSTSWagonViewer..ctor(Viewer3D viewer, MSTSWagon car)
en ORTS.MSTSWagon.GetViewer(Viewer3D viewer)
en ORTS.TrainDrawer.Load(RenderProcess renderProcess)
en ORTS.Viewer3D.Load(RenderProcess renderProcess)
en ORTS.RenderProcess.Initialize()
en Microsoft.Xna.Framework.Game.Run()
en ORTS.Viewer3D.Run()
en ORTS.Program.Start(IEnumerable`1 settings, String[] args)
en ORTS.Program.Main(String[] args)

CSS

Sorry for the inconvenience and Greetings.

[Redcoat_1812]

I've experienced the same issue, with the Feather River Route also with v360 which did not occur with v128 -

I am glad it wasn't only me, Dan.

Mike.

[Redcoat_1812]

This is the MakingTracks Irish Enterprise route v2, Belfast - Dublin. There are embankment shapes missing from under the trackbed in quite a few areas of the route.

When run from within OR, but all is ok running in MSTS.



regards,
Mike.

[mnjrr]

Brake issues in OR

For those of you who are still experiencing brake issues with trains in Open Rails, please tell Open Rails in this thread the following:

What train set are you using?

What keys are using to operate the locomotive?

Please note that the brake functions in Open Rails are more realistic than in MSTS and work a little differently than in MSTS.

Here are some relevant excerpts from the Open Rails Software guide about the brakes in V360:

Engine – Classes of Motive Power

"Open Rails software provides for different classes of engines: diesel, electric, steam and default. If needed, additional classes can be created with unique performance characteristics. At the present time, diesel and electric locomotive physics use the default engine physics. Default engine physics simply uses the MaxPower and MaxForce parameters to determine the pulling power of the engine modified by the Reverser and Throttle position. Steam engines employ a more developed, but still not complete physics model. Open Rails steam physics parses the eng file for the following parameters: NumCylinders; CylinderStroke; CylinderVolume; BoilerVolume; MaxBoilerPressure; MaxBoilerOutput; ExhaustLimit; and BasicSteamUsage. These parameters are used as input values for Open Rails independently developed steam locomotive physics equations.

Engines – Multiple Units in Same Consist or AI Engines Locomotives can either be controlled by a player, or controlled by the train's MU signals for braking and throttle position, etc. The player controlled loco generates the MU signals which pass along to every unit in the train. For AI trains, the AI software directly generates the MU signals - there is no player controlled train. In this way, all engines use the same physics code for power and friction.

This software model will ensure that non-player controlled engines will behave exactly the same way as player controlled ones.

Open Rails Braking

Open Rails software has implemented its own braking physics in the current release. It is based on the Westinghouse 26C and 26F air brake and controller system. Open Rails braking will “read” the type of braking from the ENG file to determine if the braking physics uses passenger or freight standards, self-lapping or not. This is controlled within the Option menu.

Selecting Graduated Release Air Brakes in the Options menu allows a partial release of the brakes. Some 26C brake valves have a cut-off valve that has three positions: passenger, freight and cut-out. Checked is equivalent to passenger standard and unchecked is equivalent to freight standard.

The Graduated Release Air Brakes option controls two different features. If the train brake controller has a self-lapping notch and the Graduated Release Air Brakes box is checked, then the amount of brake pressure can be adjusted up or down by changing the control in this notch. If the Graduated Release Air Brakes option is not checked, then the brakes can only be increased in this notch and one of the release positions is required to release the brakes. Another capability controlled by the Graduated Release Air Brakes checkbox is the behaviorof the brakes on each car in train. If the Graduated Release Air Brakes box is checked, then the brake cylinder pressure is regulated to keep it proportional to the difference between the emergency reservoir pressure and the brake pipe pressure. If the Graduated Release Air Brakes box is not checked and the brake pipe pressure rises above the auxiliary reservoir pressure, then the brake cylinder pressure is released completely at a rate determined by the retainer setting.

At the moment only single pipe air brakes are modeled. So the auxiliary reservoir needs to be charged by the brake pipe and depending on the WAG file parameters setting this can delay the brake release. When the Graduated Release Air Brakes box is not checked, the auxiliary reservoir is also charged by the emergency reservoir (until both are equal and then both are charged from the pipe). When the Graduated Release Air Brakes box is checked, the auxiliary reservoir is only charged from the brake pipe. The Open Rails software implements it this way because the emergency reservoir is used as the reference pressure for regulating the brake cylinder pressure. The end result is that you will get a slower release when the Graduated Release Air Brakes box is checked. This shouldn't be an issue with two pipe air brakes because the second pipe can be the source of air for charging the auxiliary reservoirs.

Open Rails software modeled most of this graduated release car brake behavior based on the 26F control valve, but this valve is designed for use on locomotives. That valve uses a control 44 reservoir to maintain the reference pressure and Open Rails software simply replaced the control reservoir with the emergency reservoir.

Increasing the Brake Pipe Charging Rate (PSI/Second) value controls the charging rate.

Increasing the value will reduce the time required to recharge the train; while decreasing the value will slow the charging rate. However, this might be limited by the train brake controller parameter settings in the ENG file. The brake pipe pressure can't go up faster than the equalization reservoir.

The default value, 21, should cause the recharge time from a full set to be about 1 minute for every 12 cars. If Brake Pipe Charging Rate (PSI/Second) value is set to 1000, the pipe pressure gradient features will be disabled and will disable some of the other new brake features, but not all of them. Brake system charging time depends on the train length as it should, but at the moment there is no modeling of main reservoirs and compressors.

Using the F5 HUD Braking information in the Game
This helps users of Open Rails understand the status of braking within the game. Open Rails braking physics is more realistic than MSTS, as it replicates the connection, charging and exhaust of brake lines. When coupling to static consists, please notice that the brake line for the newly added car doesn’t have any values. This is because the train brake line/hose has not been connected.

Pressing the Backslash key (\) connects the brake hoses for all cars that have been coupled to the engine. Upon connection charging of the brake train line commences. Open Rails uses a default charging rate of about 1 minute. Notice that upon connection all the newly added cars have their handbrakes set to 100%. Pressing the Colon key will release all handbrakes on the consist as shown below. Pressing the Shift +? (Question mark) will immediately fully charge the train brakes line if you don’t want to wait for the train brake line to charge. Dynamic Brakes

Open Rails software supports dynamic braking for Engines. To increase the Dynamic brakes press Period (.) and Comma (,) to decrease them. Initially dynamic brakes are off, the throttle works and there is no dynamic brake line in the HUD. To turn on dynamic brakes set the throttle 46 to zero and then press Period, this will add a dynamic brake line to the HUD. Pressing Period successive times increases the Dynamic braking forces. To turn off the Dynamic brakes press Comma after setting the brakes to 0%. The throttle will not work when the Dynamic brakes are on.

The Dynamic brake force as a function of control setting and speed can be defined in a DynamicBrakeForceCurves table that works like the MaxTractiveForceCurves table. If there is no DynamicBrakeForceCurves defined in the ENG file, than one is created based on the MSTS parameter values. Dynamic brake sounds have not been implemented at this time."

I hope this information helps.

[Redcoat_1812]

No offence Walter, but the info is useless when applied to UK vacuum brake systems.

regards,
Mike.