Jump to content

mgg

Members
  • Content Count

    3
  • Joined

  • Last visited

Community Reputation

1 Neutral

About mgg

  • Rank
    On the Coast
  1. Another thought - how about a server just for Linux-based players? I suspect with a password and a few Linuxy inconveniences, one could make it too hard / too much hassle for Windows players to easily join. On the downside, there'd probably only be like 2 of us playing ;) Alternatively, someone should dig into http://bugs.winehq.org/show_bug.cgi?id=31910 and see if we can just implement the missing bits that stop BE working properly - probably going to need it for the standalone.
  2. mgg

    Battleye Crash? Please Help

    I also sent an email and got a very helpful reply. In my case, it seems that it's a missing wine feature (interested Linux / wine users see http://bugs.winehq.org/show_bug.cgi?id=31910), so I'm stuck on non-BE servers until the wine guys sort it out. Oh well, at least it's good to know what the problem is and BE was very helpful in providing the info they did. Best of luck getting your issue sorted too :) It might be worth trying temporarily disabling anything that might interfere with exception handling / interrupts (e.g. antivirus/antimalware/debuggers). Obviously turn it back on ASAP after testing!
  3. mgg

    Battleye Crash? Please Help

    Good bug report :) I see exactly the same behaviour. I'd add that if I connect to a non-BE server (change filter prefs to make sure), then I have no problems at all. In my case, the error is "Unhandled exception 0x80000003 at address 0x6b88dd (thread 0009); 0x006b88dd: int $3". My situation is slightly different, as I'm running it under Wine, but it was fine up until 1.17[67]. In that version, BE started to hook into the scripting engine with breakpoints (which is what the "int $3" assembler instruction is), and presumably something to do with this isn't working. Perhaps the interrupt handler isn't installed in time? I fear there's not a lot we can do about it, short of emailing the crash reports to BE and hoping they find the cause. See http://battleye.com/support.html and be very polite :)
×