[Csantucci]

Hi Peter,
Thanks for your help.

[engmod]

Carlo,

I have isolated a problem with the calculation of derailcoff.

The discussion can be found here:- https://www.trainsim...ge3#post2316450

This problem relates to a 5 pack container set, specifically to an empty car not being an end car.

Log file for reference.

Do you have knowledge of the coder of the derailcoff?

Attached File(s)

•  OpenRailsLog.txt (12.59K)
  Number of downloads: 2
•  Clipboard_12-11-2024_01.jpg (831.55K)
  Number of downloads: 12

[Csantucci]

I haven't written such code. I had now a look on this.
DerailmentCoefficient = TotalWagonLateralDerailForceN / TotalWagonVerticalDerailForceN
and the two forces mentioned there are the result of a non simple calculation. Moreover DerailmentCoefficient is multiplied by a correcting factor > 1.

[engmod]

Carlo,

Thank you for finding the code for me.
I now believe there is no bug, just a bad calculation of numwheels in the case of 3 and 5 pack units.

This takes me back to the problems with 3 pack and 5 pack units, I have made up this table:-

axles

3 cars
2-2 2-2 2-2 = 12 axles numwheels 4

3 pack
2 2 2 2 = 8 axles A = nw3 C = nw2 B = nw3 3+2+3 = 8 axles outer cars numwheels 3 inner cars numwheels 2


5 cars
2-2 2-2 2-2 2-2 2-2 = 20 axles

5 pack
2 2 2 2 2 2 = 12 axles A=nw3 C=nw2 D=nw2 E=nw2 B=nw3 3+2+2+2+3 = 12 axles outer cars numwheels 3 inner cars numwheels 2

I will now test those figures on the activity

First test with NO derailment warnings.

[Csantucci]

In effect to be more complete from the code we have:
AA1 = Math.Abs(CarAhead.CouplerForceUSmoothed.SmoothedValue) * (float)Math.Sin(WagonCouplerAngleDerailRad) / WagonNumBogies;
BB1 = MassKG / numAxles;
TotalWagonLateralDerailForceN = Math.Abs(AA1 + BB1 * (BB2 - BB3));
so the wagon lateral derail force is reduced if WagonNumBogies and numAxles are higher.
Therefore I think you are correct in your assumption.

[Csantucci]

Revision 160.2 of OR NewYear MG is available here http://www.interazio...loads/index.php

This unofficial version has been derived from the latest official Testing release T1.5.1-1435,
plus some of the features already present in the Unstable release.


