atmel studio graphics bug - Page 1
Forum section: electronics / general

author: vidicon
author_rank: Newbie
timestamp: June 11, 2017, 10:10:15 pm
content: I have a graphics bug with Atmel Studio 7. I have been unable to find a solution for it. Atmel Studio seems to work as expected with except to this graphics bug. Please look at the image to see the bug.i have read some time ago that it has something to do with visual studio 2015 (with I have installed on my PC)

author: ataradov
author_rank: Super Contributor
timestamp: June 12, 2017, 01:17:59 am
content: Problems like this are generally related to bad GPU drivers or broken GPU memory.So you may consider updating those first.

author: BrianHG
author_rank: Super Contributor
timestamp: June 12, 2017, 02:42:27 am
content: That doesn't look like a graphics library problem, more like a GUI bug, of software bug, especially if all your other software applications don't exhibit the same behavior.Try re-installing Atmel Studio from scratch.Note that in Microchip's MPLab, I once created a similar situation when my PicKit3 froze during programming due to cables dislodging just at the wrong time during a firmware update. (This was a 1 time fluke and requires a system shutdown to fix...)

author: Naguissa
author_rank: Regular Contributor
timestamp: June 12, 2017, 06:55:22 am
content: As said by Brian, seems to be a library problem. A hardware problem will show screen corruption instead a missing graphical element.Try reinstalling whole IDE. If it breaks Visual Studio or bug continues you will need to avoid having both installed in same OS, using VMs or similar.

author: ataradov
author_rank: Super Contributor
timestamp: June 12, 2017, 06:59:56 am
content: Quote from: Naguissa on June 12, 2017, 06:55:22 amWhat library?This is 99% graphics card related. Drivers or hardware - hard to tell.AS uses hardware acceleration, and in this case, it clearly uses wring "textures" for elements.Try to disable hardware acceleration in Windows settings (I don't remember where exactly, but it should be googlable).

author: vidicon
author_rank: Newbie
timestamp: June 12, 2017, 07:48:34 am
content: I have reinstalled AS7. My graphics drivers are up to date and I don't think that is the problem as I have had this problem for a very long time (multiple driver updates and I have reinstalled windows since then). also, I have never seen anything like this on any other program. I Have considered using a VM but it's not preferable.I can't remove visual studio at this time (As a student embedded software I need it till the end of this semester).

author: Mechatrommer
author_rank: Super Contributor
timestamp: June 12, 2017, 10:44:19 am
content: library problem (built-in high level functions in the ide and distributed run time dll or environment) that cannot handle all hardware variations or incompatible version of runtime environment etc etc. developers wont publish the ide/library if they saw this bug on their screen, the fact that they didnt. so their hardware is capable, the OP's is not. the developer havent take into account the OP's hardware. thats it. the common route is... report to developer, if they have the time and resources, and they see deem necessary for the sake of the profit... they will take care of it.

author: newbrain
author_rank: Super Contributor
timestamp: June 12, 2017, 10:47:08 am
content: Quote from: ataradov on June 12, 2017, 06:59:56 amBefore doing that, maybe just try to disable graphic acceleration in AS itself, see the attached capture.I had no such problem, with AMD and intel graphics and various version of VS installed (2015+2017) at the same time as AS.

author: vidicon
author_rank: Newbie
timestamp: June 12, 2017, 04:28:45 pm
content: Quote from: newbrain on June 12, 2017, 10:47:08 amThis Seems to have solved the problem.(still have to test it with charger. I'm now in a train using my battery so will have to see if plugging in the charger at home changes something like hardware acceleration )Thank you very much