Windows 8 + nVidia + Samsung UbiSync 7 + Battlefield 3
 

I'm having a problem with this setup:

Windows 8
Samsung UbiSync 7 (bought in a bundle with SyncMaster 2263DX)
GeForce GTX 560 (non-Ti)

When i play Battlefield 3, triangles are fighting on my screen.
It looks like this: http://youtu.be/tJF5JH22-bw

Additionaly the mouse seems to lag or stutter.
Both problems are gone when i unplug the USB screen.

What to do to have a working UbiSync screen and BF3 without angry triangles? :<

push......

Hi! Have the exacte same problems too!

Took me a while to figure out that is has to do with the displaylink tech. The moment I unplug the small USB monitor, everthing is fine.

Tried many differend nvidia drivers, nothing works. Just tried to reinstall the actual DisplayLink driver. No effect.

In addition, some context-menus and bars I use on windows desktop are "destroyed" (meaning: looks broken, the images are messed up).

In fact the Displaylink Software even prevents BF3 from starting! Had to remove it so the game would run again.

Forgot to mention that I had similar problems in Company Of Heroes 2.

Support?! Hello?

Hi,

Can you post the files generated by this tool after you launch each game?http://www.displaylink.com/support/ticket.php?id=269

Thanks,
James

Hi there!

I added the file to the post. The extra image shows the "destroyed" context menu of windows, as long as the displaylink software is installed.

Funny though, after playing a short test round BF3 where the graphic bug did not appear, I tried a big map but BF3 would not start at all!

After I uninstalled the DisplayLink Software and unplugged the USB-Monitor it works again. The System Compatibility Check is fine though...all tests PASS

Hi,

Any news on this?

Oh come on!

Got still problems with the latest Displaylink Software and the lates nvidia drivers. Windows 8.1 still shows broken context menus! Look at the pictures.

Same problem with BF4 as long the DisplayLinkSoftware is installed

Only way making BF3 work perfectly is uninstalling DisplayLink drivers.
Are you kidding? Now after over a year not a single solution! :mad: