[Resolution error]

1 hour ago, jfk said:

This is typically caused by a hardware shortcoming in the connection from the graphics card output to the display. 

I might add the most common cause that I have encountered for this issue is any adaptation away from DisplayPort. i.e. a DisplayPort to HDMI adaptor not capable of 4K resolution. Note, there are two kinds of DisplayPort to HDMI adaptors - active and passive.

A passive adaptor relies on the graphics card supporting a compatibility mode where the card internally switches from DisplayPort signal types to legacy HDMI signal types. This type of capability is often referred to as DisplayPort ++. The legacy compatibility mode often offers less possible resolutions when compared to native DisplayPort signals. So the graphics card recognizes the HDMI adaptation and switches to output legacy HDMI signals. Many graphics cards are unable to output 4K in the legacy compatibility mode required by passive adaptors.

An active adaptor on the other hand operates the graphics card in native DisplayPort mode. i.e. the graphics card only outputs native DisplayPort signals. An active adaptor isolates the graphics card from the adaptation, the card only sees native DisplayPort connection. The active adaptor then converts native DisplayPort to legacy signal types required by HDMI. Native DisplayPort often provides a much wider range of output resolutions when compared to legacy mode. And that is not just 4K. I once encountered this issue with an HDMI display operating at 1400x1050. This could not be accomplished with a passive adaptor, only with an active adaptor.

So if you are converting to HDMI, you may require an active adaptor rated at 4k60p to correct this error. 

Note, active and passive adaptors often look the same and active adaptors are only slightly more expensive, often as little as $5-$10 more. 

Is there a particular adapter you recommend?

[Windows 10 Tweaking Guide]

4 hours ago, MatzeLe said:

So, in the Watchpax 62 manual, you can see that they use driver version 473.47 for the rtx a4000. Thanks for telling us. Have you experience with higher version numbers? Since this is the first DCH driver version from Nvidia, it seems that they use a Windows 10 version after or from 2018 (maybe Win10Enterprise (iot) 2019 or newer), so these hints with versions earlier than this leads to nothing.

Im doing some googling and Windows IOT Enterprise is the same as Windows Enterprise. So Im assuming running latest Enterprise LTSC would be the best bet?

[Black Screen during show]

On 2/4/2023 at 8:46 AM, Kalpesh Suthar said:

Hello, I was at show in Exibation, I have to share the issue this is very important, still I don't found why that happen, The issue was no content playing in screen and its black, I have attach link for video for reference , Watchout dose not have any error msg no from Watchout production, I have tried everything downgrade software,  everything was working condition, suddenly get this issue 

 

https://drive.google.com/file/d/1NjXAxAm5V0J2KOEmKqC6npfLvmBK1vWj/view?usp=sharing

Turn off your production firewall and see if that helps. You should have no firewalls running on any machine. Iv had this issue before and it was my firewall.

[Windows 10 Tweaking Guide]

9 hours ago, MatzeLe said:

Ah I see, the RTX A4000 is used in Watchpax 62. So can you provide Informations about the driver version used? Maybe there is the Win10 IOT version used in Watchpax, can you confirm this? 

Im actually curious what they use. I have a few older watchpax units and I think they were Windows embedded

[HAP import/playback errors on Win10 Production Laptop]

Side note did you have quicktime installed?

I had an issue with hap playing back on my win 10 production and the issue was quicktime was not installed

[Windows 10 Tweaking Guide]

On 10/20/2021 at 2:13 AM, Diego Marchente said:

After several months of testing, solutions and analysis of both versions and operating systems, we came to the unpleasant conclusion that Watchout with LTSB or with LTSC, with or without DCH driver, with an i9 processor and WX9100 graphics cards (but in some cases also WX7100) do not work. They generate calculation errors and there are continuous tripping even in offline, terrible management with resolutions beyond 1080p and the impossibility of using custom resolutions or with different resolutions on multiple screens. I would say it would be interesting to understand why they can't work together. With a clone system but with an i7 processor all this does not happen.

I went through this whole fiasco with our test systems. I believe it all to be a driver issue. Using the latest amd drivers for the wx9100 fixed the issue, but you cant use the new drivers for reliable playback. Only thing I got to reliably work is windows 7. I suspect support for AMD is dead in the water and dataton hasnt addressed any of the issues.

So we are faced with the an issue now. The only thing we can reliably use  are nvidia quadro cards. Any new AMD card would require newer drivers which will not work reliably.

Has anyone else had better success?

 

 

[windows loading freeze after using watchout]

I dont know how to thank you. Been racking my brain for a week now. Deleted the ForcePcieLinkSpeed key and windows boots just fine! I hope dataton fixes this bug in 6.3

[E2 EDID compatibility issue with AMD FirePro W7100]

On 10/8/2018 at 12:43 PM, jfk said:

That is correct, there is no space between the dash and the text. I had copied the text from an internal support document and did not catch the extraneous space.

-WmAudioRegFix off

No quotes of any kind in this command line switch 

Does that go in the watchout display startup shortcut?

So my new shortcut would have to be.

"C:\WATCHOUT 6\WATCHPOINT.EXE -WmAudioRegFix off"

[windows loading freeze after using watchout]

I am having this exact same issue. It never gets passed the windows 7 loading screen.

I have also tried windows 10 both with fresh new installations. I also tried different chipsets and still having the same issue. AMD has no idea how to resolve it.

I checked the boot files and it seems like its failing on the wx9100 driver load. W9100 cards dont present a problem. If I swap the card with a w9100, I have no issues and windows boots fine.

Does anyone happen to know the registry key " WmAudioRegFix off  " changes? I am willing to try anything at this point.