Author Topic: [invalid] 3.5.0 B2 - Shadow Glitch(reported by -archmage- on GAE board)  (Read 915 times)

Arhi

  • Guest
3.5.0 B2
Endless shadows :(
(click to show/hide)
« Last Edit: 20 April 2011, 06:25:32 by -Archmage- »

-Archmage-

  • Moderator
  • Dragon
  • ********
  • Posts: 5,887
  • Make it so.
    • View Profile
    • My Website
Shadow Glitch(reported by -archmage- on GAE board)
« Reply #1 on: 20 April 2011, 06:24:07 »
What screen resolution, and what shadow resolution?
Egypt Remastered!

Proof: Owner of glest@mail.com

Omega

  • MegaGlest Team
  • Dragon
  • ********
  • Posts: 6,167
  • Professional bug writer
    • View Profile
    • Personal site
Re: 3.5.0 B2 - Shadow Glitch(reported by -archmage- on GAE board)
« Reply #2 on: 20 April 2011, 22:48:02 »
This is caused when your shadow resolution (which must be a power of 2) is larger than the screen resolution. eg: playing the game at 1024x768 resolution will cap the shadow resolution at 1024. Larger than that causes problems (this was pointed out earlier in GAE, and has not been fixed on either engine).
Edit the MegaGlest wiki: http://docs.megaglest.org/

My personal projects: http://github.com/KatrinaHoffert

-Archmage-

  • Moderator
  • Dragon
  • ********
  • Posts: 5,887
  • Make it so.
    • View Profile
    • My Website
Re: 3.5.0 B2 - Shadow Glitch(reported by -archmage- on GAE board)
« Reply #3 on: 20 April 2011, 22:59:20 »
I believe it has to do with the 'p' part. 1024*768 is 768p, thus the limit is 512*512.
Egypt Remastered!

Proof: Owner of glest@mail.com

Omega

  • MegaGlest Team
  • Dragon
  • ********
  • Posts: 6,167
  • Professional bug writer
    • View Profile
    • Personal site
Re: 3.5.0 B2 - Shadow Glitch(reported by -archmage- on GAE board)
« Reply #4 on: 20 April 2011, 23:42:18 »
You mean the height? The "p" alone stands for progressive scan, which means all rows are rendered in order. The other option is "i", meaning interlacing, which means all odd and all even are rendered separately, then interlaced together. Interlacing can cause some flickering problems, and was really only used because it was lighter on the data sent. Pretty much all modern displays use progressive scan. In 1024x768, that is x*y, or width (number of columns) by height (number of rows).
Edit the MegaGlest wiki: http://docs.megaglest.org/

My personal projects: http://github.com/KatrinaHoffert