Help with Frisco 1522

[BigBoyFan4006]

I've erased all of the "minisize" tags for the smoke attachments that weren't allowed from the config file of the loco, but I still have one problem. CM's "View Errors & Warnings" says, "Unable to load mesh file: 'frisco_1522_4-8-2_mountain_shadow\frisco_1522_4-8-2_mountain_shadow.pm'." I've looked in the loco's files and the config file, but I can't find anything that would suggest it has the aforementioned file. Am I missing something?

Edit: I forgot to post the kuid number what version it is, as xcrossi pointed out. It's thecowboy's version of 1522; <kuid:79097:1001>.

 

[xcrossi]

I have 2 versions
thecowboy
sniper297
what version do you have
Next time please post Kuid 1st thing

 

[BigBoyFan4006]

I have 2 versions
thecowboy
sniper297
what version do you have
Next time please post Kuid 1st thing

Sorry about that! I'll edit the original post. I have thecowboy's version (kuid:79097:1001).

 

[BuilderBob]

I've erased all of the "minisize" tags for the smoke attachments that weren't allowed from the config file of the loco, but I still have one problem. CM's "View Errors & Warnings" says, "Unable to load mesh file: 'frisco_1522_4-8-2_mountain_shadow\frisco_1522_4-8-2_mountain_shadow.pm'." I've looked in the loco's files and the config file, but I can't find anything that would suggest it has the aforementioned file. Am I missing something?

The file would typically be referenced from a 'mesh' tag in the 'shadow' container of the mesh-table entry. If you can find that in config.txt then you could delete the whole shadow container and live with the warning you will get. If it's not there then I have no idea why CM might be looking for that file.

I presume you are working on a clone of the original. Did you convert the pm meshes to im?

The most effective solution would be to upgrade the asset and make a shadow mesh using PEV's QuickShadows and create the shadow container in the mesh table for yourself.

 

[xcrossi]

I use AssetX to repair Ah assets. In the AssetX folder is a file called invisible.im. I copy/paste to the folder that needs a shadow.im then edit loco cfg like so. I delete all other folders/files referring to a shadow.
mesh-table
{
default
{
mesh "frisco_1522_4-8-2_mountain_body/frisco_1522_4-8-2_mountain_body.im"
auto-create 1
}

shadow
{
mesh "frisco_1522_4-8-2_mountain_body/invisible.im"
}
}

 

[BigBoyFan4006]

I presume you are working on a clone of the original. Did you convert the pm meshes to im?

I believe it's the original. It was uploaded on the DLS by thecowboy himself. At least that's what it says.

 

[xcrossi]

There is more than one way to fix shadow errors,
pm/im errors can be fixed with PM2IM.exe
A type of shadow can be made with quick shadows but Ive had mixed results.
Shadows eat frame rates.

Who knows what evil lurks in the hearts of men? The Shadow knows!"

 

[BigBoyFan4006]

I use AssetX to repair Ah assets. In the AssetX folder is a file called invisible.im. I copy/paste to the folder that needs a shadow.im then edit loco cfg like so. I delete all other folders/files referring to a shadow.
mesh-table
{
default
{
mesh "frisco_1522_4-8-2_mountain_body/frisco_1522_4-8-2_mountain_body.im"
auto-create 1
}

shadow
{
mesh "frisco_1522_4-8-2_mountain_body/invisible.im"
}
}

The thing is is that the config file doesn't have the "shadow" container in the mesh-table entry. Heck it doesn't even have a mesh-table entry. Just all the needed kuids and smoke attachments. Plus, I just do what BuilderBob apparently does.

 

[BigBoyFan4006]

Shadows eat frame rates.

Good thing I have shadows turned off. lol

Who knows what evil lurks in the hearts of men? The Shadow knows!"

Did you come up with that yourself? That's pretty good!

 

[xcrossi]

Good thing I have shadows turned off. lol



Did you come up with that yourself? That's pretty good!

Its from a old radio show I listened to when I was a boy..before TV.
The color was much better.....

 

[BuilderBob]

Sorry about that! I'll edit the original post. I have thecowboy's version (kuid:79097:1001).

That is a bad asset and I should have recognised it when you first posted. I would recommend staying right away from it.

The kuid you quote has been superseded by
Frisco 1522 4-8-2 'Mountain Type,<kuid2:79097:1001:1>
which is flagged as built-in. N3V claims it is not supposed to be built-in. Whatever, it is faulty and will create problems if you ever manage to add it into a route - it will not appear, and is impossible to delete.

I think it is because it has been incorrectly converted from an aliased asset to one with its own mesh table. As an alias asset, the original had no mesh table at all and all mesh information was obtained from the alias. It was then upgraded when it was made built-in, and that somehow confused things so it no longer knows whether it is supposed to get mesh information from its own mesh table or from the alias. The suppressed error checking that applies to built-in assets means that the problem is not picked up. At least that's my theory.

If you cannot find a reference to the shadow mesh then perhaps CM is looking for it as a result of a reference in the alias asset. If that's what is happening then you might be able to fix that by fixing the alias asset.

Or, remove the alias reference, copy the main mesh, create a shadow mesh and build a complete mesh table.

But my preference would be to look for this loco somewhere else.

 

[BuilderBob]

The thing is is that the config file doesn't have the "shadow" container in the mesh-table entry. Heck it doesn't even have a mesh-table entry.

That's a giveaway!! Does it refer to another asset as an alias? If so, delete any mesh table you created for the asset, and fix the problem in the asset that it aliases, using QuickShadows.

 

[BigBoyFan4006]

That is a bad asset and I should have recognised it when you first posted. I would recommend staying right away from it.

The kuid you quote has been superseded by
Frisco 1522 4-8-2 'Mountain Type,<kuid2:79097:1001:1>
which is flagged as built-in. N3V claims it is not supposed to be built-in. Whatever, it is faulty and will create problems if you ever manage to add it into a route - it will not appear, and is impossible to delete.

I think it is because it has been incorrectly converted from an aliased asset to one with its own mesh table. As an alias asset, the original had no mesh table at all and all mesh information was obtained from the alias. It was then upgraded when it was made built-in, and that somehow confused things so it no longer knows whether it is supposed to get mesh information from its own mesh table or from the alias. The suppressed error checking that applies to built-in assets means that the problem is not picked up. At least that's my theory.

If you cannot find a reference to the shadow mesh then perhaps CM is looking for it as a result of a reference in the alias asset. If that's what is happening then you might be able to fix that by fixing the alias asset.

Or, remove the alias reference, copy the main mesh, create a shadow mesh and build a complete mesh table.

But my preference would be to look for this loco somewhere else.

Thanks for telling me! I'll just use sniper297's version.

That's a giveaway!! Does it refer to another asset as an alias? If so, delete any mesh table you created for the asset, and fix the problem in the asset that it aliases, using QuickShadows.

I will use that for future reference. Thank you very much!

 

[trainman7616]

If you are willing to wait awhile I am doing the 1920s version again since I lost my original mesh.