[Locomotives]	[Passenger, MU's]	[Freight, MOW, Etc]	[Scenery, Textures]	[Track, Signals]	[TrainzTrack]

 In order to download content, you must be a registered user of Auran's Trainz, and have the download helper installed. If you don't already have the download helper (UTC/SP3 users only, TRS2004 users already have it), you can get it HERE

HERE is LRV3400's F40PH project file, finish it as you see fit, just be sure to give him credit for all the fine work he's done so far.

Fixing Content to work in TRS2004
Because of the way that TRS2004 handles content differs from UTC/SP3, some items which previously worked will not work with the new version (hereafter referred to as TRS). In many cases, the content will work just fine if you're running Trainz under OpenGL, but it may appear invisible in Railyard and Driver if you're running Trainz under DirectX. If you find you've got content that you've installed and it isn't appearing in Railyard, first make sure that you have all the parts to it. A scenery item will usually be self-contained with everything it needs, but rolling stock may need custom bogies, interiors, or other items, and Locomotives may need even more things like custom enginesounds, engine profiles, and hornsounds.

If you're sure that you've downloaded and installed all the parts, the next thing to do is to run TafWeb's TrainzObjectz (available HERE) and see if it finds any errors in the configuration file (NOTE: I use the term errors here because that's what TrainzObjectz and usually TRS calls them. When the config.txt file was written, the way it was written might have been perfectly acceptable, and may not contain any actual errors. However, its syntax might not be acceptable to TRS). If it does find any errors, fix them. If you don't know how, write down what it says the problem is EXACTLY, and post a message on the Trainz forums asking for help with the problem. Chances are, someone knows how to do it, and will be more than happy to tell you. If it makes it completely through without finding any problems, you may wish to enable full error checking in TrainzObjectz and run it again, however basic error checking usually finds most severe problems which would prevent content from appearing. You might also find that you've got a duplicate KUID which is preventing an object from appearing. If even part of an object (such as a bogie) was previously installed, and now comes as part of TRS, having 2 instances of it will possibly cause every object which uses it to not appear. Deleting the version in your ...world/dispatcher/downloads/ directory should fix these problems. If TO gives you a clean bill of health, run content manager, and check the Trainz Error Log. You can safely disregard any error messages about missing shadows, and usually the ones about missing animations and bridgetrack, as there are items which TRS thinks should have them that actually have no need for them. Attempt to clear all other error messages, and once again, if you can't fix something, write down what the problem is EXACTLY, and post a message about it in the Trainz forums.

Now, after all that, if you've still got content which is "invisible" in TRS, but is showing up in TO and the Trainz Error Log without any problems, you might have a few rogue texture.txt files. Objects in Trainz consist of a 3D mesh. That mesh is textured using one or more graphic files. There's a small text file for each graphic file used as a texture. They'll be named (usually) graphicname.texture.txt where graphicname is the name of the graphic file. Occasionally, during content creation, one item is created from an existing one. As development progresses, textures specific to the new item might be used, however the old textures might still be associated with the mesh. This can also happens if textures used in the creation of an object aren't used in the final version. If the actual graphic file gets deleted but the texture.txt file doesn't, this has been known to occasionally cause the object to not appear in Railyard and Driver in TRS when running under DirectX. By checking in the directory structure of the invisible object, either placeholder textures can be assigned to rogue texture.txt file (one without the associated graphic file), or the texture.txt file can either be moved from the directory or deleted. I'd perform the first option first, in case there are any adverse effects from removing it. If not, it can always be deleted later. After this has been done for any rogue texture.txt files in the object's directory structure (remember, some might be hiding in the "shadow" directory as well), the object should appear in TRS. I haven't found one yet that hasn't.