Intermittent 132 error when changing graphics settings

[bollwerk]

Sometimes when I'm 5-boxing, I'll get random 132 errors on a couple clients, causing them to crash. The cause is always changing graphics settings with a keymap in ISboxer. Most of the time, it works just fine, but every so often it causes 2-3 of my 5 clients to crash with 132 errors. I've posted the error logs and dxdiag info on WoW technical forums and the initial reply is that Innerspace is the problem. Is their tech support just pointing fingers at the most convenient target? Or could there be some truth to it?

http://us.battle.net/wow/en/forum/topic/3881922611

Let me know if you need me to copy/paste the commands I use to change graphics settings.

[lax]

No I don't think I need any more information from you, the log is relatively specific.

Current Addon function: SetCVar
Current Addon object: Graphics_TextureResolutionDropDown

Setting that cvar is crashing you. I would start by just eliminating that one from the macro for now and see if that helps.

The customer support guy on the forums who said "It looks like the InnerSpace app you have installed is having a lot of problems with the game." doesn't really know what he's talking about, or at least his statement is just plain wrong. He has no idea why it is crashing. In order to determine the cause of this crash, a WoW developer would probably have to look at it, and crash logs posted on the wow forums probably very rarely actually get to a WoW developer. This guy's job is to filter out everything that doesn't need to go to the developers, and get your game running for you again. He could care less about Inner Space and whether it works or not, he wants you to eliminate it from the crash report and get him an identical report without it, otherwise it is not ruled out as a cause of the problem. They just don't tell you that because thats not how the business works.

So here's some links to posts of this same crash on the official WoW forums, without Inner Space running (found via google for Graphics_TextureResolutionDropDown crash):
* http://us.battle.net/wow/en/forum/topic/3229085382
* http://us.battle.net/wow/en/forum/topic/3566007583
* http://us.battle.net/wow/en/forum/topic/3196340759#6
* http://us.battle.net/wow/en/forum/topic/3764968806
* http://us.battle.net/wow/en/forum/topic/2712011713
* http://us.battle.net/wow/en/forum/topic/1827305933#3
* http://us.battle.net/wow/en/forum/topic/3424692735#7

Given this information, I seriously doubt that it is Inner Space's fault... But I don't think I can pinpoint the actual bug, it looks to me like it really is a WoW bug. I don't think they will spend much time on it, I think your best bet is my suggestion at the top of this post

[bollwerk]

I can't find the command that matches what you're talking about... here are my commands:

/console baseMIP 0
/console terrainMipLevel 0
/console textureFilteringMode 3
/console projectedTextures 1
/console waterDetail 2
/console Sunshafts 2
/console particleDensity 60
/console weatherDensity 1
/console farclip 1250
/console environmentDetail 150
/console groundEffectDensity 64
/console groundEffectDist 160

and

/console baseMIP 1
/console terrainMipLevel 1
/console textureFilteringMode 0
/console projectedTextures 0
/console waterDetail 0
/console Sunshafts 0
/console particleDensity 10
/console weatherDensity 0
/console farclip 185
/console environmentDetail 50
/console groundEffectDensity 16
/console groundEffectDist 70

[bollwerk]

Looks like baseMIP was the culprit. No more crashes when switching graphics settings, now that I've removed it.

[lax]

aha, wonderful. I am glad you figured that out even though it wasn't as clear as it should have been with the error.

[MiRai]

I was about to bump this thread if you didn't reply soon because I was curious as to what your findings were.

That's an interesting outcome, though. I did find that even before I wrote that Wiki entry that Texture Resolution was a hard hitter when
changing it on the fly and I eventually just resorted to keeping it set the same across all windows.

Have you ever run the Unigine Heaven benchmark on your card(s)? If not, I would crank up the settings and put some pressure on the GPU
to see if you can get an error. If you can, you should be able to RMA the card if it's still under warranty.