CPU vs OpenGL displ...
 
Share:
Notifications
Clear all

7th December 2023:  added payment option Alipay to purchase Astro Pixel Processor from China, Hong Kong, Macau, Taiwan, Korea, Japan and other countries where Alipay is used.

[Solved] CPU vs OpenGL display differences

15 Posts
4 Users
1 Likes
179 Views
(@mestutters)
Neutron Star
Joined: 6 years ago
Posts: 161
Topic starter  

Hi Mabula,

I don't recall seeing this topic raised previously but I've noticed recently a marked difference in the appearance of the image displayed when switching between the CPU and OpenGL options.

In the past I was in the habit of using the OpenGL but recently this option no longer seems to work less well,  aesthetically and functionally, see the below screen-shots.  Apart from switching the display mode, nothing else was changed between the screen-shots.   

CPU option:  Display looks normal, neat side-bars, image centre justified

Screenshot 2023 09 21 084502

OpenGL option:  Wide side-bars, image looks zoomed in but zoom level not changed

Screenshot 2023 09 21 084643

OpenGL option: Display zoomed out but image is top-left justified and displays only the bottom left corner and no sliders to relocate the image

Screenshot 2023 09 21 084718

 

 

*  Are these differences a 'fault' or a 'feature'?  *   I have no problem using the CPU option but my impression is that OpenGL is 'the way to go', hence I'm raising my observations for comment.

FYI:  I use a Lenovo X1 Carbon 6 laptop which employs Intel UHD Graphics processor. My imaging is done with a CCD camera using long exposures i.e. minutes, and typically I have 200-500 subs per image.  For my purposes, in my opinion, APP performs very well indeed.

Regards

 

Mike


   
ReplyQuote
(@gary-clayton)
Main Sequence Star
Joined: 3 years ago
Posts: 23
 

I am also seeing this behaviour with beta23 on my system, windows 11 using the latest Nvidia drivers with a RTX2060. 


   
ReplyQuote
(@mabula-admin)
Universe Admin
Joined: 7 years ago
Posts: 4120
 

Hi all @mestutters and @gary-clayton,

This is a known issue and is cause by a bad graphical driver installation very likely that causes OpenGL not to work as expected.

2 solutions available of which 1 definitely should work:

1) fix your graphical drivers, install drivers only from the chip maker ! do not use 3rd party drivers like microsoft drivers. Remove the drivers and then install updated drivers from the GPU chip maker.

2) update your existing drivers if they are from the chip maker.

This issue occurs easily with users of Intel UHD graphics were a microsoft graphical driver is causing this, microsoft windows 10 or 11 will automatically install these without you properly informing. Those microsoft drivers really do not provide good OpenGL support. You need to find the UHD Intel driver for your chip, remove the microsoft driver and install the UHD driver and then it should work as expected. We even got reports where users had both the Chip maker driver installed and the microsoft driver at the same time, that will always create issues like this, so you need to double check which graphical drivers are installed and if there are possible driver conflicts.

I have not heard about this issue with NVidia drivers, but the same likely applies. Clean up your system by removing all of the existing graphical drivers and then install the latest drivers from the card manufacturere or Nvidia. Nvidia driver installation has option of clean install which you should use, but still check if there are not microsoft nvidia drivers on your system, if they are, remove them !

On my windows 10 and 11 systems the OpenGL internal and external image viewers work correctly with the image correctly centered in the image viewer window and zooming working very fast and as expected, using NVIDIA GTX1060 and RTX2080 chips.

Mabula


   
ReplyQuote
(@gary-clayton)
Main Sequence Star
Joined: 3 years ago
Posts: 23
 

Hi Mabula, I have tried your above suggestion's and I am still getting this behaviour when using the image viewer in separate window mode, also when drawing the light pollution removal boxes they are drawn a few pixels away from the cursor position, but all works as it should in non separate window mode.


   
ReplyQuote
(@mestutters)
Neutron Star
Joined: 6 years ago
Posts: 161
Topic starter  

Hi Mabula,

