Lavish Software

Downloaded and compiled a release build yesterday, from the 7/17/2008 release. I placed the DLL in extensions and did "ext isxeq". Down goes Frazier. I assumed that the vs90 libraries were at fault.

I downloaded MQ, and built ISXEQ with VS 2008. No troubles there, although there were no VS2008 libraries supplied. I used the vs90 libraries, and the project linked. However, when I tried to load the extension IS crashed. I don't keep old compilers around, so I am going to need to do things with In...

Thanks for the suggestion. Innerspace has been fine for the most part, and I figured that SOE would more likely be looking for ISXEQ than Innerspace. Anyhow, (and I hate to ask this), but where do I get ISXEQ? Ismods has a compiled version from 2006, which is incompatible with the current IS. It has...

I've been having some difficulties sending commands to an EQ1 session via the "type" command. Lock foreground is checked for EQ1, and in some cases things work fine. however I have a script like the following: function main() { type "/assist fred\n" } which appears to do nothing. The command does no...

A FYI, since I saw nothing on the forums when I looked earlier:

I can confirm that IS works fine under Windows XP 64-bit w/8G.

Perhaps a bit pointless to add this, but I would have liked to know this before taking the plunge. Everything turned out fine though.

I have no idea, but it seems like you have found a bug. I base this on the fact that you can access a couple of fields, but not the other.

(There is nothing like a wrong answer to cause people to delurk )

I apologize for what might be considered excessive posts here. I am learning a lot, and imagine others must experience similar things. Hopefully others will benefit from my experiences. First, I have learned that *one* of my machines has different behaviors with Innerspace than another. This isn't t...

I saw some poor framerates when running two sessions under IS on one machine, something that WinEQ2 had no issues with. Checking the forums I read the advice about running WinEQ2 and IS together and decided to give it a shot. I turned off IS's frame limiter, started WinEQ and then launched an IS ses...

I'll update that I've gotten past the memory issue (or rather I'm not going to spend any more time on it). Memory prices being what they are, 8G of DDR2-1066 cost me $170. That should last me a couple of months, and I can turn the models back on.

And to hijack my own thread, rather than add even more at the moment: how do I get rid of games in the launcher? I can't seem to figure out the secret handshake so far. I select "Configuration" then I click on the "Game Configuration" tab. From the drop down list I select "PlanetSide" (nothing again...

Since this is a new issue I'll start a new thread. I just had an IS session hang on me. By that I mean the window no longer updates its display. I can change sizes from tiny, normal to fullscreen. But no client updates anymore. I'm not sure of the cause yet. This was on a desktop, and I was renaming...

A quick followup: the problem was an incorrect resolution in the eqclient.ini file. The profile was copied at one point from another machine and used to run at 1280x1024. Since WinEQ2 forces things into windowed mode, this wasn't a deal breaker. But in IS land it prevented the device from being crea...

Thanks for your help. "Force Windowed" did solve my problem (or at least work around it). I am thinking about installing the 64-bit XP on this machine, and that would be a good time to experiment with the video drivers. That way if anything goes wrong it is a simple matter to back out the change via...

Are you sure the driver is at fault? EQ seems to run just fine on its own, or under WinEQ2.

NVidia's driver updates don't seem to support the mobile chips. I'm told that one can edit the inf files and load the newer ones, but I'm reluctant to head down that road.

I have poked at innerspace a couple of times without success, and decided today to give it more time. The problem I am seeing at the moment is that when I start no-patch I get a black screen and then the client crashes (Visual Studio traps this and wants to fire up the debugger). I have no idea wher...