Some games running in windowed mode generate sporadic errors that wouldn't prevent the game to work, but terminate the application. Oddly enough, some games expect to notice this by themselves and work correctly only when the option is NOT set. When this option is set and a CreateSurface fails because of video memory shortage, DxWnd backs this up by creating the surface on memory. You want a second example? It has not been easy to find, but "Crush! Deluxe" suffers the same problem. The option forces a periodic blitting of the primary surface on screen even if the game doesn't request it. Some badly programmed games (namely the "Cossaks" series) don't follow the specification to blit changes on screen, they just get the primary surface memory address and keep writing there.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |