SolarStrike Software

GurdyMan wrote:Createpath.lua: It currently doesn't add the </waypoint> tag properly.

Found the error. Missing an "hf_line .."
Should be:

Code: Select all

	elseif( v.wp_type == "WP" ) then
			hf_line = hf_line ..sprintf(wp_string, i, v.X, v.Z, 
			   p_wp_type,					-- insert type=TRAVEL for waypoints if you want
			   "");							-- no command
			   hf_line = hf_line .."</waypoint>\n";

Dummy Macro button: The checking function is really antsy. Every once in a while a script won't run and it will tell me I need to define the dummy macro. If I wait a few minutes it usually fixes itself. I haven't found any connections to be able to reproduce the error.

Administrator wrote:Are you up to (or past) revision 245 and still getting the macro error? I'm unable to get it to happen here. About the only thing I can think of right now is that it might be that your computer is running too slowly and the request is timing out.

Try going to line ~364 of rom/functions.lua and look for this:

Code: Select all

		if( deltaTime(getTime(), startWaitTime) > 500 ) then

Try changing the 500 to a higher value and then see if you can get the error to happen again. If it's 1000 or higher and you still receive the error, then it would be hard to believe it's simply because it isn't processing fast enough.

Administrator wrote:After it fails, check that macros text and see what it contains. What does it say?

d003232 wrote:A good check could also be, to put a debug 'prinft' within the 'RoMScript'. Just to see, if the keybord press receive the client. There have been an issue some days before, that the RoM window don't receive the keyboar press. Just to exclude that error source a short debug would help.

	if( settings.profile.hotkeys.MACRO ) then
local rettype = 0;
 rettype =  keyboardPress(settings.profile.hotkeys.MACRO.key);
printf(sprintf("%d",rettype));
	end

It returns this: â™ T Which is a Null and the number ascii 84.

Of course then the RoMScript("000"); returns 000 right after the 815 fails.

		if( deltaTime(getTime(), startWaitTime) > 500 ) then
			break; -- Timed out
		end;

• was the message 'MACRO test: send returnvalue 1234 to macro place 2' in the ingame chat?
• see you a 'TIMEOUT in RoMScript ...' message in your MM window
• whats the content of macro 1
• whats the content of macro 2
• what happens if you press your macro hotkey ingame manual

GurdyMan wrote:It did timeout at the script.

There was a 'MACRO test: send returnvalue 1234 to macro place 2' message on the ingmae chat window followed by: "Macro test: testvalue cleared"

Macro 1:

Code: Select all

/script r='' a={xxxx;SendSystemChat("MACRO test: testvalue cleared");} for i=1,#a do if a[i] then r=r..tostring(a[i]) end r=r..'	' end EditMacro(2,'',7,r);

Macro 2 was empty.

Pressing '0' results in chat window showing: "Macro test: testvalue cleared"

Can't I assume that given the contents of Macro 1 that it did actually succeed?

d003232 wrote:

GurdyMan wrote:It did timeout at the script.

There was a 'MACRO test: send returnvalue 1234 to macro place 2' message on the ingmae chat window followed by: "Macro test: testvalue cleared"

Macro 1:

Code: Select all

/script r='' a={xxxx;SendSystemChat("MACRO test: testvalue cleared");} for i=1,#a do if a[i] then r=r..tostring(a[i]) end r=r..'	' end EditMacro(2,'',7,r);

Macro 2 was empty.

Pressing '0' results in chat window showing: "Macro test: testvalue cleared"

Can't I assume that given the contents of Macro 1 that it did actually succeed?

Yes. I you see both messages in the ingame chat and if there is NO yellow stop message in the MM window, then you pass the test successful.

GurdyMan wrote:No, that was a fail.

d003232 wrote:

GurdyMan wrote:No, that was a fail.

ok, I understand. But did you see the first message 'MACRO test: send value 1234 to macro place 2' in your ingame chat? I not I suppose the keypress did not reach your client. So be sure you have moved ingame the empty macro to the right key.

GurdyMan wrote:

d003232 wrote:

GurdyMan wrote:No, that was a fail.

ok, I understand. But did you see the first message 'MACRO test: send value 1234 to macro place 2' in your ingame chat? I not I suppose the keypress did not reach your client. So be sure you have moved ingame the empty macro to the right key.

Yes I did, and the dummy macro is at 0 on the first action bar.

Since I did see this 'MACRO test: send value 1234 to macro place 2' when it failed, it's probably timing out at the second macro.