As best as I can tell I am on the latest Intel driver for Win 11, Kaby Lake processor.  I've updated from a slightly earlier version but I see no change in the reported behaviour.

 

Mike

 

Screenshot 2023 09 27 202925

   
ReplyQuote
(@mabula-admin)
Universe Admin
Joined: 7 years ago
Posts: 4120
 

Hi @gary-clayton and @mestutters,

Okay, did you thoroughly check for dirver conflicts? Maybe multiple graphical drivers are in fact installed and this can cause this problem, we had reports like this multiple times in the last 2-3 years and each time if was resolved by completely removing all graphical drivers and then re-installing only 1 correct graphical driver. If this not solves it we need to dig deeper for sure. One thing to check which might be playing a role here is the desktop scaling, are you using desktop scaling and how much % ? Maybe that is causing the issue now. Our OpenGL dependencie had changes in this regard and maybe a bug has crept in which I can not exclude. So please check if things work okay with no desktop scaling or set it to 100% and test.

Mabula


   
ReplyQuote
(@minusman)
Black Hole
Joined: 6 years ago
Posts: 241
 

Hello Mabula, I can confirm the error occurs when scaling values are set greater than 100%. At 100% desktop scaling view is ok. In CPU mode the phenomenon does not occur.
The Linux version of APP does not seem to be affected, at least not on my machine.
I have an Nvidia GTX 1070 installed in the machine with current drivers, if that helps.

With best regards.


   
ReplyQuote
(@gary-clayton)
Main Sequence Star
Joined: 3 years ago
Posts: 23
 

I can also confirm this when using scaling above 100% on windows 11, RTX2060


   
ReplyQuote
(@mabula-admin)
Universe Admin
Joined: 7 years ago
Posts: 4120
 

Hi @gary-clayton @minusman @mestutters,

Okay, i will test with different desktop scaling on all platforms then and i will fix this now with the highest priority. I think the issue is in fact caused by our 3rd party OpenGL library having changed/improved desktop scaling detection. Previously we needed to fix this on our end... I will keep you updated. As soon as I have found the issue and have fixed it I will let you know and I will release a fixed version soon then as well.

Mabula


   
ReplyQuote
(@mabula-admin)
Universe Admin
Joined: 7 years ago
Posts: 4120
 

Hi all,

Indeed, i can confirm that I have the issue as well on Windows and I can fix this quickly 😉

Mabula


   
ReplyQuote
(@mabula-admin)
Universe Admin
Joined: 7 years ago
Posts: 4120
 

Hi @gary-clayton @minusman @mestutters,

I have fixed this, thank you very much for reporting this and please accept my apologies for first thinking it was a driver issue. The issue was indeed caused by our updated OpenGL dependency which now correctly detects any surface scaling on all platforms. We no longer need to add support for desktop scaling from our end.

macOS was not affected here, but this bug was now present on both Linux and Windows. So the next release 2.0.0-beta25 will have a correctly working external OpenGL image viewer in combination with desktop scaling on all platforms again.

Mabula


   
ReplyQuote
(@gary-clayton)
Main Sequence Star
Joined: 3 years ago
Posts: 23
 

Thank you, looking forward to your new version.


   
ReplyQuote
(@mabula-admin)
Universe Admin
Joined: 7 years ago
Posts: 4120
 

Hi @gary-clayton @minusman @mestutters,

Please try 2.0.0-beta25 which has been released with the fix for the OpenGL image viewer 😉

https://www.astropixelprocessor.com/downloads/

Mabula


   
ReplyQuote
(@gary-clayton)
Main Sequence Star
Joined: 3 years ago
Posts: 23
 

Hi Mabula

I can now confirm that the OpenGL issue is now resolved, many thanks.


   
Mabula-Admin reacted
ReplyQuote
(@mabula-admin)
Universe Admin
Joined: 7 years ago
Posts: 4120
 

Posted by: @gary-clayton

Hi Mabula

I can now confirm that the OpenGL issue is now resolved, many thanks.

Hi @gary-clayton, excellent, thanks for the feedback 😉 ! Very happy it is resolved.

 


   
ReplyQuote
Share: