View Full Version : Warcraft 3 TFT 1.22 Patch Released
haiggy
Jun 30, 2008, 09:45 PM
New 1.22 patch
Ladder reset
See the b.net site for the full changelog (nothing exciting)
Hope it makes it so maphack no longer works, tie hack, all that garbage
Go get playing!
ruinfx
Jun 30, 2008, 10:10 PM
ok i havent tried playing dota yet on my mbp but does war3 still lock up after you try and quit from the main menu? are there still the "another application is using the ports" messages?
Calipso
Jul 1, 2008, 10:15 AM
New 1.22 patch
Ladder reset
See the b.net site for the full changelog (nothing exciting)
Hope it makes it so maphack no longer works, tie hack, all that garbage
Go get playing!
Nothing exciting?? Are you kidding me. Very exciting!
Two big fixes for Intel Macs! Although im not 100% sure if the sound is acutally fixed :S
Buuut, dota sounds now work properly. yay! :)
haiggy
Jul 1, 2008, 10:51 AM
Nothing exciting?? Are you kidding me. Very exciting!
Two big fixes for Intel Macs! Although im not 100% sure if the sound is acutally fixed :S
Buuut, dota sounds now work properly. yay! :)
That's not exciting.
A new hero is exciting. ACTUAL balance changes are exciting. A twist to the game is exciting.
A bug fix for sounds in DOTA? Who gives a crap? DOTA is TERRIBLE and for people that can't play the game it's meant to be...... go look at the Battle.net forums and see how many people are laughing at the fact that they noted 'Fixed a bug with DOTA sounds on Intel Macs' in the patch/change log.......
Calipso
Jul 1, 2008, 11:23 AM
Well that is your opinion.
Blizzard obviously recognize how important DotA is to the survival of Warcraft 3. Wether you like it or not, it is a very popular game.
And they did make some balance changes.
Anyway, be interesting to see if War3 still crashes, have not really tested yet.
I am just happy they fixed the sound bugs (not dota ones). I reported it in another thread here and created a video detailing the problem and sent to Blizz. Looks like Blizzard acutally fixed it. Which is nice :)
rbarris
Jul 1, 2008, 11:47 AM
Keep us posted on your play experiences with the new patch !
Chone
Jul 1, 2008, 01:07 PM
Woot I might start playing again.
BTW rbarris, besides firing you, what can Blizzard do to you for breaking an NDA?
rbarris
Jul 1, 2008, 01:09 PM
Woot I might start playing again.
BTW rbarris, besides firing you, what can Blizzard do to you for breaking an NDA?
It might be more productive to just spell out which topic you are interested in asking about ?
Spanky Deluxe
Jul 1, 2008, 01:26 PM
BTW rbarris, besides firing you, what can Blizzard do to you for breaking an NDA?
Make him dress up as a female night elf and do 'the dance' on international television.
Calipso
Jul 1, 2008, 08:04 PM
Well I have been playing a bit now, and it does sound like the majority of the sound issues have been fixed. However I checked the system log for anything unusual, and I am still getting errors regarding the sounds. Also the problem with the background music stopping seems to be still happening (you play a game and it only plays one track then stops);
Jul 1 20:53:16 matthew-gillespies-imac [0x0-0x114114].com.blizzard.WarcraftIII[477]: WAVPlayer::SetWA
Jul 1 20:53:16 matthew-gillespies-imac [0x0-0x114114].com.blizzard.WarcraftIII[477]: VSourceImmediate: Failed to open [Unit
Jul 1 20:53:16 matthew-gillespies-imac [0x0-0x114114].com.blizzard.WarcraftIII[477]: s\NightElf\AncientProtector\TreantAttac
Jul 1 20:53:16 matthew-gillespies-imac [0x0-0x114114].com.blizzard.WarcraftIII[477]: k2.wav]
Jul 1 20:53:44 matthew-gillespies-imac [0x0-0x114114].com.blizzard.WarcraftIII[477]: WAVPlayer::SetWA
Jul 1 20:53:44 matthew-gillespies-imac [0x0-0x114114].com.blizzard.WarcraftIII[477]: VSourceImm
Jul 1 20:53:44 matthew-gillespies-imac [0x0-0x114114].com.blizzard.WarcraftIII[477]: ediate: Failed to open [Units\NightElf\AncientProtector\TreantAttack2.wav]
Jul 1 20:55:34 matthew-gillespies-imac [0x0-0x114114].com.blizzard.WarcraftIII[477]: WAVPlayer::SetWA
Jul 1 20:55:34 matthew-gillespies-imac [0x0-0x114114].com.blizzard.WarcraftIII[477]: VSourceImmediate: Failed to open [Units\Night
Jul 1 20:55:34 matthew-gillespies-imac [0x0-0x114114].com.blizzard.WarcraftIII[477]: Elf\AncientProtector\TreantAttack1
Jul 1 20:55:34 matthew-gillespies-imac [0x0-0x114114].com.blizzard.WarcraftIII[477]: .wav]
Jul 1 20:55:35 matthew-gillespies-imac [0x0-0x114114].com.blizzard.WarcraftIII[477]: WAVPlayer::SetWA
Jul 1 20:55:35 matthew-gillespies-imac [0x0-0x114114].com.blizzard.WarcraftIII[477]: VSourceImmediate: Failed to open [Units\Nigh
Jul 1 20:55:35 matthew-gillespies-imac [0x0-0x114114].com.blizzard.WarcraftIII[477]: tElf\AncientProtector\TreantAt
Jul 1 20:55:35 matthew-gillespies-imac [0x0-0x114114].com.blizzard.WarcraftIII[477]: tack2.wav]
Jul 1 20:55:36 matthew-gillespies-imac [0x0-0x114114].com.blizzard.WarcraftIII[477]: WAVPlayer::SetWAVSourceImmediate
Jul 1 20:55:36 matthew-gillespies-imac [0x0-0x114114].com.blizzard.WarcraftIII[477]: : Failed to open [Units
Jul 1 20:55:36 matthew-gillespies-imac [0x0-0x114114].com.blizzard.WarcraftIII[477]: \NightElf\AncientProtector\Treant
Jul 1 20:55:36 matthew-gillespies-imac [0x0-0x114114].com.blizzard.WarcraftIII[477]: Attack1.wav]
Jul 1 20:55:37 matthew-gillespies-imac [0x0-0x114114].com.blizzard.WarcraftIII[477]: WAVPlayer::SetWAVSourceImmediate: Failed to open [Units\NightElf\AncientProtector\TreantAttack2.wav]
Jul 1 20:55:41 matthew-gillespies-imac [0x0-0x114114].com.blizzard.WarcraftIII[477]: WAVPlayer::SetWAV
Jul 1 20:55:41 matthew-gillespies-imac [0x0-0x114114].com.blizzard.WarcraftIII[477]: SourceImmediate: Failed to open [Units\NightElf\AncientProtector\TreantAttack2.wav]
Jul 1 20:55:43 matthew-gillespies-imac [0x0-0x114114].com.blizzard.WarcraftIII[477]: WAVPlayer::SetWAV
Jul 1 20:55:43 matthew-gillespies-imac [0x0-0x114114].com.blizzard.WarcraftIII[477]: SourceImmediate: Failed to open [Units\NightEl
Jul 1 20:55:43 matthew-gillespies-imac [0x0-0x114114].com.blizzard.WarcraftIII[477]: f\AncientProtector\TreantAttack1.wav]
Jul 1 20:55:57 matthew-gillespies-imac [0x0-0x114114].com.blizzard.WarcraftIII[477]: WAVPlayer::SetWAVSou
Jul 1 20:55:57 matthew-gillespies-imac [0x0-0x114114].com.blizzard.WarcraftIII[477]: rceImmediate: Failed to open [Units\NightElf\An
Jul 1 20:55:57 matthew-gillespies-imac [0x0-0x114114].com.blizzard.WarcraftIII[477]: cientProtector\TreantAttack1.wav]
Jul 1 20:56:00 matthew-gillespies-imac [0x0-0x114114].com.blizzard.WarcraftIII[477]: WAVPlayer::SetWAVSourceImmediate: Failed to open [Units\NightElf\AncientProtector\TreantAttack1.wav]
Jul 1 20:57:36 matthew-gillespies-imac [0x0-0x114114].com.blizzard.WarcraftIII[477]: WAVPlayer::SetWAVSourceImmediate: Failed to open [Units\Creeps\HeroFlameLord\FireLordMissileDeath1.wav]
adamcz
Jul 1, 2008, 08:59 PM
Keep us posted on your play experiences with the new patch !
I haven't figured out how to install it. When I tried to update the normal way by connecting to bnet, I got a "download failed" message, so I tried to download it from the website. I saw links to mirrored ftp sites the other day, but now they are gone.
This link:
http://us.blizzard.com/support/article.xml?articleId=21220
says "Currently downloadable 1.22 patches are not available as yet, previous patches can be downloaded from our FTP page."
So how do I install it?
Edit to add: More specificly, it asks me to "launch BNUpate manually," but I don't know how to do that. There is a file in my warcraft folder by that name, but I don't know what to do with it. If I double click it, it tries to open it in photoshop!
haiggy
Jul 1, 2008, 09:18 PM
I haven't figured out how to install it. When I tried to update the normal way by connecting to bnet, I got a "download failed" message, so I tried to download it from the website. I saw links to mirrored ftp sites the other day, but now they are gone.
This link:
http://us.blizzard.com/support/article.xml?articleId=21220
says "Currently downloadable 1.22 patches are not available as yet, previous patches can be downloaded from our FTP page."
So how do I install it?
Edit to add: More specificly, it asks me to "launch BNUpate manually," but I don't know how to do that. There is a file in my warcraft folder by that name, but I don't know what to do with it. If I double click it, it tries to open it in photoshop!
Drag the patch file onto that application icon and it should run it and install it.
KingYaba
Jul 2, 2008, 01:01 PM
are there still the "another application is using the ports" messages?
Turn off your firewall.
adamcz
Jul 2, 2008, 04:08 PM
Hi - I had the same issue but you don't need to wait!
Once you've downloaded the patch using blizzards download in game and it fails navigate to
/ Applications / Warcraft III /
There is a file called BNUpdate
***
Rename this file to BNUpdate.app
Run this file it will auto update your warcraft and you'll now be 1.22
Cheers
John
That was from another thread. Very helpful.
adamcz
Jul 2, 2008, 04:34 PM
Played one game though, and it looks like they still haven't fixed the start locations in that free for all map with 3 possible start locations on each side. In a four player game, there ought to be two players on each side (and fairly spaced in the corners). What's the point of a FFA game where 1 person has half a map to themselves and the other three start out on top of each other? Does the person with a side to themselves ever lose?
SmartIndianKid
Jul 2, 2008, 06:19 PM
I was pretty surprised when I saw this patch come out. Good work Blizzard!
However, I still apple+m before quitting the game from the main menu. Can anyone confirm that it no longer freezes?
Calipso
Jul 3, 2008, 06:33 AM
Sadly, the game STILL freezes after playing for a while when you quit it. I still apple+m it too. I don't even think about it now, I just do it sub-consciously!
Cooper78
Jul 3, 2008, 12:54 PM
Have you tried giving it like 30 seconds? On quitting mine now initially hangs for like 10 seconds and then it is fine and I'm no longer hung up.
*shrug*
Xavier
Jul 3, 2008, 01:35 PM
I have never had a problem with WC3 freezing or anything. This update did no noticeable changes to my performance.
Everything runs just fine.
ruinfx
Jul 4, 2008, 12:57 AM
I have never had a problem with WC3 freezing or anything. This update did no noticeable changes to my performance.
Everything runs just fine.
do you play dota a lot? thats what causes it.
Keep us posted on your play experiences with the new patch !
i would just like to say i am disappointed with the mac side of the patch. warcraft 3 tft still locks up my computer when i try to exit after playing a dota game. very annoying. i have to enter window mode every time i want to quit the game so that i can force quit. i sent in an error report for every crash hoping that someone would get the point. luckily i only have to play warcraft 3 on my mbp when i am away from home and i can use my pc most of the time. still i expected more. :mad:
Cooper78
Jul 4, 2008, 02:44 AM
Did you give it 30 seconds to see if it unlocks itself?
ruinfx
Jul 4, 2008, 03:31 AM
ive tried waiting and it does nothing. only happens after i play dota and is very annoying. i have to force quit every time i close war3.
Calipso
Jul 4, 2008, 06:17 AM
The fact it only happens after DotA, means Blizzard cannot fix it. Its obviously linked to something in the DotA map. So I wouldn't blame them.
Mac Player
Jul 4, 2008, 10:55 AM
Keep us posted on your play experiences with the new patch !
I have with the new permanent health bar feature. (Screenshot attached)
MBP 2.16, Radeon X1600
ruinfx
Jul 4, 2008, 12:44 PM
The fact it only happens after DotA, means Blizzard cannot fix it. Its obviously linked to something in the DotA map. So I wouldn't blame them.
its a problem with warcraft 3 itself, i dont see how it isnt something blizzard shouldnt be responsible for.
SmartIndianKid
Jul 4, 2008, 03:13 PM
its a problem with warcraft 3 itself, i dont see how it isnt something blizzard shouldnt be responsible for.
Nobody's sure exactly what the problem is. If it's a problem solely caused by DotA, then it lies in the makers of DotA to fix. Luckily, DotA 6.52e is out. From the changelog:
6.52e Changelog:
=================
* Fixed some critical bugs introduced in the 1.22 patch
ruinfx
Jul 4, 2008, 04:05 PM
Nobody's sure exactly what the problem is. If it's a problem solely caused by DotA, then it lies in the makers of DotA to fix. Luckily, DotA 6.52e is out. From the changelog:
6.52e Changelog:
=================
* Fixed some critical bugs introduced in the 1.22 patch
the problem was not fixed by .52e, and was mainly about runes i believe (which are still screwy even in .52e). this is not a fatal error that happens when playing dota, this is not a freeze that happens while playing dota, this is a lock up that happens after the game has ended and can happen after i have exited battle.net. you are saying that it is IceFrogs responsibility to fix a lockup that happens on the wacraft 3 main menu?
kainjow
Jul 6, 2008, 03:46 AM
1.22 is for RoC as well.
I still wish they would add an option for letterboxing on widescreen monitors. I hate how the video is stretched. It slows down the cursor and distorts everything.
IanC
Jul 6, 2008, 12:51 PM
I still wish they would add an option for letterboxing on widescreen monitors. I hate how the video is stretched. It slows down the cursor and distorts everything.
Oh man, yes. That would be great.
Even setting it to the same res as my screen results in a stretched look, although not as blurry as a lower res obviously.
ruinfx
Jul 6, 2008, 01:08 PM
on my pc i play on a 22" widescreen at 1680x1050. i force the game to that res in the registry and it actually looks pretty damn good and there are no performance problems. also in the nvidia control panel on my pc there is an option to add letterboxing, not sure if that exists on macs.
adamcz
Jul 7, 2008, 06:20 PM
Well I can tell you that maphack is alive and well in 1.22b. I got rushed by teaming maphacking blademasters (in FFA) who both came directly to my start location, and killed all my buildings without attacking each other.
I guess I can't attach a wc3 replay file here to share with you all, but it was bizarre.
SmartIndianKid
Jul 7, 2008, 07:00 PM
the problem was not fixed by .52e, and was mainly about runes i believe (which are still screwy even in .52e). this is not a fatal error that happens when playing dota, this is not a freeze that happens while playing dota, this is a lock up that happens after the game has ended and can happen after i have exited battle.net. you are saying that it is IceFrogs responsibility to fix a lockup that happens on the wacraft 3 main menu?
I know what the problem is, it happens to me whenever I play DotA too. Which is part of the reason I stopped playing it.
Considering that not a single other map causes this problem, yes I would say it is his responsibility to fix a problem with his map.
FieryBalrog
Jul 9, 2008, 02:24 PM
still i expected more. :mad:
Don't be a baby. I'm immensely happy that a software company in this day and age is still patching a 5 year old game like TFT on a platform (Mac) that is largely ignored by gaming companies. And a Blizzard representative to give us feedback on a non-company forum to boot, that is above and beyond anything I expected.
And here you are complaining about a hangup after the game quits that appears to be caused by a particular popular custom map (DotA) as others have noted in the thread.
ruinfx
Jul 9, 2008, 04:28 PM
the only reason i still play war3 is because of customs. i havent played ladder seriously in years. so when dota, pretty much the only reason i play the game, is causing lockups i consider it a big deal. most of the time i can play on my desktop and its fine, but when i visit home i have to use my mbp and its just plain annoying.
blizzard took the time to address the sound issues in dota so they obviously care about fixing it. they realize dota is one of the main reasons war3 is still around. i just thought they might fix this annoying issue since it seems pretty common and easy to reproduce.
Calipso
Jul 10, 2008, 09:09 AM
Are you blind? The problem is related to triggers in the DotA map. It has nothing to do with Blizzard.
kainjow
Jul 10, 2008, 03:15 PM
on my pc i play on a 22" widescreen at 1680x1050. i force the game to that res in the registry and it actually looks pretty damn good and there are no performance problems. also in the nvidia control panel on my pc there is an option to add letterboxing, not sure if that exists on macs.
yep I figured out how to do that with the BootCamp graphic drivers, so I moved the game to Windows from the Mac. Works great.
ruinfx
Jul 18, 2008, 07:16 PM
well i dont know if this has been posted before but after playing a game of dota if you go back to the main menu and go into the "single player" menu and then the "campaign" menu and then quit the game will exit properly when you hit "quit".
QCassidy352
Jul 18, 2008, 08:57 PM
well i dont know if this has been posted before but after playing a game of dota if you go back to the main menu and go into the "single player" menu and then the "campaign" menu and then quit the game will exit properly when you hit "quit".
seems like a lot more trouble than just force quitting...
nutscastastroph
Jul 22, 2008, 11:50 PM
after downloading the patch from battlenet, it asked me to restart warcraft3, but then when i click restart
it says
Warcraft III.app
A battle.net update program, BNUpdate, could not be launched automatically (-10810). Please launch it manually when the game quits.
i found BNUpdate in the application folder, but then when i clicked on it nothing happened..
help!
aund
Aug 3, 2008, 03:56 PM
my wc3 STARTED freezing up after this new patch ^^ Ofc I also experienced the quitting lockup but now I'm, complaining about a midgame lockup! It hasn't done that before. It happens every second game. No special commands issued. Freezes for 30 seconds and then tells me about a kernel panic. correpsonding thread number 2 (which is solely wc3, so no sounds, graphics whatsoever problem)
any1 also experienced that?
FieryBalrog
Aug 4, 2008, 10:43 AM
the only reason i still play war3 is because of customs. i havent played ladder seriously in years. so when dota, pretty much the only reason i play the game, is causing lockups i consider it a big deal. most of the time i can play on my desktop and its fine, but when i visit home i have to use my mbp and its just plain annoying.
I'd hate to see you play any other computer game, because every little hangup seems to really bother you. One custom map in a game 5 years old on an extremely niche platform, with some of the most stellar support the PC gaming industry has ever seen?
And honestly, why would any company even care that you continue to play their 5 year old game for some custom map? Ruinfx stopped playing, whats going to happen to our non-existent subscription income! You paid $50 5 years ago once and somehow expect every single problem with every single custom map to be fixed for the next however many years? I know its fashionable to bag on game companies but this level of expectation is simply unreal. Anything they fix at this point is far beyond the call of duty.
blizzard took the time to address the sound issues in dota so they obviously care about fixing it. they realize dota is one of the main reasons war3 is still around. i just thought they might fix this annoying issue since it seems pretty common and easy to reproduce.
I just played DotA yesterday- with no issues. At all. In fact, I've never had any.
allthatremains
Jan 24, 2009, 01:23 AM
***** bonkers you all need to play more Defense of the Ancients. I dont know why my 2.4 GHz intel duo iwith 1 GB and 10.5.5 freeze while quiting a game. I am interested in the solution presented by this dude,
well i dont know if this has been posted before but after playing a game of dota if you go back to the main menu and go into the "single player" menu and then the "campaign" menu and then quit the game will exit properly when you hit "quit".
that might work but i cant try it right now or i will freeze and lose all this crap i typed. i blame aapl first! because they need to increase their appeal to games, and dota is basically a religion.
imassents
Jan 24, 2009, 02:18 AM
When Warcraft freezes fullscreen don't hold the power button on the Mac. Try this key combo:
Command+Option+Escape
It's Force-Quit and it works because OS X hasn't crashed (surprise surprise :)). You won't lose anything that you had open in the background and they will all still remain open after force-quitting Warcraft.
The freezing is a problem with Warcraft and not the map. The map works fine in Windows and Warcraft is cross-platform. The Mac version of Warcraft should behave the same as the Windows version - except it doesn't.
vBulletin® v3.8.6, Copyright ©2000-2012, Jelsoft Enterprises Ltd.