LATM's 1920 DH - 23 Open - 11.4 Closed ~500k/hour + Items + Others

[Fumi]

Hmm, Just now at 100 games run, i see thet cellar closed is at 79%.. Hotfixed? O.o

No, its pure RNG.

You got 79% closed someone else doing this might get 79% open, my Avg is around 58% closed 42% open of alltime runs

[Fumi]

Nice work !
I have question : Just before the bot starting to check loot, my VM is in terrible freeze.
After 2 hours of botting diablo crash ( freeze at the moment where the bot check for loot ).

It's a problem with scrypt or i need to change setting in my VM ?

Thx for your work ! very nice!

Whats your VM specs?

[Leschaps]

2 proc, 2 core per proc and 2 Go ram.
Win7 x64.
I run diablo fine but just at the moment where the bot check for looting = crazy freeze.

[Joe775]

Wondering if anyone else is having this issue or has any suggestions.

After a successful run where there is no loot to be salvaged, my guy will run up to the vendor, pass him, sit in the corner for a second, then pause the script and never resume. It works fine after salvaging then moving to the vendor. I have had this issue on both my VM and my PC.

Any help is appreciated.

[Fumi]

2 proc, 2 core per proc and 2 Go ram.
Win7 x64.
I run diablo fine but just at the moment where the bot check for looting = crazy freeze.

Is your diablo on Low in all settings? (i run with this)
do you run the script as admin and as x64?
try it out on your "Normal" computer if your screen is allowing it

[Joe775]

2 proc, 2 core per proc and 2 Go ram.
Win7 x64.
I run diablo fine but just at the moment where the bot check for looting = crazy freeze.

At my work I have 5 ESXi servers that run over 300 VMs. VMware tends to have worse performance with multiple processors or multiple cores. You may get better performance if you set your VM to a single core. That is what I use and I have no performance issues during the OCR process.

[Angrycoder]

This is picture of

$slot1x = 1434 ; first slot x coordinate
$slot1y = 607 ; first slot y coordinate
$offset = 48 ; offset for each slot
	
$slotLineTopX = 1414 ;First slot line x coordinate
$slotLineTopY = 632 ;First slot line y coordinate
$slotLineBotX = 1458 ;First slot line x coordinate
$slotLineBotY = 634 ;First slot line y coordinate
$slotLineOffSet = 48 ;offset for each line
	
$CellMiddleTopX = 1429
$CellMiddleTopY = 604
$CellMiddleBotX = 1435
$CellMiddleBotY =609
$CellMiddleO = 48

For anyone running a different resolution than 1920x1080, you will have to find your own values to input.

$slot1x = 1434 - The orange dot in Bag Slot 1,1. (ie, the dead center of bag slot 1,1).
$slot1y = 607 - The orange dot in Bag Slot 1,1. (ie, the dead center of bag slot 1,1).
$offset = 48 - The orange dot in either Bag Slot 1,2 or 2,1. Doesnt matter which way you go. You only need 1 offset (x or y since its a square and equally spaced).

$slotLineTopX = 1414 - This is the left green line.
$slotLineTopY = 632 - This is the top yellow line.
$slotLineBotX = 1458 - This is the rigth green line.
$slotLineBotY = 634 - This is the bottom yellow line.
$slotLineOffSet = 48 - This should be the same as $offset from the orange dots.

$CellMiddleTopX = 1429 - Left Red Line.
$CellMiddleTopY = 604 - Top Blue Line.
$CellMiddleBotX = 1435 - Right Red Line.
$CellMiddleBotY = 609 - Bottom Blue Line
$CellMiddleO = 48 - Same as above offsets.

This should allow the script to scan your items correctly on different resolutions (you will need the correct PNGs as well), but this should fix the scanning areas.

[Fumi]

At my work I have 5 ESXi servers that run over 300 VMs. VMware tends to have worse performance with multiple processors or multiple cores. You may get better performance if you set your VM to a single core. That is what I use and I have no performance issues during the OCR process.

offtopic: Imagine them all farming gold xD

Ontopic: sounds right :P i will try to turn my own down and see if it eithers improves or stays the same (if it stays the same why not use 1 )

[chancity]

They shouldn't need to get there own coords i don't believe. You just made me realize how redundant my offsets are haha

This is picture of

$slot1x = 1434 ; first slot x coordinate
$slot1y = 607 ; first slot y coordinate
$offset = 48 ; offset for each slot
	
$slotLineTopX = 1414 ;First slot line x coordinate
$slotLineTopY = 632 ;First slot line y coordinate
$slotLineBotX = 1458 ;First slot line x coordinate
$slotLineBotY = 634 ;First slot line y coordinate
$slotLineOffSet = 48 ;offset for each line
	
$CellMiddleTopX = 1429
$CellMiddleTopY = 604
$CellMiddleBotX = 1435
$CellMiddleBotY =609
$CellMiddleO = 48

For anyone running a different resolution than 1920x1080, you will have to find your own values to input.

