Fixed [Indev 0.50.1] Temporary Berry Pick Crash

[Katak]

Describe the bug you experienced here.
I was walking through route 29, I turned up to go get the berries from the berry trees inbetween the ledges, when the game crashed and the screen that tells me to run the game again appeared.
What I expected to happen:
I expected to just be able to walk up and pick the berries.

What actually happened:
The game crashed.

Steps to reproduce:
Walk along the route 29 where the 2 berry plants are, and walk up between the ledges.

(Add a crash log here if available and enclose it in the code tag with this button:

)

 

[jianmingyong]

hmm... still this bug relates many of the previous reports.

at net.Pokemon3D.Game.SkyDome.SetLastColor()
at net.Pokemon3D.Game.SkyDome.Update()
at net.Pokemon3D.Game.OverworldScreen.Update()
at net.Pokemon3D.Game.Core.Update(GameTime gameTime)
at net.Pokemon3D.Game.GameController.Update(GameTime gameTime)
at Microsoft.Xna.Framework.Game.Tick()
at Microsoft.Xna.Framework.Game.HostIdle(Object sender, EventArgs e)
at Microsoft.Xna.Framework.GameHost.OnIdle()
at Microsoft.Xna.Framework.WindowsGameHost.RunOneFrame()
at Microsoft.Xna.Framework.WindowsGameHost.ApplicationIdle(Object sender, EventArgs e)
at System.Windows.Forms.Application.ThreadContext.System.Windows.Forms.UnsafeNativeMethods.IMsoComponent.FDoIdle(Int32 grfidlef)
at System.Windows.Forms.Application.ComponentManager.System.Windows.Forms.UnsafeNativeMethods.IMsoComponentManager.FPushMessageLoop(IntPtr dwComponentID, Int32 reason, Int32 pvLoopData)
at System.Windows.Forms.Application.ThreadContext.RunMessageLoopInner(Int32 reason, ApplicationContext context)
at System.Windows.Forms.Application.ThreadContext.RunMessageLoop(Int32 reason, ApplicationContext context)
at System.Windows.Forms.Application.Run(Form mainForm)
at Microsoft.Xna.Framework.WindowsGameHost.Run()
at Microsoft.Xna.Framework.Game.RunGame(Boolean useBlockingRun)
at Microsoft.Xna.Framework.Game.Run()
at net.Pokemon3D.Game.Program.Main(String[] args)

same call stack...... Maybe it is a temporary error.

 

[Katak]

I'm on my way to test again.

Edit: Problem didn't occur again after restart of client. If it helps I was on my own Online Server as well, but like I said the issue did not repeat itself.

 

[nilllzz]

Should be fixed.