[Dugi]

try 1.112 now

[Dugi]

should be there now 

[Dugi]

it doesn’t seem to be recognizing the 2h axe, I have tested 2H axes and it seems to be working just fine. 

try typing /dugi fix 

try deleting WoWCache folder completely. 

[Dugi]

we’ll fix that up 

[Dugi]

You can get a refund without the excuses, open a ticket. 
see screenshot 

and look like blizzard swapped the ironforge portal location with exodar for some reason, we’ll fix that up. 

[Dugi]

this should be fixed now 

[Dugi]

Our installer no longer use Java for sometime now , are you using latest versions? 
https://www.dugiguides.com/dgmembers/

[Dugi]

can you test with a brand new character.
are you using any macros? can you try deleting all your macros (save them to a txt file) and try without any macro. 

[Dugi]

kbdcb said:

Hi Dugi,

I updated to the latest version last night and my frames per second went from 100 to 16. Has anything changed? Using a lot of RAM.

can you provide steps to replicate the issue with only Dugi enabled. 

[Dugi]

lessspamless said:

Problem on classic.

Hi you only have the wow retail version, you need to purchase the WoW classic guide and reinstall 

[Dugi]

sandwich62 said:

mine finally updated but now missing labels on minimap. Possibly another conflict with SpartanUI?  Worked great before update, but now…not so much.

screenshot please 

[Dugi]

 sorry for the trouble, should be fixed now

[Dugi]

There is a fixed mode where it appears below the model viewer 

[Dugi]

it shouldn’t do this, can you try to reset the ban list, perhaps the 2hander you’re currently using is also in the banned list but equipped.

[Dugi]

this should be fixed now 

[Author]

Posts