Missing Consists
Collapse
This topic is closed.
X
X
-
That wasn't my CON - that was another poster with his own CON.Your Problem is Bolded in RED above. In post #24 you said "This is the directory/filename: gordon-1/gordon.eng"
The folder name is "gordon-1" so the Enginedata line should be
EngineData ( gordon gordon-1 )
you left off the "-1" on the folder name.
FYI the format is Enginedata ( filename foldername )Comment
-
Yes, that was me. I wanted to just show that the problem is not OR per say. It has to do with alignment of the content files. Suggest that you do away with aliasing of the Cabview file, with the amount of storage available on today disk having duplicates should not matter. As I noted with the aliasing of the file, I did not had a complete Cabview even with MSTS.Comment
-
I am not aliasing the cabview...as I mentioned it shows up fine in MSTS and runs just fine there as well. In OR I can see the consist from the one OR Menu but when I switch to select the Loco from the other OR menu it is not present.Yes, that was me. I wanted to just show that the problem is not OR per say. It has to do with alignment of the content files. Suggest that you do away with aliasing of the Cabview file, with the amount of storage available on today disk having duplicates should not matter. As I noted with the aliasing of the file, I did not had a complete Cabview even with MSTS.Comment
-
I get the same problem you get. The Gordon ENG does not show in the OR Graphic Menu Engine selection list but the Consist does display in the Non-graphic Menu Consist selection List and the Eng appears when I run OR and the loco operates in OR.
One of the OD gurus need to look at the ENG file to determine why it does not show in the menu.CharlesComment
-
I am a member of the OR development team. The WPF menu has bugs (that is the one with the parchment type background). There is a discussion in the OR development form of dropping that menu, the original developer has left the program, hence maintenance has ceased. There are issue's with it even with the up-coming release.
It is best just to stick with the menu that works.Comment
-
This could be the problem: From the OpenRailsLog.txt
Information: Unknown ControlType CUTOFF in C:\MSTS\trains\trainset\gordon-1\CABVIEW\scotsman.cvf:line 92
Information: Unknown ControlType VACUUM_RESERVOIR_PRESSURE in C:\MSTS\trains\trainset\gordon-1\CABVIEW\scotsman.cvf:line 255
Line 92 of scotsman.cvf
Type ( CUTOFF LEVER )
Line 255
Type ( VACUUM_RESERVOIR_PRESSURE DIAL )
As a test I changed the Cabview folder to on of a steam ENG that does show in the menu and edited the Cabview line. BUT got the same problem the Gordon did not show in the Menu. So those Information Comments in the Log file are probably not what is causing it not to show in the menu.CharlesComment
-
35 posts in and I am not crazy.
So it sounds like it is strictly a menu problem with OR - weird it hasn't shown up before I brought this up. I love that menu - as I hate having to select things based upon Consist name but rather like to select a Loco to drive.Comment
-
But that menu is useless; unless one edits ALL their consist names to include the name of the lead ENG. If one wants to drive the Gordon loco how can that be determined from the non-graphic menu? No way unless the consist name includes "Gordon". What is the lead loco in this consist whose nameline is Name ( "3DT_WP3_Box50" )?I am a member of the OR development team. The WPF menu has bugs (that is the one with the parchment type background). There is a discussion in the OR development form of dropping that menu, the original developer has left the program, hence maintenance has ceased. There are issue's with it even with the up-coming release.
It is best just to stick with the menu that works.CharlesComment
-
Unfortunately, that is the way it is. As I mentioned in post #36 the original developer has left, and there is finite bandwidth of developer resources. One is being maintained, the other is not. Hence keeping them in synch is a problem.But that menu is useless; unless one edits ALL their consist names to include the name of the lead ENG. If one wants to drive the Gordon loco how can that be determined from the non-graphic menu? No way unless the consist name includes "Gordon". What is the lead loco in this consist whose nameline is Name ( "3DT_WP3_Box50" )?
In this particular instance a new consist needed to be created any way. Having the lead engine named in a consist in not a new concept. Many of the original MSTS files hve done it this way. Some have not. Not "ALL" consist's need to be edited, only the one's without an engine name, if you want that feature.
Sorted jumped into this thread in the middle. However, the consist, .eng, cabview files were not the problem.Last edited by wjcurrey; 09-21-2012, 06:33.Comment
-
Looks like I won't be upgraded OR then if this is what is going to happen...Unfortunately, that is the way it is. As I mentioned in post #36 the original developer has left, and there is finite bandwidth of developer resources. One is being maintained, the other is not. Hence keeping them in synch is a problem.
In this particular instance a new consist needed to be created any way. Having the lead engine named in a consist in not a new concept. Many of the original MSTS files hve done it this way. Some have not. Not "ALL" consist's need to be edited, only the one's without an engine name, if you want that feature.
Sorted jumped into this thread in the middle. However, the consist, .eng, cabview files were not the problem.Comment
-
Nice attitude. Reminds me of Run8 support.Unfortunately, that is the way it is. As I mentioned in post #36 the original developer has left, and there is finite bandwidth of developer resources. One is being maintained, the other is not. Hence keeping them in synch is a problem.
In this particular instance a new consist needed to be created any way. Having the lead engine named in a consist in not a new concept. Many of the original MSTS files hve done it this way. Some have not. Not "ALL" consist's need to be edited, only the one's without an engine name, if you want that feature.
Sorted jumped into this thread in the middle. However, the consist, .eng, cabview files were not the problem.
I did not say the Graphic menu interface needed to be fixed. But the non-graphic menu could be modified so that it is like MSTS select route, select Explore, select Loco, and then select consist.CharlesComment
-
Most likely the WPF menu will stay, however as noted there was a discussion of the possibly of doing away with it. In the future there will more then likely be menu changes, remember this is beta. But for the near term, as I stated this is a matter of developer resources, so the feature you desire is not available. It's not exactly a show stopper, the consist can have the lead engine name in the non WPF menu.Comment
-
So what you are saying is the other menu is going to be modified to display the lead engine name as well as the consist name?Most likely the WPF menu will stay, however as noted there was a discussion of the possibly of doing away with it. In the future there will more then likely be menu changes, remember this is beta. But for the near term, as I stated this is a matter of developer resources, so the feature you desire is not available. It's not exactly a show stopper, the consist can have the lead engine name in the non WPF menu.Comment




Comment