11-17-2013, 10:22 AM
Would it not go in inis folder?
Gaming Rig: Intel i7 6700k @ 4.8Ghz | GTX 1070 TI | 32GB RAM | 960GB(480GB+480GB RAID0) SSD | 2x 1TB HDD
Changing Hotkeys In PCSX2 1.0.0 Emulator
|
11-17-2013, 10:22 AM
Would it not go in inis folder?
Gaming Rig: Intel i7 6700k @ 4.8Ghz | GTX 1070 TI | 32GB RAM | 960GB(480GB+480GB RAID0) SSD | 2x 1TB HDD (11-17-2013, 10:20 AM)nhattansuphu Wrote: just create it into the main folder right? exactly @ blyss : nope. It behaves like the portable.ini file.
CPU : AMD Ryzen 7 3800X
Mobo : Asus PRIME B450-PLUS GPU : NVIDIA GeForce RTX 3070 RAM : 16 Go
11-17-2013, 11:02 AM
(11-17-2013, 10:22 AM)jesalvein Wrote: exactly feeling not working, I did exactly like u said but still... I wonder if my pcsx2_keys.ini is wrong: States_FreezeCurrentSlot=P States_DefrostCurrentSlot=\ States_CycleSlotForward=] States_CycleSlotBackward=[ Framelimiter_TurboToggle=ctrl-alt-TAB Framelimiter_SlomoToggle=ctrl-alt-F4 Framelimiter_MasterToggle=ctrl-alt-F5 Sys_Suspend=` Sys_RenderswitchToggle=ctrl-alt-F6 GSwindow_CycleAspectRatio=ctrl-alt-F7 (11-17-2013, 11:02 AM)nhattansuphu Wrote: feeling not working, I did exactly like u said but still... It _looks_ ok, but you could just try it yourself, check if it behaves as expected, and then share your conclusions on this thread. Thanks
<These are for devs>
The following are my guessing. If I'm wrong, never mind. First of all, the summary of my hypothesis: A parameter is forgotten from wxFileConfig cfg instance, so remapping function doesn't work. Code: <the summary image> 1. The wxConfigBase (base of wxFileConfig) constructor needs 5 parameters. Code: wxConfigBase::wxConfigBase(const wxString& appName, 2. The wxFileConfig constructor needs 6 parameters. Code: wxFileConfig::wxFileConfig(const wxString& appName, const wxString& vendorName, 3. The wxFileConfig cfg instance has only 5 parameters, but wxFileConfig constructor needs 6 parameters. Because of this wxConfigBase constructor would be called. Is this no problem? I worry about wxConfigBase constructor sets only 2 variables in this context. Code: void AcceleratorDictionary::Map( const KeyAcceleratorCode& _acode, const char *searchfor ) Edit: I confirmed that it works.
11-18-2013, 05:40 PM
(This post was last modified: 11-18-2013, 05:40 PM by Blyss Sarania.)
(11-17-2013, 11:25 AM)avih Wrote: It _looks_ ok, but you could just try it yourself, check if it behaves as expected, and then share your conclusions on this thread. I tried it. Key remapping doesn't work in r5745. Despite creating the file, keys remain the same. Gaming Rig: Intel i7 6700k @ 4.8Ghz | GTX 1070 TI | 32GB RAM | 960GB(480GB+480GB RAID0) SSD | 2x 1TB HDD
11-18-2013, 05:42 PM
(11-18-2013, 05:17 PM)tadatada Wrote: First of all, the summary of my hypothesis: Typically, some observation is first made, and then a hypotheses tries to explain this observation. When you start with a hypotheses, it's not clear which observation you're actually trying to explain. If you're trying to explain an observation where the remapping doesn't work, then it would be useful to first give some details of your case. E.g. what does your file look like, where did you put it, how did you conclude that it doesn't work, etc, and then other people could also come up with suggestions. Specifically, while I haven't tested remapping recently, I did test it a while ago (in fact, it was me who wrote the remapping code), and it worked just fine (especially after r4918 which fixed "normal" keys as remap targets). So, if it doesn't work for you, give us the details first, please
11-18-2013, 05:43 PM
(This post was last modified: 11-18-2013, 05:45 PM by Blyss Sarania.)
(11-17-2013, 10:22 AM)jesalvein Wrote: exactly Actually, it WORKS if you put the file in the inis folder. Haha. Winning. But the file above conflicts with GSDX shortcut F7, and THAT one doesn't work(CTRL-ALT-F7), also CTRL-ALT-TAB conflicts with Windows shortcut ALT-TAB. This is in non installed pcsx2(e.g. binary package), and the file above. Gaming Rig: Intel i7 6700k @ 4.8Ghz | GTX 1070 TI | 32GB RAM | 960GB(480GB+480GB RAID0) SSD | 2x 1TB HDD
11-18-2013, 06:18 PM
(11-18-2013, 05:43 PM)Blyss Sarania Wrote: Actually, it WORKS if you put the file in the inis folder. Haha. Winning. True. GSdx handles some keys by itself (F5 change deinterlace mode, F7 change shader, etc), and windows also handles some keys before they get to PCSX2. So those keys will conflict with PCSX2. I modified the above file as follows (and put at as pcsx2_keys.ini at the inis folder), and it works: Code: States_FreezeCurrentSlot=9 Not sure how the '\' key should be put at the file, and also ` didn't work, but ' did work. YMMV, but generally it should work except for keys that conflict with Windows or with GSdx. |
« Next Oldest | Next Newest »
|