Railworks America

It's just an alpha sort issue. Simple fix, but in the case of Stevens Pass, not so simple to get the fix distributed. RW&A is a different story, though, and I'll have a patch for Bob later today.

For those of you who enjoy hacking files, open the geo file for each affected signal head or headlight or whatever and look for the material description of each light. Near the end of each one, insert the line that begins with ZWriteEnabled.

Code: Select all

               :
               :
            </MipLodBias>
            <ZWriteEnabled d:type="bool">0</ZWriteEnabled>
            <AlphaRef d:type="sUInt32">127</AlphaRef>
            <LightGlowFadeDistance d:type="sFloat32" d:alt_encoding="0000000000000000" d:precision="string">0</LightGlowFadeDistance>
        </cHcExplicitStateMaterial>

Thanks to Michael Stephan for testing this for me.

Thanks Rick!

Super Rick to the Rescue!!

That worked! I just had to fiddle.

And this is precisely why we discuss such issues. Discussion leads to solutions. Thanks Rick!

To Rick or anybody that can explain.....

Could you possibly explain what was actually wrong? It's the curious "How things work" part of me asking. I'm wondering what was different with your signals that made them fail under TS2015 while the majority of assets in the sim did not. Did you use some unorthodox method that had some advantages over the conventional method.... hence the reason you used it?

I like postmortems so to speak.

ricksan wrote:It's just an alpha sort issue. Simple fix, but in the case of Stevens Pass, not so simple to get the fix distributed. RW&A is a different story, though, and I'll have a patch for Bob later today.

For those of you who enjoy hacking files, open the geo file for each affected signal head or headlight or whatever and look for the material description of each light. Near the end of each one, insert the line that begins with ZWriteEnabled.

Code: Select all

               :
               :
            </MipLodBias>
            <ZWriteEnabled d:type="bool">0</ZWriteEnabled>
            <AlphaRef d:type="sUInt32">127</AlphaRef>
            <LightGlowFadeDistance d:type="sFloat32" d:alt_encoding="0000000000000000" d:precision="string">0</LightGlowFadeDistance>
        </cHcExplicitStateMaterial>

Thanks to Michael Stephan for testing this for me.

Thanks mate...

The new patch is posted.

How do you open the geo file?

bpetit wrote:How do you open the geo file?

Best way is with RW Tools. It opens them right up and ready to edit.

Is there a fix for the Stp Signals?
Can this fix be used with the Stp signals?
Im confused.

ColoradoRailfan wrote:Is there a fix for the Stp Signals?
Can this fix be used with the Stp signals?
Im confused.

Sorry to hear that. What are you confused about?

buzz456 wrote:

ColoradoRailfan wrote:Is there a fix for the Stp Signals?
Can this fix be used with the Stp signals?
Im confused.

Sorry to hear that. What are you confused about?

Since the Stevens Pass Signals have this problem too, I am confused whether if editing the .GEO file and inserting the text will fix the problem or not. I have not experimented with this yet.

Yes Bob showed that this fixed the problem.

Can somebody list all the files for the Stephens Pass route signals that need to be edited for this fix? or are there to many

Can you not look yourself?