RE: [GD-Windows] XLATEOBJ_hGetColorTransform
Brought to you by:
vexxed72
From: Andrew G. <And...@ho...> - 2002-01-09 09:47:13
|
Have you tried using DDBs instead of DIBs? You should get better performance that way because they should be stored in a device friendly way. Might be worth doing a quick DDB v DIB performance comparison. I'd certainly be interested in the result :) Andrew Grant Hothouse Creations > -----Original Message----- > From: Brian Hook [mailto:bri...@py...] > Sent: 09 January 2002 02:55 > To: bri...@py...; 'Gamedevlists-Windows@Lists. Sourceforge. > Net' > Subject: [GD-Windows] XLATEOBJ_hGetColorTransform > > > It looks like about 20% of my time is spent in BitBlt() via > DIBsections. > Of that time, this funky call to XLATEOBJ_hGetColorTransform is > consuming like 98% of the time. I'm guessing from the name that it's > doing a color transform from my DIB to the screen, however both are in > 16-bit. So I'm figuring one of two things is going on: > > - BitBlt() doesn't detect the unity situation with DIB sections > > - even though the DIB is 16-bits and the framebuffer is > 16-bits, they're > both "different" 16-bits. If this is the case, is there a > way to query > for the native format to allow for a unity blit? > > And just think, we were wondering if there was even going to > be traffic > on a Windows list that didn't talk about DX =) > > Brian > > > _______________________________________________ > Gamedevlists-windows mailing list > Gam...@li... > https://lists.sourceforge.net/lists/listinfo/gamedevlists-windows > This email is covered by the following disclaimer, please read before accepting this email. http://www.hothouse.org/disclaimer/ |