~ Scheduled Maintenance Patch 3.2 AND 3.2a ~ 30 April 2015

[Altard]

I am getting bad lag on planets with a far draw distance (even with my clip plane alll the way down) like Makeb I lag really bad on where as Quesh and Voss I do not.

I have only been running the new version for a total of about 18 hours or so and I have experienced a total of 4 or 5 crashes most of them happening roughly 2hrs after starting up the bot.

The lag is noticeable with classes such as the Shadow since they have a sprint they commonly sprint towards a mob, run by it, then run back, running by it again and again and again... Usually leaving Theran to deal with the mob. I've honestly considered getting a DPS companion in the time being just to see the difference it makes.

Though I would say the lag is half as bad as it was in .638 which is nice. I can actually bot now versus before it just wasnt even worth my time.

Just got another crash after making this post, again roughly about 2hrs after starting up the bot

 

[wired203]

Questing is still broken... it regularly finishes a step and then hangs, just sitting there.

I've only tested the bot on Voss and Makeb so far. Voss has been the most stable, with only a couple of crashes hours apart... but Makeb is pretty unstable, with 4 crashes within 2 hours.

I haven't had a chance to play yet but is it finishes a step or doesn't collect the reward? I remember right before all of this occurred they were tweaking the reward code as it was amiss.

 

[cwhiz4]

I haven't had a chance to play yet but is it finishes a step or doesn't collect the reward? I remember right before all of this occurred they were tweaking the reward code as it was amiss.

I've only tested questing a little bit, but from what I've seen it stops after the next possible action.

IE, You start the profile and it determines you need to go pick up a quest... it will go pick up the quest and then just stop. Or if you need to go interact with an object, it will go interact with the object and then just stop.

 

[b2kBlaze]

I've only tested questing a little bit, but from what I've seen it stops after the next possible action.

IE, You start the profile and it determines you need to go pick up a quest... it will go pick up the quest and then just stop. Or if you need to go interact with an object, it will go interact with the object and then just stop.

exactly, and i bought trial of this crap yesterday, thought it works...

 

[slyguy]

I cant even use the bot as a routine base for operations etc, just crashes my game randomly everytime also barely any class routines even work. I guess the bot and routines are meant for open world use only?

 

[ludijak559]

The bot is still getting fixed, it crashes a lot

 

[Altard]

I cant even use the bot as a routine base for operations etc, just crashes my game randomly everytime also barely any class routines even work. I guess the bot and routines are meant for open world use only?

it can be used in them, they are probably broken from all of the changes the devs have been doing.

 

[slyguy]

it can be used in them, they are probably broken from all of the changes the devs have been doing.

Guess ill hold out a bit longer before I throw in the towel

 

[056]

I cant even use the bot as a routine base for operations etc, just crashes my game randomly everytime also barely any class routines even work. I guess the bot and routines are meant for open world use only?

What classes are you trying to use? What levels? Bot routines mostly need to be re-written a lot of them are way out of date using old stuff pre-3.0. They're not adjusted for leveling.

There's a few re-written ones in the forum that you can download and adjust. The way some classes work does not lend itself to the way the current bot base does rotations. I cannot get AP to work for Mercs because I can't find a way to program a burn phase without the ability to look at cooldowns. (i.e. if Vent heat on CD do low heat rotation, if vent heat not on CD do that high heat rotation)

The default Merc Gunnery/Assault rotation was crashing me because it was either attempting to interrupt or to change stances. I blocked those lines from the script and reduced my crash rate.

What are the stats on your machine? Are you running at high priority? (Both SWTOR and BW)

I get very rare crashes in raids and flashpoints, but I am very used to the particularities of using the bot in instances. You need to have the bot stopped while you zone. Log in, open bot, log into bot, zone in to instance, start bot, restart bot if become unhooked, kill stuff, stop bot, zone out.

The bot sometimes crashes and becomes "un-attached" sometimes on Zoning. Only start the bot when you're inside of an instance. You need to stop the bot before you rezone. Then you need to close the bot before leaving the instance.

