Correct me, if I am wrong, but did the last Windows 10 (Pro x64) patch broke something?
I was just going to look for something on my client, going to show someone an ingame mechanic, but suddenly, no module is booting up. Actually, their frame will flash once and will be terminated immediately. Exception: Certification works.
Just a simply crashlog, even on the farmmanger, lol.
Welp. If no one has a clue, isn't that bad anyways. Not into SRO anymore.
Edit: Seems like that neither the launcher nor the direct .exe launch works anymore. Nothing happens at all. Seems to be really odd. Works on my VMWare (Win7 U x64) though.
I have no bloody clue whatever happened ...
It seems to work again, despite the fact that windows update hasn't done anything nor I did anything differently than ignoring the issue lol
[Only registered and activated users can see links. Click Here To Register...]
PS: Can anyone tell me why the console trigger on Windows 10 acts weird? Using Shift + ^ usually was opening the console (and thus might be the cause of players complaining stupidly about "Console no opening!", now I get what they did mean), since that is not working anymore, why the hell ever, the current one is Shift+^+# ... that is kinda weird.
I was just going to look for something on my client, going to show someone an ingame mechanic, but suddenly, no module is booting up. Actually, their frame will flash once and will be terminated immediately. Exception: Certification works.
Just a simply crashlog, even on the farmmanger, lol.
Welp. If no one has a clue, isn't that bad anyways. Not into SRO anymore.
Edit: Seems like that neither the launcher nor the direct .exe launch works anymore. Nothing happens at all. Seems to be really odd. Works on my VMWare (Win7 U x64) though.
I have no bloody clue whatever happened ...
It seems to work again, despite the fact that windows update hasn't done anything nor I did anything differently than ignoring the issue lol
[Only registered and activated users can see links. Click Here To Register...]
PS: Can anyone tell me why the console trigger on Windows 10 acts weird? Using Shift + ^ usually was opening the console (and thus might be the cause of players complaining stupidly about "Console no opening!", now I get what they did mean), since that is not working anymore, why the hell ever, the current one is Shift+^+# ... that is kinda weird.