Author Topic: Black GUI when going into full screen mode (1.8.6.1457)  (Read 866 times)

Offline KBALLZZ

  • Newcomer
  • Posts: 5
Black GUI when going into full screen mode (1.8.6.1457)
« on: 2019 February 03 15:11:01 »
I made a similar post last month and could not figure out why PI was opening to a black GUI. After reinstalling the latest version to give 1.8.6 a try again, I figured out what was causing the issue. My PI was opening in full screen by default for whatever reason. Now I have memorized the keyboard shortcut for fullscreen to counter this issue but I thought I would bring it to your attention.

As you can see in the linked video, when clicking Full Screen, the GUI goes black but I can still see tooltips. If you happen to come around a fix or trick for me to try, it would be much appreciated, as fullscreen mode is useful for my laptop.

https://drive.google.com/open?id=1z8CUYjtU0_dxP6Jj-dC0Z3xqJY_JysvI

Graphics driver and computer recently updated.

Windows 7 Home Premium Service Pack 1
GeForce 610M
Intel Core i7-2670QM CPU @ 2.20GHz
8gb RAM

PI version 1.8.6.1457

Offline Juan Conejero

  • PTeam Member
  • PixInsight Jedi Grand Master
  • ********
  • Posts: 7111
    • http://pixinsight.com/
Re: Black GUI when going into full screen mode (1.8.6.1457)
« Reply #1 on: 2019 February 04 03:30:29 »
This cannot be reproduced under normal working conditions, on any of our working and testing machines, on any supported platform.

This is a machine-specific issue, probably caused by faulty graphics drivers. Unfortunately, many device drivers cannot be updated to valid versions anymore on Windows 7 because of lack of vendor support. Also note that Windows 7 is not one of our mainstream supported platforms for current versions of PixInsight (actually, this happened also with the previous 1.8.5 version).
Juan Conejero
PixInsight Development Team
http://pixinsight.com/

Offline KBALLZZ

  • Newcomer
  • Posts: 5
Re: Black GUI when going into full screen mode (1.8.6.1457)
« Reply #2 on: 2019 May 21 16:24:04 »
The issue has been fixed with your latest update. Thank you!