[Lamplighter]

Good work! I also use this option cabview for steam locomotives in the case of a reverse view.
The front view is the view along the tender backwards.
The left view is the original front view and the right view is again a view along the tender backwards, but on the stoker man side.
All elements were moved to the left view (ex front) using the parameter ORTSCabviewpoint (1), but it does not work for one.

Coincidentally, this is a typical element of steam locomotives - a firebox.
The usual code entry is:

Firebox (
Type ( FIREBOX FIREBOX )
Position ( 1 350 80 128 )
Graphic ( "fire.ace" )
FuelCoal ( "coal.ace" )
)

Would it also be possible to include this element in the control with the ORTSCabviewpoint (1) parameter?

In the meantime, I helped with the static texture of fire.ace and the spare workaround:

Lever (
Type ( FIREBOX FIREBOX )
Position ( 1 350 80 128 )
Graphic ( "fire.ace" )
Style ( NONE )
NumFrames ( 1 1 1 )
NumPositions ( 0 )
ORTSCabviewpoint ( 1 )
)

[Csantucci]

Yes, you are right. I forgot to add the feature to the firebox control. I'll add it in next ORNYMG release.

[Lamplighter]

Csantucci, on 03 February 2022 - 07:32 AM, said:

Yes, you are right. I forgot to add the feature to the firebox control. I'll add it in next ORNYMG release.

I also plead for the DialClock parameter. It doesn't work properly either.
I use it, for example, for historical registration speedometers (Hasler Bern)

[Csantucci]

The firebox control can now be inserted in side views with ORNYMG 117. The DialClock will be added in next revision.

[VAPOR3D]

Hello!

I am working now on a 2D cockpit that has a clock (DialClock) on the right display. I have inserted the line ORTSCabviewpoint ( 3 ), corresponding to the right screen, but the additional control is displayed in the front cockpit. I am using OR New Year MG 1.4-237 rev. 119 and it does not work.

What am I doing wrong? Thank you.

[Csantucci]

The right screen requires ORTSCabViewpoint ( 2 ) (in the usual case that the third CabviewFile entry in the .cvf file refers to the right view). Numbering starts from 0 for the central view.

[VAPOR3D]

Thank you Carlo.

I have tried with ORTSCabViewpoint ( 2 ) and it works, except for DialClock which keeps popping up in the main front window. The Dials for the brake pipes do work fine.

[jonas]

Hi Carlo,

Because I am building a CabView, I came across this nice feature here at ET about the CabView side views with separate controls.
I have a quick question about it to shorten further trying for me:

Is my impression correct that it is not backward compatible, to example with OR 1.4?

There the additional controls always show up in the middle front view. Which wouldn't really surprise me, because older OR code doesn't know the ORTSCabviewPoint parameter yet and therefore naturally attributes the additional side control to the center front view. Have I overlooked something - is there a further parameter must to use?

Greetings
Jonas

[Csantucci]

Hi Jonas,
it's as you say. In OR versions not supporting the controls in the side views, such controls are shown in the central view.

[jonas]

I see, Carlo, and still a nice extended function for the CabViews for me of course.

It is a pity that it is not implemented as a separate block, for example in a block named like ORTSCabviewControls:

SIMISA@@@@@@@@@@JINX0h0t______

Tr_CabViewFile (

	CabViewType ( 1 )

	CabViewFile ( CV_Front.ace )
	CabViewWindow ( 0 0 1024 768 )
	CabViewWindowFile ( "" )
	Position ( -0.517699 2.78 8.63 )
	Direction ( 0 0 0 )

	CabViewFile ( CV_Left.ace )
	CabViewWindow ( 0 0 1024 768 )
	CabViewWindowFile ( "" )
	Position ( -0.517699 2.78 8.63 )
	Direction ( 0 -48 0 )

	CabViewFile ( CV_Right.ace )
	CabViewWindow ( 0 0 1024 768 )
	CabViewWindowFile ( "" )
	Position ( -0.517699 2.78 8.63 )
	Direction ( 0 71.5 0 )

	EngineData ( BStE-ET_169a_Jm )

	CabViewControls ( 10
		Dial (
			Type ( MAIN_RES DIAL )
			Position ( 163 32 8 30 )
			Graphic ( CV_Pointer.ace )
			Style ( POINTER )
			ScaleRange ( 0 10 )
			ScalePos ( 227 152 )
			Units ( BAR )
			Pivot ( 20 )
			DirIncrease ( 0 )
		)

		...

	)

	ORTSCabviewControls ( 1
		TwoState (	Comment( Wiperswitch in CabViews right sight only for OR since Version 1.5 )
			Type ( WIPERS TWO_STATE )
			Position ( 500 165 13 24 )
			Graphic ( CV_WIPERSSwitch.ace )
			NumFrames ( 2 2 1 )
			Style ( ONOFF )
			MouseControl ( 1 )
			ORTSCabviewPoint ( 2 )
		)
	)
)

That would keep it compatible with OR versions not supporting the controls in the side views and even with MSTS (for MSTS at least, when the new block ORTSCabviewControls is at the end of the cvf-file code).
In addition, of course, the already existent parameter ORTSCabviewPoint would be preserved and the cvf files already made so far would still be functional for OR.

[Csantucci]

What you are requesting will be available in next ORNYMG release and, when checked, will be available also in the Unstable release. This, because it is an easy improvement. In general, however, it cannot be guaranteed that the application of new features to content hasn't drawbacks in older OR versions.

[jonas]

Hi Carlo,

Sounds great and will make it possible for me to integrate working controls for OR in the side Cab-View. Thanks for taking the time to implement this!

Greetings
Jonas

[Csantucci]

The feature is now available in ORNYMG 140.

[Weter]

Hello, Carlo.
I've decided not to start "maybe it's a bug" thread, but tell You here.
I'm very grateful, that *.cvf-files now are able to hold definitions for more, than three views: some content have variants of side/backward views, so it's possible to call all them from one, single cabview now.
But I've encounter a weak point:
During cab change procedure, ORTS (testing) tries to retain the number of current view entry: for instance, if right(second entry) was selected before cab change, *_rv.cvf tries to activate the second view for reversed cab too.
In my case, front cab had four views (front, back, left and right, which I've just added).
If I try to switch cab with right (fourth) view currently active, ORTS crashes due to "argument must be more, than zero", or so. That's because *._v.cvf-file still has only three views defined.

[Csantucci]

I don't think that OR covers the case where *.cvf and *_rv.cvf have a different number of viewpoints.