 |
alluran
Adept
Joined: 14 Sep 2005
Posts: 223
Location: Sydney, Australia
|
|
_________________
The Drake Forestseer |
 |
|
|
Zugg
MASTER
Joined: 25 Sep 2000
Posts: 23379
Location: Colorado, USA
|
 Posted: Mon Jun 16, 2008 5:03 pm
|
If you are talking about the crash dump report: "Invalid argument to time encode." then the problem is with one of your #alarm triggers and I'd need to see the exact alarm pattern that you are using.
|
|
|
|
|
alluran
Adept
Joined: 14 Sep 2005
Posts: 223
Location: Sydney, Australia
|
Posted: Mon Jun 16, 2008 10:57 pm
|
Wasn't recieving the bug in 2.18 or 2.26, will export the timer package later, pretty basic triggers as far as i know, but i'll check for others too.
|
|
_________________
The Drake Forestseer |
|
|
|
alluran
Adept
Joined: 14 Sep 2005
Posts: 223
Location: Sydney, Australia
|
Posted: Mon Jun 16, 2008 11:01 pm
|
Hmm, will also try disabling a package I recently got off someone else. It has 2 alarms in it. I suspect that could be my problem. Will let you know more.
|
|
_________________
The Drake Forestseer |
|
|
|
|
|
|
