Three AGS Oddities ("Bugs")

[Ghost]

Sorry if any of these have already been reported- it's stuff I ran across quite recently, and with the new "open-source" attitude, it might be easier to fix than before...

(I'm using the latest AGS version (AGS Editor .NET (Build 3.2.1.111) / v3.2.1, March 2011), on a computer using Windows 7 Home Edition. Graphics Card is NVidea GeForce.)

- Creating a template from a game that has a COMPRESSED sprite file turns every sprite in the template to a fully transparent one. Room backgrounds remain intact, and using an
UNCOMPRESSED sprite file solves the problem.

- Deleting a view, and then creating new ones, skips the previously deleted view numbers. As in, creating View1 to View4, then deleting some of them, will make View numbering resume from View5 instead of "filling in" the now unused numbers. A minor offense, but maybe worth a fix, since it really contradicts how numbering is handled everywhere else (sprites and rooms always try to "fill the gap").

- Colours vary noticeably in DirectDraw5/Direct3D9, to the point where colours really look weird (at least on my computer). In both windowed and fullscreen mode, especially green seem to get a darker, blueish tint, and it's always D3D9 that "screws up" the colours.

[Gilbert]

- Colours vary noticeably in DirectDraw5/Direct3D9, to the point where colours really look weird (at least on my computer). In both windowed and fullscreen mode, especially green seem to get a darker, blueish tint, and it's always D3D9 that "screws up" the colours.

My wild guess. Maybe the engine is using the colour correction data set by the video card driver under D3D9. If this is the case the situation can be even more complicated, as different users may have different results.

[Yeppoh]

Actually having read and fiddled with the rendering loop on the D3D9 device. There are originally lines that corrects the color output to match the Allegro device by making them darker as indicated by the comments.