Jump to content

QuickBunnie

Members
  • Posts

    74
  • Joined

Everything posted by QuickBunnie

  1. I wanted to update the Jaesa mechanics since there is some confusion. I have been testing this, and am not finished, but I will update this post when I do. I started as a Light 1 Sith Juggernaut and have been escaping out of the Hutta quest, resetting it and running it again after BT repetitions to reduce my alignment. EDIT: Didn't go far enough into the dialog tree before, but at least as a -50 SW, I was able to get DS Jaesa - with bugged codex however. I was going to just romance Vette and be good, but she was really annoying to me.
  2. Yeah - I could see how this would be advantageous for hutball. In Alderaan and Voidstar I think it is a disadvantage. But your point is taken. Anyways, its a team game, so I guess the point is to stun where its useful and not just a 1v1 in the middle of nowhere. Plus, I've been thinking about it, and it might actually be a game mechanic issue as well. If the target wasn't rooted/stunned before the charge, they could be out of your combat zone before you ever get there - not to mention you would be jumping to the middle of nowhere. In light of this, I think that the root/stun taking place before the jump makes sense. Now all I ask is that the duration is increased lol
  3. I did not notice this until I specced into the stun version for force charge, but it appears the stun begins as soon as you hit the button. Force charge's animation takes place, but it shaves a good chunk of the stun time off that should be within your "combat zone" because the animation can take a while. Target enemy -> Force charge -> Enemy is visibly stunned -> Warrior leaps to stunned enemy -> less than 1 second later, the enemy is no longer stunned. I hope this is not intended - Georg Zoeller has specifically stated that Juggernaut/Gaurdian is underperforming. A primary problem was that they were being kited around and unable to effectively keep an enemy within their combat zone. This effectively reduced the stun duration with which a Juggernaut/Guardian can actually keep an enemy in their combat zone. Also, please note, this happens with even with mobs, and not just PvP. It's just never that big of a deal with mobs, since they don't kite anyways.
  4. Are you sure? Why was this added with the patch then? Automated defense turrets have been added to Empire and Republic taxi spawn points.
  5. How many level 50's do you think there are on a 1-week old test server that has the ever-possibility of getting character wipes? No character transfers, remember? This was a theory-crafted patch. It was unable to be tested in a live format, and as such, it certainly didn't perform as theorized. The best plans of men and mice often go awry
  6. This was awesome! I hope there are a lot more of these, personally. Even though I didn't participate in this at all, this was by far my favorite thing that has happened in SWTOR so far. Keep up the good work!
  7. That's V-sync. It matches to the native frequency of your monitor - typically 60 if possible. If your GPU can't stay above 60, V-sync has to drop down to 30 to prevent tearing. Turn V-sync off if you don't want this feature. V-sync prevents tearing (basically an artifact generated by moving while a frame is being rendered, causing the top half to be rendered a split second earlier than the bottom half, which renders a different position because you moved). The benefit is that at 60 Hz, its good - no tearing and you get as much information as your monitor can handle - 60 Hz for most, some can do 120Hz. The drawback is that if you can't maintain above 60, it will drop you down to 30 so that it forces 2 monitor refreshes per frame rendered. For some, the no tearing is worth it. For others, the lost frames are too precious. If you're unhappy about how it looks at 30, turn V-sync off and see how it looks.
  8. The biggest boost in performance has got to be shadows - turn those off and the game is considerably less stressful. It also happens to be the most significant visual effect that you can immediately see (other than resolution maybe). Bloom in the beta was also pretty resource intensive. Tom's hardware has a good overview on GPU performance: http://www.tomshardware.com/reviews/star-wars-gaming-tests-review,3087.html
  9. Perhaps a Dev could make a clarification
  10. Hmm I don't know details, but in the beta, I heard that the PVP gear was nearly as good as the top raid drops. Something like rating 136 for PvP vs rating 140 for nightmare operations. The podcast I actually heard that on said that it was a problem since PvP top gear only required time, whereas the nightmare operations were actually tough to complete. They basically said rewarding grinding and accomplishment should be somewhat greater than rewarding grinding only, but currently that difference (though it exists) was not substantial enough. Doesn't actually answer your question, but that's what I know. Hope it helps a little.
  11. Can you have the same legacy name as one of your characters first names?
×
×
  • Create New...