Input window render doesn't erase properly
  • vjacobs
    junior Member
    Posts: 3
    Joined: Wed Dec 11, 2019 1:06 pm

    Input window render doesn't erase properly

    by vjacobs » Wed Dec 11, 2019 1:17 pm

    Hi All,

    I'm having an issue where the background of the rendering of the input window doesn't get properly erased. When I zoom out, or move around an input (e.g. TestCard, or Strobo), the zone that should become black starts to flicker. I can reset this by clicking on || ('Show the two views side by side") and then clicking on | ("Use the maximum space for the input view") again. I'm having this with all versions from 3.7.1 until 3.7.5. Screenshot is attached.

    Using:
    - Madmapper 3.7.5
    - Windows 10 Pro on Intel I7
    - Intel UHD 630 (latest drivers)

    Any ideas?
    Best,
    Vincent
    Attachments
    flickr.png
    flickr.png (262.52 KiB) Viewed 2122 times
  • mad-matt
    garageCube team
    Posts: 1478
    Joined: Mon Sep 09, 2013 5:50 pm

    Re: Input window render doesn't erase properly

    by mad-matt » Wed Dec 11, 2019 10:52 pm

    There is no such known issue.
    I would first suggest updating graphics drivers, as usual. It fixes 90% of Windows issues...
    Let us know if it solved.
  • vjacobs
    junior Member
    Posts: 3
    Joined: Wed Dec 11, 2019 1:06 pm

    Re: Input window render doesn't erase properly

    by vjacobs » Fri Dec 13, 2019 9:26 am

    Hi mad-matt,

    The Intel drivers were already the latest version, but it turned out that those drivers were released by Lenovo (I'm working on a Lenovo desktop machine). I completely removed those and installed vanilla Intel drivers and the flickering disappeared. Not sure what went wrong in those Lenovo drivers :?

    Thanks for the support!
    Best
    Vincent
  • mad-matt
    garageCube team
    Posts: 1478
    Joined: Mon Sep 09, 2013 5:50 pm

    Re: Input window render doesn't erase properly

    by mad-matt » Fri Dec 13, 2019 10:42 am

    We did some OpenGL validation and we have found no errors in MadMapper, so that's an issue in the OpenGL driver from Lenovo.
    Great that it's solved and thanks for your feedback!

Who is online

Users browsing this forum: No registered users and 31 guests