Iza Gilneas posted that he was no longer going to support VuhDo
His post is dated 4/25/2014. The last file release was 9/15/13. Are there any plans for another author to pick this up and keep it going?
I saw one ticket expressing interest in maintaining the project, but I don't know the person posting and he's not in the Authors list.
Any word on this for WoD?
- Registered User
Member for 13 years and 9 months
Last active Mon, Jan, 29 2018 00:45:39
- 0 Followers
- 11 Total Posts
- 0 Thanks
Oct 19, 2010Reposting my reply in my ticket thread here.Posted in: General AddOns
Thanks, I will load this in to debug and test for you.
The way things are working out now with Druids in the raid,Pallies are only really buffing Might. Kings and Mark of the Wild overwrite each other. This is really annoying especially with the "consolidated" buff icons, so I hope you find a way to integrate with MoTW.
Was raid healing in Beta last night, I really have come to rely on the Beacon Tracking icon. And the other buff tracking functions will be helpful. We are going to be going back to" old school" raiding, where Hand of Freedom and Hand of Protection rotations may come back into play.
I really don't think integration with Pallypower is an issue anymore. There aren't improved buffs, or class buffs, so I don't think a raid leader is going to miss setting those buffs at all.
With no more "short" buffs, the entire raid is going to get their buffs refreshed if there is a battle rez, or the rez-ee is just going to go without. Sad loss of function there on Blizzard's part, but I think Paladins won't mind losing the headache!
Jan 24, 2008I've been having trouble with Grid since the pet layout was merged in. Last night with r59048, I had the game DC a couple of times in Gruuls.Posted in: Grid & Grid2
Today after clicking to show pets, I started D/C'ing everytime a hunter landed or started flying and the layout attempted to change for their pets popping in or out. ie. the game would close to the external error reporter. This was in a party group and was happening when folks were in or out of range.
I attempted to turn off the pet options, but because of the constant disconnects, the changes were not saving. I finally reverted to r57348.11. I'm still getting the occasional nil value error. But am not disconnecting so far.
I'm running Bigwigs r59126, oRA2 r59090, Clique r92, and PallyPower r59082 along with Grid. No other mods.
The error is almost always a Sigbus error.
I recall Maia suggesting it was a graphics problem and I'm willing to concede that this is a possibility. I'm on a Mac with a Radeon 9600 Pro graphics card with limited upgrades available. (the only card available was buggy and is now discontinued since AMD bought ATI). So at this point in time, the video card upgrade isn't a viable solution.
I'm just curious why this combination of mods is forcing this error, when it did not do this before the 2.2 patch.
Is there a work around ? I really don't want to go looking for new mods as I like the Grid+Clique combination.
Dec 1, 2007Posted in: Grid & Grid2Quote from maia »
this sounds very strange - Grid does not have any specific layout code, it's all handled by the blizzard code. It should be completely irrelevant if you display the first two, three or five groups.
I"ll do some experimentation and see if I can narrow down the problem. Thanks for the prompt response.
How does the Grid Raid Layout setting tie in or call the Blizzard code? ie: what should I be looking for? The Error looks like:
Error Code: 0x85100086
Error: signo: 10, Fault address: 0x0000000c, code(1): Invalid address alignment.
Exception State: exception=3 dsisr=1073741824 Fault address=$0000000c
Dec 1, 2007Posted in: Grid & Grid2Quote from maia »
Holypally, if you're not using any additional Grid modules, and if you can confirm that you only have the problem with the layout setting "By Group 25 w/tanks", but not with "By Group 25", then it must be related to the definition of the first column: ...
Most notably the crash out of WoW to the error reporter happens when I forget I've got the Raid layout at 10 for Karazhan and accept an invite to a Gruul's Lair raid without setting the layout to 25 before receiving the invite.
Last night, I had the layout set at 15, and crashed on invite for a Karazhan raid.
So far the only time I have NOT locked up and D/C'd out of WoW was when I had the raid layout set to 25. I can then set it for 10 or whatever size is needed after zoning in.
This also occurred without CT_RaidAssist installed and no CT variable files in the addon folders.
I am not using any additional Grid Modules.
Nov 30, 2007I am new to Grid. I started using it after WoW patched to 2.3. I run it with Omen, BigWigs, Clique, PallyPower and CT_RaidAssist.Posted in: Grid & Grid2
Since patch 2.3 I've been experiencing a lockup and disconnect when receiving a Raid Invite when my Grid raid layout is set for less than a 25 slot raid. This leaves my character ghosting until I reconnect.
To be able to zone in when this happens, I have to relaunch, drop raid, make certain I have Grid set to 25 slot raid layout, then rejoin the raid group. I don't recall if I am in the same zone as the Raid Lead, but I believe the problem persists regardless of location.
I can see how trying to stuff a 25 person raid into a 10 slot layout might cause difficulties, but why does it do the same for Karazhan? (And the raid was only put into parties 1 and 2, not spread over the 8 possible parties ... as some raid leads divide by class before balancing the raid.)
This problem seems to exist without PallyPower or CT_RaidAssist running. As long as I have the 25 slot layout selected, I don't have a problem. However, the 25 with Tanks does cause the disconnect.
This most recently happened running Grid r55787.1, Omen r55025.16, BigWigs r56200, Clique r92, Pallypower r55223, and CT_RaidAssist (v2.005). I am on a Dual 2G PowerMac G5 with 2.5GB RAM and OS X 10.4.11.
I searched topics and see where there were reports of a similar problem in July ... back about page 64 of this thread. My apologies in advance if this issue is addressed elsewhere, and could I please have a pointer to that discussion, if it exists.
Oct 10, 2007Update on Mac crash issue on playing Mod Sounds.Posted in: Raid AddOns
Blue poster moved Sticky posts around. They are reproducing the problem in house. Tigerclaw posted this morning that the crash seems to be limited to playback of custom MP3 files but not .wav files. So one of the suggested work-arounds is to resave custom MP3 files to .wav format.
The other work-around is to run a macro on login to disable custom sound playback calls.
Oct 10, 2007I posted in the Omen bug reports thread about a PlaySoundFile command in mods crashing the Mac client after Patch 2.2.3.Posted in: Raid AddOns
I'm not certain which developers monitor specific threads. This problem exists with BigWigs and most likely with Omen as well. So apologies if this post is redundant.
Oct 10, 2007As of WoW patch 2.2.3 "Mods that use PlaySoundFile to play custom sounds may crash the Mac client. Stickying this thread for information gathering."Posted in: Raid AddOns
It appears that either or both BigWigs and Omen are crashing in boss fights.
The workaround for this issue on the Mac Client is to either disable the mod or disable Sound in Wow. There is a Sticky Blue post in the Mac Tech Forum:
And an additional lengthy thread in the same forum:
Oct 7, 2007Posted in: Raid AddOnsQuote from Antiarc »
The pet bug and the invisible bars have been fixed. I'm looking into the crash assertation, but I don't have a Mac, so I'm not sure where to even begin with the bug. I'll see what I can do though.
Looks like Blizzard will silence the assertion in the next update. Blue recommends folks use the latest update on Omen.
See item 2 in reference post Known Issues in 2.2.0/2.2.2
- To post a comment, please login or register a new account.