You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Have you checked that no other similar issue already exists?
I have searched and not found similar issues.
A clear and concise description of what the bug is.
Not sure who designed the status bar in backend console (e.g. [=========.....] , but that is acting quite weird and it is very annoying for systems that have hypervisor console enabled in the kernel (using SBI), logs are just getting lost (info, errors) and redirecting the output doesn't help. Trying to do stty columns 170 rows 25 doesn't help.
Is there a way to disable that status bar in backend console? I searched around and there were no concrete answers
Steps to reproduce the behaviour.
Explain how to reproduce
enable hvc0 console in kernel (console=hvc0)
Enable console on stdin in QEMU
Run GZDoom 4.12.3
Your configuration
No response
Provide a Log
No response
The text was updated successfully, but these errors were encountered:
GZDoom version
4.12.3
Which game are you running with GZDoom?
Doom
What Operating System are you using?
Other
Please describe your specific OS version
Yocto OE 4.3.2
Relevant hardware info
RISCV QEMU emulation
Have you checked that no other similar issue already exists?
A clear and concise description of what the bug is.
Not sure who designed the status bar in backend console (e.g. [=========.....] , but that is acting quite weird and it is very annoying for systems that have hypervisor console enabled in the kernel (using SBI), logs are just getting lost (info, errors) and redirecting the output doesn't help. Trying to do stty columns 170 rows 25 doesn't help.
Is there a way to disable that status bar in backend console? I searched around and there were no concrete answers
Steps to reproduce the behaviour.
Explain how to reproduce
Your configuration
No response
Provide a Log
No response
The text was updated successfully, but these errors were encountered: