Main | Known Issues »

Change Log

0.0.5.0
Public Alpha 4a
- Added Kills Per Minute calculation. Kills are averaged over the last 5 minutes, so you’ll see lower numbers than you expect for the first couple of minutes.
- Added Time to Full Inventory countdown timer. This is based on Kills Per Minute and your average Kills Per Item for the current session. “Available Inventory” is defined on the PVE tab – by default this is 80 items, but you can change the value if you keep items in your inventory. Click the Reset button to start the counter over with a new inventory number.

0.0.4.3
Public Alpha 3d
- Fixed an issue where AstroMech would crash if you had DirectOutput enabled and only one PVP kill.

0.0.4.2
Public Alpha 3c
- Now pushing Credits per Kill to the X52 Pro MFD.
- Fixed player names in the PVP Kills list where the name contained a special character. The full first name of the player should now show up correctly.
- Limited the number of characters per player name on the X52 Pro MFD. This means the PVP Kills list will not be disrupted if a player’s name is longer than 12 characters.
- Removed Pilot XP from features list. Starship Combat XP shows up on the Quest tab in SWG, not as a System Message; adding support for Pilot XP would mean complicating initial setup. If you really want Pilot XP, please let me know. I may add it back in a future version as an option.

0.0.4.1
Public Alpha 3b
- Fixed duplication of player deaths, but only if player is using Timestamp Incoming Messages for chat in SWG. If you’re not using Timestamp Incoming Messages, you’ll still get the duplication. Due to the way SWG logs player deaths, there’s no way to accurately determine if a death is a duplicate without a Timestamp.
- Set threshold for duplication at 5 seconds. If a death occurs within 5 seconds of a previous death, AstroMech considers it a duplicate.

0.0.4.0
Public Alpha 3a
- Added confirmation dialogs on the MFD for some options (in previous versions, selecting Publish, Clear, or Replay on the MFD would pop a message box on the desktop that the player would never see)

0.0.3.1
Internal Update
- Added handler to fire events from MFD when AstroMech is minimized to the System Tray

0.0.3.0
Public Alpha 2
- DirectOutput functionality for all currently enabled counters
- Configuration page on X52 MFD has all commands present in GUI

0.0.2.1
Internal Update
- Preliminary implementation of DirectOutput
- Added Credits per Kill counter
- Changed systray icon when monitoring a log file
- Added all commands in GUI to systray context menu

0.0.2.0
Public Alpha 1
- Basic functionality
- No DirectOutput

0.0.1.0
Internal Alpha
- DirectOutput proof of concept

TrackBack

TrackBack URL for this entry:
http://astromech.idolatry.org/cgi-bin/mt-tb.cgi/42

Comments (4)

ajdin:

This is a great utility, but how do I keep separate tracks of 2 different toons?

Idolatry [TypeKey Profile Page]:

Thanks for the feedback. Multi-character options are on the to-do list, but it'll be awhile before I get around to it.

How would you want to identify each character in the UI? First name and server? Would you want an option to compile all characters' scores into an overall score?

(and I've just turned comment notification on, so I can tell when someone leaves a comment in the future - sorry about the delay)

Spitfire:

congrats on a brilliant piece of work,i am curious however as to what else can be "picked up" with your program?
like for instance is it possible to one day be able to see the different stats of your or your enemies ship... ie like damage % for different components etc (this would be nice so one doesnt have to bring up the ship page and hence be able to focus more on the job at hand)

Idolatry:

Thanks.

Currently I can only display the information that gets written to the chat log.

I'd love to be able to display a whole range of things (especially given that Saitek is about to release a series of mini-LCD screens), but SWG doesn't have the capability.

I had a conversation with one of the developers, and he said some sort of data extraction API would be nice to have but is low priority.

Post a comment

(If you haven't left a comment here before, you may need to be approved by the site owner before your comment will appear. Until then, it won't appear on the entry. Thanks for waiting.)

About

This page contains a single entry from the blog posted on June 7, 2007 4:22 PM.

The next post in this blog is Known Issues.

Many more can be found on the main index page or by looking through the archives.

Powered by
Movable Type 3.33