EPTIn Jak's videos he says that they're skipping 1.1 and now it's 2.0. He also seemed to say that a lot of people on 1.0 wouldn't switch because the gains won't be nearly as large as standard to core 1.0. Main difference is it will offer more flexibility in picking what goes in what control group because it will eliminate a lot of possible finger repetition.
[G] TheCore - Advanced Keyboard Layout - Page 323
| Forum Index > StarCraft 2 Strategy |
|
kingneckbeard
United States24 Posts
In Jak's videos he says that they're skipping 1.1 and now it's 2.0. He also seemed to say that a lot of people on 1.0 wouldn't switch because the gains won't be nearly as large as standard to core 1.0. Main difference is it will offer more flexibility in picking what goes in what control group because it will eliminate a lot of possible finger repetition. | ||
|
JDub
United States976 Posts
On April 30 2014 06:02 kingneckbeard wrote: Fixing RRM and the others - Looks like it has to do with the MapDefinitions.ini file. Right now, the line "W = ForwardMouseButton,ForwardMouseButton,P" appears underneath "[RCGMaps]" and the line "V = V,M,M" appears underneath "[RAMaps]". I'm assuming this means that it thinks W and P are control groups (for random), and that V and M are abilities (for random). When you run TheCoreRemapper.py with these lines as they are, you get "ControlGroupRecall7=V" in the RRM file. When you swap the lines "W = ForwardMouseButton,ForwardMouseButton,P" and "V = V,M,M" and run TheCoreRemapper.py, you get "ControlGroupRecall7=M" Now, I don't know exactly how this thing works, so there might be more to it than what I did, but I think I have the random, terran, and protoss sets in a better place than they were before. http://pastebin.com/093kp0dR Something is still wrong with Ralley point and a few ghost hotkeys. I'm in a hurry, and I don't have time to figure it out. It probably has something to do with the MapDefinitions.ini file though. You may even want to start from the original (rather than my version) and make the changes yourself. I don't know exactly what keys should be in each categories, so I'm worried about how my changes affected the small and large layouts. tl;dr - Need to rearrange MapDefinitions.ini file. I tried to make some of the changes myself, but ralley is still unbound and a few ghost keys. Probably has to do with this file. May want to start from the original and try to make the changes yourself. Author of TheCoreRemapper checking in here. The way MapDefinitions.ini was originally designed was to handle the layouts that did or did not use the mouse buttons (e.g. there used to be a distinction between RRMM (mouse buttons) and RRM (no mouse buttons). This distinction relied on different mappings for keys depending on what type of thing that key was doing. This distinction is no longer necessary. I can make the appropriate changes to TheCoreRemapper.py to fix all the broken keys that aren't being mapped properly to the right side of the keyboard. @Jakatak I see you have not checked in any changes to the GitHub in the last 7 months. If you want to start using it again for development, I can help you out. | ||
|
JaKaTaKSc2
United States2787 Posts
Looks like we've got the 2.0 random files all set! Get em from the github if you'd like to adventure with us! https://github.com/jonnyhweiss/TheCoreConverter Enjoy. (keep in mind that the files for zerg terran and toss are still 1.0 on the github, only the random are 2.0.) | ||
|
Beedebdoo
130 Posts
![[image loading]](http://i.imgur.com/OSDMahn.png) I think the conversion from 1 to Equals and other things have happened where it should not. As Starcraft can't read this, it simply turns off 'Allow Toggle Conflicts' for me, and deletes the line. Luckily it only leaves Weapons Free on the Ghost unbound. | ||
|
JDub
United States976 Posts
On April 30 2014 22:20 Beedebdoo wrote: I think the conversion from 1 to Equals and other things have happened where it should not. As Starcraft can't read this, it simply turns off 'Allow Toggle Conflicts' for me, and deletes the line. Luckily it only leaves Weapons Free on the Ghost unbound. Good catch. Will fix tonight Update: This has been fixed. The latest versions on GitHub do not have this problem anymore | ||
|
kingneckbeard
United States24 Posts
On April 30 2014 12:53 JDub wrote: Author of TheCoreRemapper checking in here. The way MapDefinitions.ini was originally designed was to handle the layouts that did or did not use the mouse buttons (e.g. there used to be a distinction between RRMM (mouse buttons) and RRM (no mouse buttons). This distinction relied on different mappings for keys depending on what type of thing that key was doing. This distinction is no longer necessary. I can make the appropriate changes to TheCoreRemapper.py to fix all the broken keys that aren't being mapped properly to the right side of the keyboard. @Jakatak I see you have not checked in any changes to the GitHub in the last 7 months. If you want to start using it again for development, I can help you out. Thanks so much! Glad the original creator is still here. That is a much better solution  | ||
|
JaKaTaKSc2
United States2787 Posts
| ||
|
witchblade
9 Posts
On May 01 2014 09:47 JaKaTaK wrote: Agreed, kingneckbeard. JDub to the rescue! Now to get on making the Zerg 2.0 layout terrna needs buff, first terran then the ops : ) lol | ||
|
FPyro
Germany47 Posts
I've not played for like 2 weeks or so hoping to forget all the "old" hotkeys to get ready for the new 2.0 ! Gonna be so hard to relearn I suppose? But it's kinda a challenge too and fun when you get the hang of it Best of luck, Jakatak , hope you don't encounter any difficulties and bugs. | ||
|
somesuchnonsense
United States19 Posts
First time posting here, but I've been trying out the RRM 2.0 alpha, mostly as Terran, and have noticed a few things. The Camera and Control group hotkeys don't seem to match up with the Master Spreadsheet. All the hotkeys work, but many aren't assigned to the same number control group or camera position as designated on the spreadsheet. Not really a big deal in terms of functionality, but it was a little confusing when trying to learn the new layout by referencing the spreadsheet. Also, having CC Scan on a rapid fire key is not ideal, but it looks like this is a limitation of the random layout requirement of a rapid fire key for each protoss warpgate unit. Overall, I've found the new setup easier to pick up than previous iterations of the core. I mostly attribute this to the improvement in logical consistency in hotkeys. Particularly having all the transform/siege/burrow on the same hotkeys is much more intuitive. Thanks for all the hard work. | ||
|
R05
Canada47 Posts
| ||
|
Anzki
Finland24 Posts
| ||
Fluff237
Australia4 Posts
since I started playing Starcraft I am creating my own course. It is designed for old gamers who are just starting. At the moment I am creating a build order trainer. The trainer is only for The Core TRM as it is the layout I recommend in my course. If anyone is interested to do some usability test you can have access to it there: http://bepaw.com/mod/buildorder/view.php?id=4 Cheers, Fluff | ||
|
FPyro
Germany47 Posts
You are discriminating against "old gamers"! Well, I like the idea, would be cool if it worked for german keyboards and Zerg too :p It could be really epic if you included like different builds for different races and hotkey combinations like creating control groups and cameras, etc... But that might be a bit of work... :D Jakatak, how is it going?  Hope we'll have 2.0 Core ZRM soon? | ||
|
Fluff237
Australia4 Posts
 I'll have to change my code and let everyone import his own SC2 layout file. I also will let everybody create his/her own BO trainer soon.Good idea too for the control groups and cameras. I thought about it, I think it is important too as I designed my course for people like me, people who don't know what are the recommended control group/cameras. And it's so true that I actually don't know them all yet, so I didn't implement that yet. Thanks for your feedback | ||
|
FPyro
Germany47 Posts
good luck | ||
|
Antylamon
United States1981 Posts
It seems like anything on Q, S, 2, W, 2, 1, and R haven't been swapped out for their righty counterparts yet Also, set rally (excluding set bunker rally, which is on C), Load, and Nuke are unbound. I'm not sure if set rally is intentionally unbound or not, but since it's set for Bunker, it seems to be a mistake I'll update this post with more errors if I find them | ||
|
JaKaTaKSc2
United States2787 Posts
did you DL from github? | ||
|
Antylamon
United States1981 Posts
On May 04 2014 00:37 JaKaTaK wrote: @anty did you DL from github? No, onedrive. The link from the 2.0 video | ||
|
JaKaTaKSc2
United States2787 Posts
| ||
| ||
