eq1 switching question
Moderators: Lavish Software Team, Moderators
eq1 switching question
can IS switch eq1 sessions while in full screen mode? It keeps changing them to window mode before changing.
until the next release, the way to turn on PiP is to go into your EQ profile and find the "On Activate" line -- set it to "run pip". Next release it will be using a new system
You should be aware that by default, the window will return to "normal" mode when you switch to it. You can change that by editing PreInit.iss so the "pipforeground" command is "fullscreen" instead of "normal"
You should be aware that by default, the window will return to "normal" mode when you switch to it. You can change that by editing PreInit.iss so the "pipforeground" command is "fullscreen" instead of "normal"
Definitely. It's just a bind, so you just enter a command to change it. Here's what it is by default:
bind console ` console toggle
It's done internally of course, but you can use the command to change it to whatever you'd like. You can do this each time, or automatically by placing it in a file you create called AutoExec.ice. This file will be run when any game loads up through IS, and it's just a list of commands you dont want to have to type each time, such as the bind command to change the console key.
bind console ` console toggle
It's done internally of course, but you can use the command to change it to whatever you'd like. You can do this each time, or automatically by placing it in a file you create called AutoExec.ice. This file will be run when any game loads up through IS, and it's just a list of commands you dont want to have to type each time, such as the bind command to change the console key.
order of ops
Speaking of Autoexec.ice.
When do these get executed in relation to the game being ready for it.
I guess the best example would be EQ. I need to do
[code]
ext ISXEQ
ext ISXTeamspeak
Runscript TeamSpeakHud
ext ISXIRC
iconnect
...etc
[/code]
You obviously don't want to do all that when you are at the login or server select screen, so where would be the appropriate place for it, so that it executes when EQ is ready? Or would it be better to just create my own .iss to do everything I want to "startup" and when I get ingame just RunScript Startup.iss?
-Red
When do these get executed in relation to the game being ready for it.
I guess the best example would be EQ. I need to do
[code]
ext ISXEQ
ext ISXTeamspeak
Runscript TeamSpeakHud
ext ISXIRC
iconnect
...etc
[/code]
You obviously don't want to do all that when you are at the login or server select screen, so where would be the appropriate place for it, so that it executes when EQ is ready? Or would it be better to just create my own .iss to do everything I want to "startup" and when I get ingame just RunScript Startup.iss?
-Red
ISXEQ is MQ2 built for IS.. with that in mind, remember that MQ2 is loaded into the game whenever both MQ2 and the game are running -- and that can be before the EULA appears, while you're in game, etc. It's perfectly fine for you to do those commands any time.
However....
If you place those commands in autoexec.ice, they will be executed each and every time ANY IS session is started. That means the EQ patcher (if you wanted that to run), and even any other game. You would be much better off placing it in a game-specific or profile-specific startup file.
However....
If you place those commands in autoexec.ice, they will be executed each and every time ANY IS session is started. That means the EQ patcher (if you wanted that to run), and even any other game. You would be much better off placing it in a game-specific or profile-specific startup file.