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

Orders not showing correctly in the UI #8661

fmodesto opened this issue Feb 9, 2021 · 4 comments · Fixed by #8669

Orders not showing correctly in the UI #8661

fmodesto opened this issue Feb 9, 2021 · 4 comments · Fixed by #8669


Copy link

@fmodesto fmodesto commented Feb 9, 2021

Version of OpenTTD

1.10.x 1.11.0-beta

Expected result

Options stick in the UI

Actual result

Options are working but not stick in the UI.

Steps to reproduce

Select train / Orders / Full load any cargo, Full load all cargo, No loading

The three types are selectable but doesn't stick in the UI. It prevents using shortcuts to select unselect them.

Copy link

@nielsmh nielsmh commented Feb 9, 2021

I'm not sure what you mean, or what you are doing.
The full load/no loading/force unload are modifiers for existing orders. You need to select one or more orders and then use those buttons to mark the loading/unloading rules for those selected orders. If this didn't work someone else would have reported it a year ago.


This comment was marked as off-topic.

Copy link

@fmodesto fmodesto commented Feb 10, 2021

Sorry I was a bit cryptic. This is a subset of my hotkeys.cfg:

fullload = J
no_load = L

If inside any order I select the station and press J, it toggles between setting "Full load any cargo" or removing it.
But If I press L, it only sets the "No Loading" option, it never removes it.

Furthermore in the UI when selecting "Full Load any Cargo" or pressing key "J" it updates the options below.
But when selecting "No loading" or pressing "L" it doesn't update the options.

I'm using the Windows 64-bit version.

Copy link

@embeddedt embeddedt commented Feb 11, 2021

I'm not sure why @LC-Zorg's comment was marked as off-topic. I understand that it doesn't relate directly to the reported issue, but I have also experienced difficulties with explaining how this window works to newer players. A redesign (even if less major than what was suggested) might not be a bad idea to consider.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

4 participants