[ATW]

Thank's it's starting to work like a charm :oldstry:
https://scontent-a-sjc.xx.fbcdn.net/hphotos-xfa1/t31.0-8/10269033_595167097257585_8563055541931482159_o.jpg

[EricF]

:sign_thanks: Carlo!

I'm trying out the new capability, and it's working beautifully.

A while ago in one of the wishlist threads, I had hoped for a way to at least allow for some sort of overall "large / medium / small" cab font size selection to cope with various hig-resolution cabs. It would have at least allowed for a "best compromise" way to pick out a reasonable size. Your addition is easily the best way. The ability to specify the font size, plain / bold attribute, and typeface style on each individual digital display in the .CVF file is a very welcome feature; this is how cab display settings should work!

I've been trying it out on one of Borislav Miletic's cabs, which requires the gui_fnts.dat file to be swapped to get smaller numbers in MSTS. The effect in OR with accurate font sizing and selection is like night and day. And no more having to remember to kick off my font-swap batchfile every time I use high-res cabs or switch to regular cabs, as I do in MSTS.

As an aside for anyone wondering, adding the ORTSFont () lines in the .CVF file has no impact at all when switching back to MSTS with the edited .CVF file. MSTS ignores it.

[Csantucci]

Thanks for appreciation! Eric, could you too pls. post a picture of the cab you're referring to?

[Gary54]

At the risk of sounding extremely ignorant, how, exactly, is this latest upgrade accomplished? I suspect that a line or lines are to be added to the CVF, but I have no idea of the specifics or if there is a means of doing this via OR.

I apologize for what seems to be an inane question (given that so many people have been able to make the font changes), but I must have missed something in the discussion.

Many thanks for your help and patience.

Gary

[EricF]

Here's a screenshot; this is the default Dash9 leaving Whitefish Yard in Marias Pass 3.1. The cab is Boris' D9AC44 cab.
For the brake displays, the font size is '5' and the display font is "Arial". The digital speedometer display is using font size '7' and again "Arial" for the typeface. I may try using bold on that, too. For now it looks very good, though.The thumbnail image blurs the display a bit (sort of like what I get in MSTS with gui_fnts.dat substitution); at full size they're very crisp and readable.

Attached thumbnail(s)

• 

[EricF]

Gary54, on 26 May 2014 - 07:00 AM, said:

At the risk of sounding extremely ignorant, how, exactly, is this latest upgrade accomplished? I suspect that a line or lines are to be added to the CVF, but I have no idea of the specifics or if there is a means of doing this via OR.

Not ignorant at all! I've been following the thread on this eagerly and took notes, so here's how it all comes together...

This is from the .CVF file for the screenshot in my last post. I used the default Dash9 .CVF file and added the new lines.

Each digital readout in the .CVF file has a section delineated with the statement "Digital". For each one I want to modify, I located the entry in the .CVF file and added the ORTS-specific statement within the block set off by parenthesis.

For the brake indicators, it looks like this:

Digital (
			Type ( BRAKE_PIPE DIGITAL )
			Position ( 257 257 26 17 )
			ScaleRange ( 0 120 )
			Accuracy ( 0 )
			AccuracySwitch ( 0 )
			LeadingZeros ( 0 )
			Justification ( 1 )
			PositiveColour ( 1
				ControlColour ( 182 201 173 )
			)
			NegativeColour ( 0 )
			DecreaseColour ( 0 )
			Units ( PSI )
			ORTSfont ( 5 0 "Arial" )
		)
		Digital (
			Type ( EQ_RES DIGITAL )
			Position ( 257 269 26 17 )
			ScaleRange ( 0 120 )
			Accuracy ( 0 )
			AccuracySwitch ( 0 )
			LeadingZeros ( 0 )
			Justification ( 1 )
			PositiveColour ( 1
				ControlColour ( 182 201 173 )
			)
			NegativeColour ( 0 )
			DecreaseColour ( 0 )
			Units ( PSI )
                    	ORTSfont ( 5 0 "Arial" )
		)
		Digital (
			Type ( BRAKE_CYL DIGITAL )
			Position ( 257 282 26 17 )
			ScaleRange ( 0 90 )
			Accuracy ( 0 )
			AccuracySwitch ( 0 )
			LeadingZeros ( 0 )
			Justification ( 1 )
			PositiveColour ( 1
				ControlColour ( 182 201 173 )
			)
			NegativeColour ( 0 )
			DecreaseColour ( 0 )
			Units ( PSI )
			ORTSfont ( 5 0 "Arial" )
		)
		Digital (
			Type ( MAIN_RES DIGITAL )
			Position ( 273 282 26 17 )
			ScaleRange ( 0 140 )
			Accuracy ( 0 )
			AccuracySwitch ( 0 )
			LeadingZeros ( 0 )
			Justification ( 1 )
			PositiveColour ( 1
				ControlColour ( 182 201 173 )
			)
			NegativeColour ( 0 )
			DecreaseColour ( 0 )
			Units ( PSI )
			ORTSfont ( 5 0 "Arial" )
    	)

