DW SP SDP45 Cab graphic glitch

[TGM]

Hi,

I have run in to a graphic issue in the cab (top of train brake) of the new DW SDP45. Please see picture attached below.
Does anyone know what might be causing this?
I am running "open rails" ver x2634 with cab stretch at zero.

regards Tom

http://s397.photobucket.com/user/nz_kiwi/media/OpenRails2014-11-1001-42-21_zps72874c59.png.html?sort=9&o=0

[peaches461999]

Guys I've noticed this on the DW DRGW GP40's also.

[R. Steele]

This graphic problem has nothing to do with OR, rather, it is a mistake in how the animation for that particular object is presented. You'll need to open the Cab Editor and navigate to the specific cvf file for this engine. Usually done by going to the Cabview folder for the engine and opening the cvf file.
MAKE SURE YOU MAKE A COPY OF THE CVF FILE BEFORE STARTING!!!!
Once the cvf file is opened you will need to use the mouse to click on that specific part of the control so it is highlighted by a green box.

Usually clicking directly on the object will cause the green box to appear.

When the object is outlined by the green box you want to go to "CabElements" on the top menu bar and choose "properties"

The properties box for that specific cab control that is framed by the green box should now appear.

The name of the graphic ace file that is associated with it will be listed in a box entitled "Graphic"

Under the Graphic box you will see "Number of Frames" - this lists the number of frames for that animation. You need to change how those frames are displayed.

Press the change button

The next window will say "Cab Control Frames" In the upper left hand corner will be the graphic ace file displayed (small) and outlined/divided by red boxes showing how the animation is framed. This is what is most likely the problem. You will need to change this.

Look to the right and you will see two boxes labeled Frames across (on top) and Frames down (bottom box). Usually by switching the numbers in these boxes will fix the problem.

For example, if the Frames across is 1 and the Frames down is 2 use the tiny arrow buttons to reverse the numbers, you can see the effect by watching the red boxes change how the animation is framed.

When the animation appears visually correct, click on done and the window will close.

Click on OK, bottom right hand corner of Cab View Control Properties window and it will close.

Go to File/Save and then exit the Cab Editor and the Train Sim toolset (editor) back to the main desktop.

If everything worked correctly you should reload the locomotive in OR and the control should animate correctly.

Good Luck.

(if I have totally pooched this up, someone please help out, Thanks)

[TGM]

Yep. And the SD38, SD40 & SD45 as well. Obviously something in open rail graphics is causing the issue as they appear fine in the normal version of msts. Noticed too, that it seems to be the emd cabs & not the ge ones.

Tom

[R. Steele]

Folks the animation frames are incorrect for the autobrake. When the ace file is viewed in TGATool2A it shows as 3 frames across and 4 down, that had nothing to do with OR, completelty independent.

They should be changed to 3 across and 4 down, in the cab editor. I just purchased the locomotive from DW, loaded and ran a consist in OR X 2631 on the West Colton and got the same problem. Changed the frames to 3 across and 4 down and everything appeared fine in OR.

I only run OR, so no check was made in msts. If you think it is an OR bug, did you report with specifics?
Cheers

[baldwin]

So, what does it look like with cab stretch at 100%?.

[R. Steele]

So, what does it look like with cab stretch at 100%?.

Screenshot shows SP SPD45 Cab at 100% in OR X 2631 on the west colton. This was after I changed the animation frames using the cab editor. There may be another way to accomplish this, someone more experienced than I am may add something. I have always used the Cab editor, first I check the ace file in TGATools to see what it looks like.

SPD45_Cab.jpg

[baldwin]

I do not consider this to be a bug in OR, rather a demonstration of just how lax the MSTS code is in some areas.

[R. Steele]

I need to add something. I went about correcting the frame animations using MSTS Cab Editor. If you are running OR and have inserted any specific ORTS specification lines in the CVF (like the font line ORTSfont ( 8 0 "Quartz MS" ) for example) opening the file in the Cab Editor will erase those lines. (a known "feature" of MSTS Cab Editor)

The other option is to change the frames by directly editing the cvf with an editor like wordpad, CONTEXT, or some other editor of your preference. Look for the line NumFrames under the graphic (ace file) that is displaying incorrectly.

Example: Lever (
Type ( TRAIN_BRAKE LEVER )
Position ( 5 187 240 54 )
Graphic ( "..\\..\\UPY1407\\cabview\\autobrake.ace" )
Style ( NOT_SPRUNG )
MouseControl ( 1 )
NumFrames ( 12 3 4 )
NumPositions ( 5 0 1 13 14 15 )
NumValues ( 5 0 0.3 0.85 0.9 0.95 )
Orientation ( 0 )
DirIncrease ( 0 )
ScaleRange ( 0 1 )

First check the ace file by opening it in TGATools and see how it is laid out, total frames, frames across, and frames down.
NumFrames ( 12 3 4 ) - 12 = total number of frames; 3 = frames across; 4 = frames down

Adjust the numbers until the display is accurate.

[eric]

I do not consider this to be a bug in OR, rather a demonstration of just how lax the MSTS code is in some areas.

^This^

Microsoft is infamous for making code corrections on behalf of content creators and end users... Stuff that works fine in their web server engine will blow up on Apache and other rock-solid platforms. I used to use their GPS software Streets & Trips until I realized that everytime I was driving off-road, it was "correcting" to keep me on the nearest navigable highway...

We've seen countless examples between MSTS and ORTS where stuff that was coded incorrectly passes right along in MSTS. I prefer the more explicit approach ORTS has taken.

[R. Steele]

Microsoft is infamous for making code corrections on behalf of content creators and end users... Stuff that works fine in their web server engine will blow up on Apache and other rock-solid platforms. I used to use their GPS software Streets & Trips until I realized that everytime I was driving off-road, it was "correcting" to keep me on the nearest navigable highway...

We've seen countless examples between MSTS and ORTS where stuff that was coded incorrectly passes right along in MSTS. I prefer the more explicit approach ORTS has taken.

I'm straying a little off topic here: Some years ago I was told by someone ( a self-proclaimed coder ) that this is the specific reason Microsoft is so prone to hacking, breaches, and other security problems. The decision to make "code corrections on behalf of content creators and end users" was deliberate and totally business driven. That there was dispute in the company especially among coders who wanted to keep to the rock-solid platform approach.

Any truth to this?
For me, the rock solid approach is a no brainer when it comes to coding. I prefer something that has standards that I have to learn and in the long run can depend upon.