Help with Opacity for Loco Interior Windows

[Orloldman]

I have been working on fixing some AC4400 units for use in TS2010 and have run into a problem with the interiors.

I changed the ".pm" files to ".im" files, added a "rightside vent" texture and corrected the "radius" error that seems to go with all the interiors on these units. I learned the hard way that you can't use Content Creator to fix these as you will end up with no levers or guage needles going that route.

Now when I check them for errors and warnings all are cleared, except for the following:

Warning: The Boolean tag 'opacity' in container 'windows' is not a valid Boolean value.

The lines pertaining to this in the config.txt file looks like this:

windows
{
mesh "windows.pm"
att
opacity 0.4
}

I end up deleting the "att" line as it doesn't need to be there and causes an error, but how do I fix this to eliminate the "Boolean" warning?

If I just delete it, I end up with windows that really look like mirrors!

Thanks,
Duane

I realize these units will work with warnings but why not clean them up completely?

 

[clam1952]

I have been working on fixing some AC4400 units for use in TS2010 and have run into a problem with the interiors.

I changed the ".pm" files to ".im" files, added a "rightside vent" texture and corrected the "radius" error that seems to go with all the interiors on these units. I learned the hard way that you can't use Content Creator to fix these as you will end up with no levers or guage needles going that route.

Now when I check them for errors and warnings all are cleared, except for the following:

Warning: The Boolean tag 'opacity' in container 'windows' is not a valid Boolean value.

The lines pertaining to this in the config.txt file looks like this:

windows
{
mesh "windows.pm"
att
opacity 0.4
}

I end up deleting the "att" line as it doesn't need to be there and causes an error, but how do I fix this to eliminate the "Boolean" warning?

If I just delete it, I end up with windows that really look like mirrors!

Thanks,
Duane

I realize these units will work with warnings but why not clean them up completely?

Quite a few assets have this boolean error, where numbers with decimal points etc have been used instead of a boolean value which should be 0 or 1

A boolean value represents one of two data options, as in true or false not a numerical value, in this case 1 = true 0 = false.
So in theory for opacity to work it has to be 1

 

[andi06]

This is a TRS bug which has been reported several times. Opacity is validated as a boolean but should be validated as a normalised float, 0.0 for fully transparent to 1.0 for fully opaque.

 

[Bill522]

Perhaps the line that reads: mesh "windows.pm" should be changed to read:
mesh "windows.im"

 

[Orloldman]

Thanks all for the feedback.

The warning goes away if the value is set to 0.0 or 1.0 (committing converts it to either 0 or 1 in the config.txt file). Any number in between gives the warning but it does work.

0 gives VERY clean windows!

Converting the window.pm file to .im made no difference (don't know how I missed that one when "fixing" the asset).

I'm still learning and your help is appreciated.
Duane

 

[backyard]

Thanks all for the feedback.
Converting the window.pm file to .im made no difference (don't know how I missed that one when "fixing" the asset)
I'm still learning and your help is appreciated.
Duane

Did you reflect the file conversion in the config file?