is surround 3d only?
I just want to be able to play games @ the 4k rez. right now DP mts gives me a 4k desktop, but not 4k gaming options. It only plays on the first screen.

even using two different HDMI cables...
 
what am I missing here - how do I tell a game to use both screens. argh!

first time image is displayport using MST and the second post of mine with HDMI.
 
I'm not in crazy world? forget that this is one monitor, but games can run multi screen with 2 monitors, yes?
 
as far as windows/NVidia knows i'm running 2 screen.. argh! If this is an ATI only thing i'm going to go crazy ... tri-sli.. titans.. ugh.. $$$$$$$$$$$$$...
 
 

Nvidia Control Panel tells you that for Span displays with Surround you need 3 displays. Put your mouse over "Span displays with Surround" and read the bottom under Description.
I thought you could do this as well with only 2 displays.
Bill

Your Titan supports that res natively 
--> Max Digital : 4096x2160
 
It appears that your monitor does not hardware support your videocards output, but instead is dividing into dual inputs....
 
As I read the specs, a Displayport ver 1.2 cable connected to the "computer" input on the TV is the best it will do
 
You need to contact Sharp during business hours and then "try" and find someone who knows about that monitor....
Good luck
 
You are in "first adopter" territory
You "may" or may not have been $6000 burned, if playing games was your intent 
 
 

If the monitor is forcing two input streams over 1 cable for 60Hz, then someone wasn't thinking when they designed the thing. Maybe there will be a firmware fix for it. DisplayPort 1.2 was designed to provide 1 monitor with a 4K stream.
 
I guess this should serve as a word of caution for those interested in the Sharp PN-K321. I hope a fix is found soon. Otherwise, we still lack a true 4K display (4K @ native 60Hz).

Manual Here:
http://www.handpuppet.net/wow/PN-K321_manual_English_US_20121130.pdf

According to the manual, 3840x2160 will force DisplayPort to run in Multi-Stream mode. Apparently the receivers they use cannot handle one 3840x2160 image at 60Hz, so they are probably using two DisplayPort receivers, but 1 cable.
 
If you can return the thing, I would and wait for a real 4K display. There is still hope that Viewsonic's VP3280-LED won't make the same mistake.

Since you are running in SLI, are you having half the display run at 30Hz and the other half run at 60Hz like this article says happens with a two DVI connected 4K display?
http://www.brightsideofnews.com/news/2013/3/4/the-state-of-4k-and-4k-gaming-early-2013.aspx 

Ok, upon extensive research, I have come upon some things that may be of interest.
1. The reason why SLI will cause 1/2 of the monitor to have a 30Hz refresh rate is a limitation of SLI to a 400MHz Pixel Clock. This limitation can be removed with this tool: http://www.monitortests.com/forum/Thread-NVIDIA-Pixel-Clock-Patcher
2. A monitor will need ~580MHz Pixel Clock receiver or better to receive a single 4K signal at 60Hz. This number is taken from the EIZO FDH3601 4096x2160 display (290MHz per Displayport). This number is calculated by [Vertical Pixels) x (Refresh Rate) x (~1.05) = (Horizontal Refresh Rate)] x [Horizontal Pixels] x [~1.25]. Some of those ~ figures will differ depending on how the monitor is manufactured. I still have to find a receiver actually made to accept those kind of signals. One could exist, but I can't find one on VESA's certified list. Therefore, it would seem that most/all manufacturers will split the screen. In fact, I think DisplayPort 1.2 is limited to a 540MHz Pixel Clock (which theoretically could work in a very efficient monitor).
3. It seems the official way VESA plans to support 4K resolution is via MST protocol. So now it is up to nVidia to all their drivers to allow 2, 4, and 6 displays to work in 2D surround, as no other solution will work with DisplayPort.

This means that we might have to wait till HDMI 2.0 (which has a 600MHz Pixel Clock) before we see 4K displays that natively work at 60Hz without breaking the monitor into 2. However, while having a higher Pixel Clock, HDMI 2.0 has a lower overall speed due to the use of 3 lanes instead of 4. As such, they will not be able to support 30-bit color like DisplayPort 1.2.

