I hadn't tried the talent before so I hit up some target dummies to get a feel for it. The script suggested treants only once -- before I actually started attacking. I looked for them during berserk, during TF, while trinkets were procced (including RoR), etc, but they weren't suggested again. I had FoN and DoC as talents.

The "script ran too long" error is pretty much unavoidable due to the nature of ovale and the complexities of the feral script. It doesn't hurt anything though. All it means is that Blizzard stopped ovale from taking too much CPU time with an update (I believe). Simply turn off lua errors or get an addon to catch them (Bugsack). If you're getting any other kind of error, copy/paste it here.

There was a bug with the rake code that will be put into nerien's soon or you can update manually here (/ovale code; copy to custom script; paste over the old script (ctrl+a then ctrl+v))

Memory usage of that amount is fairly typical for ovale as its keeping track of a lot of things. Honestly though memory usage is of little consequence unless you're just short on memory, there's many other things (such as cpu usage, which ovale is kind of heavy on so keep it in mind if you have a slow computer) to worry about before that. I've had 200MB+ of addons before (between recount, tradeskillmaster and everything else) with no problems. Jeshu is working on getting the memory usage down though (right now I think the storing of auras unnecessarily is his next target) as it used to be much worse. Honestly, as I said I'm not particularly worried about it.

FoN support isn't really working properly right now, I think aggixx is working on it but I don't have an eta.

Katjia wrote:When I try and put in that custom script it locks up my game Guess I'll have to wait unless theres a way of doing it outside of game?

It does that to me as well but it recovers. Paste it in and walk away for a minute. Literally - 60 seconds.

Yes, given the length of the Leafkiller/aggixx/ShmooDude script, it takes a while for the UI to accept the copy and paste. Time it takes for Ovale to compile it is much, much shorter (should fit in the ~300ms execution window allowed by WoW).

@ShmooDude: You always seem to catch me in the middle of a raid online, so I forget to respond during downtimes

Regarding your discovery about certain constructs being more efficient, e.g., "ComboPoints(less 4)" is more efficient than "ComboPoints() < 4", that's the nature of the way that the parse tree is evaluated. "ComboPoints(less 4)" is a single node that takes effectively one function call to evaluate. "ComboPoints() < 4" is three nodes ("<" node with a left child of "ComboPoints()" and a right child of "4") that effectively take three function calls to evaluate. This was something that I told Leafkiller a long time ago on one of these Ovale Script threads on TFD, so it's something that's known and out there, though probably not very widely-known.

Eventually, I would like to give Ovale the full compiler treatment with lexer -> parser -> optimizer, with the last step to try to compress the parse tree into something smaller. Or pie-in-the-sky, follow up with a code-gen phase that spits out actual Lua code into a string that could be executed directly by the WoW client instead of walking the parse tree. All this is future development -- for now, I'm trying to fix more basic things, e.g., the timespan stuff I mentioned that was related to your ticket 298.

ShmooDude wrote:
FoN support isn't really working properly right now, I think aggixx is working on it but I don't have an eta.

It works just fine if you're running rune (or renataki's) but you have to have "Left: Alternate Predictive" on to see it. Once I get the logic how it should be for all the trinkets (which I think requires some additions to Ovale to pull off) I'll make sure there's a right side option for it as well.

I was wondering whether having other addons like ElvUI conflicts with Ovale+scripts?

I am using ElvUI and BigWigs along with Ovale + the newest feral script; during actual raid combat I get a ton of global (lua) errors...
Sometimes the rotation just gets stuck midway and fixes itself after awhile.

Match the version to whatever is in the version listed at the top of the leafkiller script:

# 10/03/13 version 5.4.2.1

is matched to the 5.4.2 Ovale

kcf912 wrote:1st post here...

I was wondering whether having other addons like ElvUI conflicts with Ovale+scripts?

I am using ElvUI and BigWigs along with Ovale + the newest feral script; during actual raid combat I get a ton of global (lua) errors...
Sometimes the rotation just gets stuck midway and fixes itself after awhile.

Only seems to happen during combat; not on target dummies...

Any idea what's going on?

That doesn't really tell me much, what's the error? Some LUA errors won't interfere with things running properly and others will. A lot of the time you can simply either turn off lua errors or use an addon to catch them (bugsack). As far as the rotation getting stuck, its happened once or twice but I've no idea why and haven't seen it in ages.

Last edited by ShmooDude on Fri Oct 11, 2013 9:06 pm, edited 1 time in total.

ShmooDude wrote:Currently only on Left: Small Rage Usage Box (Left: Small Predictive Box in cat form). If you're using an older version (new version should be up tonight), its called Alternate Predictive Box

This allows for you to write clear, descriptive code using the names, but have Ovale directly substitute the actual values in the script during compilation. This saves an extra function call for every time one of these "static variables" is accessed.

Jeshu wrote:I was looking at the Leafkiller script and I noticed a small change that could increase performance. Here is a small portion of the script defining static variables" as user-defined functions:

This allows for you to write clear, descriptive code using the names, but have Ovale directly substitute the actual values in the script during compilation. This saves an extra function call for every time one of these "static variables" is accessed.

Except currently defines can't take decimals, though I'm pretty sure that'd be an easy fix in the compiler. That had been what I was going to go with initially but since it didn't appear to work (I think I used a decimal number initially which just plain didn't work) I went with functions.

ShmooDude wrote:First two happen occasionally, its just because blizzard caps execution time at 300 ms per frame which happens occasionally with a script as complex as this. You can pretty much ignore them.

Looks like the 3rd one is your problem and I'm not sure why its doing that but I highly doubt its anything to do with conflicts of other addons as I've run all those except sidebar and swatter.

Error #3 happens because OvaleCompile couldn't finish compiling the script in time (error #1), so it returns an incomplete node table, which causes error #3 trying to reference a property that's not in the incomplete table.