Re: Rendering to Multiple GPUs

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

From: Phil Taylor (ptaylor_at_private-citizen.com)
Date: 06/11/04


Date: Fri, 11 Jun 2004 08:12:06 -0700

for the multi-head case, the screensaver framework does not create copies.

if its separate devices, there is no way to avoid the copies.

managed resources do not exist only in system memory, you misunderstand how
resources and resource management works.

"Eric Penner" <EricPenner@discussions.microsoft.com> wrote in message
news:94232435-0468-4E80-AB33-363CBE867E45@microsoft.com...
> Hi there,
>
> I'm interested in methods of rendering to multiple monitors. In general,
as soon as I drag a window off of one monitor it drops to software rendering
(except for a few cases like using NView to make two monitors appear as one
monitor to windows.
>
> The moire screen saver demo creates numerous devices and renders to each
independantly, but this requires creating multiple copies of all your
resources (not very fun).
>
> Is there *any* solution to render to numerous monitors at the same time or
to share resources across devices? I get errors if I use a managed resource
created on one device on a different device. It *should* be able to work
since managed resources exist in system memory.
>
> Anyway, any help would be appreciated!
>
> Eric Penner
>
>



Relevant Pages

  • Re: Rendering to Multiple GPUs
    ... There is a copy in system memory that is copied to video memory as needed. ... hw does not render from sysmem ... bet this was going to be used for sharing resources but they scrapped it. ... >> managed resources do not exist only in system memory, ...
    (microsoft.public.win32.programmer.directx.graphics)
  • Re: Rendering to Multiple GPUs
    ... I didn't say that managed resources exist *only* in system memory. ... There is a copy in system memory that is copied to video memory as needed. ... Since there is a copy in system memory DirectX *could* utilize this to share resources across devices. ... which makes multiple device rendering a big pain. ...
    (microsoft.public.win32.programmer.directx.graphics)
  • Re: Implementing IDisposible on light objects
    ... neither unmanaged resources nor managed resources which are resource ... dispose of instances appropriately. ... there will be no finalization. ...
    (microsoft.public.dotnet.languages.csharp)
  • Re: GC and dispose
    ... We often use the Dispose for cleaning managed resources ... UNMANAGED resources inside your classes get cleaned up. ...
    (microsoft.public.dotnet.framework)