Q: Does OR use one coupler definition or two?
#1
Posted 05 December 2021 - 12:48 AM
Unfortunately, the OR only knows one coupler. MSTS was better in this regard.
Some parameters are included in the Default.wag file.
#2
Posted 05 December 2021 - 02:26 AM
Weter, on 05 December 2021 - 01:03 AM, said:
What a loss :(
There are steam engines, or fixed formation MUs, that use 2 types of couplers.
Passenger cars use same couplers as freight, but with more short spring, movement.
Unfortunately yes. Although I have a little question mark in me. I read in one of the threads here before.
It would be good because the vehicles could be set up more accurately.
Coupling ( Type ( Chain ) Spring ( Stiffness ( 1E7N/m 1E6N/m ) Damping ( 1E6N/m/s 2E6N/m/s ) Break ( 1.1E8N 5E8N ) r0 ( 5cm 8cm ) ) CouplingHasRigidConnection ( ) Velocity ( 0.1m/s ) ) Coupling ( Type ( Bar ) Spring ( Stiffness ( 1E7N/m 1E6N/m ) Damping ( 1E6N/m/s 2E6N/m/s ) Break ( 1.1E8N 5E8N ) r0 ( 0cm 20cm ) ) CouplingUniqueType ( "Steam" ) CouplingHasRigidConnection ( 1 ) Velocity ( 0.1m/s ) )
Unfortunately yes. Although I have a little question mark in me. I read in one of the threads here before.
It would be good because the vehicles could be set up more accurately.
In the code snippet above, the first coupling is in the rear of the vehicle because it is an editorial of a steam locomotive [Type (Tender)]. The second coupler is the first coupler of the tender, which cannot be decomposed. At least it should be.
The CouplingUniqueType () entry is used by the German EngMex program. I took it from there.
#3
Posted 05 December 2021 - 03:08 AM
Weter, on 05 December 2021 - 02:49 AM, said:
At least, I see no sense to use both (native and include) blocks simultaneously: if use include, then original block should be deleted or commented-out from the *.eng-file.
I will delete or comment. The latter is usually when something is new to me. At that time, I also write why it was commented on and where I can find the right parameters.
If there is more than one type, the one with the lowest track number is commented on, the others are simply deleted.
#4
Posted 05 December 2021 - 04:04 AM
Also, the default.wag file is mentioned. Is this used by OR?
#5
Posted 05 December 2021 - 05:13 AM
#6
Posted 05 December 2021 - 06:32 AM
Laci1959, on 05 December 2021 - 05:13 AM, said:
Hi Folks,
As a steam loco builder - yeah - I tested this before and as far as I can tell it only uses one coupler block of code.
Also keep in mind - for precedence - if you put an "OpenRails" directory in your model's hierarchy to store things like your ENG/WAG files - ORTS will read and use that information first - overriding anything in the root directory.
Regards,
Scott
#7
Posted 05 December 2021 - 06:52 AM
#8
Posted 05 December 2021 - 07:03 AM
dforrest, on 05 December 2021 - 06:52 AM, said:
Hi David,
I did my testing a couple years ago - I think it was the second - as a result - my work only includes a single coupler block now.
Comment ( ##### COUPLER ##### ) Coupling ( Spring ( Stiffness ( 1e4N/m 4.5e6N/m ) Break ( 1200kN 1200kN ) r0 ( 5cm 5cm ) ) CouplingHasRigidConnection ( 1 ) )
Regards,
Scott
#9
Posted 05 December 2021 - 03:27 PM
#10
Posted 07 December 2021 - 12:49 AM
Hello.
I made a video. The OR does not know the different types of car couplings, otherwise the car connected to the load could not be uncoupled [Type (Bar)].
There was no such thing in MSTS. The train (stock) could not be dismantled.
Sincerely, Laci 1959