Floating mouse
#1
Posted 12 September 2012 - 04:16 PM
#2
Posted 12 September 2012 - 04:34 PM
Rerun the setup.exe found in your Ragnarok directory. On the System settings tab, check (or uncheck?) the "Mouse Exclusive" option.
#3
Posted 12 September 2012 - 04:37 PM
#4
Posted 12 September 2012 - 04:44 PM
#5
Posted 12 September 2012 - 05:58 PM
It seems that a client that can successfully save and load its configuration is too much to ask for.
#6
Posted 13 September 2012 - 07:17 PM
Even that doesn't work for me. I recently reinstalled hoping (foolishly) that it might fix the OptionInfo.lua bloating issue. Now I can't get MouseExclusive to work at all (manually changing used to fix it before reinstalling.)I had to open savedata\OptionInfo.lua in a text editing application, delete all of the duplicate sets of lines, change the line "OptionInfoList["MouseExclusive"] = 0" to "OptionInfoList["MouseExclusive"] = 1", then save my changes.
It seems that a client that can successfully save and load its configuration is too much to ask for.
Edited by Bumber, 13 September 2012 - 07:22 PM.
#7
Posted 14 September 2012 - 07:12 AM
Even that doesn't work for me. I recently reinstalled hoping (foolishly) that it might fix the OptionInfo.lua bloating issue. Now I can't get MouseExclusive to work at all (manually changing used to fix it before reinstalling.)
Do you have a file named dinput.dll in your client folder? If so, then try renaming it and then see whether the problem persists.
#8
Posted 14 September 2012 - 09:04 AM
Now I can't get MouseExclusive to work at all (manually changing used to fix it before reinstalling.)
If (and only if) you are on Windows Vista, Win7, or (God help you) Win 8, try moving the RO folder outside of program files. That seems to solve some of the config file issues on platforms with UAC (this will not fix anything if you're on XP, so it's not going to help the OP)
#9
Posted 14 September 2012 - 02:58 PM
That fixed it, thanks! (Not sure what was up with that. I didn't install mouse freedom or anything.)Do you have a file named dinput.dll in your client folder? If so, then try renaming it and then see whether the problem persists.
1 user(s) are reading this topic
0 members, 1 guests, 0 anonymous users