Sorry, I didn't see this until now... I really appreciate you having looked into all of this and responding.
I'm still seeing the regular lag spike in 4.5.1. Toggling between Sidebar and Menus fixes it just like before.
Printable View
I ran my checks in the TEST channel before 4.5 was released and was not able to see lag spikes when I had about 10 modules loaded. In anycase I dont run persistent pulsing checks for anything in my code. There are some events I monitor and if those are causing it thats API side I can't resolve. I updated the event specific to this to use the same one that JPG used for the new "Books" of theirs for 4.5.
Hey there, just curious if there's any compatibility between this extension and extensions that add new menu options, such as Timer. As it stands, the timer button does show up with the default menu but not with Better Menus. Figured I'd ask because I couldn't find anyone else experiencing this in the thread.
There is functionality that developers can use to add their own menus. The first post links to it which is here : https://www.fantasygrounds.com/forum...l=1#post574918
I'm still getting these lag spikes with 0 modules loaded and no other extensions except for Better Menus in my main campaign.
I don't get these lag spikes in a new campaign (0 Mods/other extensions)...
What else about a campaign could be possibly causing these spikes?
Do you have any guesses as to what it might be? Size of Log File? Total size of Campaign Folder? Anything like that? Leftover data from a previously used but disabled extension?
Until the default menu bar becomes movable, I'm sticking with Better Menus even with the lag spikes, but I'm willing to try to solve the issue on my end. I'm just not even sure where to start.
I am not sure if its any of those issues but my test environment would not have large files for either of those. I tested dropping various pieces connected to the modules. In that case I thought it was because I was looking for changes but even with that disabled it didnt change things. It's probably some interaction with the API but to the best of my knowledge I have no "watch for these changes all the time" which would cause it to "check" while you might be moving or anything else. My checks only trigger when a menu option is clicked.