Forum Discussion
13 Replies
- RichardT_altera
Super Contributor
Which Quartus version and Operating System (OS) are you using?
Please try to use the latest Quartus version with supported OS to check if the issue persists.
Operating System (OS) Support:
Regards,
Richard Tan
- chalieRobert
New Contributor
Quartus 24.1
OS Windows 11
- chalieRobert
New Contributor
Quartus 24.3
OS Windows 11
- FvM
Super Contributor
I can confirm, that I see the same corrupted cursor bitmap in quartus_stpw 24.1std.0 Build 1077 when moving ther cursor over waveform zone, where a magnifier glass with crosshair should be displayed. I see the bug on different computers, OS is Windows 10 Pro respectively Enterprise, most recent Build 19045.
I see the same problem with 24.2 Pro, 24.3 Pro and 25.1 Pro Signaltap but not with pre 24 versions, e.g. 23.1std. Display resolution is 1920x1080. The problem doesn't occur when forcing VGA resolution by connecting a different Monitor. - RichardT_altera
Super Contributor
Hi @FvM,
That's an interesting finding.
Seem like this might related to the display resolution setting.
Could you help to share the display information or any details for the pass and fail (1920x1080) case?
I found this information under the Advanced display. Perhaps it might offer more detailed insights?Hi @chalieRobert ,
Could you try the solution provided by FvM and check if the cursor issue resolved?
Regards,
Richard Tan
- RichardT_altera
Super Contributor
- FvM
Super Contributor
I believe an open question to original poster is which display resolution was set when the problem occurred. Depending on the computer configuration, setting a different resolution isn't necessarily an option, except for debugging purposes.
In any case, there's obviously a bug, or at least a problem with Windows display functions. Software guys can do their work.
I probably have the option next week to check different display resolutions with an external 4K monitor.- FvM
Super Contributor
Hi,
I did a test with external display attached to HP ZBook G10. The problem shows slightly different now. I see corrupted cursor bitmap in Signaltap waveform display area only on internal display but not on external display, independent of resolution settings.Below a photo of corrupted cursor, there should be a magnifier glass with cross hair.
ā
- RichardT_altera
Super Contributor
Thank you @FvM for the information.
Do you have any details or specification on the internal screen and external monitor, for better comparison?
So I can share these information to the tool specialist.
Regards,
Richard Tan
- FvM
Super Contributor
Grapics adapter is NVIDIA Quadro K610M (ZBook G2) respectively NVIDIA RTX 2000 (ZBook G10), with internal Display 1920 x 1080, 32 Bit/Pixel.
External Display HP E27m G4 QHD, 2560 x 1440Regards
Frank - RichardT_altera
Super Contributor
Thank you for the information. I have filed a case to the tool specialist to investigate on this.
I also noticed that the cursor changes in the Technology Map Viewer and RTL Viewer after I right-click and select "Goto Top Level".
(This was observed in Quartus version 24.1std.0.)
When connected to an external monitor and switching display modes using Ctrl + Win + P, the issue occurs under the following conditions:
PC screen only, Duplicate, and Extend modes ā only when the GUI window is dragged to the internal display.
The cursor disappears in Second screen only and Extend modes ā only when the GUI window is dragged to the external display.
Regards,
Richard Tan
- RichardT_altera
Super Contributor
I think it is the zoom in/ zoom out cursor that is the problematic. I already found this corrupted cursor in 3 GUI windows (technology map viewer/ signal tap/ chip planner) window, whenever you try to zoom in the respectively GUI window, the zoom in cursor is not displayed properly (issue only occur in internal display).
As of now, try to workaround by connecting to an external display.
Regards,
Richard Tan
- FvM
Super Contributor
Thanks for confirming the bug. As reported above, it can be seen in all Quartus std and pro versions starting with 24.1 Hope that it will be fixed in new releases.