(1019Kb)

Updated: 09-17-14 05:27 AM

Add Favorite

Install Help

Portal

Bugs

Features

Compatibility:	Warlords of Draenor Pre-Patch (6.0.2)
Updated:	09-17-14 05:27 AM
Created:	02-16-10 12:26 PM
Downloads:	18,546
Favorites:	51
MD5:

Aloft Alpha

Version: Aloft-5.3.2-alpha3

by: acapela [More]

This is a "development" version of Aloft (the nameplate addon). Please refer to the main page for that addon for a comprehensive description.

This is an ALPHA release. That means it has not had a substantial amount of testing under all circumstances. By installing this version, you are basically agreeing to help test . Please report any/all bugs with this release in the comments section of this WoWInterface addon page.

This version of Aloft is functionally identical to Aloft-5.2.8-2574.

This version of Aloft is updated to work with WoW "6", aka "Warlords of Draenor", currently in beta test. All modules have been enabled, LUA errors fixed (mainly to do with obsolete spell IDs), and all the basics seem to work on the WoW 6.X PTR. There were not many changes required.

I now have Beta access, so am incorporating that into my testing.

This version of Aloft will probably not work on current live realms... there is at least one new spell that doesn't exist there yet (Storm Elemental Totem), plus several that have been removed.

5.3.2-alpha3 (Warlords of Draenor)
- fixed cast bar LUA error and configuration mode update issues
- updated Ace3 to latest/greatest (r1114)[/color]

5.3.1-alpha2 (Warlords of Draenor)
- updated/fixed "Nameplate Glow>Recently Damaged Only" functionality

5.3.0-alpha1 (Warlords of Draenor)
- for WoW 6.X PTR and WoD Beta

5.0.1-2418 (Mists of Pandaria)
- enhanced to cover monk/brewmaster tanking
- added a check to avoid divide-by-zero problems in the stacked points (combo points/etc) module
- fixed some divide-by-zero problems in threat management (the MoP threat system seems to zero out perdiodically, during fights)

5.0.0-2404 (Mists of Pandaria)
- changed GetNumRaidMembers() to GetNumGroupMembers()
- changed GetNumPartyMembers() to GetNumSubgroupMembers()
- changed (MiniMapBattlefieldFrame.status == "active") effectively to (select(IsInInstance(), 2) == "pvp")
- updated Shaman totem manifest and spell IDs
- added Monk class color (0x00ff96), class name, and associated options, to code and documentation
- added Pandaren race short form
- verified crowd control spell IDs, added Shaman "Bind Elemental" to crowd control spell IDs
- combined obsolete PARTY_MEMBERS_CHANGED/RAID_ROSTER_UPDATE events into new GROUP_ROSTER_UPDATE event
- no changes to Aloft related to GetGuildRosterInfo() (Aloft doesn't use all the arguments), or UnitIsGroupLeader() (Aloft previously updated away from deprecated functions)
- no apparent changes related to GetBattlefieldScore()/GetWhoInfo()/GetFriendInfo()

- TODO: add brewmaster tanking characteristics (for nameplate glow control)
- TODO: hunter trap snakes (specifically "Viper"; E/W Plaguelands and Uldum) and (possibly) DK bloodworms now seem to have names in common with some normal NPCs

4.4.9
- updated the cast warning module to detect animation update interval of 0 and use OnUpdate directly, instead of AceTimer-3.0 (seemns marginally faster/smoother)
- updated LibBabble-Faction-3.0 to latest/greatest (4.3-release32)
- updated Ace3 to latest/greatest (r1057)

4.4.2-2308
- merged in zhTW localization contributed by WoWInterface user aa9012456.

Comment Options

Page 13 of 17

« First

Last »

03-29-10, 01:29 PM

acapela

A Cobalt Mageweaver

Forum posts: 241

File comments: 1313

Uploads: 5

Originally posted by Viceversa
I've been trying to hide the name plate on the 'Drudge Ghoul' on the Lich King encounter but everytime i add it to the list i get

sorry for the delay in responding. this have been a bit hectic lately.

that error results from Aloft needing data for the "[PetOwnersName]" tag, and not being able to activate the module that provides it.

the most likely explanation is that somewhere in your text fields, you are using the text tag "[PetOwnersName]". a few other Aloft features look for data like this in an "implicit" fashion (for instance, hiding hostile/friendly pets, under Aloft's "Visibility" options, requires access to this data).

you can track down where that text tag is being used and take it out, or failing that, you can enable the "AloftPetOwnersName" module (under Aloft's "Modules" options). in general, the simplest solution will be to enable that module. you may need to reload your UI in the process.

hopefully that will clear everything up for you, but once that has been resolved, if you continue to have problems hiding nameplates by name, feel free to post again.

__________________
Retired author/maintainer of Aloft (the nameplate addon)
http://www.wowinterface.com/download...AloftBeta.html
-----
Zippy said it best: "All life is a BLUR of Republicans and Meat!"

03-29-10, 08:27 AM

Viceversa

A Kobold Labourer

Forum posts: 0

File comments: 12

Uploads: 0

I've been trying to hide the name plate on the 'Drudge Ghoul' on the Lich King encounter but everytime i add it to the list i get

Aloft: Unable to determine module providing data: petOwnersName

then the name plate is still there. This doesn't happen for the couple of other names i have hidden.

Last edited by Viceversa : 03-29-10 at 08:28 AM.

03-29-10, 08:03 AM
waha A Kobold Labourer Forum posts: 0 File comments: 112 Uploads: 2	It appears the option to disable startup messages is broken, nothing happens when clicking the checkbox in the options window. Took a peek at the lua code too (as Aloft spams its version 4 times every time I launch WoW), and it appears Aloft prints its version first once, and then again if the startup messages is enabled.

03-28-10, 06:47 PM
Intangir A Kobold Labourer Forum posts: 1 File comments: 35 Uploads: 1	[2010/03/28 19:35:25-1-x1]: Aloft-3.0.5-1709-enUS\AloftHealthBar\AloftHealthBarDeficit.lua:136: attempt to perform arithmetic on local 'value' (a nil value) Aloft-3.0.5-1709-enUS\AloftHealthBar\AloftHealthBarDeficit.lua:239: in function `?' CallbackHandler-1.0-5 (Ace3):147: in function <...Ons\Ace3\CallbackHandler-1.0\CallbackHandler-1.0.lua:147> <string>:"safecall Dispatcher[2]":4: in function <[string "safecall Dispatcher[2]"]:4> <in C code>: ? <string>:"safecall Dispatcher[2]":13: in function `?' CallbackHandler-1.0-5 (Ace3):92: in function `SendMessage' Aloft-3.0.5-1709-enUS\Aloft\Aloft.lua:1187: in function `SetupNameplate' Aloft-3.0.5-1709-enUS\Aloft\Aloft.lua:508: in function `ProcessChildFrames' Aloft-3.0.5-1709-enUS\Aloft\Aloft.lua:519: in function `Update' Aloft-3.0.5-1709-enUS\Aloft\Aloft.lua:348: in function <Interface\AddOns\Aloft\Aloft\Aloft.lua:348> (tail call): ?: <in C code>: ? <string>:"safecall Dispatcher[1]":9: in function <[string "safecall Dispatcher[1]"]:5> (tail call): ?: AceTimer-3.0-5 (Ace3):166: in function <Interface\AddOns\Ace3\AceTimer-3.0\AceTimer-3.0.lua:138> ---

03-27-10, 08:00 AM

Limb0

A Cobalt Mageweaver

Forum posts: 220

File comments: 298

Uploads: 5

Originally posted by acapela
the visual artifact on health bars, near death, may be related to the LUA error (i.e. if a LUA error is encountered, graphical updates may also not be performed properly). have you noticed whether these two problems are associated in any way?

The error is usually popping up when no hostile nameplates are within range to be visible. It usually happens once, and only when I'm OOC, mounted, or in stealth. I get the error in Dalaran, any BG, Arenas, and while flying in Northrend.

The texture issue occasionally substitutes near full hp bars as well now but seems separate from the lua error.

__________________

Masque: Renaitre, SharedMedia: Renaitre
Tidy Plates: Renaitre and DHUD4

03-26-10, 07:28 PM

break19

A Flamescale Wyrmkin

Forum posts: 116

File comments: 99

Uploads: 3

Of course, if your system is so low on memory that +/-1.2M of memory is a problem, then you should seriously consider upgrading your machine. I mean, WoW claims a minimum of 512Meg for windows, and 1GB for mac OSX.. if 1.2M is an issue..... well..

Originally posted by acapela
yeah, the module LUA code itself is still loaded, even if the module is not enabled. the LUA code is never executed, in this case, but it is still sitting in memory (and i expect it is paged out the whole time).

if you really want to take the chance, and you believe that 1.2Mb will really make a difference to your game experience, deleting the files from the Aloft install directory would prevent that LUA code from even loading (which would recover some memory). there will be some errors on game startup (generated out to the WoW client log file), but other than this you might well be perfectly OK.

03-26-10, 02:23 PM

acapela

A Cobalt Mageweaver

Forum posts: 241

File comments: 1313

Uploads: 5

Originally posted by shinx
if i uncheck unwanted modules ingame by aloft setting my memory usage stay at 2mb but if i delete unwanted modules in the aloft ordner my memory usage drops from 2mb to 0.8mb

yeah, the module LUA code itself is still loaded, even if the module is not enabled. the LUA code is never executed, in this case, but it is still sitting in memory (and i expect it is paged out the whole time).

if you really want to take the chance, and you believe that 1.2Mb will really make a difference to your game experience, deleting the files from the Aloft install directory would prevent that LUA code from even loading (which would recover some memory). there will be some errors on game startup (generated out to the WoW client log file), but other than this you might well be perfectly OK.

03-26-10, 08:28 AM
shinx A Defias Bandit Forum posts: 2 File comments: 75 Uploads: 0	HI, im not rly good in english , sry ... if i uncheck unwanted modules ingame by aloft setting my memory usage stay at 2mb but if i delete unwanted modules in the aloft ordner my memory usage drops from 2mb to 0.8mb. bb

03-25-10, 06:22 PM

acapela

A Cobalt Mageweaver

Forum posts: 241

File comments: 1313

Uploads: 5

Originally posted by Limb0
To add to this, when players/mobs get to an almost dead hp, the texture of the bar changes as well.

the LUA error is being worked on. hopefully not too much longer.

the visual artifact on health bars, near death, may be related to the LUA error (i.e. if a LUA error is encountered, graphical updates may also not be performed properly). have you noticed whether these two problems are associated in any way?

03-25-10, 06:21 PM

acapela

A Cobalt Mageweaver

Forum posts: 241

File comments: 1313

Uploads: 5

Originally posted by shinx
hi, aloft does not unload modules if they are uncheckt, i delete all modules manualy they are not in used and now my memory usage drops from 2 mb to 0,8 mb

you have to reload your UI in order to actually get rid of the modules (the modules consist of dynamically loaded LUA code... hard to release that after it has been allocated).

i don't quite understand what you are saying about how your memory usage changes. are you saying that after you disable modules, your memory usage is reduced? if so, that is the desired outcome.

03-25-10, 04:45 PM
shinx A Defias Bandit Forum posts: 2 File comments: 75 Uploads: 0	hi, aloft does not unload modules if they are uncheckt, i delete all modules manualy they are not in used and now my memory usage drops from 2 mb to 0,8 mb, can you take a look what happend?

03-25-10, 03:59 PM

Viceversa

A Kobold Labourer

Forum posts: 0

File comments: 12

Uploads: 0

I've been trying to hide the name plate on the 'Drudge Ghoul' on the Lich King encounter but everytime i add it to the list i get

Aloft: Unable to determine module providing data: petOwnersName

then the name plate is still there. This doesn't happen for the couple of other names i have hidden.

03-25-10, 01:00 PM

Limb0

A Cobalt Mageweaver

Forum posts: 220

File comments: 298

Uploads: 5

I'm experiencing a Health Bar Deficit error as well in both BGs and Raids..

Code:

"errors"] = {
		{
			["message"] = {
				"Aloft-3.0.5-1709-enUS\\AloftHealthBar\\AloftHealthBarDeficit.lua:136: attempt to perform arithmetic on local 'value' (a nil value)\nAloft-3.0.5-1709-enUS\\AloftHealthBar\\AloftHealthBarDeficit.lua:239: in function `?'\nCallbackHandler-1.0-5:146: in function <...end\\libs\\CallbackHandler-1.0\\CallbackHandler-1.0.lua:146>\n<string>:\"safecall Dispatcher[2]\":4: in function <[string \"safecall Dispatcher[2]\"]:4>\n<in C code>: ?\n<string>:\"safecall Dispatcher[2]\":13: in function `?'\nCallbackHandler-1.0-5:91: in function `SendMessage'\nAloft-3.0.5-1709-enUS\\Aloft\\Aloft.lua:1187: in function `SetupNameplate'\nAloft-3.0.5-1709-enUS\\Aloft\\Aloft.lua:508: in function `ProcessChildFrames'\nAloft-3.0.5-1709-enUS\\Aloft\\Aloft.lua:519: in function `Update'\nAloft-3.0.5-1709-enUS\\Aloft\\Aloft.lua:348: in function <Interface\\AddOns\\Aloft\\Aloft\\Aloft.lua:348>\n(tail call): ?:\n<in C code>: ?\n<string>:\"safecall Dispatcher[1]\":9: in function <[string \"safecall Dispatcher[1]\"]:5>\n(tail call): ?:\nAceTimer-3.", -- [1]
				"0-5 (Aloft):166: in function <...face\\AddOns\\Aloft\\Libs\\AceTimer-3.0\\AceTimer-3.0.lua:138>\n\n  ---", -- [2]
			},
			["type"] = "error",

To add to this, when players/mobs get to an almost dead hp, the texture of the bar changes as well.

__________________

Masque: Renaitre, SharedMedia: Renaitre
Tidy Plates: Renaitre and DHUD4

03-25-10, 10:40 AM

acapela

A Cobalt Mageweaver

Forum posts: 241

File comments: 1313

Uploads: 5

Originally posted by Intangir
ive also been getting an error in AloftHealthBarDeficit

i have a fix in i am testing (LUA error traces are very helpful, at least the first few lines, they can direct me to the specific line in the specific file), and will be trying to reproduce to make sure there are not any more problems (especially running past/through a large number of mobs).

if you have a LUA trace (from BugSack or TekError or whatever), feel free to send it to me in a PM (or post it here, either way). either that or confirm it is the same error that the other user experienced (for which they posted the LUA trace).

the cast bar is showing the flickering as it casts (flickers between full and its actual %) and im not using a blizz texture for that one.. or at least i set it to x-perl's 8th texture

yeah, this has been a problem from the beginning in the Ace3 version (specifically the flickering, at least), not related to these most recent WoW 3.3.3 problems.

this probably doesn't need "fixing", since the whole cast bar needs to be replaced (and the Blizzard cast bar, which is flickering, will be hidden) to fix the WoW 3.3.3 issues (texture tile/clip, etc). i don't expect the cast bar replacement to exhibit any flickering.

03-25-10, 12:52 AM
Intangir A Kobold Labourer Forum posts: 1 File comments: 35 Uploads: 1	ive also been getting an error in AloftHealthBarDeficit but the issue with the the healthbar is fixed (i used non-blizz texture for healthbar already) the cast bar is showing the flickering as it casts (flickers between full and its actual %) and im not using a blizz texture for that one.. or at least i set it to x-perl's 8th texture Last edited by Intangir : 03-25-10 at 12:52 AM.

Page 13 of 17

« First

Last »

Report this File

Category Jump:

Support AddOn Development!

You have just downloaded by the author . If you like this AddOn why not consider supporting the author? This author has set up a donation account. Donations ensure that authors can continue to develop useful tools for everyone.

[Disable these notices]