$slot1x = 1434 - The orange dot in Bag Slot 1,1. (ie, the dead center of bag slot 1,1).
$slot1y = 607 - The orange dot in Bag Slot 1,1. (ie, the dead center of bag slot 1,1).
$offset = 48 - The orange dot in either Bag Slot 1,2 or 2,1. Doesnt matter which way you go. You only need 1 offset (x or y since its a square and equally spaced).

$slotLineTopX = 1414 - This is the left green line.
$slotLineTopY = 632 - This is the top yellow line.
$slotLineBotX = 1458 - This is the rigth green line.
$slotLineBotY = 634 - This is the bottom yellow line.
$slotLineOffSet = 48 - This should be the same as $offset from the orange dots.

$CellMiddleTopX = 1429 - Left Red Line.
$CellMiddleTopY = 604 - Top Blue Line.
$CellMiddleBotX = 1435 - Right Red Line.
$CellMiddleBotY = 609 - Bottom Blue Line
$CellMiddleO = 48 - Same as above offsets.

This should allow the script to scan your items correctly on different resolutions (you will need the correct PNGs as well), but this should fix the scanning areas.

[Leschaps]

Yeah full low setting and yes i run the script as admin.
When i try on my normal computer, there are no frezze when he checks.

Thank for your help !

[JackLinks]

negative, works perfectly. you are the only person reporting an issue. if its sleeping you might have to mash x a few times.

I just double-checked. Before initiating (pressing "="), the X on both the main GUI and the settings GUI doesn't close the windows.

[chancity]

Here are all the scan areas, the little middle box is checking to see if there's an item in the slot, the line in between the cells tells us if there's a two slot item, and the big box is just the area to move the mouse to do the image search.


$offset = 48

BIG BOX

$slot1topx = 1414  ; first slot x coordinate
$slot1topy = 588; first slot y coordinate
$slot1botx = 1457 ; first slot x coordinate
$slot1boty = 630; first slot y coordinate

SLOT LINE

$slotLineTopX = 1414 ;First slot line x coordinate
$slotLineTopY = 632 ;First slot line y coordinate
$slotLineBotX = 1458 ;First slot line x coordinate
$slotLineBotY = 634 ;First slot line y coordinate

LITTLE BOX

$CellMiddleTopX = 1429
$CellMiddleTopY = 604
$CellMiddleBotX = 1435
$CellMiddleBotY =609

The point of analscan is to remove the highlight around the new items, if thats there the pixelsearch for slot line will fail. I'm working on making the mouse move to random cells each time it does the analyzing but still check all the cells.

[LATM]

I just double-checked. Before initiating (pressing "="), the X on both the main GUI and the settings GUI doesn't close the windows.

works for the other 900 people who have downloaded so far.

899/900 means something on your end.

replacing line 803-807 with

RandClick("middle", Round(20 * $x_ratio), Round(708 * $y_ratio), 1, 1) ;moves to doorway leading to rare inside cellar
Moving(2800)
RandMove(Round(425 * $x_ratio), Round(70 * $y_ratio), 1, 1)

also fixes the blind spot issue with the mob on the far left. Loaded for Bear hits all mobs then. I copied it from another script but there I copied it from one too so I don't know who came up with that spot but it wasn't me.

I will work on making that part of the script, only actually using smokescreen so it doesn't take 2800 seconds.

I have a issue with the inventory... the script start searching/selling from the middle of the inventory and go to the right side (searching outside the window) :/

any solution for this?

1600x900

you need to take your own screenshots, read the thread.

when i first start the script it says "updating" i changed the autoupdate in the ini but it still does it an di have to hit "=" to get it to run. Happening to anyone else?

= is the start button. what the hell are you asking

Just curious, did this part of the script manage to get fixed or is it still being worked on

Ive been busy Ill do it tonight

[Angrycoder]

They shouldn't need to get there own coords i don't believe. You just made me realize how redundant my offsets are haha

Well, if im running on a 1366 x 768 and the offsets are set to

$slot1x = 1434 ; first slot x coordinate
$slot1y = 607 ; first slot y coordinate
$offset = 48 ; offset for each slot

For me, when the time comes to scan, it is scanning off my screen (i can actually see the mouse move to the second monitor and do its thing lol). Thats why i had to grab my own coords. Everything else in the script works flawlessly. The looting, the pathing, the killing, even repairing. But i havent been able to get the salvaging or stashing to work, since its looking off my screen when the scan starts.

[chancity]

They should be getting converted when used..

Well, if im running on a 1366 x 768 and the offsets are set to

$slot1x = 1434 ; first slot x coordinate
$slot1y = 607 ; first slot y coordinate
$offset = 48 ; offset for each slot

For me, when the time comes to scan, it is scanning off my screen (i can actually see the mouse move to the second monitor and do its thing lol). Thats why i had to grab my own coords. Everything else in the script works flawlessly. The looting, the pathing, the killing, even repairing. But i havent been able to get the salvaging or stashing to work, since its looking off my screen when the scan starts.