[Csantucci]

Yes.

[Weter]

Worth to try, Carlo :)
We have some cabview folders with variants of *.ace-files for it's side views.
So can we specify controls&gauges as
ORTSCabViewpoint ( n )
Where n is not restricted to be 1 or 2 only?

[Csantucci]

Yes.
Clearly you have to add at the top of the .cvf file, before the EngineData() line, a block like the following one for each added cabviewpoint

	CabViewFile ( GP38Right.ace )
	Position ( 1 3.7 6 )
	Direction ( 10 84.22 0 )

[Weter]

Thanks alot for the code sample, Maestro!
Look, Carlo:
I have just remembered one cabview for our famous locomotive wth double cabs.
It's feature was "right" viewpoint (it was designed at pre-MSTS-bin days), which represented central view from the backward cabin.
Certainly, it included all levers and needles (as opposed to "active" front cab's main picture, where all of that was deleted for further animated *ace's to overlay) so that backward cab was "static".
So, now, we can substitute it by an "active" variant and set-back our locomotive without actual cab-change command?
i.e. change control stand for a while by just cycling viewpoints via right/left arrow keys instead of performing complete "procedure for abandoning the cab", then pressing Ctrl+E, what will swap the track monitor as well... and after that - doing all that again for returning to previous cab...

I would say, as well, about another feature... but now - the feature of the real locomotive:
it has a "Maneure" button, bringing it's power unit to Run1 state while pressed, moving a vehicle to pre-selected (by the reverser) direction carefully.
The button is easyly accessible when the driver stucked from his side window, while performing, e.g. coupling/uncoupling maneurers.
So, thanking Your efforts, we can have such functionality at ORTS now.
Thank you one more (but not the last - I'm sure about that) time!

[Csantucci]

Yes, that's possible.

[Weter]

Two more questions, if you don't mind, please:
1. At your code sample i can't see CabVieWindowFile block.
So far is it not needed?
2. Must the block ORTSCabViewpoint ( n ) to be just as it wrote, or must it include in braces all of it's related control's code, as

ORTSCabViewpoint( n
 Cab_Control's_Type
  This control's purpose ()
  position/size ()
  graphics ()
  num frames ()
  num positions ()
  etc.etc.etc.
)

[Csantucci]

CabViewWindowFile line is not used by OR.
ORTSCabViewpoint ( n ) must be inserted INSIDE every cabview control that must be enabled in CabViewpoint n, and not at top of the list of such controls.
Example:

		TwoState (
			Type ( HORN TWO_STATE )
			Position ( 106 125 30 21 )
			Graphic ( Horn.ace )
			NumFrames ( 2 2 1 )
			Style ( ONOFF )
			MouseControl ( 1 )
			ORTSCabviewpoint ( 1 )
		)

[Weter]

I see now. Thank you for explainations.
a bit off-top:

Spoiler

BTW, do you know, that they guess, that so-called window-file might be intended to show semi-transparent effects as snow flakes and raindrops, spilling down the windshield's glass as well as reducing the size of wiewport's area for reducing computing demands for low-grade machines (the latter, though, is no more critical now)

[Traindude]

On a sort-of-related note, I'd love to see some kind of perspective distortion effect for gauges. In the past, working with photos for 2D cab views means dealing with perspective distortion on the dial faces, which makes aligning needles/hands properly more difficult, and the result is often less than convincing.

[Csantucci]

Blueprint https://blueprints.l...-for-side-views .

[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.