Stellyx

Citizen
  • Posts

    2
  • Joined

  1. [ QUOTE ]
    Any one have endurance numbers for Phase Shift?

    [/ QUOTE ]

    Did some testing this weekend to find out the numbers for invis and phase shift, neither of which I see on the chart.

    Phase Shift is an end hog - easily the most expensive toggle I've found in the game. I did five tests, and with NOTHING else running, I ran out of endurance in 75, 76, 76, 76, 77 seconds. That's too fast to be very precise... but it yields a rough approximation of 2.98 EPS... yikes!

    I tested Invisibility a number of different ways:
    1) Invis by itself running -- after 15 minutes, the bar was still at the top.
    2) Invis + sprint: power down at 550 seconds. Taking the posted value of .35 for sprint, Invis comes out at ~1.502
    3) Invis + Maneuvers: power down at 336 seconds. Taking the posted value of .45 for maneuvers, invis comes out at ~1.518
    4) Invis + Assault: power down at 335 seconds. Taking the posted value of .44 for Assault, invis comes out at ~1.528
    5) Invis + Assault + Maneuvers: power down at 131 seconds. Using .89 for Assault + Maneuvers, invis comes out at ~1.543

    Side note: If Maneuvers and Assault are indeed different EPS, I should have seen a ~13 second change in the time-to-power-down on my invisibility test when I used them individually, but I didn't. The only difference was within the realm of testing error (one second), which makes me think that contrary to the postings here they ARE the same value. Furthermore, that the value is probably .46 EPS as was posted at the top of the thread, not .45/.44 as was in the latest one. Using .46 for each gives the following results:

    1) no change
    2) no change (~1.502)
    3) Invis + Maneuvers (.46): Invis ~= 1.508 (would yield 335.57 sec)
    4) Invis + Assault (.46): Invis ~= 1.508 (as above)
    5) Invis + Maneuvers + Assault (.46): Invis ~= 1.512

    These values make all of my observed data consistent in a way that the lower/different values cannot, so I trust them far more. It's not a MAJOR difference, but it is enough to screw up other calculations if people are running leadership toggles plus X to try and get a value for X...

    Anyway... If you go with the more consistent set of data, then Invis ~= 1.51 for all tests. It would make more sense to me if Invis were 1.5 and Phase Shift 3.0 (instead of 1.51 and 2.98, as I calculated), but who knows what's in the developers' minds?

    I've got an unused respec sitting around, so I think I'll go to the test server and try picking up Stamina, superleap, and whatever else I can get for my existing build, then give it another try to see if I can get the numbers to match. Will post the raw data here. In the mean time... great thread, nice numbers, and I hope this helps.
  2. The VB program works superbly. I used it last week so I could make a set of binds for MOUSE5, and it functions as advertised.

    One thing to remember (which I forgot, and which isn't specific to this program) is that you cannot have a path with spaces in it, so no using 'Program Files' anywhere in the path, or the bind_load_file will treat it as the end of one argument and the beginning of another... so it will cack, as it only expects one. Other than that self-induced annoyance, I am VERY grateful to you for creating this and making it available to all of us. Many thanks, and five stars.