I found one thread vaguely relating to this with the last post in August and no clear response from LavishSoft.
I run Windows 7 x64. I have a Creative X-Fi Ultimate Gaming card and the latest drivers from Creative.
I also have the latest ALchemy from Creative.
All of which work as expected when running through Station Launcher or directly from the Everquest2 executable.
However, when I run via IS, the sound system is reset to Miles 2D, the CPU and RAM utilization jump an average of 15% and EQ2 becomes semi-unstable (random system freezes, crash to desktop, etc.) after several hours of play.
Setting sound to Miles 2D _without_ IS, the RAM /CPU bloat is there, but no instability.
Is there a secret code to change the behavior of IS so that it does not reset sound?
EQ2, EAX and functionality
Moderators: Lavish Software Team, Moderators
Inner Space does not do anything sound related. I don't know why your sound isn't working. I haven't had anyone ask about this in several months.
To be honest, it's a wonder that my Creative X-Fi works in Windows 7. Creative's driver support has been terrible for Vista and Windows 7. I have to install the drivers for a different X-Fi card or "What U Hear" doesn't work, and then I've had to re-install those several times after it stopped working again from a reboot. In fact, I bought the X-Fi because my Audigy 2 stopped working when I upgraded to Vista, because of terrible audio static. Which I still get with that card to this day, on Windows 7, with the official drivers or Daniel_K's unofficial drivers. And then the whole ALchemy thing. I'm never going to buy another Creative sound card because of my experience with these cards. I don't trust them to put out a product that is going to be stable.
But, I digress. I don't know why it would be any less stable for you with IS than without, assuming it's a vanilla IS install. If you're using ISXEQ2 then that could be contributing to instability. If you're playing multiple instances and using the Lock Foreground option (or the "Make game believe it is foreground window" option in ISBoxer), that could be related as well. Particularly if that means you now hear sound from multiple windows, where you would not have before.
To be honest, it's a wonder that my Creative X-Fi works in Windows 7. Creative's driver support has been terrible for Vista and Windows 7. I have to install the drivers for a different X-Fi card or "What U Hear" doesn't work, and then I've had to re-install those several times after it stopped working again from a reboot. In fact, I bought the X-Fi because my Audigy 2 stopped working when I upgraded to Vista, because of terrible audio static. Which I still get with that card to this day, on Windows 7, with the official drivers or Daniel_K's unofficial drivers. And then the whole ALchemy thing. I'm never going to buy another Creative sound card because of my experience with these cards. I don't trust them to put out a product that is going to be stable.
But, I digress. I don't know why it would be any less stable for you with IS than without, assuming it's a vanilla IS install. If you're using ISXEQ2 then that could be contributing to instability. If you're playing multiple instances and using the Lock Foreground option (or the "Make game believe it is foreground window" option in ISBoxer), that could be related as well. Particularly if that means you now hear sound from multiple windows, where you would not have before.
None of the above.
Vanilla IS install with ISXEQ2 running at startup. Patching only to "stable" version, not dev.
It's truly odd - start via "EverQuest2.exe" and I get full EAX 4. Start via IS (which calls EverQuest2.exe) and it resets to Miles.
A quick edit of eq2_recent.ini or running EQ2Settings.exe to reset to EAX4 and it's back and working.
Turning off ISXEQ2 does not change this behavior.
I'm puzzled...
Are there any debug or runtime logs I can post to help?
Vanilla IS install with ISXEQ2 running at startup. Patching only to "stable" version, not dev.
It's truly odd - start via "EverQuest2.exe" and I get full EAX 4. Start via IS (which calls EverQuest2.exe) and it resets to Miles.
A quick edit of eq2_recent.ini or running EQ2Settings.exe to reset to EAX4 and it's back and working.
Turning off ISXEQ2 does not change this behavior.
I'm puzzled...
Are there any debug or runtime logs I can post to help?