Comments on: X-Plane, SLI and CrossFire https:/2011/10/x-plane-sli-and-crossfire/ Developer resources for the X-Plane flight simulator Wed, 05 Oct 2011 17:33:56 +0000 hourly 1 https://wordpress.org/?v=6.6.1 By: Eric Liskay https:/2011/10/x-plane-sli-and-crossfire/#comment-2996 Wed, 05 Oct 2011 17:33:56 +0000 http://www.x-plane.com/blog/?p=3754#comment-2996 In reply to Joe.

Which games/engines do you notice micro stuttering in? I added a second GTX 480 to my system a few months ago and didn’t notice anything like this.

]]>
By: Ilari Kousa https:/2011/10/x-plane-sli-and-crossfire/#comment-2995 Wed, 05 Oct 2011 12:45:15 +0000 http://www.x-plane.com/blog/?p=3754#comment-2995 Speaking of performance, it would be nice to know something about the perf effects of the AI subsystem, now that we’re approaching release. Could you wrap up a post on this as it would be very useful for those of us building FTDs such as myself. Now, it’s pretty clear you won’t be able to just crank it up to max and not get an effect, but it would be nice to see how XP10 performs in this regard at this stage.

]]>
By: Andzin https:/2011/10/x-plane-sli-and-crossfire/#comment-2991 Tue, 04 Oct 2011 20:47:44 +0000 http://www.x-plane.com/blog/?p=3754#comment-2991 I think Eyefinity with bezel correction is already very useful technology (except you can’t drag&drop windows) on X-Plane. 5 vertical HD monitors gives me 1.8m wide display with 5600pix. The virtual cockpits are almost real size + TrackIR. It would be nice to have 2 cards working on XP10, XP9 can’t saturate the 5870 E6 even with 11Mpix. Unfortunately no promisses, so let’s forget about it.

]]>
By: James https:/2011/10/x-plane-sli-and-crossfire/#comment-2990 Tue, 04 Oct 2011 16:17:15 +0000 http://www.x-plane.com/blog/?p=3754#comment-2990 I completely agree that scissor mode is not desirable. That’s why I’d love to see X-Plane optimized for AFR some day 😉

The good news on the hardware side is not just that PCIe 3.0 is coming, but also that Sandy Bridge E will bring 40 lanes of PCIe bus with it – so 16x/16x will eventually be mainstream and not exclusive to X58/LGA1366.

All in all, these are exciting days – it’s really great to know that we are starting to get the most of the cards that we have in our machines. Thanks Ben and LR for the amazing progress!

]]>
By: Ben Supnik https:/2011/10/x-plane-sli-and-crossfire/#comment-2988 Tue, 04 Oct 2011 14:58:15 +0000 http://www.x-plane.com/blog/?p=3754#comment-2988 In reply to James.

My view is: if we have to run scissors to run SLI, there’s no point in doing it at all – X-Plane needs bus bandwidth, and asking a user to get an expensive 16×16 mobo to have the honor of making two insanely expensive GPUs both work is diminishing returns. At some point you’re better off with two cheaper computers.

]]>
By: James https:/2011/10/x-plane-sli-and-crossfire/#comment-2987 Tue, 04 Oct 2011 14:00:38 +0000 http://www.x-plane.com/blog/?p=3754#comment-2987 In reply to Ben Supnik.

This is why scissor tends to be the rendering mode of choice for apps not optimized for this type of technology – it means that each card processes every frame (to avoid some of the problems mentioned by Ben), but in the end will render only half of each. It is not efficient since all cards have to process essentially everything including geometry, and the bandwidth of the PCIe bus can be easily saturated because of all the data traffic. Because of that, the best results will be achieved by cards running on motherboards that support a 16x/16x configuration (instead of 16x/8x).

]]>
By: James https:/2011/10/x-plane-sli-and-crossfire/#comment-2986 Tue, 04 Oct 2011 13:28:42 +0000 http://www.x-plane.com/blog/?p=3754#comment-2986 In reply to Joe.

This is more of an issue with AFR and happens when you have a 2-card setup. Tests have shown that a 3-card setup eliminates the issue – at the cost of making the solution prohibitive 😉

]]>
By: Ben Supnik https:/2011/10/x-plane-sli-and-crossfire/#comment-2985 Tue, 04 Oct 2011 12:38:50 +0000 http://www.x-plane.com/blog/?p=3754#comment-2985 In reply to Ilari Kousa.

In order to cleanly split the rendering between two cards, the app has to avoid operations that are legal for OpenGL but very inefficient for two GPUs in a Crossfire/SLI setup. The ones I know about include:
* Any type of inter-frame render-to-texture dependency.
* Any read-backs from card (or any other potential time-stamp stalling operation) that are delayed only one frame and not two frames.
These operations have basically no penalty on a single GPU but chew bandwidth or limit what the second card can do on a dual-GPU system. So we have to make sure we have none of these cases in X-Plane. I know off-hand that we have at least two of them.

]]>
By: Ilari Kousa https:/2011/10/x-plane-sli-and-crossfire/#comment-2984 Tue, 04 Oct 2011 12:01:16 +0000 http://www.x-plane.com/blog/?p=3754#comment-2984 Can you explain why CrossFire/SLI would have to be supported at the level of the XP codebase? I thought it’s the driver that distributes the load between cards…

]]>
By: Joe https:/2011/10/x-plane-sli-and-crossfire/#comment-2983 Tue, 04 Oct 2011 11:41:38 +0000 http://www.x-plane.com/blog/?p=3754#comment-2983 With SLI/Crossfire, most graphic engines suffer under so called micro stuttering, most likely X-Plane will do so, too. In timing-sensitive applications like flight simulations this is a serious issue. SLI/Crossfire seem to be a clever idea, in practice they often are a disappointment.

]]>