filling station (not working animations and fill rate)
#21
Posted 17 January 2017 - 05:58 AM
PickupAnimData problem fixed in x.3757.
By the moment I don't see fast ways to solve the problem of the fast filling rate.
By the moment I don't see fast ways to solve the problem of the fast filling rate.
#22
Posted 17 January 2017 - 09:47 AM
The filing rate is not that much important in my opinion. One can use "Slow motion" key AltGr + page down to adjust :-)
Thanks for fixing it!
Thanks for fixing it!
#23
Posted 18 January 2017 - 01:36 AM
I'm yet working on the filling rate as I found a reasonable way to implement that.
There is however a question to MSTS experts: which is the unit of measure of the filling rate of the pickup as defined in the RE and then written in the .w file? I see from the OR code that it is straightforwardly interpreted as Kg, but I wonder whether MSTS intended lbs (because capacities are expressed in lbs in the standard .eng files), and I wonder whether it is gallons for diesel pickups.
There is however a question to MSTS experts: which is the unit of measure of the filling rate of the pickup as defined in the RE and then written in the .w file? I see from the OR code that it is straightforwardly interpreted as Kg, but I wonder whether MSTS intended lbs (because capacities are expressed in lbs in the standard .eng files), and I wonder whether it is gallons for diesel pickups.
#24
Posted 18 January 2017 - 04:13 AM
The filling rate in MSTS is lb per sesond.
I remember to made some measuring tests few years ago like this:
Desired fill rate was 10 m³ per minute. I.e. 10000 liter per minute -> 21997 lbs per minute (10000 liter / 0.454609 = 21996.9248 lb).
Divide this by 60 to get a result in seconds you get 367 lbs (21996.9248 / 60 = 366.61541 lb)
So when using 367 as fill rate a fill process with a tender of 31.5 t water capacity needs about 3:09 minutes in MSTS (31.5 t / 10 m³ -> 31500 liter / 10000 liter = 3.15 minutes).
I remember to made some measuring tests few years ago like this:
Desired fill rate was 10 m³ per minute. I.e. 10000 liter per minute -> 21997 lbs per minute (10000 liter / 0.454609 = 21996.9248 lb).
Divide this by 60 to get a result in seconds you get 367 lbs (21996.9248 / 60 = 366.61541 lb)
So when using 367 as fill rate a fill process with a tender of 31.5 t water capacity needs about 3:09 minutes in MSTS (31.5 t / 10 m³ -> 31500 liter / 10000 liter = 3.15 minutes).
#25
Posted 18 January 2017 - 04:29 AM
Thank you very much! Does this apply also to diesel fuel?
#26
Posted 18 January 2017 - 04:53 AM
Csantucci, on 18 January 2017 - 04:29 AM, said:
...Does this apply also to diesel fuel?
IIRC I would say yes. For coal I had the similar measurings. MSTS always simply uses lb, at least for water, coal and diesel. This is according to that you never find a measuring unit in tdb or world files about pickups (I'm rather sure about this, but no guarantee).
#27
Posted 18 January 2017 - 05:14 AM
Thank you again. This is the source patch
Pickupfillrate.zip (1.81K)
Number of downloads: 235
I attach it here, because as it is not an elementary patch, I prefer to have the OK by James to upload it before release 1.2.
Pickupfillrate.zip (1.81K)
Number of downloads: 235
I attach it here, because as it is not an elementary patch, I prefer to have the OK by James to upload it before release 1.2.
#28
Posted 18 January 2017 - 05:16 AM
For the case you build up pickups with MSTS keep in mind there is a bitter bug in MSTS while adjust values of pickups. Specifically the type of a pickup will almost ever not properly written into the tdb!
So the made entry in tdb and tit files often looks like this:
PickupItem (
___ TrItemId ( 1206 )
___TrItemSData ( 518.465 00000006 )
___TrItemPData ( -265.898 -305.171 -5536 15046 )
___TrItemRData ( -265.898 1.34109 -305.171 -5536 15046 )
___PickupTrItemData ( 200000 00000000 )
)
but instead of the 00000000 there must be values like this: 00000280 = Water, 00000300 = coal, 00000380 = diesel
Here you can download a tool I've made to fix this problem with pickups (using without guarantee). Using the tool by copy it to the directory of the desired route and make sure the world files are un-compressed.
So the made entry in tdb and tit files often looks like this:
PickupItem (
___ TrItemId ( 1206 )
___TrItemSData ( 518.465 00000006 )
___TrItemPData ( -265.898 -305.171 -5536 15046 )
___TrItemRData ( -265.898 1.34109 -305.171 -5536 15046 )
___PickupTrItemData ( 200000 00000000 )
)
but instead of the 00000000 there must be values like this: 00000280 = Water, 00000300 = coal, 00000380 = diesel
Here you can download a tool I've made to fix this problem with pickups (using without guarantee). Using the tool by copy it to the directory of the desired route and make sure the world files are un-compressed.
#29
Posted 18 January 2017 - 05:30 AM
Fortunately OR does not seem to use the TDB data for pickups.