| Forum Index > BW General |
|
Jealous
10253 Posts
On October 05 2016 12:58 mca64Launcher_ wrote: did you try diffrent text? I guess they banned noob word Yes, I did. I just tried "Test" right now and it still doesn't let me. I have also e-mailed a bug report to them about it but have not heard back. | ||
|
SuGo
United States681 Posts
Do you know about some sort of BEX error? It seems that wdetector.w is triggering it, so once I try to launch Fish, I see the BW screen but then it crashes and throws the error saying it's wdetector.w I tried uninstalling MCA, deleting the wdetector.w file and letting it automatically refresh, even tried not using mca and use wdetector directly. No matter what, I can't go to fish using wdetector. If I disable wdetector it works fine. I can also go to iccup fine. It seems to just be the wdetector.w file that is causing issues. Any idea? This just started happening today about 3 hours ago and I play on Fish everyday... I even tried System Restore to an earlier date but it doesn't fix this issue. I also tried uninstalling C++ redistribute packages and even .NET frameworks. | ||
|
Hunter Killer
17 Posts
I am trying to connect to the official bnet servers using mca64Launcher with wDetector option checked (after a few months pause), and now I am getting a crash (connecting to icCup still works fine). As far as I know, nothing changed on my computer, except OS updates. Tried deleting the wDetector.w file so that the launcher downloads a new version, also tried to run an older launcher version... same result. Here are the error details: Problem signature: Problem Event Name: BEX Application Name: Starcraft.exe Application Version: 1.16.1.1 Application Timestamp: 496589ca Fault Module Name: wDetector.w Fault Module Version: 3.0.39.0 Fault Module Timestamp: 5592b6c7 Exception Offset: 0000d1c7 Exception Code: c0000409 Exception Data: 00000000 OS Version: 6.1.7601.2.1.0.256.1 Locale ID: 1033 Additional Information 1: 6fa8 Additional Information 2: 6fa8acd705c02428b30dd68cdc885a5c Additional Information 3: 0eac Additional Information 4: 0eacc617e000671973c9894820718808 Also from Event Log Faulting application name: Starcraft.exe, version: 1.16.1.1, time stamp: 0x496589ca Faulting module name: wDetector.w, version: 3.0.39.0, time stamp: 0x5592b6c7 Exception code: 0xc0000409 Fault offset: 0x0000d1c7 Faulting process id: 0xcac Faulting application start time: 0x01d2202cc23132f6 Faulting application path: d:\games\StarCraft\Starcraft.exe Faulting module path: D:\Games\mca64Launcher 2.0.0.121\wDetector.w Report Id: 041a75a1-8c20-11e6-a1f4-84a6c8d6dfbb Any idea about this? (Let me know if you need more info...) Thanks | ||
|
SuGo
United States681 Posts
On October 07 2016 09:06 Hunter Killer wrote: Hi, I am trying to connect to the official bnet servers using mca64Launcher with wDetector option checked (after a few months pause), and now I am getting a crash (connecting to icCup still works fine). As far as I know, nothing changed on my computer, except OS updates. Tried deleting the wDetector.w file so that the launcher downloads a new version, also tried to run an older launcher version... same result. Here are the error details: Problem signature: Problem Event Name: BEX Application Name: Starcraft.exe Application Version: 1.16.1.1 Application Timestamp: 496589ca Fault Module Name: wDetector.w Fault Module Version: 3.0.39.0 Fault Module Timestamp: 5592b6c7 Exception Offset: 0000d1c7 Exception Code: c0000409 Exception Data: 00000000 OS Version: 6.1.7601.2.1.0.256.1 Locale ID: 1033 Additional Information 1: 6fa8 Additional Information 2: 6fa8acd705c02428b30dd68cdc885a5c Additional Information 3: 0eac Additional Information 4: 0eacc617e000671973c9894820718808 Also from Event Log Faulting application name: Starcraft.exe, version: 1.16.1.1, time stamp: 0x496589ca Faulting module name: wDetector.w, version: 3.0.39.0, time stamp: 0x5592b6c7 Exception code: 0xc0000409 Fault offset: 0x0000d1c7 Faulting process id: 0xcac Faulting application start time: 0x01d2202cc23132f6 Faulting application path: d:\games\StarCraft\Starcraft.exe Faulting module path: D:\Games\mca64Launcher 2.0.0.121\wDetector.w Report Id: 041a75a1-8c20-11e6-a1f4-84a6c8d6dfbb Any idea about this? (Let me know if you need more info...) Thanks Ok cool, so it's not just me.... This is the same exact issue I'm having from my earlier post. Well, except his says he is using wdetector 3.39, mine is the most updated 3.40. Also he said he hasn't played in a few months, but I played every day and just happened a few hours ago. Otherwise the error message is the same. | ||
|
[sc1f]eonzerg
Belgium6793 Posts
| ||
|
SuGo
United States681 Posts
Even though it randomly occurred, I waited about 2-3 hours, and now it fixed itself.... lol I think it's some weird memory/64-bit OS issue. Strange that a few of us all had this issue at the same time though. Might have something to do with that wDetector.w connecting to a server as well, idk. | ||
|
RedW4rr10r
Switzerland749 Posts
On October 07 2016 11:13 ProtossGG wrote: UPDATE FOR ALL: Even though it randomly occurred, I waited about 2-3 hours, and now it fixed itself.... lol I think it's some weird memory/64-bit OS issue. Strange that a few of us all had this issue at the same time though. Might have something to do with that wDetector.w connecting to a server as well, idk. Thanks for that hint! My friend and I had the same issue yesterday night, like ~9 hours ago. Now it's working again without doing anything actually xD | ||
|
SuGo
United States681 Posts
On October 07 2016 19:04 RedW4rr10r wrote: Thanks for that hint! My friend and I had the same issue yesterday night, like ~9 hours ago. Now it's working again without doing anything actually xD Yeah, I would say if it happens to anyone, just wait it out. I was about to reformat my entire computer lol. But I still uninstalled SC, .NET frameworks, reinstalled/updated Drivers, even tried not using MCA, etc etc. I tried it all and wasted a lot of time. Just wait out or unless anyone knows the exact root cause to avoid it. | ||
|
chrisolo
Germany2609 Posts
 edit: found it: http://www.teamliquid.net/forum/brood-war/465487-mca64launcher-20?page=30#597 Thank you anyway  | ||
