Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>Yes, there is a difference.</p> <p>I managed to find useful information:</p> <p>From <a href="http://msdn.microsoft.com/en-us/library/windowsphone/develop/jj662943(v=vs.105).aspx" rel="nofollow">http://msdn.microsoft.com/en-us/library/windowsphone/develop/jj662943(v=vs.105).aspx</a>, under "The Direct3D with XAML project template"</p> <p>"This template is recommended if you want to create a game that only uses the managed app as a thin wrapper around an essentially native game in order to take advantage of some of the features that are only available to managed apps, such as live tiles. This template uses the DrawingSurfaceBackgroundGrid control to display Direct3D graphics on the screen. Unlike the DrawingSurface control, this control must be placed at the root of the XAML tree and always covers the entire screen. Like the other template, the Direct3D code for rendering graphics is implemented in a separate Windows Phone Runtime component. <strong>The frame rate of a Direct3D with XAML app is slightly better than a XAML with Direct3D app.</strong>"</p> <p>And from <a href="http://tiptoptool.com/tag/sdk/" rel="nofollow">http://tiptoptool.com/tag/sdk/</a>, under "DrawingSurfaceBackgroundGrid"</p> <p>"DrawingSurfaceBackgroundGrid is a very special element that must always be the root element of a page and allows developers to render directly to the background from Direct3D using C++. DrawingSurfaceBackgroundGrid, as its name implies, inherits from Grid so you can position child elements using Grid layout. The child elements are automatically composed by the platform on top of the Direct3D rendered background. <strong>DrawingSurfaceBackgroundGrid allows developers to render directly, instead of requiring a copy (through a Direct3D swap chain) like DrawingSurface requires, which results in faster performance.</strong> DrawingSurfaceBackgroundGrid was introduced to support games or other apps that require ‘to the metal’ graphics performance, but also want to use existing XAML elements for UI and have access to some features not available in the native app model like Live Tiles or Notification"</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload