Trees lined with white.

[reginaldfan1]

When I was in My Strasburg Railroad route the trees were lined with white, I tried tinkering around in the video settings, but I can't seem to find a fix. Any help would be appreciated.



Here is a picture of what is happening.

https://atrainzfan.tumblr.com%2Fpost%2F739170102307618816

also be patient with me

 

[MasterTracklayer]

I can`t see what`s supposed to be wrong there, but the description sounds to me like the textures in your trees have issues with their alpha channels. If I am correct, then no amount of tinkering with the video settings will ever help. I have no idea how to fix the issue, but I do think that I recognize the symptoms, having seen it in other games as well. Good luck!

 

[JCitron]

If you are using an NVIDIA card, update to the latest driver as that appears to fix the problem at least for now.

 

[reginaldfan1]

JCitron, Thanks I will try that.

 

[Forester1]

To really see the issue in his picture, you have to click on the picture, then copy and paste it into something like IrfanView to get full size. The result looks like the trees are peppered with small white dots, kind of like they are infested with wooly aphids or something.

 

[MasterTracklayer]

Thank you, Forester1; I hope you will pardon me if I take your word for it. The game I best remember seeing the alpha issue in before had white lines around the edges of the game`s trees. This is apparently slightly different, but I think that it is probably from the same cause. I`ve done some programming using the 3D render engine Irrlicht, and I believe that the docs had a warning about this, and a solution, but that solution is probably impossible here.

 

[Dinorius_Redundicus]

We may be able to give better answers if we could look at the internal details of these trees. What are the kuid numbers? Where can the tree assets be obtained from? Are they speedtrees or other types? Otherwise we are just guessing.

 

[reginaldfan1]

Dinorius_Redundicus I don't know if they are speedtrees but I know the kuids.

<kuid2:211025:21042:2> st_rmm_dub15_3912_30m
<kuid2:211025:21084:1> st_rmm_dub20_4870_25m
<kuid2:211025:21088:1> st_rmm_dub24_3370_25m
<kuid2:211025:21353:1> st_rmm_elka36_708_6m
<kuid2:211025:21085:1> st_rmm_dub21_1618_12m
<kuid2:211025:21187:1> st_rmm_kust70_1952_7m
<kuid2:211025:21082:1> st_rmm_dub18_2090_15m
<kuid2:211025:21190:4> st_rmm_kust73_1580_8m
<kuid2:211025:20400:1> st_rmm_kust17-d5_755_15m
<kuid2:211025:21029:2> st_rmm_dub11_1248_15m
<kuid2:523:1328:4> Tree RedDeliciousApple 01
<kuid2:211025:21440:1> st_rmm_kust13ge_892_3m
And those are only some, EVERY tree in the route experiences this problem. If it helps, the route is from Fired Up Trainz' website.

 

[reginaldfan1]

Thank you, Forester1; I hope you will pardon me if I take your word for it. The game I best remember seeing the alpha issue in before had white lines around the edges of the game`s trees. This is apparently slightly different, but I think that it is probably from the same cause. I`ve done some programming using the 3D render engine Irrlicht, and I believe that the docs had a warning about this, and a solution, but that solution is probably impossible here.

You Said PROBABLY, it still might be possible so please tell me the solution.

 

[MasterTracklayer]

Yeah, but the fix isn`t anything anyone but N3V can put in place. It involves using different processing to remove the issue when blending partially-transparent textures into the mix. I do not recall if it is or is not possible to fix the issue by altering the source image, but for anyone who cares to look, that information is in the Irrlicht documentation (to the best of my memory, but I`m pretty sure), although the answer might have to be inferred from what else they say about the issue. It`s been a while since I`ve read the relevant documentation, so the details are a little fuzzy.

 

[Forester1]

Have you contacted Fired Up Trainz? Maybe they have heard of it before and have a solution.

 

[MasterTracklayer]

I haven`t, Forester1; I`ve never heard of them. Who were you asking, anyway?

 

[wreeder]

This thread is getting ridiculous. As per Zec of N3V, the programmers saw a new feature was added to recent versions of the Nvidia drivers. They made changes to the rendering engine to make use of this feature. That is the cause of this issue with some speedtrees made by mostly one creator. They suggested updating drivers as the solution but then discovered that some older cards still show the problem even with the newest drivers. They could fix this by removing the feature they added that is causing the issue with the trees. But they are unlikely to do that and will likely just up the specs for the minimum graphic card that works with TRS22 and Trainz Plus. This has been covered ad nauseam by other threads on the same issue.

 

[Forester1]

@MasterTracklayer, I was asking the OP. He is using the Strasburg route from there.

 

[MasterTracklayer]

Sorry; I couldn`t tell and your post was immediately after mine, so I had to ask. Whatever, I`m OK with it. Thank you for doing me the courtesy of answering.

 

[Forester1]

Yeah, I should have indicated. My bad, actually.

 

[reginaldfan1]

I have updated to the newest driver. Soo...Only N3V Games can fix this problem and I simply have to deal with it. I am fine with that, just asking.

 

[MasterTracklayer]

From what I`ve read, that seems about par for the course.

 

[Dinorius_Redundicus]

Dinorius_Redundicus I don't know if they are speedtrees but I know the kuids.

<kuid2:211025:21042:2> st_rmm_dub15_3912_30m
<kuid2:211025:21084:1> st_rmm_dub20_4870_25m
<kuid2:211025:21088:1> st_rmm_dub24_3370_25m
<kuid2:211025:21353:1> st_rmm_elka36_708_6m
<kuid2:211025:21085:1> st_rmm_dub21_1618_12m
<kuid2:211025:21187:1> st_rmm_kust70_1952_7m
<kuid2:211025:21082:1> st_rmm_dub18_2090_15m
<kuid2:211025:21190:4> st_rmm_kust73_1580_8m
<kuid2:211025:20400:1> st_rmm_kust17-d5_755_15m
<kuid2:211025:21029:2> st_rmm_dub11_1248_15m
<kuid2:523:1328:4> Tree RedDeliciousApple 01
<kuid2:211025:21440:1> st_rmm_kust13ge_892_3m
And those are only some, EVERY tree in the route experiences this problem. If it helps, the route is from Fired Up Trainz' website.

Thanks for the kuids. In TRS19, they all look fine, so it's a problem only in TRS22. As others have already pointed out, it has to do with changes N3V made in TRS22 so only they can fix it. They are all speedtrees, so not well-suited to manual editing anyway.

 

[wreeder]

Yes, at the moment this only appears in TRS22 SP3 and the latest "stable" build of Trainz Plus. But John (JCitron) has pointed out that a similar issue has appeared in the past in TRS19 but stopped happening when newer builds were released. Oddly, it only happens with LOD level 2 of the trees. My best guess is the issue is related to the version of the speedtree software used to create the trees since other speedtrees seem to be fine and the new feature added by the Trainz programming team which exposed the issue with the trees. Now this issue is very noticeable due to the trees being used on the showcase route KSC 2 TRS22 included in base installs of the program. If the trees were just on the DLS then I guess the advice would just be don't use those trees.