How do you deal with the NAVS car files???

[slipperman]

Hi Gerry,
The instructions supplied with each pack specify which 'base' pack is required, together with the sounds pack.
The trouble is that I didn't read the instructions properly!

The RDG pack specifies "NAVS_Hopper_100t_Triple_Type1_BASE". Although not indicated, that IS the .zip file name, but if that is put into the main search box, the only download selected is the Paint Kit, which, admittedly, does refer to the required .zip file. The title of the required base pack is : NAVS Z-Series 100-Ton Triple Hopper Type 1 - no mention of 'Base'. This also applies to the Quad set, where its title includes "Foobie Kit", whatever that means!!

Cheers,
Ged

[R. Steele]

Foobie??? I never knew either...I assumed it referred to something that was fake because all my research pulled up was the following:

Foobie, a compound word made up of fake, and boobies

Foobie (not to be confused with Fooby) is a Furby fake that was distributed by an anonymous company

Foobie. 1 a generic exclamation to address the approach of another. 2 one who is silly or meaningless; a doofus. commonly used with friends or friendly aquaintances. Hey, Foobie!

Urban Dictionary >> a fat doobie made with a minimum of 3 papes

Erick used the term, maybe he knows what he specifically meant by it, or maybe he just went "off the rails that day"??!!

[SD40-2]

Gerry,

Foobie is an old term from the model railroading world meaning something that is intended to stand in for something else, and is off in some significant way. (Wrong Door, wrong dimensions, wrong details, etc.)

Defined here: https://listserv.linguistlist.org/pi...ch/097205.html

In the context of the NAVS hopper cars, they're not meant to represent any particular model or specific class of hopper, just a representative rib-sided 3/4 bay hopper.

[R. Steele]

Gerry,

Foobie is an old term from the model railroading world meaning something that is intended to stand in for something else, and is off in some significant way. (Wrong Door, wrong dimensions, wrong details, etc.)

Defined here: https://listserv.linguistlist.org/pi...ch/097205.html

In the context of the NAVS hopper cars, they're not meant to represent any particular model or specific class of hopper, just a representative rib-sided 3/4 bay hopper.

Thanks, my tagline "Forever, ridin' drag in railroad knowledge" remains as accurate today as it was yesterday...although I learned something new.

[geepster775]

The trouble with NAVS material is that its not very self-contained or turn-key for users who want that simplified installation experience. You end up having to pull textures from here, shapes from there, and sounds from yet another place, and then any real prototype textures are payware from that other site. And I know some users are begging him often for more highly prototype models and not this foobie Kuju default replacement stuff that he seems to be so preoccupied with.

That said, I usually bite my tongue knowing the whole OR rolling stock landscape is in flux, and pretty much every new release can often times be a far cry from the last recent release - and that's usually on purpose. Let these guys experiment and test out some new ways of designing and doing things, and potentially keep what methods work best. Maybe come up with ready-to-run stuff for turn-key fans and the old "Athearn blue box" stuff for guys who like to assemble things themselves.

I did find one advantage to the recent separation of trucks from the carbody that he did with the revised flatcars, that being you can shape shift as needed to meet the same dimensions of another vendor's product without having the carbody stretching/shrinking changes you apply impact the trucks, the roundness of the wheels, and holding the proper gauge.

I hate when this happens between different vendors



But then I can narrow the carbody shape and/or load (I haven't narrowed the F/A for the reporting marks yet)



And keep the trucks/gauge/wheel shape unaffected

[crstagg]

Well...everybody's cook book ideas ARE FAILURES.............I HAVE INSTALLED THE "avs_hopper_100t_quad_type1_base.zip " and INLX and RDG files to the Trainset folder.

The screenshot is what I AM looking at.....and YES Charles, don't be so arrogant you can't read directions....while OR isn't really new to us, these NAVS files ARE for ones that have handled the original MSTS files of 20 years ago.

I have NO idea why I am not getting the thumbnails or the RDG car files are NOT showing up in the consist I made.

So Ged and Gerry thanks for your "frustration factor"......the rest of you, the snotty comments are NOT ONE BIT OF A HELP

NOTE that below I am referring to the TRIPLE Base ZIP not the QUAD Base ZIP. The RDG Hoppers are triple not quad.

After correctly installing the navs_hopper_100t_triple_type1_base.zip file I now get this:
RDG.JPG
The first time I installed navs_hopper_100t_triple_type1_base.zip file I noticed that It had 2 folders NAVS_Common and NAVS_Hopper_100t_triple_type1_base. Since I had already had a NAVS_Common folder in my Trainset I only drug the NAVS_Hopper_100t_triple_type1_base folder from the ZIP to my Trainset folder. Tested with TSRE-CE. No-Joy. WAG still did not show. Then I noticed the the NAVS_Common folder in the Triple_base ZIP file has a different sub-folder than the NAVS_Common folder in the Quad_base ZIP file. Now after dragging the NAVS_Common folder from the NAVS_Hopper_100t_triple_type1_base.zip file to my Trainset folder the RDG Hopper displays in TSRE-CE like it should.

Did you make the same mistake? ...\TRAINS\TRAINSET\NAVS_COMMON should look like this:
NAVS_Common.JPG

And BTW I've been working with MSTS files for almost 23 years and still make mistakes.

[R. Steele]

While TSRE will open and view NAVS car files ( for instance either of the open top quad or triple hopper wag type1 base files ) you cannot use shapeviewer to open the wag files...because it does not read include files. Not NAVS problem, but sometimes I like to use shapeviewer for a quick view, instead of opening up the CE of TSRE. ...or am I missing something?

[rrdiesel87]

It sounds like this issue has been resolved, however just to clarify for anyone that still is having issues..

The "NAVS_Common" folder serves as the main reference point for the entire NAVS library of rolling stock, everything the car packs need is contained within that folder. If you do not have this folder set up/named exactly as it is outlined in the original NAVS readme text, it simply will not work appropriately.

My repaint files contain only the .wag files and .dds files in each folder and reference the specific files located with the "NAVS_Common" folder accordingly. Assuming the end user has correctly installed the NAVS base packs per the readme instructions, all that is needed is to simply drop the repaint folder in to the "trainset" folder. I have all of these in my own trainset folder and have tested every car in TSRE prior to upload. That being said, if there is still an issue it is most certainly related to mis-mangement or incorrect file names in the "NAVS_Common" folder.

It should be noted that my repaints do NOT utilize the NAVS decal system, so that can be ruled out as a potential issue when troubleshooting.

[rdayt]

I've got 10'6".
How wide are they supposed to be?
flat.jpg

Randy

[crstagg]

I've got 10'6".
How wide are they supposed to be?
flat.jpg

Randy

You used ShapeViewer to select an S file to open a Shape file. Gerry was referring to ShapeViewer's tool to select a WAG or ENG file to open its shapefile. Note that he pointed out that the reason is ShapeViewer does not recognize Include statements. Shape files do not contain Include statements.