Xyf

That is not a solution, just a band aid fix. A solution means identifying the problem (what is different on mac vs pc and why it happens) and fixing so it does not happen.

Seems fixed now.

If you must know the "exact" specs, here you go, straight from the box:

The torrent to the mac client needs to be changed, it's incomplete and a lot of people come and ask for alternatives.

SET gxWindow "1" .. it's right in the name.

@ka.ba your second link is the same as the first. Can you correct that? (only app files).

I may have not understood what exactly you want to do, but if you want to have the same size for the target status text as your status do this: Edit MobHealth3_BlizzardFrames\MH3_Blizzard.lua and replace GameFontNormalSmall with NumberFontNormal (lines 42 and 48, if you have the same version as I have). If you want to change the size of the names also , you need to create a small addon to do that.

If you search for "wow vanilla portrait bug" you will find more people with exact the same bug. A person said it was fixed when setting multisample to 2, you could try that.

I tried it and it was stopping for me too after some steps, then I changed the "Click-to-move camera style" to some other setting and it was working .. weird. Also, as suggested you can use autorun as an alternative.

get https://www.techpowerup.com/downloads/SysInfo/GPU-Z/ and check that the GPU is not downclocking for some reason. It might be stuck on a low clock profile.

@Athena I think it's allowed because, although it runs custom code in WoW's proccess address space (the d3d9 shim), it does not actively modifies the process memory in any way. Edit: This made me think of a way to make the "so" desired updated model / texture pack to work without modified game files: - create d3d9.dll shim, pass calls to real d3d9.dll - on init, create vertex buffers/ texture for the replacement resources - on draw calls, check signatures for used textures, replace with the update one. For models, I assume model pose and hardware skinning is used, otherwise unable to get a signature of a model. This way only replace vertex buffer. This won't work if model has more bones. Also old animations will be used ( so just the mesh is updated).

I don't have any Mac knowledge, but if what Undertanker says is true, can't you copy it to an external storage and run it from there? Or if enough ram is available, maybe make a ram disk, copy the game there and run from there? I don't know the possibility of doing this on Mac, just throwing some ideas.

You can't control what happens on other people's screen. What you want is not possible.

Do you have the ACL enabled? and perhaps the layer with the prompt is not visible? Can you post a image if something is visible when "file explorer freezes"? Try to run as administrator: right click on wow.exe and choose "Run as administrator".

You should have used a torrent download. I could suggest some things to try to maybe get something out of the downloaded data, but I think it's too much hassle and you should just download it again. My suggestion (keep in mind it's just theoretical ) - find out where the temp file is stored from the mega download (if it was not erased). - open it with 7zip or whatever achiver ( should be able to open incomplete files, as long as the start is present). extract whatever is possible. - make list of whatever is missing (hopefully nothing too great or else there is no point in this) - hope someone can somehow share just that part. If you are lucky maybe just the movies are missing and you can live without them, but I doubt it.

Most likely he has not, but what he said and I agree, there is no need for any kind of connection to start the client. Move the game from program files, that folder has restrictions regarding file access for normal users, or lauch with admin rights.

What? No. Just use one of the million web proxy you can find on google.

What I have suggested are parameters that are passed to the IDirect3D9::CreateDevice (Directx9 initialization) which could make it fail. As far as I know gxMaximize just makes the window stretch to the screen in windowed mode. Have you removed the 3 lines I suggested? Edit: might also try removing gxTripleBuffer line.

Like I said , remove lines: SET gxRefresh "60" ( if you have your desktop refresh at >60Hz (e.g. a 120Hz monitor) SET gxMultisample "8" SET gxMultisampleQuality "1.000000"

I don't understand what the problem is, if you figured out is a gx setting, just clear all gx* from config and reset then in game. Do you have perhaps a monitor with >60Hz refresh? From what I know, mismatch of refresh rate and color depth from what is set on desktop will cause the DirectX init to fail (for windowed mode). Try to clear only gxRefresh gxDepthBits gxColorBits gxMultisampleQuality.

As Ellipsea said, try compatibility mode (win 7 first then win xp sp3 if it does not work) ( on the wow.exe , not on the laucher). Also I don't think you need to mess with directx files, as long as one instance can start, you know you have all it needs to work. Have you checked <WoW folder>/logs/gx.log ? Does it say anything meaningful ?

Do you hear sound for the second instance? Try setting the graphics to windowed mode, maybe something happens and the second instance can't acquire full screen for some reason. Edit , also might want to check the logs, for some hint if something goes wrong.

KLHThreatMeter\Code\GUI\KTM_Gui.lua Line 498 change that 12 to like 6 or something. Also you change the damage meter so the buttons I've changed don't match anymore lol.

https://drive.google.com/file/d/0B7mgGJ9vgPjiYXppNjNSUHpVOEU/view You can change colors in KLHThreatMeter\Code\GUI\KTM_Gui.lua Lline 81

Pack it in a table, like the ellipsis does: call: mod:Report("%s is = %d ",{"someVal",2}) function: function mod:Report(fmt, arg) local test=string.format(fmt,unpack(arg)) message(test) end