Graphics problem

[GSkid]

I made a Youtube video showing it in action on Stevens Pass....

Stevens Pass Signal Glitch in TS2015

http://youtu.be/VHelbKHnnss


Notice the black squares there and as the mountains slowly go behind it instead of sky, the black squares start to slowly disappear exactly in sync with the mountains passing behind it? But when it's nothing but sky, it becomes nothing but a black square behind it?

Also....I said clone the scenario so you don't mess with the original scenario. A guinea pig scenario so to speak for testing.

[plethaus]

Forget it, he's convinced there's something wrong with our computers.

[GSkid]

Forget it, he's convinced there's something wrong with our computers.

The saying goes "You can lead a horse to water, but you can't make him drink."

[Ericmopar]

Do you have Stevens Pass, Ericmopar?

No. Didn't realize early on that was the route with the particular signals.

I don't think it's the assets in question, because they were fine before the update.
It's like I was saying before, there are small errors all over the place, related to the core game change.
I swapped over my 2014 core files, and everything is fine afterwards, minus 3D weather and the new menus etc, of course.
This isn't applying directly to the Stevens Pass signals in my case as I don't own it, but all the other little bugs in my DLC go away. Like the headlight bug in the SD75 and the new bug in the DDA40X dynamic brakes when using the F4 HUD.
It's things in the core program.

BTW. I don't blame the PC's themselves in this, but I was wondering in my earlier post, if differences in hardware, explained the differences in experienced glitches in graphics.
I was talking about this with a serious gamer at Fry's tonight. He said they all had different bugs with the exact same mods in the same games. (amongst friends) That the only difference was the hardware used between players.
He went on about data pipes etc all being different.

[DrewG]

I decided to take a look at this and I've only been able to replicate this with the signals made by gtrax used on Stevens pass and the RWA. I tried with the signals from Marias pass, portland terminal, pacific Surfliner and rcap, none of which showed this error. I'm guessing it has something to do with how Rick made the signals.

[arizonachris]

Neat. 5 pages of "no it doesn't" "yes, it does" "I see it" "I don't".

So I take it that this problem shows up when you edit an existing TS2014 route with a new feature designed for TS2015? (or does this 3D turn on by itself on some routes?) And after editing these routes you find an anomaly? And you want DTG to fix this anomaly, which doesn't occur when the route isn't edited? I also seem to remember a similar thing happening when TSX was introduced, everyone fussing when it couldn't be applied to legacy "stuff". (or with mixed results)

I dunno, y'all, but maybe this 3D weather just isn't gonna work with some routes, and wasn't designed to do that anyways. I'm not gonna edit my stuff to find out. I'll leave all the tinkering and associated moaning/ griping/ comparing/ analyzing/ to you all.

I enjoy Railworks as is and TS2015 seems to run just fine. (didn't say perfect, mind you) Lucky I guess.

[Ericmopar]

Neat. 5 pages of "no it doesn't" "yes, it does" "I see it" "I don't".

So I take it that this problem shows up when you edit an existing TS2014 route with a new feature designed for TS2015? (or does this 3D turn on by itself on some routes?) And after editing these routes you find an anomaly? And you want DTG to fix this anomaly, which doesn't occur when the route isn't edited? I also seem to remember a similar thing happening when TSX was introduced, everyone fussing when it couldn't be applied to legacy "stuff". (or with mixed results)

I dunno, y'all, but maybe this 3D weather just isn't gonna work with some routes, and wasn't designed to do that anyways. I'm not gonna edit my stuff to find out. I'll leave all the tinkering and associated moaning/ griping/ comparing/ analyzing/ to you all.

I enjoy Railworks as is and TS2015 seems to run just fine. (didn't say perfect, mind you) Lucky I guess.

They seem to be using the 3D weather for quick drive.
I'm seeing this in the RW&A, but only with the 3D weather enabled.

[buzz456]

Well said Chris.

[artimrj]

No it is 3 textures. One red, one green and one yellow that are causing the problem. I said this for the 3rd time now. They only do this in 3D weather. No editing of the route required. You just have to choose a 3D weather. If you do not like our analyzing, read another thread. This is how many bugs have been fixed over the years, by us. Now your going to complain when we do it? Your kidding right?

[plethaus]

No it is 3 textures. One red, one green and one yellow that are causing the problem. I said this for the 3rd time now. They only do this in 3D weather. No editing of the route required. You just have to choose a 3D weather. If you do not like our analyzing, read another thread. This is how many bugs have been fixed over the years, by us. Now your going to complain when we do it? Your kidding right?

Thank you!

Also the headlight sprite on the BN/BNSF SD40-2 has the bug also, there may be other items with issues but I haven't had time to go through them and test them all.

[buzz456]

I plan to just not use the 3D sky in these situations. To call it a bug is a bit questionable to me. Since it didn't appear until 3D let's call the bug if there is one in 3D Sky since that is what causes the problem.

And let's all agree that we can disagree without being disagreeable.

[robbit]

Seeing how this is a 3d weather issue thread I guess I will chime in and tell you that the GP20 also has an issue with the 3d weather. If you use the 3d weather and you are driving in the cab of the gp20 the sky is black, but all is good from outside the cab.

[wackyhuman]

> the GP20 also has an issue with the 3d weather

The ICE-T used to have it too, but DTG found that one before releasing it. There is a wide range of items that have these issues as discussed (big word for this thread). DTG is aware of the issue, but since it requires adjusting transparency on objects, like signals, engines and other items that use the same method of building the graphics, it will not be a quick fix for now. And as with every issue, not everybody sees it, which is fine and which does not require more of the same messages we already seen in this forum

Unless you have a useful thing to add to the discussion, it is time to end this discussion

[buzz456]

Frank,
I think that adding information like the GP20 is worthwhile. If I loaded it up to use and the sky was black, looking to the 3D would not be my first reaction so knowing that makes it easier to get a satisfactory outcome.

[artimrj]

Editing the textures did nothing. So it may have something to do with the geo file or even the bin, but that part is beyond me. I did all the trouble shooting I know how to do. So we don't use 3D weather on the Lakeside or LSW extension or Stevens Pass and 2 engines so far. The textures and the sky are not compatible. I can remember this happening in some MSTS routes about 100 years ago.