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

[Bug] Scanner room has incorrect usage cycle #2537

Open
lewri opened this issue Mar 24, 2024 · 0 comments
Open

[Bug] Scanner room has incorrect usage cycle #2537

lewri opened this issue Mar 24, 2024 · 0 comments
Labels
bug issue type

Comments

@lewri
Copy link
Member

lewri commented Mar 24, 2024

Describe the issue

In CorsixTH when a patient uses the scanner we follow the current incorrect pattern:

  1. Patient enters and undresses
  2. Doctor goes to stand by the console
  3. Patient enters the scanner, doctor sits down
  4. Scanner loop fires 1x
  5. Scanner operates before doctor operates console, sometimes finishing operations after the scanner cycle ends.
  6. Patient leaves, doctor gets up.

Steps to Reproduce

Have a patient use the scanner room.

Expected Behaviour

In TH, the Scanner machine goes through roughly three usage cycles in the following order:

  1. Patient enters, gets undressed
  2. Doctor sits down at console and waits for patient to enter scanner
  3. Doctor presses buttons, scanner operates. For a standing up operation, this is 3 times. [If the scanner leans back, it's slightly different, but scanner still waits for doctor input]
  4. Patient leaves scanner. Doctor leaves console.

Save Game

Save game attached to report: No

CorsixTH Version

0.67

Operating System

Windows 10

Theme Hospital Version

GOG.com

Gamelog.txt

No response

Additional Information

This is noted too in the scanner.lua file

--[[This is incomplete as the scanner and console should be in sync with each other
 i.e. Dr sits down and pushes some buttons and the scanner scans, the he pushes the lever and it
 will tip back etc.]]
@lewri lewri added the bug issue type label Mar 24, 2024
@lewri lewri linked a pull request Mar 30, 2024 that will close this issue
@lewri lewri removed a link to a pull request Mar 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug issue type
Projects
None yet
Development

No branches or pull requests

1 participant