RW&A ALCo HH660 problem

Post your problems and installation issues here!

Re: RW&A ALCo HH660 problem

Unread postby ChrisOnline » Sun Feb 14, 2016 6:44 pm

OK, we seem to be going around in circles.

The bottom line is . . . everything seems to be in the right place, appropriate asset boxes are checked in the Editor's flyout menu, and the couplers aren't visible!

Chris
ChrisOnline
 
Posts: 331
Joined: Tue Oct 02, 2012 11:47 am

Re: RW&A ALCo HH660 problem

Unread postby buzz456 » Sun Feb 14, 2016 6:51 pm

Sometimes this thing can be a little quirky. Have you deleted the locomotive cleared the cache, closed the game, re-started and installed this beast again? I've chased these problems around for hours some times only to find that for whatever reason the game was saving the configuration on something.
Buzz
39 and holding.
"Some people find fault like there's a reward for it."- Zig Ziglar
"If you can dream it you can do it."- Walt Disney
Image
User avatar
buzz456
Site Admin
 
Posts: 20940
Joined: Sun Mar 21, 2010 8:30 am
Location: SW Florida

Re: RW&A ALCo HH660 problem

Unread postby qrfan3 » Sun Feb 14, 2016 6:52 pm

Chris
I think your problem may be with the coupler blueprint ( coupler_ms.bin ) itself in the coupler folder...it has a path to:

<?xml version="1.0" encoding="utf-8"?>
<cBlueprintLoader xmlns:d="http://www.kuju.com/TnT/2003/Delta" d:version="1.0">
<Blueprint>
<cCouplingTypeBlueprint>
<UncoupledGeometry d:type="cDeltaString">GreatNortherner\Allegheny\RailVehicles\Coupler\[00]coupler_ms_open</UncoupledGeometry>
<Bogey d:type="cDeltaString"></Bogey>
<Strength d:type="sFloat32" d:alt_encoding="0000000000C06240" d:precision="string">150</Strength>
<CouplingConnection>
<cCouplingConnectionBlueprint d:id="49956832">
<Type d:type="cDeltaString">buckeye</Type>
<CoupledGeometry d:type="cDeltaString">GreatNortherner\Allegheny\RailVehicles\Coupler\[00]coupler_ms_closed</CoupledGeometry>
<ReceivingGeometry d:type="cDeltaString"></ReceivingGeometry>
<PivotType d:type="cDeltaString">eMidPoint</PivotType>
<MinDistance d:type="sFloat32" d:alt_encoding="0000000000000000" d:precision="string">0</MinDistance>
<MaxDistance d:type="sFloat32" d:alt_encoding="000000A09999B93F" d:precision="string">0.1</MaxDistance>
<TargetDistance d:type="sFloat32" d:alt_encoding="000000A09999A93F" d:precision="string">0.05</TargetDistance>
<SpringCoefficient d:type="sFloat32" d:alt_encoding="0000000000000000" d:precision="string">0</SpringCoefficient>
<Damping d:type="sFloat32" d:alt_encoding="0000000000000000" d:precision="string">0</Damping>
<MaxForce d:type="sFloat32" d:alt_encoding="000000C0FDFFEF47" d:precision="string">3.40282e+038</MaxForce>
<ManualCoupling d:type="bool">0</ManualCoupling>
</cCouplingConnectionBlueprint>
</CouplingConnection>
</cCouplingTypeBlueprint>
</Blueprint>
</cBlueprintLoader>

If you don't have the GreatNortherner\Allegheny\RailVehicles\Coupler folders in your system that may be your problem.

HTH
User avatar
qrfan3
 
Posts: 443
Joined: Sun Feb 28, 2010 11:38 pm
Location: Downunder from the Sunshine State.

Re: RW&A ALCo HH660 problem

Unread postby buzz456 » Sun Feb 14, 2016 6:55 pm

Gosh I never looked there.
Buzz
39 and holding.
"Some people find fault like there's a reward for it."- Zig Ziglar
"If you can dream it you can do it."- Walt Disney
Image
User avatar
buzz456
Site Admin
 
Posts: 20940
Joined: Sun Mar 21, 2010 8:30 am
Location: SW Florida

Re: RW&A ALCo HH660 problem

Unread postby ChrisOnline » Sun Feb 14, 2016 8:27 pm

qrfan3 wrote:Chris
I think your problem may be with the coupler blueprint ( coupler_ms.bin ) itself in the coupler folder...it has a path to:

<?xml version="1.0" encoding="utf-8"?>
<cBlueprintLoader xmlns:d="http://www.kuju.com/TnT/2003/Delta" d:version="1.0">
<Blueprint>
<cCouplingTypeBlueprint>
<UncoupledGeometry d:type="cDeltaString">GreatNortherner\Allegheny\RailVehicles\Coupler\[00]coupler_ms_open</UncoupledGeometry>
<Bogey d:type="cDeltaString"></Bogey>

- - - - etc etc - - - -


If you don't have the GreatNortherner\Allegheny\RailVehicles\Coupler folders in your system that may be your problem.

HTH


That's it! Excellent, thank you! I have edited the coupler_ms.bin file to set the correct path for the Geo files (same folder) and it works a treat!

Of course, that does mean that the actual download is incorrect (as a self-contained file, as intended), and will only work if someone already has the coupler files in the \Allegheny folder from another installation

Bear in mind, I wasn't the original OP here, so hopefully Matchstick101 is picking up on this.

Again, many thanks grfan3/HTH! And thanks for trying to help, Buzz!

Chris
ChrisOnline
 
Posts: 331
Joined: Tue Oct 02, 2012 11:47 am

Re: RW&A ALCo HH660 problem

Unread postby qrfan3 » Sun Feb 14, 2016 8:33 pm

ChrisOnline wrote:Again, many thanks grfan3/HTH! And thanks for trying to help, Buzz!


YVW...just helping Buzz out with his workload.... *!!wink!!* I don't know how he gets time to do all the work he does here and also keep the bride happy at the same time!
User avatar
qrfan3
 
Posts: 443
Joined: Sun Feb 28, 2010 11:38 pm
Location: Downunder from the Sunshine State.

Previous

Return to Problems and Peculiarities

Who is online

Users browsing this forum: No registered users and 8 guests

cron