TsFreddie / much-programming-core

Such Core, Much Programming | Programming Util for Vortex CORE
MIT License
95 stars 27 forks source link

for same key settings, L3 works but L1 does not work. #8

Open kzwmsyk opened 4 years ago

kzwmsyk commented 4 years ago

In this export.txt, L1 is same as L3. (Actually, L1 is clone of L3.)

Strange to say, though L3's key setting of L_SPACE to NUM_0 work well, L1's key setting of L_SPACE to NUM_0 does not work.

L1's base key setting seems to have limitation, like Issue #7 . I tried delete key settings of some upper keys and then L_SPACE works. I tried and found when I increase more base key settings in L1, more bottom-right keys does not work.

Is this also firmware bug/limitation? (or only my vortex core is broken?)

export.txt

imjoshellis commented 4 years ago

I was also having issues with L1... For me, I couldn't get L1 to update from default.

What (inexplicably) ended up working for me was to clone L1 to L3, which made L1 work like a charm... No clue why, but would love some insight.

Originally, I was just going to test to see whether the layout worked on L3 but I happened to notice L1 started working fine all of a sudden.

Did you find a solution/explanation for this?

isti115 commented 4 years ago

I have encountered very similarly odd behavior while configuring my layouts, after they start to get more complex, some layers lose half of their functionality or just drop out completely at times and swapping two of them can make the situation better or worse.

TsFreddie commented 4 years ago

For now, move keys around seems to make the situation a bit better.

I still have no idea why this happens, but I'm rewriting a custom binary generation routine that moves the data around a little bit which may or may not fix this.

The new routine may take a while to finalize, I'll update you all when it is ready.

TsFreddie commented 3 years ago

Hi, everyone, I wish you all a happy new year.

I know this is long overdue. But I've just updated the MPC with my own implementation of binary generation (use the "Generate Binary (Custom)" button), see if it helps.

I've also added memory usage calculation, so try your best to keep the binary within 8KB. Seems like binary file larger than 8KB can also cause problems.