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

Press F1 for Help on Accessibility screen in Setup doesn't work #1144

Open
dftf-stu opened this issue Jan 23, 2024 · 3 comments
Open

Press F1 for Help on Accessibility screen in Setup doesn't work #1144

dftf-stu opened this issue Jan 23, 2024 · 3 comments

Comments

@dftf-stu
Copy link

Background

Crispy Doom: 6.0.0 (31 Mar 2023)
Operating System: Windows 10 Home (x64) 22H2 Build 19045.3930
Game: DOOM / DOOMII / Master Levels / Plutonia / TNT / Freedoom Phase 1 / Freedoom Phase 2 (etc.)

Bug description

Observed behavior:

I wanted to see if there was an option in the "Accessibility" section to make levels be constantly fully-lit ("full-bright", I think is the DOOM term -- though the GameBoy Advance ports referred to this as "static lighting"), as on some devices (especially those with OLED screens) I am finding some darker-areas almost-impossible to see.

My only current workaround is to type IDBEHOLDL, but this only last for two-minutes, so this isn't ideal.

I went into Crispy DOOM Setup, then to Accessibility, but I'm not-sure what all of the options do.

CDA1

I pressed F1 to go to a help-page, but it takes me to a page that doesn't exist:

CDA2

Expected behavior:

That when pressing F1, it would take me to a page that explains what each option does.

To have an accessibility-option that would do as I suggested, so I don't have to repeatedly type IDBEHOLDL every two-minutes

@kitchen-ace
Copy link
Collaborator

Definitely a bug to not have those help screens up. In the meantime turn up Extra Lighting to 8, to have (nearly) full brightness.

@fabiangreffrath
Copy link
Owner

We rely on Chocolate Doom's online help for the different pages in the setup tool, but Chocolate Setup of course doesn't have an Accessibility page.

@dftf-stu
Copy link
Author

@fabiangreffrath: could you not perhaps host the page for that on here?

For example: create a ticket on here which explains the options, then close it, and then link to that page in Crispy? Or are you saying the URLs are not something you can change (i.e. they are hard-coded into the bits of code you take from Chocolate)?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants