Stuck on loading items tables

[rock5]

IPerhaps we need to compare the specs of the machines where the 67% issue occurs to see if there is something in common?

Good idea.

Mine's
Intel Core 2 Quad Core 2.4 ghz, 2GB ram and Win 7 Ultimate 32 bit.

[raff]

Actually I'm surprised you could run rom inside a virtual machine. How powerful is your machine if you don't mind me asking.

Yes my pc is not too bad .

my spec is:
Windows 7 64bit Home Premium
Intel Core i7 CPU 960 @ 3,20GHZ
12 GB ram

= stuck at 67%

[rock5]

12 GB ram

My cpu isn't bad but with only 2 gb ram I don't think I'll be able to do it. One day I gotta update.

[jduartedj]

not too bad .

not too bad? that's abusively modest, don't you think?

[ezgitaran]

My Computer;
Microsoft Windows XP Professional
Intel(R) Core(TM)2 Quad CPU Q6600 @ 2.40GHz
NVIDIA GeForce 8800 GTS 640 MB
3.00 GB Ram

Maybe it's related with that "lite" client? I'm using it atm.

Before revision 547 I was getting 67% stuck error
With revision 549 I am getting "macros.lua:85 Macro number needs to be between 1 and 49." error. What does that mean O.o? Tried anything with no luck, looks like it's not seeing the macro.

[rock5]

My Computer;
Microsoft Windows XP Professional
Intel(R) Core(TM)2 Quad CPU Q6600 @ 2.40GHz
NVIDIA GeForce 8800 GTS 640 MB
3.00 GB Ram

Maybe it's related with that "lite" client? I'm using it atm.

Your the first to report it with XP. Maybe you're right, I'm using the slim version too. I'm already half way through downloading the full version to test just that. I'll see if it makes a difference tomorrow after tonight's maintenance is done (assuming the patch doesn't resolve the problem).

Before revision 547 I was getting 67% stuck error
With revision 549 I am getting "macros.lua:85 Macro number needs to be between 1 and 49." error. What does that mean O.o? Tried anything with no luck, looks like it's not seeing the macro.

That's strange you shouldn't get that error during startup. That was more for if users used that function for whatever reason. What the error means is it's trying to write to a macro number that doesn't exist.

I'll try to make some suggestions.
1. Make sure there are no conflicts from when you updated.
2. Delete all the rombot macros and action bar icons and see if rombot recreates them when you start the bot.
3. Maybe the 'macro.bsd' file is corrupt. Stop the game, back up 'macro.bsd' file then delete it then start the game and see if that works.
4. If it still doesn't work I'll need more info on what section is sending the wrong info.

Just before the error message on line 85 of macros.lua,

Code: Select all

		error("Macro number needs to be between 1 and 49.")

add these lines

Code: Select all

print( "macroNum", macroNum)
print( "body", body)
print( "name", name)
print( "icon", icon)

and tell me what it prints.

[raff]

not too bad? that's abusively modest, don't you think?

hehe yes, it was meant to be modest.

My cpu isn't bad but with only 2 gb ram I don't think I'll be able to do it. One day I gotta update.

Hm, but it should work, before I got my new pc, I had a Intel Core 2 Dou 1,86ghz and also 2GB ram. And I was able to run 1 rom and bot with vmware. I used it, before the bot was able to harvest without foreground.

And btw. it seems the prices for ram are currently very low, I bought my hardware in Januar this year, and I paid 250€ for my ram kit, 1 or 2 months later, the price raised up to 450€. Also my CPU costs now 100€ more, as I bought it!

http://www.alternate.de/html/product/Sp ... =DDR3-1600
thats the ram I bought a year ago for 250€, when you click on Preisentwicklung, you can see the price history, its very crazy

but thats a bit off topic

I have just tested to limit my ram in start -> run -> msconfig, but didn't helped.

And btw I am using the normal client, I didn't even know that there is a slim version available

[rock5]

before I got my new pc, I had a Intel Core 2 Dou 1,86ghz and also 2GB ram. And I was able to run 1 rom and bot with vmware. I used it, before the bot was able to harvest without foreground.

I guess I'll give it a go then, after the patch and trying the full version that is.

And btw I am using the normal client, I didn't even know that there is a slim version available

So you were getting the problem with the normal client? Well there goes the theory it had something to do with the slim client.

[raff]

Yes, I guess it's the normal client and I am getting the problem with it. The size of my Runes of Magic folder is: 9,83 GB.

[atroxa]

Maybe somewhat connected to Core2Quad (or i5/7)?

Cause on my Core2Duo no probs at all, anyone with Core2Duo and 67% bug?

Greetz

[botje]

yes me, core2duo 3ghz with 3 gig of ram.

i have the stuck bug, but not always O.o

Botje

[jduartedj]

Core2Duo 2Ghz no problems! 2GB ram (Win 7 x64 ULT.)

EDIT: ALSO I use Slim version of RoM.

[zoked]

Hi guys,

I just wanted to tell you, i also have an xp system running and the 67% bug also affects me. I run slim client on this machine. Anoither machine has the full client and worked, also on xp, but i had it only once running so i cannot confirm it always works.
Both run on revision 549.

Besides (off topic) this is my first post in this forum and I'd like to thank you for the amazing work! It's just awsome!!

Cheers!

[ezgitaran]

I'll try to make some suggestions.
1. Make sure there are no conflicts from when you updated.

Thx rock5, you're the №1
Well, found the error source, it was my modified "settings.lua" After replacing it with original file its turned back to 67% error T_T

Btw, I tried MicroMacro on Normal Runes of Magic too but again stuck at 67%

[deathdealer1252]

Just to add input, I have a i7 950 @ 4.5 and I never get stuck at 67%. Not exactly sure what you guys mean tho, it literally gets stuck at 67% and goes no where, or just takes a long time to get past 67%?

[zoked]

... it literally gets stuck at 67% and goes no where,...?

Exactly

I have now tested on my other machine again, and, what can i say, no problems.

So.. the differences i can figure out are the following:

working / stuck at 67%
xp 32 / xp 32
normal client / slim client
updated rom via loader / updated rom via downloaded patch
admin on machine / not admin on machine

That's all I can think of now, well the one is a laptop, the other a workstation, differtent cpu and ram... if I shoud go more into detail on those things, just tell me.

BTW, did anybody yet try to manually delete mm/scripts/rom/cache/itemstablesXXX.lua ?
I doubt that's the solution, anyways I'll try it out tomorrow morning on the not working machine.

[jduartedj]

could it be issues with user rights? like not being admin or so?

[jduartedj]

Another idea is to carefully look at what is happening. As far as I can tell the bar always pauses at 67% even if only for a very brief moment. This indicates it is doing a specific task. By investigating which task it is doing we can get closer to elaborate about what is causing the 'stuckness'.

[Sumdumguy]

when I run the bot on the win7 ultimate laptop, even though it *does* load inventory past 67%, the bot doesn't loot corpses.
Can anyone confirm this or did I make a mistake somewhere?

[jduartedj]

So I figured the only place it can be sticking ins at the 19th iteration (i=18) of the LoadTables_memory function in memorytable.lua. more specifically at line 399:

Code: Select all

		realTablePointer = memoryReadInt( proc, tablePointer + ( i * 4 ) );

this specific memory read is making your life miserable!
and tablePointer is coming from:

Code: Select all

memoryReadIntPtr( proc, addresses.tablesBase, addresses.tablesBaseOffset );

another memory read, so basically (reading addresses.lua ofc and 18*4 = 72):

Code: Select all

memoryReadInt( proc, memoryReadIntPtr( proc, 0x9DAB24, 0x28) + (72) ); -- == nightmare

but this is safe:

Code: Select all

memoryReadIntPtr( proc, 0x9DAB24, 0x28)

because it is loaded before 67% stuck.

So Assuming

Code: Select all

local harmless =  memoryReadIntPtr( proc, 0x9DAB24, 0x28);

Code: Select all

memoryReadInt(proc, harmless + (72)); -- == nightmare

but i can't provide values a.t.m. because I'm at work and don't have the necessary software.

will run testes at home later and BTW to everyone i told I'll test this or that and didn't do far, sorry! been busy xmas stuff