It's kinda always done this. Back in 2.0 Joe's combat used to freeze the machine up on zoning out of a KDY. Joe had a hotkey built into the routine to un-attach the bot when this sort of thing happened. DefaultCombat isn't quite that robust and it only rarely does that on zoning because it usually crashes.

 

[slyguy]

What classes are you trying to use? What levels? Bot routines mostly need to be re-written a lot of them are way out of date using old stuff pre-3.0. They're not adjusted for leveling.

There's a few re-written ones in the forum that you can download and adjust. The way some classes work does not lend itself to the way the current bot base does rotations. I cannot get AP to work for Mercs because I can't find a way to program a burn phase without the ability to look at cooldowns. (i.e. if Vent heat on CD do low heat rotation, if vent heat not on CD do that high heat rotation)

The default Merc Gunnery/Assault rotation was crashing me because it was either attempting to interrupt or to change stances. I blocked those lines from the script and reduced my crash rate.

What are the stats on your machine? Are you running at high priority? (Both SWTOR and BW)

I get very rare crashes in raids and flashpoints, but I am very used to the particularities of using the bot in instances. You need to have the bot stopped while you zone. Log in, open bot, log into bot, zone in to instance, start bot, restart bot if become unhooked, kill stuff, stop bot, zone out.

The bot sometimes crashes and becomes "un-attached" sometimes on Zoning. Only start the bot when you're inside of an instance. You need to stop the bot before you rezone. Then you need to close the bot before leaving the instance.

It's kinda always done this. Back in 2.0 Joe's combat used to freeze the machine up on zoning out of a KDY. Joe had a hotkey built into the routine to un-attach the bot when this sort of thing happened. DefaultCombat isn't quite that robust and it only rarely does that on zoning because it usually crashes.

Certain classes work but lag hard and by the looks since im only using it on low level chars the routines are not exactly doing anything decent on the ones that are running, swtor and bw are on high priority and when I get into instance I start bot and 9 1/2x/10 somewhere along the way (mostly towards beginning or instance) mt game crashes etc :/

Joes lags even harder than default and makes my game sound go haywire

i7-2630 @ 2.00GHz
8GB Ram
Radeon Graphics, unsure of specs

 

[Altard]

Any update on progress?

Its been awhile since one

 

[Michael4700]

From the official game forums:



And from Thursday, April 30th:



New Users: After the patch drops, Buddy Wing will not function until updated. Please be patient. Users can check Buddy Updates for a version number higher than 1189.638 to determine if the update is ready.

When available, patch notes will be found here: Patch 3.2a

Cheers,
-D

Can you give some new on the state of questing for leveling with the bot? Currently it will pickup the quest and then stop and still try to pickup the same quest even tho its already done so.

A "rough" ETA ... 2 weeks 3,4 etc?

Thanks,

/Michael

 

[ludijak559]

We are already w8ing for the fix for over 2 months so dont get your hopes up 2 much

 

[Michael4700]

We are already w8ing for the fix for over 2 months so dont get your hopes up 2 much

Wow ...thought it was just since middle of April.

Wont get my hopes up - would just be nice now that there is a 12xXP going again on class quests untill fall.

 

[alexio86]

Maintenance unscheduled today ... damn bioware


All servers will be unavailable on May 12th while we apply Game Update 3.2b

Date: Tuesday, 12 May 2015
Time: 5:00AM PDT (12:00 GMT) - 7:00AM PDT (14:00 GMT)
Version: 3.2b

During maintenance, all updates and additional information will be posted on our Twitter account. Thank you for your patience as we maintain service for Star Wars™: The Old Republic™.

 

[Altard]

Maintenance unscheduled today ... damn bioware


All servers will be unavailable on May 12th while we apply Game Update 3.2b

Date: Tuesday, 12 May 2015
Time: 5:00AM PDT (12:00 GMT) - 7:00AM PDT (14:00 GMT)
Version: 3.2b

During maintenance, all updates and additional information will be posted on our Twitter account. Thank you for your patience as we maintain service for Star Wars™: The Old Republic™.

yay~! This actually forces the developers to come here and answer our questions instead of ignoring us

<3