[Bug 41670] BattlEye launcher stuck at 'Starting BattlEye Service...' ( PUBG, Planetside2, H1Z1: King of the Kill, Tibia 11)

[wine-bugs at winehq.org]

https://bugs.winehq.org/show_bug.cgi?id=41670

games at mail.timekill.org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |games at mail.timekill.org

--- Comment #40 from games at mail.timekill.org ---
(In reply to darin.avery from comment #10)
> Right, and if i'm reading the fora correctly (i'm new to ps2, never actually
> played it), then this happened back in March.  So i don't understand the
> gold tests in November and august.
> 
> I do get what look to my untrained eye to be related errors on the
> commandline output, see the attachment in #4 and comment #5.
> 
> On #8's comment: i got a crash every time during the post install start.  I
> suppose i should have closed the installer before trying to play the game
> the first time.  But in any event the first time i run it i get a different
> error in the battleye launcher than subsequent attempts.  I don't have time
> right now to get that error because it takes 10GB download to re-install. 
> I'll see later whether i can find and clear an init file that it would have
> written to so i can get that error again.


You are correct that PS2 didn't have BattlEye in the past.  The game it self,
IIRC, is DX9 based and worked well with Wine after some DirectX code changes
were made for some UI and DX issues (the reason for the bad reviews in the very
beginning).  The addition of BattlEye to counter cheating issues within the
game reduced the wine rating to "Garbage" status.

An alternative I posted somewhere else is that the developers of "ARK: Survival
Evolved" paid BattlEye to create a Linux native version of at least one
version.  WineHQ might be able to implement an anti-cheat API that can pass
those OS/kernel calls out to a native executable to avoid the inevitable
security issues of trying to handle them from withing Wine (which should be
fully in user space).  I am not a developer but I suspect something similar is
happening with calls to 3D graphic drivers (let the native Linux kernel driver
handle the call made from the program's request within Wine, versus having Wine
directly make a hardware interrupt / access from a windows device driver).  I
am assuming BattlEye developers would be favourable to this because it seems
their business model is focused on payments from the developers and not from
end users.

-- 
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.