google-code-export / dark-nova-android

Automatically exported from code.google.com/p/dark-nova-android
0 stars 0 forks source link

Miscalculation of warp distance after buying new ship leads to force close on android. #50

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
   Not easily reproducible.
1. at warp screen select a system at edge of your range
2. buy a ship with smaller range
3. try to warp to the selected system

What is the expected output? What do you see instead?
I expect that the system selected would no longer be selectable.  It was and I 
was still able to buy products to take to the out-of-range system.

The app became unresponsive and the phone asked me to provide feedback for the 
failure.  I remember the failure was in Dark Nova/.Prices.

What version of the product are you using? On what operating system?
Droid X with froyo 2.1
Dark Nova Android 1.2 

Please provide any additional information below.
I started filling in feedback and that, too, crashed.  It left my phone 
unusable, off, and I could not figure out how to turn it back on.

Original issue reported on code.google.com by kalim.ja...@gmail.com on 20 Dec 2010 at 8:59

GoogleCodeExporter commented 9 years ago
Hi Kalim,

Thanks for reporting. I have tried to recreate the bug. I have repeated the 
steps above but when I get to step 3, I try and select the planet on the short 
range chart but it doesnt allow me as expected. ("insufficient fuel"). With the 
DroidX did you use the keyboard or re-select the planet by touching?

Many thanks,

Jatin

Original comment by jatin2...@gmail.com on 21 Dec 2010 at 6:23

GoogleCodeExporter commented 9 years ago
I had the planet pre-selected then bought a new ship with lower range.  The
ship was the first one with 2 crew quarters.
I then purchased some cargo and hit warp.  It hung at that point.

Now here's the really interesting thing.

I was able to recreate the same issue with teh same consequences again today
by loading the saved game.  I started filing the automated droid X bug info,
but that locks up after 1.5 -> 2 minutes.  I can recover only by poppoing
out the battery!  So I will try to reproduce it, then get to submit without
a lot of explanation.  So please be on the lookout for a bug filing from
this address.

If that does not work, what are the chances I could send you the save game
file as an attachment to the bug?
In other words, please give me a procedure to follow to get you the
info/files you need.
Thanks for looking into it.

KJ

Original comment by kalim.ja...@gmail.com on 22 Dec 2010 at 2:12

GoogleCodeExporter commented 9 years ago
Dang.  Sorry to get your hopes up.  I was not able to recreate again
tonight.

After loading the saved game I could see some info..
Ship bought was yt-1300.
I had $ -183 somehow.

Give me tonight to try reproduce.

KJ

Original comment by kalim.ja...@gmail.com on 22 Dec 2010 at 2:27

GoogleCodeExporter commented 9 years ago
Hi Kalin,

Unfortunately, the bug report crashing is a google issue, its quite unstable on 
2.1.

Any chance you can get 2.2?
http://androidcommunity.com/droid-x-update-available-now-2-2-1-blur-2-3-340-2010
1210/

This should send me the stacktrace so I can pin point the problem. 

The other issue your getting is the negative value, I will look into that as 
well.

Thanks

Jatin

Original comment by jatin2...@gmail.com on 22 Dec 2010 at 10:59

GoogleCodeExporter commented 9 years ago
RE: 2.2: OK I will update and try again.

RE: negative credits:
I agree that the negative credits value is a separate issue.
If we don't already have a bug on it, I'll file one.  I noticed during play
testing that if I clicked warp to an out-of-range system, my credits
decreased (maybe due to paying personnel or buying news).  That value went
from 8cr to ~-140.
I lost my saved games in the process so I'll file that if I can reproduce.

KJ

Original comment by kalim.ja...@gmail.com on 22 Dec 2010 at 7:54

GoogleCodeExporter commented 9 years ago
After update of android to 2.2 the issue seems fixed.
No crashes since the update and believe me I have played a lot this holiday!
Let's chalk this issue up to android instead of dark nova and close it.

KJ

Original comment by kalim.ja...@gmail.com on 23 Dec 2010 at 11:48

GoogleCodeExporter commented 9 years ago
Thanks! Please continue to send us feedback as it will help us improve the game!

Original comment by jatin2...@gmail.com on 25 Dec 2010 at 8:01

GoogleCodeExporter commented 9 years ago

Original comment by jatin2...@gmail.com on 29 Dec 2010 at 11:42