Driver

There is no software driver support for the Vortex CORE at the time of release, and this review, with all functionality and programming being hardware based. As such, I have chosen to combine the Driver and Performance pages into one here.

Performance

At first thought, it might seem ridiculous to even consider such a thing as it might limit functionality of a peripheral. I will admit I had a strong apprehension myself, and this did not change until 12 days into using the keyboard. It did not help that I was also using a larger than full size keyboard along with this so muscle memory was not a helping factor. I decided to print out a layout map and have it on the bottom of my monitor and this helped tremendously. So this is how the CORE is programmed for the default layer as well as secondary functions on the default layer (Fn +, Fn1 + and Fn1 + Shift +):

There were a few things I liked, and did not like about the default layout. For example, with there already being a Shift button I would have rather Caps lock be replaced by Tab or another Fn/Fn1 button on the left instead. Secondly, the manual is incorrect in the description of the Fn1 + Shift descript in that the actions are all one row lower than they actually are. This means that in actuality the secondary legends associated with those numbers (!, @ etc) are on row 2 as well when using Fn1 + Shift. So please note this and do not rely on the layout provided blindly. Thankfully this is where the programmability of the CORE comes in to assist with customization as you would prefer the layout be.


By default, you are in layer L0 which can not be programmable and the layout above is applicable to it. Fn + M is a way to access L0 as well, and there is no backlighting under the left space bar to denote this. Fn + < activated layer L1 and the LED under the left space bar lights up red accordingly as a visual notification. Similarly, Fn + > and Fn + Right shift activates layers L2 and L3 with the corresponding notification LED color being green and blue respectively. This is the second LED on the non-backlit version and both are thus for function only, not aesthetics. The upcoming RGB backlit version, which is what I have a sample of and will inevitable cost more, has RGB lighting under all the keys with LED control and animation as well if that is something you were interested in. For those looking to the non backlit version, Pn + T, and Pn + Q/W/E will allow some control over the three RGB LEDs. I will leave it to you to enjoy what these do.


Say you want to program layer L1. The left space bar will have the red light under it as seen above, and the following are the steps for programming:
1) Press Fn + right Control to initial programming. The LED under the right space bar will light up a steady blue.
2) Press the key you want to program, this will be visually confirmed by the right space bar LED now flashing red.
3) Press the key(s) you want the above key to be assigned to do, and then press Pn to end the programming. Following this, the right space bar LED will turn back to a steady blue.
4) Repeat steps for other keys as necessary, and then press Fn + right control again to exit programming. The right space bar LED will now turn off as expected.

This sounds good in theory but in practice has some limitations. For instance, you can not re-program the keys assigned for M, <, > and right Shift since they help toggle between the layers. You also can not re-program right Control since it is used to activate and exit programming mode. Then there is the matter of the secondary functions- if you wanted to use a secondary function normally available by pressing Fn/Fn1/Fn1 + Shift, then it will be a while before you are satisfied and not have done an error.

It is for this reason that Vortex has some limitations. You can program the default layout descript as well as Fn layer descript, but no more. Between the two, you get 94 keys although I will note here that the two space bars can not be programmed independently of each other so 92 it is. Still plenty enough I would say, and I found myself mostly using the default layout prescript with L1 and L2 at most.

A couple of other rules:
1) Each key programming can have a maximum of 32 key strokes, so you can set up complicated macros.
2) Time delays between key strokes are supported, and that is where the Fn + descript comes in. Fn + T gives you 15 ms of delay each time, Fn + G gives you 0.1 s delay each time, and Fn + B gives you 0.5 s delay each time they are pressed. Each consecutive time delay will add up, and you can use combinations as you please, but they will only count as one key stroke per delay between key strokes thus not cutting into your allocation of 32 key strokes.

Two more points concerning restore to factory settings:
1) Press and hold Fn + R to erase any programming on the layer you are on. This of course applies only to L1 through L3, and is shown by the left space bar LED flashing white for 5 seconds after which you can stop holding the two keys.
2) Press and hold both Alt keys to erase any programming on the entire keyboard aside from L0. This too will be shown by the left space bar LED flashing white for 5 seconds after which you can stop holding the two keys.

Finally, if you found it a hassle to get to the arrow keys but needed them consistently, then pressing left Windows + left Alt + right space bar together will turn right Shift, right Alt, Menu and right Control as arrow keys.

This was a massive wall of text, and may have led to a lot of readers losing interest in the product. I would say it is not as bad as it looks, but also understand part of the concerns. A fully programmable keyboard with a GUI based configurator would have helped a lot. But there is just not enough demand to warrant it from a mass produced, and yet extremely niche product such as this. All this is covered in the manual a buyer will get, so there will be a reference available. Take your time, and get used to it.


Back to the keyboard as a whole now. This Vortex CORE sample came with Cherry MX Blue RGB switches, and as usual Cherry QC was up to par. I measured the actuation force only here since the audible click makes it fairly obvious, and the average across 20 keys was 50.3 cN, very close to the rated 50 cN. There was a slight "scratchy" feeling as the stem pressed down though, and this is something you will really only be able to tell by comparing against switches without said feeling. Overall, not bad at all.


It took me a good one week plus to get used to the CORE, and even then I had to stop using any other review keyboards to get anywhere near my usual 95-105 WPM typing speed. The sound clip above is at an average of 90 WPM with 85% and above accuracy, and for context this is the Cooler Master Storm Trigger Z with Cherry MX Blue (non RGB) switches, and this is the Bloody B840 we took a look at previously with their new LK2 Blue switches. The PBT, DSA keycaps with the aluminum case have a tangible contribution to the sound signature here as well.


There is six-key-rollover USB here, as Aqua's test confirmed this. The reason you see more than 6 keys highlighted there is because I tested again just to double check. Similarly, no key chatter was detected using Switch Hitter.