Fuel tank through cab error again, please help

[_o_OOOO_oo-Kanawha]

Since this is a Britkits model I suppose it comes in "kit" form. The phenomenon you describe is caused by messed up the child objects.
The locomotive base model is fitted with different accessories like fuel tanks, handrails, fans, horns etc to suit different roads or timeframes. Also there are payware versions that have more detail and different options.

Have you been mixing versions, i.e. RW2 with RW3, since many of Britkits models have recently been updated?
Then my solution would be to delete the whole Britkits folder and install the only the latest versions anew, taking care to read the manuals first so as not to mix old and new stuff as perhaps some files need to be copied around.

[_o_OOOO_oo-Kanawha]

All default and freshly installed, ... ..., then the model itself must be at fault.

Have you used the function "Check loco for missing assets" of your RW_Tools?

When child objects start to float, the preceding object in the engine.bin child object hierarchy is missing or faulty. Usually this means light or smoke emitters in my experience.
What is the exact file you installed? Please state name, filesize and timestamp, so some of us could take a look inside the folders and bins and try to find out what went wrong.

[_o_OOOO_oo-Kanawha]

Also, the NC (No Crew/Empty Cab) units don't have this error for some reason

That is a very helpful hint, Mr. Durdan!
Usually crew in cab is aliased to some other engine or even route. Since these are first generation units, it could be the crew figures are from a steam era route which you perhaps haven't installed. And since these seem to be missing, the next child object in the hierarchy gets rendered in their place, taking into account the offset of that next asset, otherwise you would have a fuel tank sitting in the engineers seat.

[_o_OOOO_oo-Kanawha]

Oompff, now it is getting difficult.

Intermittent problem, no changes to running system ....

The obvious remedy would be to clear cache and do a verify by the Steam client. If all else fails: "Format C:\" and start all over again.
But now I remember you just got yourself a nice custom built gaming system, so I suppose it it still reasonably clean and uncorrupted by relentless hacking at those assets.
Britkits is impervious to Steam, but perhaps its dependencies are not.

You have checked your loco for missing assets by RW_Tools, haven't you? That is the only sensbile advice I can give you right now.
Because I still think it is the missing crew figures that need to be aliased into your engine.
Is cab crew scenario dependent? I guess not. Your engine looks like this when placed on the track in a new free roam on whatever route, right?

Anyway, you still haven't told which Britkits file you installed so we can check its dependencies.

[KCJones]

It could be the cab sound which is linked directly to the default SD40. If you load that loco in your scenario or at least click on the RailsimulatorUS box in the right flyout of the scenario editor it will probably work.
When I get to upgrading the GP I will correct that problem. At the moment I am finishing my E8/9 models and then on to the various Fs

Dick

[_o_OOOO_oo-Kanawha]

There you are, a hint to the right solution by the man himself.

So it might be an aliasing problem after all, strange though it includes a piece of default rolling stock users have hardly ever deselected.
Perhaps even RW_Tools doesn't report a missing sound file bin or sound file patches referenced by that bin. This could be the case if Mr. Durdan inadvertedly messed the sound file hierarchy up by installing/deinstalling custom horns, bells and whistles.
There are so many things that can go awry in the complicated .xml object hierarchy of TS2012's asset management.

[harryadkins]

I have a similar problem with the Britkit 2-6-0 and 2-6-2. Do I need to have any other steam locos selected when I try to insert these locos into scenarios?

[Douglasmrs]

It could be the cab sound which is linked directly to the default SD40. If you load that loco in your scenario or at least click on the RailsimulatorUS box in the right flyout of the scenario editor it will probably work.
When I get to upgrading the GP I will correct that problem. At the moment I am finishing my E8/9 models and then on to the various Fs

Dick

Hi! I bought your package on the GP9 last saturday 06/02 and also had this problem, but now following this hint the problem was solved. I would like to thank for a package desponabilizar as perfect as those that are: Alco RS-3 and GP-9 I hope to soon get the package E8 / 9 and if possible future purchase the package C30-7 or C36-7 ATSF (This is clear if you want to export them in Railworks) Thank you!