search

jetbalsa / pos-tracker-eve

Automatically exported from code.google.com/p/pos-tracker-eve
0 stars 0 forks source link

Silo Linking #1

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. Link a silo to another on the viewpos page. The numbers become screwed up 
and are unable to update the linked silo.

Original issue reported on code.google.com by frozenic...@gmail.com on 17 Oct 2010 at 11:59

GoogleCodeExporter commented 9 years ago 
Need to set limiters for silos as amounts greater than what a silo should hold 
makes it start fire. Fire bad.

Original comment by frozenic...@gmail.com on 11 Dec 2010 at 8:27

GoogleCodeExporter commented 9 years ago 
Issue 5 has been merged into this issue.

Original comment by frozenic...@gmail.com on 23 Apr 2011 at 7:09

GoogleCodeExporter commented 9 years ago 
Figured out why the silo linked bug happens in the POS Tracker. See example. d 
is the linked silo. 

D should equal the current amount of everything - silo capacity. So when we 
have 33600, only 3600 should show up in the linked silo as the silo capacity 
for the first silo was 30000. But for some reason it shows up 33600 which is 
the problem as then all the linked silos show this...but why? Well lets see... 
Remember d should equal 3600 in the end.

Here's the code's math.

a = 33600/(1+0)

b = a * 1

c = silo_cap - b

d = a ...so happy we had the calculations going for b and c.

But part 2 of the problem is even more awesome.

If the amount in the linked silos goes to the 3rd silo and beyond we notice a 
small little issue. 

c = silo_cap - b . If lets say the silo cap is 30000 and you have 63300 units 
of goods in storage. b = 63300 and so you can see if the command only takes off 
one silo amount so the silo is still full because it thinks there is 33300 left 
inside of it. It doesn't actually take off this amount either, it just keeps 
going. So all the next silos are 63300 - 30000. Which causes the other linked 
silos to think the same way. So since it sees the silo in front of it as "full" 
it keeps going 63300 - 30000. So what you have in the end is the first silo at 
30000, and all the other linked silos show as 33300. Yay for math!

Fix coming along, should be good to go in 5.1.5. Will close issue once 
confirmed.

Original comment by frozenic...@gmail.com on 18 Jul 2011 at 3:11

GoogleCodeExporter commented 9 years ago 
Fixed in 5.1.5. Rewrote the production code to be a little be less stupid. Silo 
bug should be officially squashed.

Original comment by frozenic...@gmail.com on 18 Jul 2011 at 9:27

GoogleCodeExporter commented 9 years ago 
Thats good to here,

Where do i download the Full Install????

Original comment by stevenjw...@gmail.com on 18 Jul 2011 at 10:26

GoogleCodeExporter commented 9 years ago 
NM Found it

Original comment by stevenjw...@gmail.com on 18 Jul 2011 at 10:47