Then, the speedometer is a little further down past some of the other gauge and display statements. It gets its own slightly different setting, with a bigger font for the larger speed readout.

Digital (
			Type ( SPEEDOMETER DIGITAL )
			Position ( 304 271 30 30 )
			ScaleRange ( 0 80 )
			Accuracy ( 0 )
			AccuracySwitch ( 9.9 )
			LeadingZeros ( 0 )
			Justification ( 1 )
			PositiveColour ( 0
				ControlColour ( 182 201 173 )
			)
			NegativeColour ( 0 )
			DecreaseColour ( 0 )
			Units ( MILES_PER_HOUR )
			ORTSfont ( 7 0 "Arial" )
		)

I chose to leave the MSTS statements all together and tag the ORTS-specific statement on the end, just before the line with the closing parenthesis.

The format is:

ORTSfont ( fontsize fontstyle "fontfamily" )

Where:

fontsize is a floating-point value up to 10 that controls the size (10 corresponds to default size, which is what you get without this line)
fontstyle is an integer value of 0 or 1; "0" means regular and "1" means bold
"fontfamily" must be enclosed in double-quotes( " " ) and is the exact name of the font family. I chose "Arial" for the universal Microsoft sans-serif typeface.

- Be sure to put the spaces in so that the line is parsed correctly.
- Remember that the font chosen must be installed on the computer; that's why I went with "Arial" for sans-serif. Every Windows PC has it, so if you copy my settings, they'll work. If you're preparing a locomotive to distribute with this feature, you'd want to use a font that's built-in with Windows.

If you use aliases to a common.cab folder or similar setup, you'll only have to apply the additional lines to the master file that the aliases point to, and everything aliasing to it will show the same changes.
Individualized .CVF files will have to be edited one-by-one.

And if you go back and run the same locomotive and edited .CVF file under MSTS, the ORTS statement will be ignored and the cab displays will work as they always have -- the addition is truly specific to Open Rails and transparent to MSTS.

[Howky]

i have small problem , I tried to resize digital clock numbers and nothing happened.

my writing

DigitalClock (
Type ( CLOCK DIGITAL_CLOCK )
Position ( 267 306 42 25 )
Style ( 24HOUR )
Accuracy ( 2 )
ControlColour ( 0 36 0 )
ORTSfont ( 5 1 "Arial" )
)

and screen No change is still large

http://www.imagehosting.cz/thumbs/openrails2.png

[markus_GE]

Try changing the opening line of the block of code you posted from DicigtalClock( to Digital(. Be sure to have a backup of the file, though!

Cheers, Markus

[Gary54]

Thanks very much, Eric. Works like a charm. Also, many thanks for the tip regarding the short horn blasts.

Gary

[EricF]

No problem! I've been up to my eyeballs in after-hours training for work, plus a huge load of Spring house and yard work, and I haven't been on the forums or touched a train sim in weeks. But this has been a great weekend for me in trainsimming -- Saturday night I figured out how to make some stubborn horns work, all because of "lazy" MSTS handling of statements that hid the problem, and Sunday morning I got to try out Carlo's improvement for cab display fonts. The fonts have been a major annoyance to me; it just breaks the realism. Carlo's work is a gift to my eyes!:dance:

Now I've got a whole bunch of .CVF's I want to edit... :thumbup3: