[Lookup Anything] crash on some smaller resolutions

Question

[Lookup Anything] crash on some smaller resolutions

Pathoschild opened this issue 8 years ago · 3 comments

Pathoschild commented 8 years ago

If the screen resolution is smaller than expected (≈≤1280×768), the lookup UI crashes with the following error:

[ERROR] An error occured in the overridden draw loop: System.ArgumentException: The scissor rectangle is invalid. The scissor rectangle cannot be larger than or outside of the current render target bounds.
Parameter name: value
   at Microsoft.Xna.Framework.Graphics.GraphicsDevice.set_ScissorRectangle(Rectangle value)
   at Pathoschild.LookupAnything.Components.LookupMenu.draw(SpriteBatch spriteBatch)
   at StardewModdingAPI.Inheritance.SGame.Draw(GameTime gameTime)
[03:42:31.174 PM] [ERROR] An error occured in the overridden draw loop: System.InvalidOperationException: Begin cannot be called again until End has been successfully called.
   at Microsoft.Xna.Framework.Graphics.SpriteBatch.Begin(SpriteSortMode sortMode, BlendState blendState, SamplerState samplerState, DepthStencilState depthStencilState, RasterizerState rasterizerState, Effect effect, Matrix transformMatrix)
   at Microsoft.Xna.Framework.Graphics.SpriteBatch.Begin(SpriteSortMode sortMode, BlendState blendState, SamplerState samplerState, DepthStencilState depthStencilState, RasterizerState rasterizerState)
   at StardewModdingAPI.Inheritance.SGame.Draw(GameTime gameTime)

Reported in the forums (see 2016-10-06 #1 and 2016-10-06 #2).

Pathoschild · Answer 1 · 2016-10-09T00:16:19.000Z

I can't reproduce this, so it's hard to test. Possibly fixed via b32059a.

Pathoschild · Answer 2 · 2016-10-15T13:24:28.000Z

I haven't heard anything back from those who reported it, so I assume this is fixed.

Pathoschild · Answer 3 · 2019-08-07T00:53:15.000Z

Fixed in the upcoming Lookup Anything 1.23.

The issue is rare, but one player was able to reproduce it and run some tests for me. It happens when the game's viewport size (Game1.viewport) is larger than the graphics device's viewport (Game1.graphics.GraphicsDevice.Viewport), which caused UI calculations to incorrectly place the menu partly outside the device viewport. The game itself is affected too, but it rarely causes noticeable errors.

Share to