Skip to main content
gamedev.net
🔒 Locked

Buffer flags

Started by Axiverse 1 reply 350+ views
Original Post
Axiverse
Axiverse
Does anyone know what the following two flags do and what conditions are optimal for their use?? D3DLOCK_NOSYSLOCK D3DLOCK_NO_DIRTY_UPDATE
Morpheus011
Morpheus011
D3DLOCK_NOSYSLOCK - The default behavior of a video memory lock is to reserve a system-wide critical section, guaranteeing that no display mode changes will occur for the duration of the lock. This option causes the system-wide critical section not to be held for the duration of the lock.

The lock operation is time consuming, but can enable the system to perform other duties, such as moving the mouse cursor. This option is useful for long-duration locks, such as the lock of the back buffer for software rendering that would otherwise adversely affect system responsiveness.

D3DLOCK_NO_DIRTY_UPDATE - By default, a lock on a resource adds a dirty region to that resource. This option prevents any changes to the dirty state of the resource. Applications should use this option when they have additional information about the set of regions changed during the lock operation.

msdn ftw
Axiverse
Axiverse
Yeah I've read that (duh) but what do those mean...

Topic Locked

This topic has been locked by a moderator. New replies are not allowed.

Sign in to reply to this topic.