Is there a list anywhere that describes any (all?) of the recently added .wag and .eng parameters?
Page 1 of 1
New parameter() list?
#2
Posted 23 June 2014 - 08:37 AM
Ok... I'll try this then: I'm trying to put a relative path into the Include() value and OR won't take it. Why not?
#3
Posted 23 June 2014 - 11:32 AM
Genma Saotome, on 23 June 2014 - 08:37 AM, said:
Ok... I'll try this then: I'm trying to put a relative path into the Include() value and OR won't take it. Why not?
There's no reason that won't work, as long as you have correctly quoted it and what not. Attach a log from loading something where you are certain the file containing this include is read?
#4
Posted 23 June 2014 - 12:13 PM
Genma Saotome, on 23 June 2014 - 08:37 AM, said:
Ok... I'll try this then: I'm trying to put a relative path into the Include() value and OR won't take it. Why not?
You have not given enough information on the problem.
Relative paths do work in the include directive......
In the code fragment below both eng_inc and TA_AU_vic_H220 are in
openrails_data/TRAINS/TRAINSET.
Comment ( required by new parser ) Wagon ( TA_AU_VR_H220_FA_P Comment ( The wagonshape parameter MUST be in the main eng file ) WagonShape ( TA_AU_VR_H220.s ) include ( H220_Wagon.inc ) include ( ..\\eng_inc\\Brake_Westinghouse_single_pipe_wagon.inc )
Lindsay
#5
Posted 23 June 2014 - 01:19 PM
It must be the quotes then...
SIMISA@@@@@@@@@@JINX0D0t______ Wagon ( xm_atsf_142331_mt Include ( XM_ATSF_142331_Mesh_Dimensions.inc ) Include ( "..\\fleet_stds\\Std_Type_Coupler_Generic_Draft_Gear.inc" ) Mass ( 21.45t ) Adheasion ( 0.2 0.4 2 0 ) DerailRailHeight ( 5cm ) DerailRailForce ( 48.6486t ) DerailBufferForce ( 373.7216kn ) MaxBrakeForce( 7.095kN ) MaxHandbrakeForce( 8.6kN ) Friction ( 820N/m/s -0.260 5.690mph 5.10N/m/s 1.59 5.1N/rad/s 1 -1rad/s 0 1 ) Include ( "..\\fleet_stds\\Single Pipe AB Brakes.inc" ) Sound ( "genfreightwag1.sms" ) Name ("XM 40' ATSF 142331 MT") )
#6
Posted 23 June 2014 - 01:43 PM
Ahhh... nope. :sign_thanks: Somethin' else.... :whistling:
#7
Posted 23 June 2014 - 02:14 PM
Genma Saotome, on 23 June 2014 - 01:19 PM, said:
It must be the quotes then...
SIMISA@@@@@@@@@@JINX0D0t______ Wagon ( xm_atsf_142331_mt Include ( XM_ATSF_142331_Mesh_Dimensions.inc ) Include ( "..\\fleet_stds\\Std_Type_Coupler_Generic_Draft_Gear.inc" ) Mass ( 21.45t ) Adheasion ( 0.2 0.4 2 0 ) DerailRailHeight ( 5cm ) DerailRailForce ( 48.6486t ) DerailBufferForce ( 373.7216kn ) MaxBrakeForce( 7.095kN ) MaxHandbrakeForce( 8.6kN ) Friction ( 820N/m/s -0.260 5.690mph 5.10N/m/s 1.59 5.1N/rad/s 1 -1rad/s 0 1 ) Include ( "..\\fleet_stds\\Single Pipe AB Brakes.inc" ) Sound ( "genfreightwag1.sms" ) Name ("XM 40' ATSF 142331 MT") )
I think you will find that quotes will be required around "Single Pipe AB Brakes.inc" otherwise it will not be seen as a single item. Its usually worth making these a single word (using underscores instead of spaces) to prevent this sort of thing.
It appears although windows allows spaces in file names its filename parsing code has to be protected from seeing any spaces.
Lindsay
#8
Posted 23 June 2014 - 05:29 PM
No... it was the usual confusion of having mini routes and not being able to keep them in sync.
IMO that problem could be solved if absolute paths(*) were allowed in the WagonData() line of consist files... I'd aim them all at the same location. Problem solved!
(*) the relative path is far too big and does it even handle different disks? An absolute path would work.
IMO that problem could be solved if absolute paths(*) were allowed in the WagonData() line of consist files... I'd aim them all at the same location. Problem solved!
(*) the relative path is far too big and does it even handle different disks? An absolute path would work.
Page 1 of 1