MantisBT - VCMI
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0000496VCMIOtherpublic2010-06-02 17:192011-03-01 23:29
ReporterWarmonger 
Assigned ToIvan 
PrioritylowSeveritymajorReproducibilityalways
StatusclosedResolutionfixed 
PlatformLaptopOSWindows 7OS Versionvanilla
Product Version0.81 
Target VersionFixed in Version0.84 
Summary0000496: Creatures are deformed and misplaced in 1366x768 windowed mode
DescriptionCreatures are misplaced, rotated and Archangel is just missing both in Town Screen and battle.
Fullscreen mode works fine with this resolution.
Steps To Reproduce
Additional InformationI'm pretty sure similar bug was reported before.
TagsNo tags attached.
Relationships
has duplicate 0000497closed Tow dragon visual problem 
has duplicate 0000621closed Tow Resolution Bug 
Attached Filesrar 1366x768creatureglitch.rar (1,987,990) 2010-06-02 17:19
https://bugs.vcmi.eu/file_download.php?file_id=409&type=bug
Issue History
Date ModifiedUsernameFieldChange
2010-06-02 17:19WarmongerNew Issue
2010-06-02 17:19WarmongerFile Added: 1366x768creatureglitch.rar
2010-06-03 01:25ZamolxisNote Added: 0000933
2010-06-03 01:26ZamolxisNote Edited: 0000933bug_revision_view_page.php?bugnote_id=933#r876
2010-06-04 17:05ZamolxisRelationship addedhas duplicate 0000497
2010-10-03 19:21WarmongerRelationship addedhas duplicate 0000621
2011-02-06 17:33IvanNote Added: 0001516
2011-02-06 17:34IvanStatusnew => feedback
2011-02-17 10:45WarmongerNote Added: 0001523
2011-02-17 10:45WarmongerStatusfeedback => new
2011-02-17 10:45WarmongerStatusnew => resolved
2011-02-17 10:45WarmongerFixed in Version => 0.89
2011-02-17 10:45WarmongerResolutionopen => fixed
2011-02-17 10:45WarmongerAssigned To => Ivan
2011-03-01 23:29ZamolxisNote Added: 0001583
2011-03-01 23:29ZamolxisStatusresolved => closed

Notes
(0000933)
Zamolxis   
2010-06-03 01:25   
(edited on: 2010-06-03 01:26)
Well, this is exactly the problem that I was talking about and why I didn't want to go for 1366x768 in the first place (even though I knew that statistically it's most frequently used of the four 13xx resolutions out there).

See the comments on 1366x768 (and 2nd screenshot) from my forum post back in February: http://forum.vcmi.eu/viewtopic.php?p=4297#4297 [^]

And I've repeated this concern in most of my comments on report 0000431. Perhaps I should have waited for more testing feedback before making the change, 'cause now I'm not sure which bug is easier to fix: the one you reported for 1336x & 1360x resolutions, or this one.

Hopefully I'll manage to get my hands on a laptop with this resolution to perform more tests. Somehow the fact that these bugs don't occur on other resolutions, makes me think it could be an issue of card/driver support, or perhaps also Windows settings (and here I'm thinking of the window resizing issue you reported at 0000431).

So what we have so far is:

1360x768 : fails in full screen mode (on my machine it refuses to go full screen, on Warmonger's the screen doesn't get resized over the basic 800x600) but it works fine in window mode. As per various statistics and reports I found on the net on the 13xx resolutions, this is the 2nd most used but the one supported by most video cards.

1366x768 : works in full screen mode (for both myself & Warmonger), but in window mode the creature graphics are very much misplaced and deformed. This is the 1st most used resolution in the 13xx range (most 15.6 - 16" laptops use it lately), but not very well supported by many graphic cards.
(0001516)
Ivan   
2011-02-06 17:33   
There is a chance that I've fixed it in rev 1949 - found small bug in creature blitting which *may* result in something like this. Please recheck.
(0001523)
Warmonger   
2011-02-17 10:45   
Marked as resolved.
(0001583)
Zamolxis   
2011-03-01 23:29   
It's fixed indeed. Great find Ivan. :)

I do have the issue that F4 (fullscreen) doesn't work anymore in this resolution, but I guess that's because my video card doesn't support it properly. When I hit F4, I get this in the console: "Error: SDL says that 1366x768 resolution is not available!" > if others have this as well and it's indeed a bug, then you are free to open a new report (or let me know here and I'll open one).