Zugg Software :: View topic

Newbie Joined: 05 Nov 2009 Posts: 3

I've bought 2 license for CMUD,since I have two laptop, one at home and one in office.

I met 2 big issues for me:

1) When using one window and several sessions, noramlly in the second session window, the script won't work correctly. The variable value can't be correct set.
Now I have to open one cmud for one session. Normally I will login 6 ID in a mud, then I have to use 6 cmud window. It causes a lot of time to create these 6 windows each day.
This issue have been met since I first use CMUD in Jan. 2009.

2) When running 6 CMUD windows for 24 hours, each CMUD window will always sunddenly occupy 100% CPU resource. I have to close all the 6 windows, and recreate 6 CMUD windows.
Then I can use them for one day. I don't need to reboot WINXP or Vista(I have two laptop, play in home and office sometime).

These 2 issues troubled me a long time. It hasn't been solved even in latest version 3.12.

Is it a known issue? Or any advices to solve them? Or have to wait for new release?

Best Regards

Posted: Thu Nov 05, 2009 10:59 pm

1) cmud does support multi playing, sometimes you have to write your scripts to be multi play friendly, scoping can be tricky. why won't what script work right? what does it do? it's hard to find a solution to it doesn't work.

2) i regularly run cmud for days at a time, i do know thou that after playing for a long time if you have an exceptionally long scrollback buffer and you try to resize the window it can take a long time to adjust.

Newbie Joined: 05 Nov 2009 Posts: 3

1) I found a previous report in forum for this multi play issue.
http://forums.zuggsoft.com/forums/viewtopic.php?p=150979

I met the same thing. When I set different id name in @me, set different weapon name in @weapon. In Multi window, all sessions will use the variable in the first windown. Therefore, when I use auto-login trigger, all the session will login the same id. I tried to assign diffent package names for all the window, also disable all the other packages in "list packages enabled in this window".
Still no use.

2) Currently I open 6 cmud windows, while not one. Because cmud can't support multi play well(varaible value can't be set correctly in multi-sessions in just one cmud window).
So, after one day, suddenly several windows will occupy CPU 30-70%/each window. So, CPU will not have free resource. It will last for around 10 seconds. After one to several minutes, it will occupy again all the CPU resources. I can't play in this situation. Have to close all 6 windows, and reopen them. The opening for each window cause around 10s to 30s. 6 windows cause 1 to 3 minutes, troubled me a lot. Each day when I start to play, I must to enjoy this bad feelings first, when not enjoy the play first!

3) Must I write VB DDE program to make a workaroud solution? I don't know why CMUD can't support multiplay well, while zmud is good. I can run stable for long time with 6IDs' windows in ZMUD during 2006.

I like CMUD, because more friendly for Multi-country language support. It is much better than zmud. It is fast, I like it. But it will suddenly be slow, bad feelings.

4) These two issues troubled me for the most time in this year, I can't solve them. So I ask for help!
Other issue, like auto enable small keyboard(numlock) when restart CMUD, I finally find the solution to add "NUMLOCK =0;NUMLOCK2 = 0" in cmud. ini to solve it. This issue only found in VISTA when I bought the second license in the end of this Sept. Troubled me for 1 month, and I finally solve it.
But for the above two issues, I have no solution for 10 months. Could anyone help me? Is it really bugs or any workaround solution for it?

Wizard Joined: 22 Mar 2007 Posts: 2320

You'll have to explain a lot more what you are doing. Cmud can handle multiplay just fine. You just need to set it up right. What do you mean by "varaible value can't be set correctly in multi-sessions in just one cmud window"?

The best way to set up multiplay would be to create a separate session for each session you want to have. Then, make a new "supersession" which opens each of the packages for the other sessions. Is this how you did it? If not, how did you make your multiplay session?

As for the problem with CPU, you may have to figure out what it is doing when the usage spikes like that. You might try running with the debugger window open to see what is happening. It could be some kind of trigger firing with massive looping, or something.

Newbie Joined: 05 Nov 2009 Posts: 3

The multi-play issue is that:
When set @me value in window2, it will set the value in @me in window1, while window2's @me hasn't been changed. When use @me in window2, it will use the value of @me in Window1.
When t+,t- classes, the same behaviour like variable.

I don't know what is the "super session". Each window use a different session in my case. I created 6 sessions for one mud, because I have 6 IDs for this mud. Now mud difficulty become harder and harder for a single role, I have to create a big self team to play the mud.

I do tried create a 7th session which is empy. I launch this session first, then launch other 6 sessions. No helps. The same issue occur.

Posted: Fri Nov 06, 2009 5:46 pm

If you want to have variables shared by multiple windows, you need to create a Shared Package with a global module that contains the variables. That is what Rahab means by setting up CMUD properly to support multiplay. There are dozens of different ways for people to multiplay and CMUD tries to be flexible enough to handle them all, but that means more work on your part to structure your sessions properly for this.

If you really MUST change a variable in a different window, you can use the syntax:

#VAR //windowname/classname/varname value

to set the variable, and @//windowname/classname/varname to access the value.

What Rahab means by a "super session" is that once you have opened your 6 sessions, you can then use the File/Save Session As command to save this to a "super session" which will give you an icon in your session window that can be used to automatically open all six session windows again in the future.