View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
0000048Populous: The BeginningGlitchpublic2015-06-07 16:342017-11-29 16:30
ReporterBrandan Assigned ToBrandan  
PriorityurgentSeveritymajorReproducibilityhave not tried
Status resolvedResolutionfixed 
Fixed in Version1.1 
Summary0000048: Sky at high resolutions.
DescriptionSky stops drawing on higher resolutions.
TagsNo tags attached.
Build Number

Relationships

duplicate of 0000088 closed Sky / Horizon screen glitch on high resolutions 
related to 0000156 closedBrandan Only the first 222 lines of the sky flashes red when you win 
child of 0000154 resolvedRed Width draw bug 

Activities

Brandan

2015-08-12 03:19

administrator   ~0000054

This was made worse on the VS2013 builds, now its anything bigger than the stock resolution 800x600.

Red

2015-08-12 21:10

developer   ~0000064

The ViewDrawParameters -> NumClearScreenLines property is hard coded to 222 in Players.cpp (line 227). This should probably be calculated per the user's resolution. I hard coded it to a higher value and verified that the sky displays correctly on higher resolutions.

Brandan

2015-08-12 21:56

administrator   ~0000065

Last edited: 2015-08-12 21:56

 (see hipchat img too large) That works with the vertical lines but the horizontal lines.

Brandan

2015-08-12 22:11

administrator   ~0000066

NumClearScreenLines = (gnsi.ScreenW*gnsi.ScreenH)*(37/51200);

This needs to be recalculated again ONCE THE GAME STARTS, because the resolution changes from the main screen to gameplay.

Brandan

2015-08-12 22:12

administrator   ~0000067

(640*480)*(37/51200) = 222
 (1080*1920)*(37/51200) = 1499

I double checked this and if its below 1498 you get the draw problems on 1080x1920.

Brandan

2015-08-12 22:50

administrator   ~0000069

Fly by mode fixes the draw bugs, but then they return once flyby is complete.

Brandan

2015-08-12 22:58

administrator   ~0000070

If you play with the zoom in/out buttons -/+ this also fixes the problem temporarily.

Brandan

2015-08-12 22:59

administrator   ~0000071

This is a completely different bug.

Issue History

Date Modified Username Field Change
2015-06-07 16:34 Brandan New Issue
2015-06-12 13:35 Brandan Relationship added duplicate of 0000088
2015-08-12 03:19 Brandan Note Added: 0000054
2015-08-12 03:20 Brandan Priority normal => urgent
2015-08-12 03:20 Brandan Severity minor => major
2015-08-12 21:10 Red Note Added: 0000064
2015-08-12 21:56 Brandan Note Added: 0000065
2015-08-12 21:56 Brandan Note Edited: 0000065
2015-08-12 22:11 Brandan Note Added: 0000066
2015-08-12 22:12 Brandan Note Added: 0000067
2015-08-12 22:50 Brandan Note Added: 0000069
2015-08-12 22:58 Brandan Note Added: 0000070
2015-08-12 22:59 Brandan Note Added: 0000071
2015-08-12 22:59 Brandan Status new => resolved
2015-08-12 22:59 Brandan Fixed in Version => 1.1
2015-08-12 22:59 Brandan Resolution open => fixed
2015-08-12 22:59 Brandan Assigned To => Brandan
2015-08-12 23:02 Brandan Relationship added parent of 0000148
2015-08-12 23:03 Brandan Relationship deleted parent of 0000148
2015-08-12 23:03 Brandan Relationship added child of 0000148
2015-08-12 23:05 Brandan Relationship deleted child of 0000148
2015-08-12 23:05 Brandan Relationship added child of 0000154
2015-08-19 18:55 Brandan Relationship added related to 0000156
2017-11-29 16:30 Brandan Category Glitch => Glitch1
2017-11-29 16:40 Brandan Category Glitch1 => Glitch