Question - What Launcher to use for MQ to run Live and Test simultaneously

[Chibz]

I am trying to run MQ on the same computer for both Live and Test environments at the same time. I am currently using Redguides Launcher and thought I saw this was possible, but I can't figure it out. I tried creating a new directory and launching from there for the alternate Live or Test environment, but that didn't work for me. I only seem to get one instance of MQ up at a time and get the mismatch message if I try to log into the wrong server environment.

So, the first question, will Redguides launcher work for me, and if so, how should I configure it. I assume I need to get two instances of MQ running at once....

Follow up question, will an alternate launcher work better for this purpose?

 

[Sic]

I am trying to run MQ on the same computer for both Live and Test environments at the same time. I am currently using Redguides Launcher and thought I saw this was possible, but I can't figure it out. I tried creating a new directory and launching from there for the alternate Live or Test environment, but that didn't work for me. I only seem to get one instance of MQ up at a time and get the mismatch message if I try to log into the wrong server environment.

So, the first question, will Redguides launcher work for me, and if so, how should I configure it. I assume I need to get two instances of MQ running at once....

Follow up question, will an alternate launcher work better for this purpose?

You want an independent directory for your live test and emu installations but the method of launcher doesn't matter you can use the red guides launcher or you can use redfetch which is what I would recommend.

RG's launchers aren't going to be better or worse for this specifically.

You emphatically want a independent directory for each mq/EQ type tho

You would launch whatever macroquest and then you can launch the other type I would exit out of the first one in sys tray first. But very easy

 

[Chibz]

You want an independent directory for your live test and emu installations but the method of launcher doesn't matter you can use the red guides launcher or you can use redfetch which is what I would recommend.

RG's launchers aren't going to be better or worse for this specifically.

You emphatically want a independent directory for each mq/EQ type tho

You would launch whatever macroquest and then you can launch the other type I would exit out of the first one in sys tray first. But very easy

Thanks for the quick response! I think I am missing something simple but obviously critical.

I have two directories for EQ, I launch Live from one and Test from the other.

I created two directories for Redguides Launcher, one for Live and one for Test. I copied one directory to the other, should I perform a complete second install instead?

If I exit the first MQ from the sys tray, it closes the program for the first instance of EQ. If I leave the Live MQ running in the sys tray, the Test MQ from the independent directory will not run.

 

[Sic]

Thanks for the quick response! I think I am missing something simple but obviously critical.

I have two directories for EQ, I launch Live from one and Test from the other.

I created two directories for Redguides Launcher, one for Live and one for Test. I copied one directory to the other, should I perform a complete second install instead?

If I exit the first MQ from the sys tray, it closes the program for the first instance of EQ. If I leave the Live MQ running in the sys tray, the Test MQ from the independent directory will not run.

this is older

MacroQuest (core) - - Running both Test & Live MQ2 compiles at the same time

What this does: Allows you to run Macroquest2 on both Live & Test servers at the same time, on the same machine. This is made easier by eqmule's recent changes. Requirements: 1) You need to have two separate Everquest folders, one for live, and one for test. 2) You need to have two seperate...

www.redguides.com

but it might give you an idea

exiting out of the sys tray doesn't /unload from in-game for the toons that area already connected

 

[Redbot]

You can run both at the same time so long as each has a unique MacroQuestWinClassName= in MacroQuest.ini

By default, VeryVanilla Test's is
MacroQuestWinClassName=__MacroQuestTrayTest

 

[Chibz]

exiting out of the sys tray doesn't /unload from in-game for the toons that area already connected

I didn't know this, but it works for me thanks!

 

[Chibz]

You can run both at the same time so long as each has a unique MacroQuestWinClassName= in MacroQuest.ini

By default, VeryVanilla Test's is
MacroQuestWinClassName=__MacroQuestTrayTest

Tried this, but I still can only get one running at a time.

 

[Redbot]

I reproduced the problem. It looks like they now need unique MacroQuestWinName as well.

MacroQuestWinClassName=__MacroQuestTraylive
MacroQuestWinName=MacroQuestLive

Then give it a try.

 

[Chibz]

I reproduced the problem. It looks like they now need unique MacroQuestWinName as well.

MacroQuestWinClassName=__MacroQuestTraylive
MacroQuestWinName=MacroQuestLive

Then give it a try.

Working on this, but would like to clarify something.

I have two separate directories for MacroQuest, one for Live and one for Test. Do I need two separate directories also for RedGuides Launcher?

 

[Sic]

Working on this, but would like to clarify something.

I have two separate directories for MacroQuest, one for Live and one for Test. Do I need two separate directories also for RedGuides Launcher?

He is talking about in each directory you would edit your macroquest.ini to have those independent tagline

 

[Chibz]

He is talking about in each directory you would edit your macroquest.ini to have those independent tagline

Understood, I have made those changes:

For the macroquest.ini in the Live/Release directory:

[MacroQuest]
MacroQuestWinClassName=__MacroQuestTrayLive
MacroQuestWinName=MacroQuestLive

For the macroquest.ini in the Test directory:

[MacroQuest]
MacroQuestWinClassName=__MacroQuestTrayTest
MacroQuestWinName=MacroQuestTest


Still cannot get both instances up at the same time in the sys tray.

 

[Chibz]

It is working now, thank you very much!

It was something in the macroquest.ini file. I copied the Release folder to the Test folder, this also copied the exact macroquest.ini which included this line:

[Internal]
SpawnedProcess=*************

The * is an alphanumeric named unique file (not sure how it is generated), but it appears to be specific to the MQ version you are trying to launch. So even though I was starting the Macroquest application from the correct directory, it was triggering the same live version of this application file.

I created my own problem by copying the macroquest.ini file from one directory to another. Thank you very much for helping me sort it out!!