hello handnavi, i've encountered huge fps drops in UBRS even on minimal settings :C any thoughts? [17:43:18.264 N] Honorbuddy v2.5.12061.757 started. [17:43:30.389 N] Logging in - Pastebin.com
Mh, there are no errors in your logfile. Can you try to reduce your Ticks per Second? 15 should be okay. I will try to run UBRS this weekend and see if i can improve some functions - but not sure if i can find time this weekend.
Handnavi, always much love on your work. Question: When I switch off Rip cycle the routine still wants to apply rip. How can I get it to only keep Roar up and FB with extra points? Thanks in advance.
You cant. It will apply Rip since its part of the basic rotation. The Rip cycle check mark is only used in multi dotting scenarios, where multiple targets can have a rip up on them. Why would you want to turn off rip?
Is this something that can be implemented? For PVP and from what I've heard in Raiding, players who stack Crit find their dps increased when dropping Rip from their rotation completely. Don't quote me or ask for specific numbers to prove that, but if that's the case it would be a good option to have.
um to explain further, ur cc is excellent, my needs are for farming purposes, as i am stacking run speed bonus and enchants i am running feral as my farmer, i wold like for it to be able to use dash and roar on cd as to further boost his farming speed. thanks
Hey Handnavi, I'm not sure why, but my DPS on trash in heroic dungeons is atrocious. Am I not using the right settings? I have everything at default.
v168? If so, im not experiencing anything as described above. You know the procedure, if you think something is wrong, post logs please.
I'm noticing the rotation is really slow - I mean it takes a few seconds between spells, which is resulting in less than 6k dps in Guardian spec... normally I do about 18k by myself. I have no errors, or anything to report... what can I do to fix this?
You can attach a log. By the sound of it, its either the bot base, hard lock or mesh issues. Without the log its hard to tell. Make sure you are using Enyo bot base, its free @ Buddy Store. Make sure to enable hard lock at at least 15 TPS. Let me know if you are using movement support, as the meshes can introduce problems into the routine. Also that Aoe 0 mobs setting. Lel. Tell me you use spells other then trash, lacerate and pulverize
I'm just using grindbot - and I should still be using Enyo? The bot is having issues targeting extra mobs too, it will just sit there and let stuff hit it. Why is this a paid routine if it doesn't work?
Because it is the greatest routine for HB period? And it works fantastic for what it is meant for. If you were to raid, you would not agitate the author by posting stupid shit. And no, you cannot use Enyo while using grindbot. You do have to enable hard lock in settings to make sure routine is given all the resources for best performance. Post a log and you will be helped, possibly to fix all your issues. Bitch again without a log, get ignored.
Still pretty low - it went up to 8k dps. and still, anytime it attacks the robot guys in SMV>Darktide Roost, and the gnome engineer pops out of its dead head, the bot ignores it and just stands there letting it hit him. log: Edit: This is with a fresh install
Hi handnavi, I noticed my routine was Thrashing as soon as I selected enemy mobs today, even if I was out of combat and they were out of range :s I don't think it's a setting because I put it to default and the same problem occured. Sorry for such a big log Thankyou for your help!!
Hey olfson, please post a complete logfile next time. Also upload the logfile here, i wont click on any third party websites. You can .zip the file if its too big for uploading.
Hey Areli, isnt the routine working correctly, or is it pushing buttons and we are still low? Our burst AOE dmg is low (very low!) compared to nearly all other classes / specs. We are really strong in single target and 2-4 add fights (if the adds live a little longer...) It might be the case that it isnt using our aoe spells correctly, because some meshes are wrong or not there. Then it might not detect all enemies in range. But still: i think its the szenario described above.
