Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - OMGBurgers

Pages: [1] 2 3 ... 36
1
Scripting Chat / Re: Client crashing testing
« on: May 17, 2021, 05:33:07 PM »
So I did some more testing today, but i'm getting bored of it, so maybe i'll mess with it more one day.  Here are my findings thus far.

Only certain events/exevents in succession will cause a crash.  The amount can be as little as two in a row, but the order matters.
Those events I have found are:
Event exmsg
Event sysmessage
Event pathfind
Speech commands (Event macro 1 0, Event macro 2 0, Event macro 3 0, Event macro 4 0)

The instability and crashing will occur only with certain combinations/orders and positions of a delay.  I have examples below, red for crash causing, green for stable.
event macro 3 0 test, event pathfind #charposx #charposy, wait 1
event pathfind #charposx #charposy, event macro 3 0 test, wait 1
event macro 1 0 test, event sysmessage test, wait 1
event sysmessage test, event macro 1 0 test, wait 1
You can see above a slight pattern, and i'm sure that pattern would be even more clear if additional testing was done on every event/exevent, but that's too time consuming.
You can also see a wait is not needed after every event/exevent, but even just as small as a "wait 1" is required for some to prevent crashing.  You can see this shown with 6 events in a row in an example at the bottom, with no delay between any actions, only one at the end to prevent "You must wait to perform another action".

I have found, in my testing, that the above is not worsened/improved based on connection speed to the uo server.  I have done testing with ping at 8-16ms (I live in state of the local uo server), testing on sakura (~160 ping), and testing with my vpn connected to Istanbul Turkey (~270 ping) and results are the same.

The same results happened at a connection lost.  What I mean by this is logging in, disconnecting internet to bring the connection lost gump (you are now disconnected from the server).
The client will still crash if you do:
Code: [Select]
event macro 3 0 test
event sysmessage test
wait 1
But it will not crash when doing:
Code: [Select]
event sysmessage test
event macro 3 0 test
wait 1

Okay, now another example.  With just 2 events in a certain order, we can cause a crash.  But we can perform 6 in a row perfectly stable, even though one of them is a speech command, which was causing crashing with the other 3 events above.  The following is stable ( I stopped at a bit over 400 cycles):
Code: [Select]
set #lpc 1000
while A <> B
{
event macro 3 0 3
event macro 8 7
event macro 8 2
event macro 5 0
event macro 9 7
event macro 9 2
event sysmessage test
wait 22
}

2
Scripting Chat / Re: Client crashing testing
« on: May 16, 2021, 10:50:24 PM »
I include easyuo as a potential problem point because it is a bit shoddy software lol.  But it's out of my ability to determine the culprit.

I have been using easyuo since 03 according to my easyuo account age and have never experienced uo and easyuo working together being such a delicate operation haha, and I've wrote some pretty bogus trash scripts along the way 😂

3
Scripting Chat / Re: Client crashing testing
« on: May 16, 2021, 09:49:00 PM »
Yes I would assume a wait of that magnitude would reduce crashing, but would render something like an auto spawner unproductive.

There must have been a change at one point or another, somewhere,  be client side, server side, or easyuo.

I have unmodified scripts I used to run long ago that still work properly, but not reliable because of crashing. These are scripts I could run all day without issue. 

4
Scripting Chat / Re: Client crashing testing
« on: May 16, 2021, 08:55:26 PM »
I have managed to now get Razor Enhanced to crash.
Some of the combinations of statements last longer when waits are given.

Did you try these in the non-auto-update version of easyuo? (did i miss your response?)
That's good it had you crash also.  I don't have waits in there just as a worst case scenario. I created a sub to globally handle events ro ensure delays are there, and stopped using event exmsg and I no longer crash.  I was just curious if it would crash others.

I tried to compile my own easyuo based on some instructions here but I messed up and was unsuccessful.  So my only option (that I'm aware of) is to use the auto updating one.

5
Scripting Chat / Re: Client crashing testing
« on: May 16, 2021, 08:30:47 PM »
Ran your snippets a while and didn't have any crashing.  I killed skeletons with the 2nd and 3rd script individually for about 30 minutes with no crashing.  I'm only crashing with opening easyuo and client a certain way or sometimes client swapping but what you're dealing with is way worse.  I dig up pipelines and fix them for a living so obviously I have no useful input, but maybe if a few others test this you'll be able to determine if it's a you problem or an everyone problem.  If you've got anything else you wanted to test I'll give it a shot for you.   

Yeah the one I showed in the skeletons & shadow wisps shouldnt crash.  It was to check if it also skipped the event macro 17 corpse open and/or the event exmsg ocasionally if you ran them both at the same time, not seperate.  But I removed those.

The remaining one I edited to the condition that will force a crash for me in ~5 - 10 seconds every time.

6
Scripting Chat / Re: Client crashing testing
« on: May 16, 2021, 08:07:56 PM »
You have a lot of parameters to testing this that are unspecified.
"Steam/razor/razor-enhanced" - am I supposed to try all of these?
I just noted about why I don't use the uoxl cli new button to start clients, those "assist tools" have no effect as far as I can tell.  Just any way you normally open a script & play it will work.

Your script issues a "gosub action init", but your sub action has no "init" test to do anything. I think you intend for all your variables to be N/A instead so you try to set these up, but what does "if N/A < #systime - 3000" mean in the evaluation? Reading this and it seems it needs a clearer execution path.
The gosub action init will do something, even though it specifically doesn't use the init part.  It will still hit the first 2 if statements, and bypass the 2nd two, thus initializing the namespace variables. You can put anything there as long as its not set/wait and it would do the same.  I could initialize the sub by just calling a gosub action wait, or gosub action set, but I do this way for searching purposes when im debugging.
I will remove these scripts, as they have nothing to do with the crashing, as I think it's causing confusion.  It was just there to test if when running "test script" and "test2 script" if the client/easyuo would skip the event macro 17 or the event exmsg occasionally.
Edit:  Those are removed.

How do you guarantee there are no actions happening in the other applications?

I tried writing a simple looter to pick up gold on the ground. I was running a few clients (razor/razor-enhanced) in the same way you describe. I would get a crash all the time when 2 clients would try to pick up the same item.

When it comes to client actions, it doesn't matter what the source - the client has to be able to process the actions and have appropriate wait times or it is guaranteed to crash. :) So how do you isolate that nothing is happening in the other software that interacts with the client?
I am running no other scripts, nor are any other applications doing anything.  I thought the video showed that.  The only actions done were the easyuo scripts shown in the video.



So I tried the first script.
No crashes, but it does nothing, because %p = 0 and then it only moves when %p = 1.

How are you setting %p to 1 so it actually tries to move?

I hard coded it to 1, and let it run now. 100+ pathfinds later and no disconnect.

I stopped it once %count reached 200.

I went to try to use Razor Enhanced - it doesn't want to connect to OSI. I have only used it on freeshards.

So Razor Enhanced (started first!) and then Easyuo (Auto-update version) modified %p=1 script and more than 200 pathfind loops without a crash.
Sorry, maybe that was an oversight on my part.  The script will do nothing unless you uncomment the event lines, and set %p to 1 to enable pathfinding.  I had it set in an idle state so people could enable things a set at a time, rather than all at once.  You absolutely should not get a crash if it only pathfinds.

I have edited the post to have %p 1, and all lines uncommented.  Next time I should just grab my mic and explain it better in the video.

Code: [Select]
set #lpc 1000
set %count 0
set %p 1

loop:
   if %p = 1
      {
      if #random > 500
         set %y #charposy + 1
      else
         set %y #charposy - 1
      event pathfind #charposx %y
      }
   event macro 3 0 crash
   event exmsg #charid 0 90 crash , #spc , %count
   event sysmessage crash , #spc , %count
   event macro 8 2
   exevent popup #charid

   set %count %count + 1
   wait 2s
goto loop

The one w/ the gold loot and auto attack isn't expecting any crash.  It shouldn't crash.  As per my video, I showed how it would skip either the event exmsg or the event macro 17 to open the corpse.  I was curious to see if others had the same problem with that one.

7
Scripting Chat / Re: Client crashing testing
« on: May 16, 2021, 02:18:09 PM »
I have been trying different start methods for a few months now.  No different combination or order gave me better stability overall.

I have reduced my crashes to 0 yesterday since discovering what I shown in the videos.  I was running 3 clients, all razor enhanced with uncapped FPS, easyuo with 7 scripts and 4 of them doing uoxl swapping at speeds of < 100ms controlling all clients at once.

I'm really just interested if others experience the same oddities with easyuo as I shown in the video, along with the crashing with those events, or if it's an isolated with my stupid computer lol.

8
Scripting Chat / Re: Client crashing testing
« on: May 16, 2021, 01:59:50 PM »
Also if it matters, I am using the latest EasyUO, and a fully patch UO client, Windows 7 64.

If anyone has time, if they could test and see if they encounter the same things as me that would be greatly appreciated.  I have the (one) scripts I used in the videos here below. (I removed the others, as it seemed to cause confusion)

Script to force crashing:
Code: [Select]
set #lpc 1000
set %count 0
set %p 1

loop:
   if %p = 1
      {
      if #random > 500
         set %y #charposy + 1
      else
         set %y #charposy - 1
      event pathfind #charposx %y
      }
   event macro 3 0 crash
   event exmsg #charid 0 90 crash , #spc , %count
   event sysmessage crash , #spc , %count
   event macro 8 2
   exevent popup #charid

   set %count %count + 1
   wait 2s
goto loop

9
Scripting Chat / Client crashing testing
« on: May 16, 2021, 01:53:10 PM »
Ok, so I've been complaining about client crashing since I started playing again, as you can see from the thread below haha.

Eventually I found an issue with lines in the script not being executed, which led me to figure out my crashing problems for the most part.

I'm unsure if it's something on EasyUO's end, or with the client itself.  But this is an issue I haven't encountered when I played previously.  I sold all my account back in 2012-2013.  I have not started experiencing these problems until we got the auto updating EUO.

So in the first video, you can see I use a script that just opens the corpse, loots the gold.  When opening the corpse it will output the ID above the character.  I added that because I was unsure what was going on with it not doing the "event macro 17", but then found it would skip the event exmsg even.
Video:


After finding that, I clamped the rate of the "event macro 27 0" usage on my combat script.  This fixed an issue with quite a few things I did, but I was still crashing on other scripts.  The one I would crash on often was the Shadowguard helper which helps with Orchard room.  So I have no "Event macro 27 0" command going here.  I originally thought it was from more than one script sending an event macro, or exevent command to the client at the same time.  But I was crashing with a single script.  So that would mean I was crashing because of a combination of events being sent, or the speed in which they've been sent.  I can force a crash using many combinations of events, so I'm not sure it's a specific one.  I have noticed that event exmsg displays weird at times though, and when it does I can prepare for a crash.  But even without event exmsg, I will still crash.

Here's a video showing the crashing with multiple event commands, and with a few different methods of running euo/client.
Video:


I know everyone has their own way they swear on to load everything, but believe me, I have tried for weeks to resolve this and I cannot find a better way which works.  Starting a client with uoxl cli new button in easyuo is not an option, as I use either steam/razor/razor-enhanced and they have to start the client.  But it also doesn't help if I do.  So this isn't about that.

10
Submit your Script / Re: OMG Durability Scanner
« on: April 18, 2021, 03:17:25 PM »
Hi, long time no see! :)

I attached a screenshot, it's nothing special.  But for someone running a lot of clients maybe it will be of use lol

11
Submit your Script / OMG Durability Scanner
« on: April 17, 2021, 07:43:43 PM »
This is a quick script I put together that scans all items on the paperdoll, and some weapons inside the main #backpackid (Just double axes and bladed staffs).  This helps with having to check between 4 clients of 4 sampires and dealing with the annoying issue of having to remove robe or certain boots just to check some of your armor.

You can add/remove more types for %weapons and also adjust %menux & %menuy for menu opening position.

Maybe it will be of use to some others, I may improve it to use the repair bench also in the future since i'm lazy.

12
Scripting Chat / Re: Weird crashing problems?
« on: January 21, 2021, 10:21:36 PM »
For the past hour I haven't had any problems by starting all 3 clients first, and easyuo last.  I'm running 4 scripts that all swap clients, along with UOSteam.

I'm going to give it a go another hour and then off to bed and will test different methods tomorrow.

Restarting my computer wouldn't clear the "Entering Britannia..." error previously, so I'm not sure closing all in the task manager will, but I'll try.

13
Scripting Chat / Re: Weird crashing problems?
« on: January 21, 2021, 07:29:11 PM »
I know this isn't an issue about performing actions, all of my scripts use a action queue system I implemented in all my scripts so they can work without interfering with each other, and the only action being performed is a bandage healing script.

I've also never had the black screen problem logging in.  Last night I encountered it just getting stuck on the grey screen/gumps for "Entering Britannia..."

What you mentioned about the uoxl swap is a good idea.  I can slow down the bandage one a bit and even the combat one a bit I suppose.

I've been searching google and came across a lot of people complaining about it crashing also so at least I know it's not just me haha.  They all suggest loading in certian orders, and also I found this on the Technical Problems board (http://www.easyuo.com/forum/viewtopic.php?f=53&t=54153).  They say to start all clients before loading easyuo.  I'll just keep messing around.

I've had my combat script going for about close to 2 hours without a crash so far.  But I'm also using just one client swapping script.  I'll start checking if it could be related to multiple client scripts running at the same time and all.  Hopefully I can figure it out, if I do i'll post what seems to help lol.

Thanks for the ideas!  And also about the update to the menu, I didn't know that change was ever implemented lol.

14
Scripting Chat / Re: Weird crashing problems?
« on: January 21, 2021, 05:31:47 PM »
The only actions being performed is using a bandage, and arming a special move.  I've never had this problem in the past before, and I've ran similar scripts for hours a day without fail.

I am using UOSteam, so I am going to just off the basic client and see if UOSteam is the problem, though I previously used it lol.

Like you said the only time I have ever had problems/crashes from scripts is dragging while moving, expecially with exevent, and issuing move/pathfind commands while not logged in (if you forget to pause some at a DC lol)

I was just wondering if it's something anyone else experienced.  I've played UO about 16 years and scripted a bulk of it, and never experienced it locking me out of a shard on just one account before.  I tried everything, restarting, razor, vanilla client, using a hotspot instead of wifi for a different ip etc.  Nothing worked.  I was worried my account was flagged haha

I'm going to do some testing now.  I'll go ahead and record the screen and do some tests.

15
Scripting Chat / Weird crashing problems?
« on: January 21, 2021, 02:42:04 PM »
I haven't played UO in a few years, but have started recently.  My friend had trouble getting a few of my scripts working and when I team viewed in, he was crashing oddly and just blamed it on his computer.

Last night I experienced a crash similar to his, but I was locked out actually logging onto any character on the shard and just stuck at "entering britainna...".  After about 45 minutes it cleared and let me back on.  I was able to log on all other shards, just not the one I originally crashed on.

The scripts I was running was just a cross healer, and a combat assister, two scripts.  Each script does all actions on a client, swaps to the next, and repeats.  Obviously the healing one just uses a bandage and targets.  The combat one is only arming special moves.

I've never experienced something like this before, and have ran these scripts along with others at the same time for like 5+ years easily lol.

Has there been any changes to anything in UO or easyuo that could be causing a problem?  My scripts currently do client swapping at intervals of about 20-50ms on average and gather info and act when needed, so not sure if thats a problem now, but never has been.

Pages: [1] 2 3 ... 36