Home/ Questions/Q 4260254
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-21T05:53:43+00:00

I have created 16 Direct3D devices with size approximately 320×200 pixels. I invoke IDirect3DDevice9::Present

  • 0

I have created 16 Direct3D devices with size approximately 320×200 pixels. I invoke IDirect3DDevice9::Present for each device in a separate thread every 40 ms. On laptops with Windows XP and integrated Intel GMA945 graphics part of devices is not updated if system tooltip or Start menu are shown. IDirect3DDevice9::Present doesn’t return any error codes at that moment, in program everything looks fine, but user can see that move on several of devices freezes. What could be a reason for that?

This works fine on Windows 7 with the same hardware and on Windows XP with different hardware, so the problem only with this combination. I should support this since my customers are use this combination of the hardware and OS. MSDN says nothing about that I should create only one D3D device (at least I can’t find it) so problem should be elsewhere.

What I’m trying to find is that possibly there’s some combination of flags that could solve my problem. At the moment I use the following:

D3DPRESENT_PARAMETERS param = {};
param.Windowed = TRUE;    
param.SwapEffect = D3DSWAPEFFECT_DISCARD;   
param.hDeviceWindow = GetSafeHwnd();
param.BackBufferCount = 1;
param.BackBufferFormat = D3DFMT_UNKNOWN;
param.BackBufferWidth = m_szDevice.Width;
param.BackBufferHeight = m_szDevice.Height;
param.MultiSampleType = D3DMULTISAMPLE_NONMASKABLE;
param.Flags = D3DPRESENTFLAG_VIDEO;
param.PresentationInterval = D3DPRESENT_INTERVAL_IMMEDIATE;
param.MultiSampleType = D3DMULTISAMPLE_NONE;
param.MultiSampleQuality = 0;
Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    I’ve distributed DirectX software for a couple of years and along the way learnt that Intel graphics chipsets have incredibly crap drivers. Once I even saw a driver revision that couldn’t render a quad properly. So when you have a problem with an Intel chipset, if you’re on the latest driver version, you pretty much have to accept your solution is going to be “start shotgun hacking things until it works”.

    Sorry to give you a lame answer, but Intel chipsets are not well engineered at all. They’re solely there to get something – anything – on the screen, probably for office worker type use. Beyond “does it do aero glass” Intel probably don’t give a hoot what it does or how well it works. An alternative “solution” is to distribute your application anyway, state that Intel chipsets are not supported due to glitches in the hardware/driver support, and contact Intel and see if you can get a fix from them.

    And people say OpenGL has bad drivers…

    • 0