[Brace_2011]

Thanks for this, Carlo.

It all makes sense - especially that there is no need to edit the *.sms files depending on its host route/installation. Different routes in a given installation will have different ttype.dat files, and I couldn't see how the *.sms would cope with this - this avoids problems.

Thanks

Martin

[Coolhand101]

I've had the "CurveForce" parameter in my set ups from last year like this:

SIMISA@@@@@@@@@@JINX0x1t______


Tr_SMS (
	ScalabiltyGroup( 1
		Activation	(	Distance    ( 100 )	TrackType	( 12 ) ExternalCam() PassengerCam()  )
		Deactivation(	Distance    ( 100 )	TrackType   ( 12 ) CabCam() )
		Volume (0.9)
		Streams ( 1
		Stream (
			Priority (5)
			Triggers (3
                        Variable_Trigger ( CurveForce_Inc_Past  101	StartLoop ( 1 
                                                     File ( "x_curvesqueal2.wav" -1 ) SelectionMethod ( SequentialSelection )	) )
			       Variable_Trigger (  CurveForce_Dec_Past  100 ReleaseLoopRelease() ) 
                         Variable_Trigger (  Speed_Dec_Past       0.1 ReleaseLoopRelease () )
                           ) 
                           VolumeCurve( 
                                        CurveForceControlled 
                                        CurvePoints ( 3 
                                                0      0.0
                                                100    0.25 
                                                3000   1.0 
                                        ) 
                                        Granularity ( 10 ) 
                                ) 
                        )      
                  )
		)
      )
  

I cannot remember if OR supports this via the routes TTYPE file? I know it works for SMS Train set files!

Thanks

[Csantucci]

The CurveForce triggers work independently from the tracktype. They are generated directly by the physics of the train.
In principle they are alternative to the automatic curve/switch track sound as described in this thread, although they can co-exist.

[steamer_ctn]

Carlo,

Given that track pieces inside tunnels are differentiated from normal track pieces, would it also be possible to have a global sound "trigger" for tunnels as well? This would further reduce the number of points where the TType style of sound trigger would need to be inserted into the route?

Thanks

[Csantucci]

Yes, that could be possible. However the benefit in general is lower, because while practically all routes have many curves and/or switches, many routes have no tunnels or few of them. And many of them already are equipped with specific sound regions in tunnels.

[steamer_ctn]

Yes, I agree that the benefit is possibly lower, however if the code changes are minimal, then I still think it would be appropriate to add it, thus maintaining some level of consistency, and further reducing the number of locations that TType soundregions would need to be placed in a route.

[ErickC]

Csantucci, on 07 April 2018 - 09:57 AM, said:

The CurveForce triggers work independently from the tracktype. They are generated directly by the physics of the train.
In principle they are alternative to the automatic curve/switch track sound as described in this thread, although they can co-exist.

The way I see it, route-based curve squeal sounds are a good way to create an approximation for old content (using existing sounds without modification), and new content might be better off with curve squeal defined in the individual rolling stock's SMS. It's a good kind of flexibility to have, since I'd wager retrofitting a route is a lot simpler than retrofitting a whole bunch of legacy content, and the effort to implement the curve force dependent squeal into new SMS files is minimal.