Aha. I see what you mean now. Borders within borders... I'll add sbig back in for that I guess.
Can you check something? In the same settings as that pic, look in the 2.5 allegro.log and see if triple buffering is enabled.
Aha. I see what you mean now. Borders within borders... I'll add sbig back in for that I guess.
Can you check something? In the same settings as that pic, look in the 2.5 allegro.log and see if triple buffering is enabled.
This post contains the official Gleeok seal of approval. Look for these and other posts in an area near you.
Tell me the precise message it should say when Triple buffering is enabled. I can have it say "Triplebuffer available" when setting Double Buffer and Triple Buffer to 0 in ag.cfg, and I can have it say "Triplebuffer not available" when I set those values to 1. Either way it doesn't seem to do anything or at least has no impact on input lag, the same goes for vsync, setting that to 0 or 1 seems to have no impact on anything. Display is tear free so long as Cap FPS is set to 1, lots of screen tearing when set to 0 regardless of every other setting (as well as running at 2,000fps).
All this is tested in fullscreen mode.
Computer specifications:
Windows 10 Pro x64 | Intel Core i7 @ 2.66GHZ | Asus P6T Motherboard | 6GB DDR3 RAM | Integrated Sound | Nvidia Geforce 560 Ti 2048MB PCI-E | Corsair AX760 Power Supply | Thermaltake Armor+ MX case
If it doesn't say anything then it's triple buffered. (unless you override in the config file.)
How is the off-screen background blue only in 2.5... Maybe I can add another option "bg_color" for this and have it default to 0 (black).
[edit] @franpa : Does it look the same in 2.5 if you set the resx, resy to 640x480 and let your graphics card do all the work?
Last edited by Gleeok; 11-23-2012 at 07:56 PM.
This post contains the official Gleeok seal of approval. Look for these and other posts in an area near you.
There are currently 2 users browsing this thread. (0 members and 2 guests)