Quote:
Originally Posted by tjubutsi
The actual rendering toggle:
Code:
func toggleRendering()
if not $botInitialized then return
$renderingDisabled = not $renderingDisabled
if $renderingDisabled then
disableRendering()
winSetState(getWindowHandle(), "", [MENTION=330060]Sw_[/MENTION]HIDE)
clearMemory()
else
enableRendering()
winSetState(getWindowHandle(), "", [MENTION=330060]Sw_[/MENTION]SHOW)
endIf
endFunc
|
To be honest, i've never seen that kind of flag for the winsetstate-func.
Could you try this one please:
Code:
WinSetState(GetWindowHandle(), "", [MENTION=330060]Sw_[/MENTION]SHOW)
WinSetState(GetWindowHandle(), "", [MENTION=330060]Sw_[/MENTION]HIDE)
I verified the en-/disable rendering func in your GWA2 and its exactly the same i use.
It can by a Problem caused by Windows 10, not sure; but im still on Win7 so i can't test and me and a couple of other people don't have any Problems so far.
The only problem i've heard from while disable rendering is that some model-states can't be read in a proper way.
But if simple moveto get skipped thats really strange.
BTW: ClearMemory() does not work the way its supposed to do. AFAIK it just frees memory from gw-process, but doesn't frees the memory from windows.
I recommend to do it this way: when the bot zones/loads map just enable rendering some (1-2) seconds before, do your map-load/zone while rendering is enabled and disable rendering when map is loaded. So your GW-Client can clear unused memory in a good way.
Edit: Forgot what i said with WinSetState ... seems like this board cant "write" the @-symbol.