[BUG]MissionController.ClearPocket: ReloadALL: Reload if [True] #55

Closed
oldmeat opened this Issue Apr 20, 2012 · 10 comments

Projects

None yet

2 participants

@oldmeat

I have sometimes a problem with the fact that the bot is hanging on a mission and does not attack the target. ISDPPL write the customer's fault or lag eve but when i push manual missiles everything returns to normal operation. http://pastebin.com/08ih551L

@oldmeat

But target is active and visible on top window, i must only click on missile launcher and everything back to work properly.

@oldmeat

I've noticed that now the problem occurred at a time when the launcher I have remnants of a former missile other than those needed for this mission. I manually reloaded and bot returned to normal operation.

@oldmeat

But this does not happen every time, but from time to time.

@ISeeDEDPpl
Owner

odd..

@ISeeDEDPpl
Owner

try this branch:
https://github.com/ISeeDEDPpl/Questor/tree/DebugActivateWeapons

I will need the resulting logs when you experience the issue again. The logs will be spammy, but it shouldnt be too bad, a few days of logs would likely still be under a few MB... I hope =)

@oldmeat

Today again encountered this problem. Problems log in https://github.com/ISeeDEDPpl/Questor/tree/DebugActivateWeapons branch: http://pastebin.com/uGAUTB8j .
When i manually change old ammo in bay from exp to em, bot start work properly.

@ISeeDEDPpl
Owner

Until I can come up with a real fix... make sure you have at least 2 groups of guns.

@oldmeat

I have ungrouped all guns and the problem still exist. I opened two clients the same time on the same pc 2 different bots and I noticed with both of them are stuck at the same time. Of course,enough just group the weapon, reload or anything and everything returns to work

@ISeeDEDPpl
Owner

at the same time?! that is very odd...

@ISeeDEDPpl
Owner

can you generate that log again please. I need at least 3 min of it not working. in that log above it looks like it could have been waiting a timer to expire... Id need a longer log to confirm

The issue Dim experienced was a different issue and Dim's prob is now fixed.
Is this issue still occurring occasionally? If so please login to IRC and convo me when you have time to discuss.

@oldmeat oldmeat closed this May 3, 2012
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment