Script runs too long?
Morphyloon opened this issue · 4 comments
I get this regularly on first load. If I /reload with all assets already in memory/cached, I don't get this error. I suspect it's related to the Ace library that's included with GSE v2104 and something that GSE is trying to do.
When you disable all your other mods except GSE does it still occur? It
looks like one of your other mods is causing a conflict.
…On Sat, Aug 12, 2017 at 9:54 AM, Morphyloon ***@***.***> wrote:
I get this regularly on first load. If I /reload with all assets already
in memory/cached, I don't get this error. I suspect it's related to the Ace
library that's included with GSE v2104 and something that GSE is trying to
do.
gs_scriptrantoolong.txt
<https://github.com/TimothyLuke/GnomeSequencer-Enhanced/files/1219344/gs_scriptrantoolong.txt>
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#338>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AAjBFfnEJuEkzPwa8XFpqTZ-CESQxIOBks5sXPDPgaJpZM4O1QLM>
.
--
*Timothy Minahan**M* 0406 413 680 | *E *[email protected]
Looks like Skillet is running a different version of the Ace3 Libraries and
this is causing the problem.
On Sat, Aug 12, 2017 at 10:27 AM, Timothy Minahan <[email protected]>
wrote:
… When you disable all your other mods except GSE does it still occur? It
looks like one of your other mods is causing a conflict.
On Sat, Aug 12, 2017 at 9:54 AM, Morphyloon ***@***.***>
wrote:
> I get this regularly on first load. If I /reload with all assets already
> in memory/cached, I don't get this error. I suspect it's related to the Ace
> library that's included with GSE v2104 and something that GSE is trying to
> do.
>
> gs_scriptrantoolong.txt
> <https://github.com/TimothyLuke/GnomeSequencer-Enhanced/files/1219344/gs_scriptrantoolong.txt>
>
> —
> You are receiving this because you are subscribed to this thread.
> Reply to this email directly, view it on GitHub
> <#338>, or mute
> the thread
> <https://github.com/notifications/unsubscribe-auth/AAjBFfnEJuEkzPwa8XFpqTZ-CESQxIOBks5sXPDPgaJpZM4O1QLM>
> .
>
--
*Timothy Minahan**M* 0406 413 680 | *E ***@***.***
--
*Timothy Minahan**M* 0406 413 680 | *E *[email protected]
I have 81 addons so a cold start takes some time, even with a SSD. After disabling all addons except GSE, there was no timeout error. The same can be said with a warm start after WoW has loaded and I use a "/reload" command in game, the addons load much faster from cached areas preventing a timeout error.
I'd also like to note that most of those 81 addons use Ace3Lib. Why can't GSE use the Ace3 Lib already installed with it?
Because Ace3 uses a shared install so all mods using Ace3 use the same install. This isn't something that GSE controls this is how Ace3 works. Even though it's released with GSE it uses a common install.
The problem is that when a mod modifies the Ace3 libraries then all mods are forced to use the modified version. GSE uses the latest Ace3 release. However the Skillet version of Ace3 is different and all mods that use Ace3 are using its version. (Hence why you get an error message with Skillets ace libraries in your stack trace.)
What you have proven though is that the problem is not GSE but one of your other 81 mods is causing a conflict.
TimothyLuke
… On 14 Aug 2017, at 5:00 am, Morphyloon ***@***.***> wrote:
I have 81 addons so a cold start takes some time, even with a SSD. After disabling all addons except GSE, there was no timeout error. The same can be said with a warm start after WoW has loaded and I use a "/reload" command in game, the addons load much faster from cached areas preventing a timeout error.
I'd also like to note that most of those 81 addons use Ace3Lib. Why can't GSE use the Ace3 Lib already installed with it?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.