What's new
By:
  • Visit Rebornbuddy
  • Visit Panda Profiles
  • Visit LLamamMagic
  • Visit Resources
  • Visit Downloads
  • Visit Portal

Targeting/Casting Slow

Ah k thx 4 posting deathboy00 guess i wont be getting a Agent then.. :(
 
any current class that actually works botting with now?? no offence to the buddyteam :) i love u guys! waiting patiently for a fix :)
 
JoeBrewski said:
Ok, tried numerous solutions, and for me, it all seemed to end with a 'forced cast' (using a Cast called from another 'lib'). IF YOU HAVE AN IMPERIAL CARNAGE MARAUDER ONLY - you can try the attached. It's a bastardized version of the WingIt class script. Drop it into the appropriate advanced class folder for WingIt. It seems to have fixed my casting, and also erratic movement, issues. Uses a Sequence vs. a Priority Selector to first do the 'forced cast', and then does the movement, and remaining priorities. Again I'm sure this is not sanctioned by WingIt - it's just something that may get get you through until more dev is done on the Cast composite. If you have a marauder with another spec and going through hell, you can always respec, Imperial retrainer is in the NE quadrant of the station. Carnage only here.

EDIT: Cleaned up the script a little (alot of commented-out code previously resulting from various tests to see what would actually work).
Click to expand...

Thank you for the contribution, and I'm sorry its come to this.

The underlying cause is BWcore is pulsing the Behavior Trees at a ridiculously slow rate. On a 2.2 Gigahertz quad-core with 16GB of RWM, the combat Behavior Tree is being pulsed at as 2.3 hertz (cycles per second)--this number should be 30-50. I'm sure what is causing the slow pulsing is also responsible for slowing predicate evaluation in the Cast 'castWhen' causes. Since the two are intertwined, its hard to say specifically which is the cause.

I've spent several days trying to chase the problem, but can get no further than to isolate the problem to the BWcore. None of the work arounds I've tried have had any effect. I wouldn't even consider rewriting the Combat Routines in terms of Sequence--they are written in terms of PrioritySelector for very good reasons.

I've even gone so far as to try to 'profile' the code. Alas, this effort was fruitless because I don't have access to the BWcore's symbol set, and also the way Buddywing compiles & packages WingIt, much valuable information is lost in that process also.

Something significant changed between Buddywing drop 294 and drop 297. Even reverting WingIt as far back as changeset #601 (three weeks ago--the current changeset is #677), the 2-3 second delays in casting are still present. I'm convinced the problem is not of WingIt's making. I feel your pain, as it makes changes to WingIt pretty much untestable.

The solution you offer here is definitely a point-solution. It has bypassed a much of the LazyRaider and target selection system. The Sleep() is a major 'no no' for reasons I won't get into here. But I'm very glad it works for you, and possibly others.

I just wish someone would own this critical problem, and confirm it is being addressed at a high priority. I feel BW is going to lose the customers it has because of this problem. Alas, such priority decisions are not mine to make.

I've been out of town for over a week helping some family through surgery. I've been out-of-touch with Aevitas, Neo93, and the rest of the WingIt team. When I get back in town, I'll reconnect with them to see what can be done to help.


cheers
chinajade
 
Last edited:
I know for me its getting old. I have 3 swtor accounts, the 3 keys.
Only able to bot 1 at a time for long time now.
With this problem I cant bot at all. Ive been playing diablo3 for fun passing time. Just last night started wow back up botting it.
I just dont feel right unless I got a bot going. Lol. Sad I know.

If BW doesnt get fixed soon I will have to move on.

Hopefully fixed enough so I can finish the warrior class quest line.
 
You must log in or register to reply here.
Back
Top