WombatFromHell / OriginSteamOverlayLauncher

An executable wrapper for Steam to make third-party launchers more convenient to use with a Steam Controller
MIT License
413 stars 25 forks source link

Doesnt work with Battlefield 4 #24

Closed Serkan14 closed 6 years ago

Serkan14 commented 6 years ago

The first try actually worked I could use the overlay but after a couple of times (always a random ammount) the game crashes. And now the overlay launcher doesnt work at all. Even after reinstalling it. Is there anything that can be done ?

WombatFromHell commented 6 years ago

It likely depends on what other overlays you're running (if any). Some Origin games are very buggy with stacking multiple overlays (like Afterburner, Origin, and Steam together). It can also depend on which GPU you're using (AMD is more difficult to get working than Nvidia).

There are some pointers on the OSOL project Wiki pages if you skim through them.

(Edit: Also, apologies for the delay in response. I've been busy with non-OSOL related projects.)

Serkan14 commented 6 years ago

Hey no problem man. running no extra overlays besides Steam and ofc Origin since u play bf4 on it but I disabled origin ingame. Yeah I have an AMD GPU. an R9 380. Maybe ill look through the wiki but i guess there is no point in trying it with an amd gpu. besides I really have no clue what im doing anyway haha. Im not really good with that stuff. Thanks for your answer tho. Appreciate it

SubSonix commented 6 years ago

I've used it with BF4 in the past myself and know it worked. I can't test it right now, but I can eventually if no one else can try.

Serkan14 commented 6 years ago

Some Kind of update from origin probably messed it up then. Also r u using an AMD GPU ? I can try again later. Will let you know how it went

Serkan14 commented 6 years ago

Tried it again now and I cant get it to work. Cant really find anything on the wiki too but maybe im just blind. BTW I turned this AMD External Events Utility off too.

WombatFromHell commented 6 years ago

Marking this as invalid as it falls outside the current scope of the OSOL project. If this issue can be narrowed down to being OSOL-specific in cause then feel free to attach additional information and I'll follow it up.