That's what I've been trying to tell evga/nvidia but here's the support response:
 
Hello,
I have a follow up from the product team.
This particular display is a Tiled display, meaning it REQUIRES dual inputs in order to operate at the full 60Hz.
This is NOT supported on GeForce.
GeForce supports 4K displays that use a single DisplayPort connector.
 
Thanks
Dave
 

omegaw666
This is NOT supported on GeForce.
GeForce supports 4K displays that use a single DisplayPort connector.

... ****es just give us the software that lets us do it then - there is nothing special about their other lines that would prevent it fro working on "Geforce"
 
/me cries on Omegaw666's shoulders..
 
 
what is the net effect of playing games @ 30hz... other than it "feels" off. Is it just refreshing in a fast enough and i'd get the feeling that I was playing at a low framerate? aren't a lot of console games running @ 30hz (i'm pretty sure halo plays @ 30hz) - but that is on a big screen very face from ones face.

hrmm... looks like NVidia might look into it.
 
https://forums.geforce.com/default/topic/539645/nvidia-surround/2-monitor-gaming-/post/3791148/#3791148
 
my guess is all high end 4k screens (ie, 60hz) are going to 2 screens for the next year-ish.

Do we think NVidia looks at "bug" submissions?
http://nvidia-submit.custhelp.com/app/answers/list
 
maybe i'll post one. Other feel free do to too :) (i'm guessing the more ppl they see with the issue...)

oh hell yeah...

We are working on adding support for these types of monitors and hope to have it in a driver release soon.

https://forums.geforce.com/default/topic/539645/nvidia-surround/2-monitor-gaming-/post/3796149/#3796149

Aggressor Prime
Until HDMI 2.0 is released, which features a 600MHz pixel clock over DisplayPort 1.2's 540MHz pixel clock.

Where do you hear about this 540 Mhz pixelclock limitation? In my Xorg.log:
 

 (--) May 28 18:12:33 NVIDIA(0): DFP-3: 330.0 MHz maximum pixel clock
(--) May 28 18:12:33 NVIDIA(0): DFP-3: Internal Single Link TMDS
(--) May 28 18:12:33 NVIDIA(0): DFP-3: DFP is not internal to notebook
(--) May 28 18:12:33 NVIDIA(0): Name Aliases for DFP-3:
(--) May 28 18:12:33 NVIDIA(0):   DFP
(--) May 28 18:12:33 NVIDIA(0):   DFP-3
(--) May 28 18:12:33 NVIDIA(0):   DPY-4
(--) May 28 18:12:33 NVIDIA(0):   DVI-D-0
(--) May 28 18:12:33 NVIDIA(0): DFP-4: 960.0 MHz maximum pixel clock
(--) May 28 18:12:33 NVIDIA(0): DFP-4: Internal DisplayPort
(--) May 28 18:12:33 NVIDIA(0): DFP-4: DFP is not internal to notebook
(--) May 28 18:12:33 NVIDIA(0): Name Aliases for DFP-4:
(--) May 28 18:12:33 NVIDIA(0):   DFP
(--) May 28 18:12:33 NVIDIA(0):   DFP-4
(--) May 28 18:12:33 NVIDIA(0):   DPY-5
(--) May 28 18:12:33 NVIDIA(0):   DP-1 

 
On my macbook pro retina its only 480 Mhz (I believe because the DP 1.1 vs 1.2 bandwidth difference).
 
Of course on linux nvidia's drivers are limited to 400Mhz pixelclock on anything just due to legacy issues anyway but still...
 

If you are from Japan, Amazon.jp has it:
http://www.amazon.co.jp/%E3%82%B7%E3%83%A3%E3%83%BC%E3%83%97-32v%E5%9E%8B-4K2K%E6%B6%B2%E6%99%B6%E3%83%87%E3%82%A3%E3%82%B9%E3%83%97%E3%83%AC%E3%82%A4-PN-K321/dp/B00B04SC8M