Notice to all visitors and members of the Train-Sim.Com message forums: If you plan on using a signature banner in your posts, we would like to remind you that there is a maximum size for banners. That maximum is 450 pixels wide by 120 pixels high, and not to exceed 25k. Your compliance is appreciated. FORUM RULES Problems? There are two common reasons for problems with logging in and posting messages. The first is that you are running a firewall that prevents your messages from being sent to the server. The other is that you have cookies disabled; the DCForum software requires cookies to work properly.
Some cabview files cannot be aliased to some engines. Does anyone know if there is some code in the ENG file which determines what cabview files will work.
No I'm using MSTS Activity Editor but what I'm looking for is the piece of information in ENG file or elsewhere that prevents certain CabView files from working with certain locomotive....the loco simply won't accept that alias....it produces a "CabView" error. I edit the ENG file directly with Notepad and modify the Cabview line for the alias...sometimes won't work
There are two methods of aliasing both cabs and sounds. The first uses cab and sound folders to hold the cvf and sms files which call on the various files needed from other folders.The second method makes the cab and sound calls directly from the eng file to the alias folder.In both methods for the cab to work properly the alias cvf must have the full path to each ace file used. Here is one line from a UK Class 158 DMU aliased cvf, CabViewFile ( ..\\..\\common.cab\\158\\158front.ace )In this example it is using the common.cab system, but could just as easily have been using items fron the GP38 folder. Beer is not a matter of life and death. It is much more serious than that. mervyn.
I am not unaware of the aliasing path issues. This is about the compatibility of some engines and some cabview files. I think I found the answer. Cabview files contain a CabView Type config entry and it appears only a cabview file with the same type as the default will work. I'm not sure where the "type" parameter is set, possibly in one of the .ace files that accompany the loco.