|
Jealous
10253 Posts
| ||
|
iu1nguoi0iuminh
Vietnam44 Posts
My index apm is about 200, I don't know how to increase it. My hotkey is numbers 1, 2, 3, 4 and it I used about 30% of total index apm. | ||
Ziggy
South Korea2105 Posts
| ||
|
mca64Launcher_
Poland629 Posts
| ||
|
zaMNal
Mongolia385 Posts
![[image loading]](http://i.imgur.com/NknCXYB.png) weird supply display when obs or watch replay. 5 = 4.999999999999994390679 etc. | ||
|
B-royal
Belgium1330 Posts
| ||
|
Jealous
10253 Posts
| ||
|
oKhydra[RO]
3 Posts
First of all , i m back from starcraft 2 , and is verry hard for my eyes to play on bigest monitor on main resolution. On window mode at 1900/1080 , cant play because units and buildins are so little. So i want to ask you , how can i modify the window mode size 2x at costum window size, with some pixels larger. I dont want to change the main resolution. Thanks a lot! | ||
pheer
5392 Posts
On October 31 2016 16:31 oKhydra[RO] wrote: I dont want to change the main resolution. Thanks a lot! You have to change the resolution. There is no way to make the game appear 3x, 4x, 5x in window mode... the only option is 2x. So you will have to change your resolution to 800x600. If you have NVidia or ATI graphics, there is a custom resolution option for each game. You can set starcraft.exe to run in 800x600 and it will automatically change the resolution when you run the game. | ||
|
Golgotha
Korea (South)8418 Posts
Thanks for this! love the mcalauncher since it has so much more. i like the overlay that displays the race of each player. i got the shittyplugin to show up in wlauncher but can't seem to find the settings to turn on overlay and other stuff. | ||
|
mca64Launcher_
Poland629 Posts
| ||
| ||
|
|
Monday Night Weeklies
WardiTV Invitational
Replay Cast
WardiTV Invitational
ByuN vs Solar
Clem vs Classic
Cure vs herO
Reynor vs MaxPax
Replay Cast
Sparkling Tuna Cup
Replay Cast
Wardi Open
|
|
|
EPT
