Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Stations: using property 1A sometimes shows incorrect railtype ground tile #6222

Closed
DorpsGek opened this issue Jan 26, 2015 · 3 comments
Closed

Comments

@DorpsGek
Copy link

@DorpsGek DorpsGek commented Jan 26, 2015

mart3p opened the ticket and wrote:

I found this problem when a station is built with one particular railtype from NuTracks 2. The railtype is NuTracks' combined monorail/maglev. Other railtypes work as expected.

I have written a test GRF which is attached, along with a zip file with the source NFO and a sprite sheet. The GRF contains 2 stations. Both are coded using property 1A and are identical, except that the second station has bit 1 set (add offset to sprite) for its platform sprite. The register for this offset is always set to 0. In both cases the ground sprite has no flags set.

In the case of station 1 everything works as expected. Station 2 shows incorrect ground sprites when used with NuTracks combined monorail/maglev.

To reproduce:

  1. Load NuTracks 2 (available from online content download).
  2. Set NuTracks parameter "Force narrow gauge tracks" On. This also makes the combined monorail/maglev railtype available.
  3. Load the test grf supplied "Station property 1A test".
  4. Start a new game in 2020.
  5. Select "Maglev/monorail track construction".
  6. Open the station build menu and select "Station property 1A test".
  7. Build Station 1 - it works correctly and shows the correct ground sprite track graphics.
  8. Build Station 2 - it shows the wrong ground sprite track graphics.

At first, I thought this must be a bug in NuTracks, but I can't see what could cause this problem. And as I said, the ground sprites are coded identically. It is only the platform sprite coding that differs, yet it is effecting the ground sprites.

Using:
OpenTTD 1.5.0-beta1 (also occurs in 1.4.4)
NuTracks 2 r247

Attachments

Reported version: 1.5.0-beta1
Operating system: All


This issue was imported from FlySpray: https://bugs.openttd.org/task/6222
@DorpsGek

This comment has been minimized.

Copy link
Author

@DorpsGek DorpsGek commented Mar 8, 2015

frosch wrote:

Test savegame

Attachments


This comment was imported from FlySpray: https://bugs.openttd.org/task/6222#comment13809
@stale

This comment has been minimized.

Copy link

@stale stale bot commented Mar 25, 2019

This issue has been automatically marked as stale because it has not had any activity in the last two months.
If you believe the issue is still relevant, please test on the latest nightly and report back.
It will be closed if no further activity occurs within 7 days.
Thank you for your contributions.

@stale stale bot added the stale label Mar 25, 2019
@LordAro

This comment has been minimized.

Copy link
Member

@LordAro LordAro commented Mar 26, 2019

arbitrary bump

@stale stale bot removed the stale label Mar 26, 2019
kiwitreekor added a commit to kiwitreekor/OpenTTD that referenced this issue Apr 2, 2019
@TrueBrain TrueBrain added the pinned label Apr 2, 2019
@PeterN PeterN closed this in bc9b47d Apr 8, 2019
PeterN added a commit to PeterN/OpenTTD that referenced this issue Apr 8, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
5 participants
You can’t perform that action at this time.