gap between couplings
#1
Posted 07 August 2016 - 09:44 AM
With one locomotive, I have the following problem:
By default coupling tender side and distance tender / locomotive is fine. Only with the coupling on locomotive side I gets a gap? ( on Photo they are coupled....!)
fig:1
With a sister locomotive, I had also to change a few centimeters in the .ENG and .WAG file. >>> Size ( xxx yyy zzz=lenght) <<<
Who now works correctly. But in this model the couplings are then correct, but no space between tender / locomotive.
fig:2
If I correct the tender length again, the rear coupling is back with a gap.
fig 3
it seems to me that this tender is "asymmetrical", the center of the shape file is probably not exactly the center, so you do not get it properly with settings in the .WAG file. [ by >>> Size ( xxx yyy zzz=lenght) <<< ] (The sister locomotives have other tenders ...).
I've tried various settings, but it continues to go wrong at any of the three points.
Does anyone have any idea how you can correct this?
.
#2
Posted 10 August 2016 - 11:09 AM
#3
Posted 11 August 2016 - 09:59 AM
Good information and the "shape viewer" is also very useful.
However, it has no effect on "my problem".
It seems that the rule "CentreOfGravity (X Y Z)" does not have any effect. Probably only effect in "flipped" situation? But you can not shift the tender backwards or forwards. Actually, only the length in "Size (X Y Z)" has an effect on the locomotive and tender. (But only with this you do not get it right ....)
Maybe one more idea?
#4
Posted 11 August 2016 - 12:15 PM
#5
Posted 11 August 2016 - 12:20 PM
Edward K.
#6
Posted 11 August 2016 - 01:08 PM
#7
Posted 11 August 2016 - 11:21 PM
Hobo, on 11 August 2016 - 12:15 PM, said:
This is a Russian type LV steam locomotive. This model can be downloaded on the Russian site "http://www.trainsim.ru/download/192/".
After my opinion they make lots of fantastic models for MSTS. (And so ORTS).
The "sister locomotive" LV-#0441 2-10-2 and some L-type 2-10-0 locomotives are no longer present on this site.
It's the same engine, but the # 0441 is an older model from a few years ago. (Not just repainting), and this had a slightly different 6-axis and 4-axis tenders.
The #0182 is newly released, apparently to 99% based on the previous one.
edwardk, on 11 August 2016 - 12:20 PM, said:
Hmm, that's bad news. This means that no adjustment is possible for me ....
I was also hoping that if the length in "ESD_Bounding_Box" (.SD file) was correct, and the lenght in "Size ( X Y Z )" make smaller, this is the right "coupling to coupling" length could be. But this has no effect. Indeed, if the length of "Size ( X Y Z )" are too short, locomotive and tender melt together.
I think there is no possibility of having to give a different length from the center point towards the front and rear.......
And "CentreOfGravity (X Y Z)" does not have any effect. (Maybe in "flipped" situation, but you can not flipped the tender....)
So the problem is stuck in the shape file?
.
#8
Posted 12 August 2016 - 01:38 AM
Here's a spacer....
Attached File(s)
-
Invisiwag_spacer.zip (3.52K)
Number of downloads: 744
#9
Posted 12 August 2016 - 05:19 AM
There doesn't seem to be much wrong with the loco's couplings.
The loco is in its "as-downloaded" state and the wagon is an MSTS default. As can be seen, there is a slight difference in gap but nothing like QJ-6811 showed in his original post.
In case it's pertinent, I am using the MSTS default default.wag
EDIT : I have to apologise that my test and screenshot were taken in MSTS; I have now tested in Open Rails and there is, in fact, a large gap between the front of the loco and wagon. This would seem to imply that it's an OR problem.
Cheers,
Ged
#10
Posted 12 August 2016 - 11:06 AM
Further to this problem :
It appears that Open Rails doesn't read the CentreOfGravity entry from the eng file. This loco's entry is : CentreOfGravity ( 0m 2m -1.3m ). If that line is replaced with : CentreOfGravity ( 0m 0m 0m ) and run with MSTS, EXACTLY the same problem occurs with the front-coupled wagon.
As has been mentioned previously, it seems that the only way to correct it for the current version of OR is to modify the shape file. That doesn't seem to be the right way to go, because who knows how many other locos will have the same problem? Wouldn't it be better if OR read that entry and acted on it as MSTS does?
Cheers,
Ged