Bug #2180
Task bar shows only partially (Intel Mobility)
0%
Description
Build 2109 (and earlier)
When I press ESC to see the task bar on the home screen only the left portion of it appears - the command line (1.jpg). When I click on the right bottom corner the menu appears (2.jpg)
Related issues
History
#1 Updated by Drako almost 8 years ago
Please see the attached images with descriptions.
The in-game behavior is new in build #2152, in the following way. After pressing shift-esc now almost everything is black, in previous builds I saw the last frame before pressing shift-esc.
#2 Updated by skyjake almost 8 years ago
- Tags changed from UI to UI, OpenGL
#3 Updated by skyjake almost 8 years ago
- Related to Feature #2116: Compatibility with limited FBO functionality (old OpenGL drivers) added
#4 Updated by Drako almost 8 years ago
Isn't the fix made in Revision 02236bd3 ("fade to black in home UI") also related to this issue. It has not been fixed in the builds 2229/2230 (the behavior is the same as described above).
#5 Updated by skyjake almost 8 years ago
I'm curious if build 2241 will affect this issue. It introduces significant optimizations for UI drawing, although the changes are quite low-level.
#6 Updated by Drako almost 8 years ago
- File 7.jpg 7.jpg added
- File 8.jpg 8.jpg added
- File 9.jpg 9.jpg added
- File 10.jpg 10.jpg added
- File 12.jpg 12.jpg added
Now it is better, but still not the way it should be. First shift+esc works as it should, I can see all the icon and menus. Then I change "show fps" - please see images 7-10 and 12. I ended up in the situation where only the lower strip was refreshed (clicking on icons on the lower strip did not result in showing menus)
#7 Updated by Drako over 7 years ago
It seems that all those problems occur only in a full screen mode.
#8 Updated by Drako over 7 years ago
- File 13.jpg 13.jpg added
- File 14.jpg 14.jpg added
- File 15.jpg 15.jpg added
- File 16.jpg 16.jpg added
- File 17.jpg 17.jpg added
- File 18.jpg 18.jpg added
Build #2259 (possibly also some earlier ones but not older than 2244.
All the problems also appear now in the windowed modes.
After running doomsday and pressing esc 3 times I get 13.jpg.
After entering a command generating a log entry I get 14.jpg.
After pressing the icon in the bottom on the right - to the left of version number (15.jpg), the whole menu shows up correctly but immediately after it appears in full I get 16.jpg. [BTW the version number is incorrect, it is 2.1, it should be 2.0 - see 15.jpg]
After pressing in the text "Enter command here" I get 17.jpg . I think that the whole screen appears only because the log entry is displayed.
After pressing anywhere on the screen I get 18.jpg.
All of that happens on windows x64 and an old Intel Mobility laptop graphic card supporting only OpenGL 2.1.
#9 Updated by skyjake over 7 years ago
Drako wrote:
BTW the version number is incorrect, it is 2.1, it should be 2.0 - see 15.jpg
The unstable builds have switched to 2.1 now that 2.0 is frozen for release: http://dengine.net/blog/2017/03/doomsday-2-0-rc1/
I added a new UI option for the next unstable build. You can now disable the background blur effects, in case it's those that are messing up the rendering. Try disabling "Background Translucency" in UI Settings and then restart Doomsday.
#10 Updated by skyjake over 7 years ago
- Subject changed from Task bar shows only partially. to Task bar shows only partially (Intel Mobility)
#11 Updated by Drako over 7 years ago
Unfortunately, I cannot test that option because immediately after I click the settings icon the screen goes black. Please watch the video to see what happens: https://youtu.be/wZvoz6Nclh0 .
Is there a command to disable "Background Translucency" ?
#12 Updated by skyjake over 7 years ago
In the currently available build, does it help if you run in windowed mode?
There is a way to toggle the option via the Doomsday command prompt:- Right-click the [>] button to switch the prompt to Script mode (it changes to say [$]).
- Enter the command:
Config.ui.translucency=False
- Right-click the [$] button to return to regular console mode.
- Restart.
#13 Updated by Drako over 7 years ago
Config.ui.translucency=False does not work in build #2265. The same happens as in the video attached above. Both, in the full screen-mode and in the windowed mode.
#14 Updated by Drako over 7 years ago
build 2250 behaves differently than 2265 (win x64).
Namely, the first run (when the "runtime" directory is not present) allows to see the menu in home UI - see https://youtu.be/HzS5Kr0gDLA
While the second run behaves like build #2265, that is the screen goes black (except the command line) after clicking the menu icon - see https://youtu.be/zoUr7AZskxQ
build 2253 behaves like 2250
build 2254 behaves like 2265
#15 Updated by Drako over 7 years ago
build 2268 behaves like 2265
#16 Updated by skyjake over 7 years ago
- Target version set to Rendering