[m61]

I have a problem with all diesel locomotives or.trainsim.pl/sm42 from or.trainsim.pl . Until the release of the trial version U2019.08.23-0936 2019-08-23 10:43:17 they work ok in the visiting and timetable mode. From version U2019.08.29-0736 2019-08-29 08:43:13 to the latest test after starting the engine turns off in both modes and works only in the autopilot 🙁

[R H Steele]

I don't know if this will address your specific problem, however, the ORTS Diesel engine is incomplete, it is missing a DieselTorqueTab. From the manual: sec 8.2.1 ORTS Specific Diesel Engine Definition:

Quote

If the ORTS specific definition is used, each parameter is tracked and if one is missing (except in the case
of those marked with Optional), the simulation falls back to use MSTS parameters.

The only optional parameter I am aware of is "ExhaustDynamicsDown"

Please see here for the relevance of the DieselTorqueTab >>> http://www.elvastowe...uom-for-torque/ Post#3
Thanks for the link to the website. I couldn't find the locomotive shown in the pictures...probably my error. Found it....thanks for the link, convenient having both the proper cabview and sounds in the same area, good page layout. Nice to see the Common.inc folder is being used by the OR community elsewhere.

...and a beautiful route, great cabviews....I have always wondered why many of the European cabviews are so much better than the ones we generally have for North American Equipment. Ah well....someday we will catch up. Have fun!

[Hamza97]

Quote

I have always wondered why many of the European cabviews are so much better than the ones

Its because I guess most of their cabviews are made out of actual photos plugged in cvf file... :D

[steamer_ctn]

m61, on 02 October 2019 - 04:18 AM, said:

I have a problem with all diesel locomotives or.trainsim.pl/sm42 from or.trainsim.pl . Until the release of the trial version U2019.08.23-0936 2019-08-23 10:43:17 they work ok in the visiting and timetable mode. From version U2019.08.29-0736 2019-08-29 08:43:13 to the latest test after starting the engine turns off in both modes and works only in the autopilot 🙁

I have looked into this issue, and it has raised several aspects that need to be considered when developing ENG files.

Firstly there appears to be a pre-existing error in the INC file, as identified by the message in the logfile when I run the test locomotive.

Warning: Diesel engine model has some errors - loading MSTS format in D:\Open Rails - CTN Test Route\trains\trainset\PKP_SM42_18D-OR\PKPIC_SM42-3002.eng:line 35

This appears to be caused because some parameters that are expected to be included in the code block for the diesel engine are "missing". These include the maxoilpressure, minoilpressure parameters, etc (a comparison of the manual will identify which parameters should be in the code block, and which ones outside of it).

Normally OR would attempt to correct for this by using the default (parameters normally included in a MSTS file) as a fall back. However in this situation the second problem with the ENG files comes into play, ie data input sequencing. Strictly speaking if the diesel engine code block is fully described, it shouldn't be necessary to add a lot of the MSTS parameters.

By data sequencing I mean that data is processed in the sequential order that it appears in the ENG file, so for example, in the Agregat_6Dg.inc file the Diesel Engine block is processed before the fallback MSTS values (which are below the code block in the file). Hence when the diesel engine is setup in OR, and if there are any missing values, it will attempt to use the MSTS values, but in this case they maybe zero as they have not been processed (read by) by OR yet (OR does have some hard coded defaults which might be used instead). Hence ideally all the MSTS should be above the diesel engine code block.

The main reason why the locomotive was not moving was because there was a zero power value assigned to it, so hence no power no go. This probably wouldn't have been an issue if the Tractive Force Curves had been correctly defined for the locomotive, as for some reason they appear to be embedded in the enginecontrollers section of the ENG file.

I believe that the solution to this issue has a number of elements as follows:

i) The ENG files need to be correctly setup to achieve the best outcome out of OR. I personally believe that the fool proof way to do this is either go with a BASIC configuration, which requires only a small simple set of parameters, and expects OR to set appropriate defaults and do all the relevant calculations, or alternatively do an ADVANCED configuration where all the relevant parameters are setup to achieve the best performance. At the moment the configuration seems to be somewhere between a BASIC and ADVANCED one. OR will only ever be as good as the data provided to it. It also demonstrates the importance of checking and investigating any relevant error messages.

ii) I have added some code to provide more detail in regard to the error message, so that users can more easily identify data issues and fix them.

iii) I have included a hard coded default if the real power values are not available when the diesel engine is initialised. This is not ideal as it won't provide a "real" performance for the locomotive, but it will allow the locomotive to move.

I have been working with some testers to try and develop some standards and guidelines to help users, but like all things in life it is slow work as other priorities keep intruding.

The update code should be available in version U2019.10.04-0436 of the unstable version. Give it a good and confirm that the locomotive is now moving.

[m61]

Hello Peter.
After installing the version U2019.10.04-0436 via Options / Updater / Unstable
https://james-ross.c...&utm_medium=app
diesel locomotives move correctly in both Timetable and Activity mode. Thank you for quick help, I will pass your suggestions to Polish Open Rails fans. https://or.trainsim.pl/aktualnosci/

Attached thumbnail(s)

• 
• 

[jpmackay]

I hate to complain about your latest version that I updated the Open Rails Monogame but thought to let you know now. Before the update of the version I got no problem to run the simulator in 60 FPS but after the update earlier today and I got just 7 to 8 FPS in simulator with the same route and activity. I was surprised to see the big drop in FPS. I did not touch or change anything in Options Menu and just like before but why am I getting very low FPS. The route is Trainsimulations CN Ruel Subdivision and the activity is VANCOUVER_LASER. Here is the log file.txt in zip below.

Let me know about this.

Thank you,

John

Attached File(s)

•  OpenRailsLog.zip (32.34K)
  Number of downloads: 263

[jpmackay]

Just download the next version with " U2019.10.05-2021 " from the site of Open Rails - Project (James Ross). Now it's solved and good FPS with 60 FPS not like the previous version with 7 FPS.

Thank you again,

John

[m61]

The corrected .inc file displays such errors in the Open Rails log U2019.10.04-0436 2019-10-04 05-43-12
https://youtu.be/boDRSHsXShA
https://or.trainsim.pl/su42/

Attached File(s)

•  OpenRailsLog.txt (533.43K)
  Number of downloads: 252
•  Agregat_6Dl.inc.txt (2.78K)
  Number of downloads: 257

[R H Steele]

The attachment should help, I constructed an OR engine file with ORTS Max Tractive Curves included. The ORTS diesel engine defintion does not require UoM in the tables --- for example in the DieselPowerTab the UoM for Watts "W" is included...I believe that is why you are not getting any power at any rpm...as shown in the log.
Try the attached, as is, and see if that helps. If you require any parameters/values to be adjusted, either post in this thread or PM me. Regards, Gerry
Formula used to calculate the values for the Diesel Torque tab is: Torque = (Watts × 9.5488) ÷ RPM ---- Torque values are in N.m

Comment ( ORTS Adhesion parameters for WAGON section of Engine file == ORTSCurtius_Kniffler ( 7.74 51.244 0.161 0.7 ) )