Moreover this version includes some features not (yet) available in the Open Rails testing official version, that is:
- addition of track sounds in the sound debug window (by dennisat)
- F5 HUD scrolling (by mbm_or)
- checkbox in General Options tab to enable or disable watchdog
- increase of remote horn sound volume level
- when car is selected through the F9 window, the car's brake line in the extended brake HUD is highlighted in yellow (by mbm_or)
- improved distance management in roadcar camera
- signal script parser (by perpetualKid): reduces CPU time needed for signal management
- general options checkbox for optional run at 32 bit on Win64 (consumes less memory, recommended for computers with 4 GB RAM)
- panto commands and animations now swapped when in rear cab
- correction to reduce transfer flickering at short distance
- option to skip saving commands (reduces save time on long activities), see http://www.elvastowe...post__p__257687
- skip warning messages related to ruler token, that is introduced by TSRE5
- track gauge can be changed over the whole route, see http://www.elvastowe...ng-track-gauge/
- re-introduced advanced coupling, by steamer_ctn
- bug fix for https://bugs.launchp...or/+bug/1895391 Calculation of reversal point distance failing
- bug fix for http://www.elvastowe...-brakes-in-hud/
- bug fix for http://www.elvastowe...post__p__265463 , by mbm_OR
- tentative support for RAIN textures for objects, terrain and transfers
- dynamic terrain and scenery loading strategy (useful for slower computers)
- commands to selectively throw facing or trailing switches, see http://www.elvastowe...post__p__270291
- preliminary bug fix for http://www.elvastowe...timetable-mode/
- max fog distance increased to 300 km
- camera following detached wagons in hump yard operation by pressing Ctrl key while clicking with mouse on coupler in Train Operations Window to uncouple wagon
- bug fix that didn't check for null label text, see http://www.elvastowe...post__p__273496
- Various fixes related to reversals and couplings, see e.g. http://www.elvastowe...post__p__277369
- workaround for http://www.elvastowe...post__p__278074
- "ORNYMG only" option tab, including all option checkboxes available only in ORNYMG
- kept Locomotive() TCS script hook
- kept various options in ORNYMG only tab
- add PERCENT UoM to ORTS_SIGNED_TRACTION_TOTAL_BRAKING
- add cabview controls ODOMETER_UP and ODOMETER_DOWN
- fix crash when reinitializing EOTs on a carless train
- enable modifying and compiling the .fx shader files, see http://www.elvastowe...post__p__295571
- accept ORTSAirBrakeMainResVolume as .eng files token, used in some TrainSimulations routes (see https://www.trainsim...365#post2285365)
- Add curve force and brake cylinder pressure in sound debug window
- Sort of hack to fix http://www.elvastowe...rriages-emudmu/
- Re-instate and extend Precision and UpdateTime for SPEEDOMETER in cabvies, see http://www.elvastowe...post__p__300651
- (ORNYMG only?) bug https://www.elvastow...post__p__302120
- Tentative (ORNYMG only?) bug fix for https://www.elvastow...post__p__302440
- (signalling) No speed update parameter, by roeter, see https://www.elvastow...post__p__302320
- (timetables) Many options to define power related features, by roeter, see https://www.elvastow...post__p__293894
- Timetable: open/close doors on AI trains and some minor extra features, see https://www.elvastow...timetable-mode/
- Disable Polach adhesion, see here https://www.elvastow...post__p__305613 and following posts
- Fix for https://bugs.launchp...or/+bug/2057708 ORTSScreenPage parameter doesn't work for Dials
- Bug fix for https://www.elvastow...-for-no-reason/
- Fix 3Dcab digits alignment, see https://www.elvastow...post__p__307374
- Bug fix for https://www.elvastow...post__p__307975
- Workaround for https://www.elvastow...to-an-ai-train/
- Conditionally correct invalid values of TrainPipeLeakRate and Auxiliary Reservoir Volume
- Add slider to set wind variability in ORNYMG only options
- fix for https://www.elvastow...post__p__309405
- fix for https://www.elvastow...ch-on-platform/ (ORNYMG only?)
- Bug fix for https://www.elvastow...-a-new-service/
- Bug fix for chuffing in multiplayer, see https://www.elvastow...or-multiplayer/
- features which are present in Unstable release or on Github but not yet in the publicly available testing release:
*- allow for .sms sound specific for AI trains. see http://www.elvastowe...post__p__295008
(PR #896); event numbers changed from 32n to 33n for compatibility with Testing release
*- Signal Function OPP_SIG_ID_TRAINPATH, by roeter, see https://www.elvastow...post__p__302318 (PR #892)
*- ETCS DMI Updates, including 280 km/h max tacho setting by gpz (PR #900)
*- Added mouse wheel support for controls which can be moved by pressing the left mouse button, by sweiland (PR #919)
*- Add curve squeal to route, by steamer_CTN (PR #923)
*- Fix Lights Crash on Corrupt Shapes (PR #953 by steelfill)
*- Multiple lightglow types, see https://www.elvastow...ting-trainsets/ (PR #981)
*- Replace dynamic brakes by engine brakes at low speeds, by cesar (PR #996)
*- NEW: Fix: TrainCarViewer overlaps when display size changed, by mbm_or (PR #1009)
*- NEW: Bug fix for https://bugs.launchp...or/+bug/2092489 Containers not appearing in timetable mode (PR #1020)
- NEW: Standalone multiplayer server, forked from OR Ultimate (now FreeTrainSimulator). Can be started from the "Tools" button in the Main Menu Window
- NEW: Watch Mode for Timetable Mode, see https://www.elvastow...post__p__313401
- NEW: Bug fix for https://www.elvastow...t__p__313536bug
- NEW: Bug fix for https://www.elvastow...post__p__313550 wrong messages about missing light graphic
- NEW: Fix for ORNYMG only bug about superelevation (see https://www.elvastow...superelevation/ )



Info about content of the various PR to the Unstable release can be found here
https://github.com/o...openrails/pulls

The Monogame related code intentionally coincides only partly with the code of the OR official testing version.

Instructions and additional files to use the AWS TCS are available here http://www.elvastowe...post__p__255510 .

Users having not more than 4 GB RAM are suggested to run selecting general options checkbox for optional run at 32 bit on Win64.

When running on Win64, the player can select if he prefers running at 64 bit or 32 bit. In this second case RunActivity32.exe is run, and only a maximum of 4 GB of RAM can be accessed by OR. If the computer has only 4 GB RAM, selecting the option to run at 32 bit on Win64 is recommended.
Note for developers: Runactivity32.exe is not generated by building the pack, but manually doing a copy of Runactivity.exe, renaming it Runactivity32.exe, and using on the Developer Command Prompt command corflags with the modifier -32BITPREF+

NOTE: See here http://www.elvastowe...mg-and-reshade/ for an installation guide of ReShade.

When running on Win64, if you are running OR at 64 bit (option not checked) you must point ReShade to OpenRails64.exe; if you are running OR at 32 bit (option checked) you must point ReShade to OpenRails.exe.

It is suggested to unpack the .zip using 7zip, if other unpackers lead to problems.

Revision 159 can still be downloaded from here http://www.interazio...loads/index.php (click on OR_NewYear_MG_oldrecent.zip) .

[engmod]

Hi Carlo,
I was having trouble with a reverse point and I got what is in the jpg.The crash in the log was behind it on the screen.

Attached File(s)

•  Clipboard_12-20-2024_01.jpg (137.67K)
  Number of downloads: 0
•  OpenRailsLog.txt (19.21K)
  Number of downloads: 5

[Csantucci]

This is a crash that occurs in a code part that is really very well consolidated, in all OR versions. Maybe this is connected with the 2 preceding log lines, that is

Information: Train PLAYER (0) : Looped at 3101

I attach here a patch for ORNYMG 160 (not 159) that logs some data that might be useful to understand what happens.
If you are willing to, you can apply the patch to ORNYMG 160, run the activity again and attach here the logfile after you get the crash.
 Orts.Simulation.zip (1.1MB)
Number of downloads: 1

[engmod]

Shall do.

[Niknak]

Carlo I've just downloaded v160 and then tried to resume a save made with v159. There is NO error message saying that it's not possible but after loading the game is frozen at the loading screen and needs Ctrl+Alt+Delete to sign out and in again. I've tried this with two different routes which have saves from v159. Starting an activity from new with v160 works fine except I get 'light glow' errors shown.. OR logs attached.

Attached File(s)

•  OpenRailsLog.zip (4.41K)
  Number of downloads: 1
•  OpenRailsLog v160.zip (4.32K)
  Number of downloads: 4