Screen Refresh errors using Minecraft and CodeBuilder

Tom Griffiths

• April 11, 2024 16:31
• Report a Concern

We are using devices with Windows 10 Education 22H2 and Windows 11 Education 22H2 installed (64-bit).

Since upgrading to MinecraftEE v1.20.1305, we have found CodeBuilder to be buggy in the respect that it will not perform screen updates correctly (click a button and nothing appears on screen, but it has loaded - just isn't displayed).

The window will refresh (and the content appears) if the focus is swapped to another app / the game window and then swapped back again, or if a modal dialog box is presented (i.e. an error message with an OK button)

More interestingly, we had a staff machine with a duplicated screen output to Projector and the Monitor - the projector image updated and the monitor screen didn't.

Is there a quirk in the way that CodeBuilder performs screen updates?

This problem is present on devices with single and multi-monitor setups, there is also different hardware (Ryzen and Intel platforms), so I wouldn't immediately say it was a graphics driver issue.

All thoughts gratefully received!

0

• 

  Caleb

  • April 11, 2024 21:38

  Hey Tom, 
  I'm Caleb with the Minecraft Education Support team. Happy to help! 
  
  We have seen similar issues in the past when users are screen sharing and using Intergrated Graphics. I do see Veyon installed. Would it be possible to disable this on a system temporarily and see if that mitigates the issue? 
  
  Also, do these machines have Dedicated Graphics? If so, can we confirm under Windows Settings > Display > Graphics that Minecraft Education is set to use the High-Performance card? 
  Would you also be able to provide a screenshot of DxDiag (without giving out any personal information)? 

  Let us know if you have any additional questions, or concerns!

  Thanks,

   

  0
• 

  Tom Griffiths

  • April 15, 2024 13:46
  • Report a Concern

  Hi Caleb,

  Being USFF machines, they all have integrated graphics.

  I have removed Veyon and the problem has resolved - I'm also pleased to say that re-installing with the latest version (4.8.3.0 at the time of writing) does not re-introduce the issue.

  Many thanks,

  Tom.

  0
• 

  Caleb

  • April 15, 2024 22:39

  Awesome to hear you got that sorted! 
  
  Let us know if the issue returns. I'll keep this in my arsenal for future Veyon users

  0

Please sign in to leave a comment.