First open StarCraft II (however), login, and then alt-tab out and start the editor. Along with the message "Killed." after the wait. If you hit Yes some information is shown at the bottom:ĭownloading region information (5s)"Ī) the whole thing will crash, along with a Blizzard response window that allows you to elaborate what happened.ī) your whole computer will freeze for 5 minutes. "Warning: you must log in to to authenticate your StarCraft II account before using the editor. If you start-up the editor via `cd ~ & cd '.wine/drive_c/Program Files (x86)/StarCraft II/Support64' & wine64 SC2Editor_圆4.exe`Ī StarCraft II window will show up and it'll seem to be loading fine.
#STARCRAFT 2 EDITOR WONT PUBLISH MAP 2015 HOW TO#
That may help! I have no idea how to analyze it in the context of WINE :-( No crash prompt (as you mentioned) or editor crash logs, but the editor still fails to start up.Ī. I tried installing winhttp with winetricks, but that did not work.
#STARCRAFT 2 EDITOR WONT PUBLISH MAP 2015 CODE#
So I'm guessing this is a bug in their code that isn't reached on MS Windows systems, and happens to be reached using WINE? Looking on battlenet I don't see no new editor bugs. I assume this is their code accessing memory that isn't theirs anymore. ACCESS_VIOLATION reading from 0x000000000000FFFE: DBG-OPTIONS DBG-ADDR("") DBG-OPTIONS ~/documents/StarCraft II/EditorLogs/ 23.12.03 crunchbang B48645 Crash/ 23.12.03 crunchbang B48645 Crash.txtĮxecutable D:\StarCraft II\Support64\SC2Editor_圆4.exe I think the authentication step in the editor startup is new with a recent patch, and that is where the bug is. The editor used to work perfect on my system, 2 patches ago.
0 kommentar(er)