ORTSDieselEngines ( 1
	Diesel (		
	IdleRPM ( 600 )		
	MaxRPM ( 1800 )		
	StartingRPM ( 500 )		
	StartingConfirmRPM ( 650 )
	ChangeUpRPMps ( 150 )		
	ChangeDownRPMps ( 95 )		
	RateOfChangeUpRPMpSS ( 23 )		
	RateOfChangeDownRPMpSS ( 15 )		
	MaximalPower ( 563004W )		
	IdleExhaust ( 2 )		
	MaxExhaust ( 8 )		
	ExhaustDynamics ( 1.6 )		
	ExhaustDynamicsDown ( 0.8 )		
	ExhaustColor ( 33777777 )		
	ExhaustTransientColor ( 222b2930 )		
	DieselPowerTab (		
		0	0
		750	70096
		900	140937
		1050 211033
		1200 281875
		1350 351970
		1500 422066
		1650 492908
		1800 563004
	)
	DieselConsumptionTab (
		0	0
		600	25.9
		1800 151.4
	)
	ThrottleRPMTab (		
		0	600
		12.5	750
		25	900
		37.5	1050
		50	1200
		62.5	1350
		75	1500
		87.5	1650
		100	1800
	)		
	DieselTorqueTab (		
		0	0
		600	8960
		750	7168
		900	5973
		1050 5120
		1200 4480
		1350 3982
		1500 3584
		1650 3258
		1800 2987
	)		
	MinOilPressure ( 58psi )		
	MaxOilPressure ( 90psi )
	MaxTemperature ( 90degc )		
	Cooling ( 3 )		
	TempTimeConstant ( 720 )		
	OptTemperature ( 70degc )
	IdleTemperature ( 50degc )		
	)		
)			
MaxForce ( 219340N )
MaxContinuousForce ( 129999N )
ORTSMaxTractiveForceCurves (					
		0 (			
			0	0	
			2.71	0	
			3.13	0
			3.58	0	
			4.02	0	
			4.92	0	
			6.26	0	
			8.05	0	
			11.18	0	
			16.99	0
			33.53	0	)
	0.125 (				
			0	27476	
			2.71	27476	
			3.13	23794	
			3.58	20820	
			4.02	18507	
			4.92	15142	
			6.26	11897	
			8.05	9254	
			11.18	6663	
			16.99	4384	
			33.53	2221	)
	0.25 (				
			0	54951	
			2.71	54951	
			3.13	47588	
			3.58	41640	
			4.02	37013	
			4.92	30284	
			6.26	23794	
			8.05	18507	
			11.18	13325	
			16.99	8767	
			33.53	4442	)
	0.375 (				
			0	82426	
			2.71	82426	
			3.13	71382	
			3.58	62459	
			4.02	55519	
			4.92	45425	
			6.26	35691	
			8.05	27760	
			11.18	19987	
			16.99	13150	
			33.53	6663	)
	0.50 (				
			0	109670	
			2.71	109670	
			3.13	94976	
			3.58	83104	
			4.02	73870	
			4.92	60439	
			6.26	47488	
			8.05	36935	
			11.18	26594	
			16.99	17496	
			33.53	8865	)
	0.625 (				
			0	137145	
			2.71	137145	
			3.13	118770	
			3.58	103924	
			4.02	92377	
			4.92	75581	
			6.26	59385	
			8.05	46189	
			11.18	33256	
			16.99	21879	
			33.53	11086	)
	0.75 (				
			0	164620	
			2.71	164620	
			3.13	142564	
			3.58	124743	
			4.02	110883	
			4.92	90723	
			6.26	71282	
			8.05	55442	
			11.18	39918	
			16.99	26262	
			33.53	13306	)
	0.875 (				
			0	192096	
			2.71	192096	
			3.13	166358	
			3.58	145563	
			4.02	129389	
			4.92	105864	
			6.26	83179	
			8.05	64695	
			11.18	46580	
			16.99	30645	
			33.53	15527	)
	1.0 (				
			0	219340	
			2.71	219340	
			3.13	189951	
			3.58	166208	
			4.02	147740	
			4.92	120878	
			6.26	94976	
			8.05	73870	
			11.18	53187	
			16.99	34991	
			33.53	17729	)
		)

Attached File(s)

•  Agregat_6Dl.zip (1.27K)
  Number of downloads: 273

[steamer_ctn]

m61, on 06 October 2019 - 09:59 AM, said:

The corrected .inc file displays such errors in the Open Rails log U2019.10.04-0436 2019-10-04 05-43-12

There is a more recent version to correct this issue (see the posts immediately above yours).

When reporting an issue, please always check against the latest available version first, as sometimes an issue has been found and fixed.

If there are issues with the latest version, please advise.

Thanks