Zugg Software :: View topic

Apprentice Joined: 29 Dec 2000 Posts: 146 Location: USA

I've tried with 2.37, and 3.06.
Compatibility report shows no issues.
I've sent at least 2 reports.

Let me know what else you'd like to see. I'd really like to run cmud, instead of Z. I've been trying for quite a while now. Playing 1 session works great, adding that 2nd one, and it crashes either instantly, or within 30 seconds.

this was a fresh install of 2.37, which was then upgraded to 3.06

Posted: Wed Apr 29, 2009 7:23 pm

Is the 2n'd session a different session, or a duplicate of the first session?, if a separate session, both run fine while a single session?

Have you tried exporting, and importing your settings again?

Apprentice Joined: 29 Dec 2000 Posts: 146 Location: USA

yep. 2nd session is different
and I've re-imported all my sessions several times.
I've had trouble with running multiple sessions since the first beta tho.

I can run with any 1 session open, and it runs great. I try to start 2, and the longest I've ever been able to keep it open was about 10 mins.

I wonder if the problem is, you can't run the same package, on multiple sessions ? altho that's the whole point of me wanting to upgrade to cmud from zmud.

Posted: Wed Apr 29, 2009 7:38 pm

Are you re-importing your .mud files or using cmud's xml export/import?

since which beta? 3.xx?

Apprentice Joined: 29 Dec 2000 Posts: 146 Location: USA

I've tried both, in version 2X, I haven't imported in 3x yet.

and since the VERY FIRST beta.

Posted: Wed Apr 29, 2009 7:56 pm

*wrinkle* thats not cool.

1) Might try selectively importing your settings in small chunks while both sessions are running, would help determine if/where you've a script gone crazy, but I've the feeling that could be a large task since your settings are obviously keeping you from making the switch...

2) post the crash dump here, someone might notice something in there.

Posted: Wed Apr 29, 2009 8:07 pm

Each session should have it's own separate "primary" package file. Click the Edit Session action for each session icon and go to the Files/Packages tab. Make sure each session has it's own primary package filename. If you want to share some scripts between multiple sessions, you need to create a separate shared package, put the scripts into that package, and then add the shared package to the list of packages being loaded for each session.

And yes, post the crash dump here, or tell me what name/email you used when you submitted it. The "Send bug report" goes into a giant database and isn't tied to your forum username, so it's hard for me to search that to connect a crash dump with a forum post.

Apprentice Joined: 29 Dec 2000 Posts: 146 Location: USA

that's exactly what I have setup with packages. one primary, and then 1 or 2 packages that are shared.
I'll send you my email. If I haven't tried in a while, but last time I didn't share any packages, I didn't have any problems.