Quantcast
 
Results: 6Comments by: redx25
File: FreeUI08-30-12
I don't understand. What your WoW b...
Posted By: redx25
I don't understand. What your WoW basically thinks is that your resolution is 720x576, which is far smaller than what it actually is. This causes the auto UI scaler in FreeUI to mess up. Until Blizzard fixes it, you can simply delete the entire part beginning from 'resolution support' in core.lua, then go to the ingame options and...
File: FreeUI08-30-12
redx25; I might be on to something....
Posted By: redx25
redx25; I might be on to something. Can you open up the core again and add a few more prints after the 'scale' variable: print(({GetScreenResolutions()})) print(GetScreenHeight()) Let me know what comes out. 720x576 1097.1427753993 Also, do you have your resolution in WoW set to a lower resolution than what y...
File: FreeUI08-30-12
@Haleth: The output was 1462.8571...
Posted By: redx25
@Haleth: The output was 1462.8571864537 1 1.3333333333333
File: FreeUI08-29-12
knas; customPoint, not costumPoint...
Posted By: redx25
knas; customPoint, not costumPoint :) @ redx; That's very strange indeed. When I set my WoW resolution to your resolution (1600x1200) it doesn't do that. If you disable all other addons, does it still happen? Also, are you playing on a Mac? Just tried with everything but freeui off and still no luck. I'm on Windows 7.
File: FreeUI08-29-12
redx25; Can you take a screenshot?...
Posted By: redx25
redx25; Can you take a screenshot? Degausser; You can change the sFilter table in options.lua and use it to display any kind of buff. There is no included alerter for cooldowns. This is what it looks like whenever i log in/ reload ui http://i.imgur.com/qyuzA.jpg This is what keeps changing http://i.imgur.com/Pbxey.jpg...
File: FreeUI08-29-12
My UI scale is resetting to max whe...
Posted By: redx25
My UI scale is resetting to max whenever i login or reload if I have freeui enabled. I'm not getting any lua errors either. There is also a error with using custom points for sFilter tracking. It had unpack(customPoint) and changing it too data.customPoint fixes it.