Innerspace all transparent, what's up?

intelligence · Post by **intelligence** » Wed Feb 20, 2008 9:54 pm

Hi,

Just got InnerSpace and I seem to be having some difficulties.

Config Window:

Running OpenBot

Notice cursor hovering over wow window

Not hovering the window

Is this a setting? If so, I can't find it in all that mess
I did a quick search and found nothing of value, if there is a topic post about this, I'm sorry, please redirect me there

Thanks

Post by **Lax** » Wed Feb 20, 2008 10:14 pm

There's no setting, no. And there's no posts because, well, this is the first time something like this has come up.

The first thing I would do is check for new video drivers. There seems to be some odd bug with alpha blending or something on your system, I haven't seen this before.

intelligence · Post by **intelligence** » Wed Feb 20, 2008 10:21 pm

Figured I'd get that answer.

Thing is, I can't really change my drivers, since I'm not on a regular PC
I'm on a Mac, running XP through Parallels which supplies me with video drivers, can't install official ATI drivers on my own, the VM can't handle it.

So I guess I'm stuck with this
Any other suggestions are welcome

Post by **Lax** » Thu Feb 21, 2008 9:42 am

Ok, given that information, if I can detect that you're running Parallels I can probably fix the bug (I believe it may be the same bug I had to work around for supporting Cedega). What I *can't* do is test it myself, let alone try to determine a detection method myself. But the good news is I can try to use information about the video driver itself to handle this.

To get me the info I need for this, I need you to switch to the current development build. Open up the IS Patcher window (you shouldn't have any trouble viewing this one) and check the "Download Development Patches" box, then restart IS. It will patch probably 4 files. Once that happens, open up the IS console (in the uplink via the Console menu item is fine) and enter the command diag. Some diagnostic information will open up in notepad. It's important to do this in the development build (4605) because I just added video driver info to the diagnostic information. If you can paste the full diagnostic information to me here or via email (lax@lavishsoft.com) I may be able to fix this.

intelligence · Post by **intelligence** » Thu Feb 21, 2008 11:02 am

Mail sent