Several errors given, all .wags mentioned have their folders created as a symbolic link:
Quote
Warning: When expecting a number, we found a ) marker. Using the default 1 in E:\Bin\Open Rails - US West 1930-1952\trains\trainset\GS_SP_92536\GS_SP_92536_Ld.wag:line 10
Warning: When expecting a number, we found a ) marker. Using the default 1 in E:\Bin\Open Rails - US West 1930-1952\trains\trainset\XM_PRR_X29\XM_PRR_569178_LD.wag:line 6
Warning: When expecting a number, we found a ) marker. Using the default 1 in E:\Bin\Open Rails - US West 1930-1952\trains\trainset\XM_GN_USRA_DS\XM_GN_23715_LD.wag:line 7
Warning: Found a suffix ')' which could not be parsed as a Distance unit in E:\Bin\Open Rails - US West 1930-1952\trains\trainset\XM_ATSF_142331\xm_atsf_142331_mt.wag:line 5
Warning: When expecting a number, we found a ) marker. Using the default 1 in E:\Bin\Open Rails - US West 1930-1952\trains\trainset\XM_GN_USRA_DS\XM_GN_23715_MT.wag:line 7
Warning: When expecting a number, we found a ) marker. Using the default 1 in E:\Bin\Open Rails - US West 1930-1952\trains\trainset\XM_PRR_X29\XM_PRR_569178_MT.wag:line 7
Warning: When expecting a number, we found a ) marker. Using the default 1 in E:\Bin\Open Rails - US West 1930-1952\trains\trainset\XM_RDG_5087\XM_RDG_5087_MT.wag:line 7
Warning: When expecting a number, we found a ) marker. Using the default 1 in E:\Bin\Open Rails - US West 1930-1952\trains\trainset\XM_PRR_X29\XM_PRR_571797_MT.wag:line 7
Warning: When expecting a number, we found a ) marker. Using the default 1 in E:\Bin\Open Rails - US West 1930-1952\trains\trainset\XM_GN_USRA_DS\xm_gn_25096_ld.wag:line 7
Warning: When expecting a number, we found a ) marker. Using the default 1 in E:\Bin\Open Rails - US West 1930-1952\trains\trainset\GS_SP_92536\GS_SP_92536_ld.wag:line 10
Warning: When expecting a number, we found a ) marker. Using the default 1 in E:\Bin\Open Rails - US West 1930-1952\trains\trainset\XM_PRR_X29\XM_PRR_569178_ld.wag:line 6
Warning: Ignored missing wagon E:\Bin\Open Rails - US West 1930-1952\trains\trainset\RS_SFRD_Rr_40\RS_SFRD_8225_clsd_mty.wag in activity definition Loose consist.
Warning: Ignored missing wagon E:\Bin\Open Rails - US West 1930-1952\trains\trainset\RS_SFRD_Rr_35\RS_SFRD_7145_clsd_mty.wag in activity definition Loose consist.
Warning: Ignored missing wagon E:\Bin\Open Rails - US West 1930-1952\trains\trainset\RS_SFRD_Rr_40\RS_SFRD_8220_clsd_mty.wag in activity definition Loose consist.
Taking one .wag as an example (bold, in color, above)... it's .wag:
SIMISA@@@@@@@@@@JINX0D0t______
Wagon ( xm_gn_23715_MT
WagonShape ( GN_USRA_box_23715.s )
Include ( "..\\Common_Model_stds\\USRA_DS_Boxcar_Tim_Muir_Model\\XM_USRA_DS_Mesh_Dimensions.inc" )
Include ( "..\\Common_Fleet_stds\\Std_Type_Coupler_Generic_Draft_Gear.inc" )
Adheasion ( 0.2 0.4 2 0 )
Include ( "..\\Common_Model_stds\\USRA_DS_Boxcar_Tim_Muir_Model\\XM_USRA_DS_MTY_Weight.inc" )
Include ( "..\\Common_Fleet_stds\\Single_Pipe_KC_Brakes.inc" )
Sound ( "genfreightwag2.sms" )
Name ( "XM 40' GN 23715 MTY" )
)
The error complains about line 7. That file is present and it contains this code:
Comment ( XM_USRA_DS_Mesh_Dimensions.inc )
Type ( Freight )
FreightAnim ( USRA_50t_parts.s 1 1 )
Size ( 3.1m 4.6m 13.275m )
WheelRadius ( 36in/2 )
NumWheels ( 8 )
InertiaTensor ( Box ( 3.1m 4.6m 12.975m ) )
All of the .wags mentioned in the error report were functional before I created symbolic links to replace the actual folders.
Some images of the directory listing (click on image for clarity):
That shows the presence of the "common" include files as peer directories to all of the .wag and .eng folders. These are the target s for many include files specified in .wags
That shows the folders within the "Common_Model" folder.
That shows the folders from the missing in the loose consist errors.
And that shows the folder holding the .wag file I displayed above.
The editor I use, EmEditor Pro, does understand that symbolic links are present. When I have the .wag file that I example above open in my editor I can click on the filename listed in the include statement and if the path is correct it will open that file. That gives me a very handy way to make sure I have not entered a typo of some kind. Were I to make an edit and save I can go over to what I'm calling the source library and verify the edit has migrated from the virtual to the actual file.
An observation: Previously I used junctions to make copies of entire routes. No problems at all. This week I am trying Symbolic links instead of junctions. AFAICT the difference between them is I can delete the virtual side of the symbolic link w/o harming the real files whereas w/ junctions a delete on the virtual side will kill everything on both sides. If that is correct I think symbolic links would be safer for me to use and that's why I decided to try them.
Last, from the command window this string: dir e:\ /a:l /s >"%Userprofile%\Desktop\Junctions.txt" will produce a text file showing all symbolic links and junctions of the specified drive (in this example, E:). Once one goes beyond a certain number there is a need to regularly produce this information and make sure it is on a backup. I certainly would not want to do 200 links by hand a second time.
If you need to see any more examples, let me know and I'll post them ASAP.
Also, let me know if you conclude this needs a bug report and I'll create it.