OR suddenly dislikes units

OR suddenly dislikes units Rate Topic:

#1 ErickC

Superintendant

Group: Status: Elite Member
Posts: 1,001
Joined: 18-July 17
Gender:Male
Location:Hastings, MN, US
Simulator:ORTS
Country:

Posted 24 November 2018 - 11:30 PM

I have had this issue with the last couple of testing versions:

Warning: Found a suffix 'n/m' which could not be parsed as a Resistance unit in E:\ORTS_CONTENT\trains\trainset\NAVS_SOO_GP7\SOO_GP7_377.eng:line 15

Warning: Found a suffix 'n/m' which could not be parsed as a Resistance unit in E:\ORTS_CONTENT\trains\trainset\NAVS_SOO_GP7\SOO_GP7_377.eng:line 15

Warning: Found a suffix 'n/m' which could not be parsed as a Resistance unit in E:\ORTS_CONTENT\trains\trainset\NAVS_SOO_GP7\SOO_GP7_377.eng:line 15

Warning: Found a suffix 'n/m' which could not be parsed as a Resistance unit in E:\ORTS_CONTENT\trains\trainset\NAVS_SOO_GP7\SOO_GP7_377.eng:line 15

Warning: Found a suffix 'n/m' which could not be parsed as a Resistance unit in E:\ORTS_CONTENT\trains\trainset\NAVS_SOO_FREIGHT\Soo_27_1979.eng:line 7

Warning: Found a suffix 'n/m' which could not be parsed as a Resistance unit in E:\ORTS_CONTENT\trains\trainset\NAVS_SOO_FREIGHT\Soo_27_1979.eng:line 7

Warning: Found a suffix 'n/m' which could not be parsed as a Resistance unit in E:\ORTS_CONTENT\trains\trainset\NAVS_SOO_FREIGHT\Soo_27_1979.eng:line 7

Warning: Found a suffix 'n/m' which could not be parsed as a Resistance unit in E:\ORTS_CONTENT\trains\trainset\NAVS_SOO_FREIGHT\Soo_27_1979.eng:line 7

Warning: Cannot parse the constant number 51.000in in E:\ORTS_CONTENT\trains\trainset\NAVS_SOO_FREIGHT\CABVIEW3D\Soo_27_1979_cab.cvf:line 5

Warning: Cannot parse the constant number 158.156in in E:\ORTS_CONTENT\trains\trainset\NAVS_SOO_FREIGHT\CABVIEW3D\Soo_27_1979_cab.cvf:line 5

Warning: Cannot parse the constant number -25.456in in E:\ORTS_CONTENT\trains\trainset\NAVS_SOO_FREIGHT\CABVIEW3D\Soo_27_1979_cab.cvf:line 5

This was never an issue before.

Attached File(s)

OpenRailsLog.txt (13.75K)
Number of downloads: 226

#2 steamer_ctn

Open Rails Developer

Group: Status: Elite Member
Posts: 1,889
Joined: 24-June 11
Gender:Male
Country:

Posted 24 November 2018 - 11:48 PM

Can you also post the ENG file for the locomotive?

#3 ErickC

Superintendant

Group: Status: Elite Member
Posts: 1,001
Joined: 18-July 17
Gender:Male
Location:Hastings, MN, US
Simulator:ORTS
Country:

Posted 24 November 2018 - 11:54 PM

SIMISA@@@@@@@@@@JINX0D0t______

Wagon ( SOO_GP7_377
	WagonShape ( SOO_GP7_377.s )
	Mass ( 246000lb )
    Sound (	"../../NAVS_COMMON/audio/EMD_567/X_567BC-3.sms" )

	ORTS3DCab(
            ORTS3DCabFile ( SOO_GP7_377_VC.s )
            ORTS3DCabHeadPos ( 47.244in 137.273in 140.462in )
            RotationLimit ( 360 360 360 )
            StartDirection ( 0 0 0 )
	)

	Include( "../NAVS_COMMON/INCLUDE/AAR_Type-E.inc" )
	Include( "../NAVS_COMMON/INCLUDE/NAVS_GP7_wag_gen.inc" )
	Include( "SOO_375_lights.inc" )

	ORTSFreightAnims (
		MSTSFreightAnimEnabled ( 0 )
		FreightAnimStatic (
			Shape( ../NAVS_COMMON/SHAPES/ENGINEER_E.s )
			Offset( 1.121, 2.759, -3.739 )
			FreightWeight( 220lb )
		)
		FreightAnimStatic (
			Shape( ../NAVS_COMMON/SHAPES/CONDUCTOR_A.s )
			Offset( -1.164, 2.759, -3.297 )
			FreightWeight( 220lb )
		)
	)

	)

Engine ( SOO_GP7_377
   	Name ("Soo GP7 #377 c. 1980")
	Wagon ( SOO_GP7_377 )	
   	Sound (	"../../NAVS_COMMON/audio/EMD_567/567BC-3.sms" )
    DieselEngineMaxRPMChangeRate( 65 )
	
	Effects (
		DieselSpecialEffects (
				Exhaust1 (
					0.000 4.618 -0.880
					0 1 0
					0.1
				)
				Exhaust2 (
					0.000 4.618 -3.153
					0 1 0
					0.1
				)
			)
        )

	Include( "../NAVS_COMMON/INCLUDE/NAVS_16-567B.inc" )
	Include( "../NAVS_COMMON/INCLUDE/NAVS_GP7_62_15.inc" )
	Include( "../NAVS_COMMON/INCLUDE/NAVS_EMD_PM_compressor.inc" )
	Include( "../NAVS_COMMON/INCLUDE/NAVS_26L.inc" )
	Include( "../NAVS_COMMON/INCLUDE/NAVS_vigilance.inc" )
	Include( "../NAVS_COMMON/INCLUDE/NAVS_GP7_NDB_controllers.inc" )
	Include( "../NAVS_COMMON/INCLUDE/procedures_ndb.inc" )
	Include( "../NAVS_COMMON/INCLUDE/NAVS_GP7_description.inc" )
	)

But that isn't going to do you any good. I suspect the problem is in the coupler definition:


Comment ( //////////AAR Type E Couplers\\\\\\\\\\ )

	Coupling (
		Type ( Automatic )
		Spring (
			Stiffness ( 1.1e6N/m 4.8e6N/m )
			Damping ( 1.1e6N/m 1.1e6N/m )
			Break ( 1.6e6N 1.6e6N )
			r0 ( 20cm 30cm )
		)
		Velocity ( 0.1m/s )
	)
	Coupling (
		Type ( Automatic )
		Spring (
			Stiffness ( 1.1e6N/m 4.8e6N/m )
			Damping ( 1.1e6N/m 1.1e6N/m )
			Break ( 1.6e6N 1.6e6N )
			r0 ( 20cm 30cm )
		)
		Velocity ( 0.1m/s )
	)
	Buffers (
		Spring (
			Stiffness ( 1e6N/m 5e6N/m )
			Damping ( 1.1e6N/m/s 1.1e6N/m/s )
			r0 ( 0m 1e9 )
		)
		Centre ( 0.5 )
		Radius ( 1 )
		Angle ( 0.5deg )
	)

But that's been the same for ages and never caused an error until I updated on Wednesday. To be sure, I tested in an older build, and no problem.

#4 steamer_ctn

Open Rails Developer

Group: Status: Elite Member
Posts: 1,889
Joined: 24-June 11
Gender:Male
Country:

Posted 25 November 2018 - 12:28 AM

In preparation for some work that I was doing on a coupler with advanced physics, I recently made changes to OR (last two months or so) which made it read the Damping value in the coupler parameters. Previously it had ignored it, hence why there was no error.

Looking at your ENG file, I notice that you have assigned UoM of N/m to the Damping parameters. The actual UoM for damping are N/m/s (as I understand from my research).

I have also confirmed this in the MSTS ENG/WAG reference documents which quotes the following UoM:
Stiffness - Newton meters
Damping - Newton meters per second

Though interestingly looking at some of the default MSTS ENG/WAG files it appears that different UoM were used in different sections of the coupler. This leads me to think that MSTS wasn't using these values either, or alternatively not correctly.

Currently the Damping value is still not being used (until work on the Advanced coupler is completed), so the error is only cosmetic, but it can be corrected by changing the UoM to the correct ones.

#5 Csantucci

Member, Board of Directors

Group: Status: Elite Member
Posts: 6,998
Joined: 31-December 11
Gender:Male
Country:

Posted 25 November 2018 - 08:23 AM

If it is Newton meters or Newton per meter? If it is Newton meters it should be Nm.

#6 R H Steele

Executive Vice President

Group: ET Admin
Posts: 3,436
Joined: 14-March 13
Gender:Male
Location:known universe
Simulator:Open Rails
Country:

Posted 25 November 2018 - 10:05 AM

It is Newton meters per second. OR has always given a log warning when the "s" is missing from the term. I've found it is a very common error found in the damping line. Some sort of carry over from the basic MSTS files??

#7 Hobo

Foreman Of Engines

Group: Status: Contributing Member
Posts: 969
Joined: 19-December 04
Gender:Male
Location:Paris,Ont- Canada
Simulator:OPEN RAILS & MSTS
Country:

Posted 25 November 2018 - 03:11 PM

Carlo !
The " N/m and N/m/s " have always been recognized by OR and was always used by MSTS . You could be correct about the Nm and Nm/s but please don't change anything unless both are recognized or every eng. and wag. will have to be changed .
Just an opinion !

#8 Csantucci

Member, Board of Directors

Group: Status: Elite Member
Posts: 6,998
Joined: 31-December 11
Gender:Male
Country:

Posted 25 November 2018 - 11:56 PM

I haven't changed anything and won't change anything... it's not my field of intervention.

#9 ErickC

Superintendant

Group: Status: Elite Member
Posts: 1,001
Joined: 18-July 17
Gender:Male
Location:Hastings, MN, US
Simulator:ORTS
Country:

Posted 26 November 2018 - 12:14 AM

All right, I'll fix my Type-E include files and issue a fix whenever I get a chance (probably after final exams are done!).

Page 1 of 1

You cannot start a new topic
You cannot reply to this topic

Elvas Tower: OR suddenly dislikes units - Elvas Tower