Jump to content

After injecting WLauncher, X and A on Controller no longer function


Go to solution Solved by PaulMuadDib,

Recommended Posts

Posted

After I disable Battleye, go to Main Menu, inject WLauncher, start Story Mode and/or go to Invite Only Session; X and A on Controller no longer function properly.  For example, I can't run, jump, or access pause screen menus or maps.  Any ideas?  Anything I should disable? 

  • Administrators
Posted
5 hours ago, PaulMuadDib said:

After I disable Battleye, go to Main Menu, inject WLauncher, start Story Mode and/or go to Invite Only Session; X and A on Controller no longer function properly.  For example, I can't run, jump, or access pause screen menus or maps.  Any ideas?  Anything I should disable? 

Interesting, I need to check it.

Posted

I think the new update got rid of all FSL file saves.  But removing the LUA scripts folder returned my controller to normal.  Let me know what you think.  Thanks.

  • Administrators
Posted
4 hours ago, PaulMuadDib said:

I think the new update got rid of all FSL file saves.  But removing the LUA scripts folder returned my controller to normal.  Let me know what you think.  Thanks.

Yes, FSL is outdated for now, until the dev won't update it. Also, I can't fix lua script, the menu works fine. Report that problem to script author.

Posted

@med1ed Well I originally, I didn't have any LUA scripts loaded.  Then that last time I started a game, they were there and that's when the trouble began.  So naturally through process of elimination I figured out that they were the problem.  I didn't attempt to isolate which one was the issue.  But the speedometer was plainly active, other than that, I don't know what other LUA were running.  I just took out the whole folder. 

  • Solution
Posted (edited)

@lightsword8045I went into Windows (C:) > ProgramData > DIS2RBED and I deleted the Lua folder.  It gets rid of all of the Lua Scripts, but your controller works again.  I didn't take the time to turn each one off/on to determine which one was affecting my controller.  I didn't care, just wanted to make it work again.

Edited by PaulMuadDib

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...