Jump to content

glulab

Member
  • Posts

    14
  • Joined

  • Last visited

Posts posted by glulab

  1. This "error" is actually just a warning message, and it occurs here because the virtual display thinks it "sees" the 3d object, which is using the same virtual display as texture.

     

    One way to make sure you don't get this message is to place the 3d object, and the displays (3d projectors) looking at it, on a separate stage tier.

     

    Hope this helps.

    Hi tried this but still have same error message

     

    any other options?

     

    thanks

  2. ops! Sorry it seemed to be an old thread.

     

    There is any particular reason to don't move on DirectX 12? it seems that Microsoft is focused on DirectX 12. Other big software in the market moved to win 10 and, after a while, they work flawlessly.

     

    Thank you for your time.

  3. Hi All,

     

    Do you have some news related testing WO6 on WIN10?

     

    I'm testing a WIN10 1607.14393.0 computer display equipped with fire pro with 6 out. What can I see here is that sometimes the WO display crashes but I can't understand what trigger it, sometimes seems to be related to network communication but it's a sporadic behaviour.

     

    Does Dataton has some experience to share with us?

     

    Cheers

  4. The issue is a bug in Windows 10 multi-ouptut DirectX 3D full screen rendering.

    WATCHOUT can not overcome the flaw in Windows 10.

    Microsoft has acknowledged this bug is confirmed and will be fixing it in the future.

    As to when that future is going to happen, your guess is as good as ours.

     

    As is often the case with Microsoft's operating systems,

    it is not until the first major revision that they get it right.

    Exact same thing happened in Windows 8, which is not compatible with WATCHOUT either.

    They cleaned up the problems in Windows 8.1, which can be made to work with WATCHOUT.

    Although Windows 7 is still preferable.

    Windows 8.1 has no improvement from a WATCHOUT perspective,

    and has plenty of additional things you do not want and must tune out.

     

    Thank you for your fast reply!

     

    If I understood we should wait the "Windows 10 anniversary update" that should came up at the end of June / beginning of July.. I will keep my fingers crossed.

     

    Tnx

  5. Hi,

     

    are you using their recommended STP Cat5e cable and a separate power supply per extender?

     

    From Kramer website:

     

    Cable

    -

    Requires STP (shielded twisted pair) cable. For optimum range and performance, use Kramer's BC−DGKat524, BC−DGKat623 or BC−DGKat7a23 cables.

    Note that the transmission range depends on the signal resolution, graphics card and display used.

    The distance using non−Kramer CAT 5, CAT 6, and CAT 7 cables may not reach these ranges.

     

    /jonas

     

    Hi Jonas,

    I actually used a CAT6 cable and not CAT5 kramer cable. I used a power supply, but only on the transmitter (the receiver don't have a power supply).

    Now i have solved with video Cables To Go TruLink 89037 - 1 x 1 - UXGA - 50 m (http://www.dgstore.it/connettoreprolunga-video-cables-trulink-89037-uxga-p-334955.html?cPath=0_90160_10769) it's cheaper and transport the signal with 2 different CAT5, 1 for the DCC and another one for the video.

     

    thank for your suggestion

     

    Emanuele

  6. hi,

    i have an watchout display on windows 7, when it start it run an minimize window mode. I have other 6 display identicals on win 7 with the same mainboards graphic cards etc.. but only one display minimize the windows on startup. I have tried to format and reinstall windows (and watchout 4.3) but the problem remain. Somebody have a solution? the same problem?

     

    best regard

    emanuele foti

×
×
  • Create New...