Win10 modifier hotkeys no longer work

[gtcard]

hoping someone has some insight into this problem--i recently updated to windows 10 due to win7 end of life, and my skyrim install with MO works for the most part. The one part that doesn't seem to work anymore is that aside from the default keybinds in the normal game settings, any keybinds that require a modifier key no longer works. That means Shift key doesn't go back a step anymore in SL, ctrl key no longer modifies just that one stage, etc. In fact, these keys still don't work even if I change the binding to another key (ie: changed Shift key to Y for SL, and it still doesn't go back). The hotkey for ENB brute force mode (Shift+B) also doesn't work. However, the hotkey to bring up the ENB settings Shift+Enter does work. Running/walking in the game also works (Shift +WASD).

 

Anyone have any idea what may be happening here? This started right after I upgraded to win10 from win7. No settings were changed as far as I am aware.

[Guest]

2 hours ago, gtcard said:

надеясь, что кто-то поймет эту проблему - я недавно обновился до windows 10 из-за окончания срока службы win7, и моя установка skyrim с MO работает по большей части. Одна часть, которая, кажется, больше не работает, состоит в том, что, кроме стандартных привязок клавиш в обычных настройках игры, любые привязки клавиш, для которых требуется клавиша-модификатор, больше не работают. Это означает, что клавиша Shift больше не возвращается на шаг назад в SL, клавиша ctrl больше не изменяет только один этап и т. Д. Фактически, эти клавиши по-прежнему не работают, даже если я изменяю привязку к другому ключу (то есть: изменен Клавиша Shift на Y для SL, и он все еще не возвращается). Горячая клавиша для режима грубой силы ENB (Shift + B) также не работает. Однако горячая клавиша для вызова настроек ENB Shift + Enter работает. Бег / ходьба в игре тоже работает (Shift + WASD).

 

Кто-нибудь знает, что здесь происходит? Это началось сразу после того, как я перешел на win10 с win7. Насколько я знаю, настройки не были изменены.

если клавиатура рабочая,поставь обратный модификатор на другую клавишу.

[gtcard]

On 1/10/2020 at 10:54 PM, makosh said:

если клавиатура рабочая,поставь обратный модификатор на другую клавишу.

i tried reassigning the reversal key, but it still doesn't work. what i notice is that pretty much all 2 key combinations (modifier + hotkey) shortcuts don't work for any of the mods. 2 key combinations for my enb work, except for "brute force mode" which is Shift + B. this used to make my skyrim stutter like crazy when activated, but now it has no effect. Shift + Enter will still bring up the ENB menu, and Shift + F12 will still turn on and off the ENB. shift does work in the game itself, because i can hold Shift to press WASD and my character will walk. i can also use shift to capitalize letters in the console, so the key is working. it is like whatever script or or code that's checking for hotkeys used with modifier for mods and ENB isn't working. 

[Guest]

6 minutes ago, gtcard said:

Я попытался переназначить ключ отмены, но он все еще не работает. Что я заметил, так это то, что почти все сочетания клавиш (модификатор + горячая клавиша) не работают ни для одного из модов. 2 комбинации клавиш для моей работы enb, за исключением «режима грубой силы», который называется Shift + B. Это раньше делало мой скайрим заиканием, как сумасшедший, когда активирован, но теперь это не имеет никакого эффекта. Shift + Enter по-прежнему вызовет меню ENB, а Shift + F12 по-прежнему включает и выключает ENB. shift работает в самой игре, потому что я могу удерживать Shift, чтобы нажать WASD, и мой персонаж будет ходить. Я также могу использовать Shift для заглавных букв в консоли, так что ключ работает. это похоже на любой скрипт или код, который проверяет горячие клавиши, используемые с модификатором для модов, а ENB не работает. 

какой мод использует горячие клавиши,по мимо секслаба?

[gtcard]

6 hours ago, makosh said:

какой мод использует горячие клавиши,по мимо секслаба?

looks like any mod that uses modifier hotkeys defined in MCM menu instead of hotkeys built into the game engine. SL Tools Shift + H to open up the menu to select stages doesn't work, and Shift + X in SLSO to show/hide the enjoyment bars also doesn't work. i believe something is up with my skse and install of win10, as i'm having a lot of problems loading saves with a *.skse file attached to it too. i'd imagine it's skse in the background that's allowing all these modifier hotkeys to work as well

[Just Don't]

Where is your Steam/Skyrim installed? You could try to disable the Steam overlay and see if the issue persist. Also, set all your executables to run as admin if you haven't already.

[Guest]

4 hours ago, dontknowdontcaredontask said:

Где установлен ваш Steam / Skyrim? Вы можете попробовать отключить оверлей Steam и посмотреть, не исчезнет ли проблема. Кроме того, установите все свои исполняемые файлы для запуска от имени администратора, если вы еще этого не сделали.

ты уверен что это мешает?

[Grey Cloud]

11 hours ago, gtcard said:

i believe something is up with my skse and install of win10,

I doubt it has anything to do with Win10. More likely it is a mistake you have made when reinstalling. Double-check you have not missed anything.

[gtcard]

my win7 was upgraded to win10 via microsoft's update tool. since the upgrade i notice the problem with the shift key not being passed to mods. the shift key itself works fine within the game (ie using it with WASD will make my char walk, and i can type upper case letters in the console). it's as if whatever process running in the background which listens for the shift key used for mods doesn't work. that's really the best way i can explain it. in fact even normal alignment keys are severely delayed during animations. the JKL; keys for actor alignment seem to be delayed 5-10 seconds (ie i can keep pressing it and not see movement for a few seconds, then see the actor shifted 10 or 15 steps in the pressed direction all at once). 

 

the problem persists even if i change the modifier key from shift to something else. i tried remapping it to Y instead of shift, and it's still not being registered. really not sure what's going on. my steam (and skyrim) install is on a drive separate from my primary OS drive, so my skyrim install, mod organizer files, and enb files were completely untouched before and after the win10 upgrade. the issue was immediately evident after the win10 upgrade though, so i was some widely known compatibility issue somewhere. i guess that isn't the case

[GenioMaestro]

6 hours ago, gtcard said:

t's as if whatever process running in the background which listens for the shift key used for mods doesn't work. that's really the best way i can explain it. in fact even normal alignment keys are severely delayed during animations. the JKL; keys for actor alignment seem to be delayed 5-10 seconds (ie i can keep pressing it and not see movement for a few seconds, then see the actor shifted 10 or 15 steps in the pressed direction all at once). 

Your problem not have any relation to Win7 or Win10.

Seems that your game have Script Overload. Enable the Papyrus log and look for Stack Dumps.

Try locate the mod causing the problems or upload your papyrus log.

Other option is open your savegame with ReSaver and look the Active Script section.

 

The process of the keys in SexLab are made with Scripts. If the Papyrus Script Engine is Overloaded the script that process the key can have a big delay, from 1 second to 3, 10, 15, 30...

The process of the movement keys (WASD) are procesed internally by the game, made in C++, and are not affected by the overload in the Papyrus Script Engine.

[gtcard]

On 1/18/2020 at 3:57 AM, GenioMaestro said:

Your problem not have any relation to Win7 or Win10.

Seems that your game have Script Overload. Enable the Papyrus log and look for Stack Dumps.

Try locate the mod causing the problems or upload your papyrus log.

Other option is open your savegame with ReSaver and look the Active Script section.

 

The process of the keys in SexLab are made with Scripts. If the Papyrus Script Engine is Overloaded the script that process the key can have a big delay, from 1 second to 3, 10, 15, 30...

The process of the movement keys (WASD) are procesed internally by the game, made in C++, and are not affected by the overload in the Papyrus Script Engine.

you're exactly right, it feels a lot like script lag. i've had this issue before when papyrus kept stack dumping and my keys are delayed. the difference with this case though is it started happening after i upgraded to win10 over my win7 install, with no changes in my mods or anything. since you know what i'm talking about, this is the best way i can describe this issue:

 

sometimes back on win7 when i have script lag, i sometimes have to hold onto the shift key a bit longer while pressing JKL; to do a reverse move. it's like it just takes a bit longer for the scripts to register. right now, it feels like the scripts are so lagged, the shift key is never registered as being held onto. so whenever i press JKL; while holding shift, the mods think I'm just pressing JKL; without holding shift. the amount of lag i'm getting now is much more severe than what i got on win7.

 

also particularly peculiar is that Shift + B no longer activates my ENB's "brute force" mode. i'm using the exact same enb as before, with the exact same enblocal.ini and enbseries.ini (steam folders and mod folders are installed to separate drives, so nothing overwritten during win10 upgrade). all the other ENB hotkeys work (shift+enter, shift+f12). 

 

since i am using MO, it's easy for me to rename my current skyrim folder and do a fresh launch of it with my modlist cleared and fresh install of ENB 0.404. while i can't test if this has any issues with the shift keys in sexlab commands, the problem remains with Shift + B not activating brute force mode on the enb. i feel like whatever's causing this keyboard shortcut to not work on my enb is probably related to what's causing the script lag and my shift key not working in mods.

 

i don't know what else to try since i've already ruled out it's not a mod related issue and even on a completely fresh install of skyrim from steam, i have the problem with enb's brute force mode not activating

[gtcard]

one thing i do notice is that after my upgrade to win7, my microsoft c++ redistributable packages for 2012, 2013, and 2017 were updated with a jan 6, 2020 install date (the day i upgraded windows) while my 2005, 2008, and 2010 redistributables were not updated. i see .cpp files in skse's src folder, so skse is written in c++ right? can this be an issue, since skse is also required by enb?

[GenioMaestro]

3 hours ago, gtcard said:

i don't know what else to try since i've already ruled out it's not a mod related issue and even on a completely fresh install of skyrim from steam, i have the problem with enb's brute force mode not activating

Seems that you have two diferent and separated problems and you are mixing it and joined it, simply, because the two problems have relation to the Shift key. Go to separate it.

 

If the combinations of Shift+Enter and Shift+F12 works in ENB but the combination Shift+B not works only can be caused because other program are making a interference in the keys. Open your enblocal.ini and change the KeyBruteForce=66 to KeyBruteForce=101 (numpad 5) or to any other key. Look the key codes in this page.

 

Second, have you look your Papyrus.0.log???

Save your game while you are running the animation and open the savegame with Resaver to know how many Active Scripts you have. We need know, with a 100% security, if the problem are related to the Active Scripts.

 

How many FPS do you have in your game with Win10?

The execution of the scripts are linked to the Frame Rate. As more FPS more scripts are executed each second.

If you play Skyrim below 30 FPS you can have a lot of delay in the scripts up to 5, 10, 30 seconds.

[GenioMaestro]

2 hours ago, gtcard said:

can this be an issue, since skse is also required by enb?

I not know where you get that info, but is totally false. SKSE and ENB not have any relation. Are two diferent and separated utilities and you can run each one of them in a separated way.

 

If you use the two tools, SKSE and ENB at the same time, the configuration of each tool, inside SKSE.ini and enblocal.ini, are related because one utility can cause interferences in the other utility.

You can not use ExpandSystem64 in enblocal.ini if you put DefaultHeapInitialAllocMB=1024 in SKSE.ini

But that not mean that you need install SKSE to use ENB and you not need remove SKSE to use ENB.

Simply mean that you must put the correct configuration in each INI file.

 

Aditionally, the C++ libraries are managed by the operating system. Normally, a problem in one of the libraries cause CTD. But the problems that you have with the keys not have any relation to the the C++ libraries.

[gtcard]

On 1/20/2020 at 1:44 AM, GenioMaestro said:

Seems that you have two diferent and separated problems and you are mixing it and joined it, simply, because the two problems have relation to the Shift key. Go to separate it.

 

If the combinations of Shift+Enter and Shift+F12 works in ENB but the combination Shift+B not works only can be caused because other program are making a interference in the keys. Open your enblocal.ini and change the KeyBruteForce=66 to KeyBruteForce=101 (numpad 5) or to any other key. Look the key codes in this page.

 

this is good advice thank you. i tried swapping the Enter and B keys for brute force and show editor (13 with 66), and the editor continues to work, while brute force does not. so i do not think it is something interfering with the keys (my first thought was sticky keys or IME problems with foreign keyboard, but that wasn't the case even when i changed all regions to English). after swapping the keyboard shortcuts in enblocal.ini, shift + B does work to bring up the ENB config menu, but Shift + Enter doesn't work to enable brute force. this is the exact same enb with the same enblocal.ini i was using in win7. so after switching to win10, the brute force command no longer works for some reason. i am currently running v0.305, but i have tried v0.404 and still have the same problem with brute force not working. not that it's a big deal, but i feel like whatever is causing this to not work may be related to why my reverse modifier key doesn't work in game.

 

regarding the c++ libraries, i am in fact getting CTD right now on save loads. this has not happened before. what i used to get randomly when i load my game is a popup screen telling me "AFT has been updated" (amazing follower tweaks). it's just a popup with OK as the only option, and since it never interfered with my playing, i never paid attention to it. it happens randomly when i load a save, even in win7. now on win10 my save loads will CTD unless the AFT popup shows up. when it does, the game will load normally. this is now happening with brand new saves from a brand new game. i do not believe there is an issue with active scripts on a brand new save, but the CTD problem remains when i load the newgame save, as well as the reverse modifier key not working in SL. i believe it's crashing the exact moment when enbhost.exe begins offloading textures from tesv.exe (ie enbhost.exe begins growing in memory used size). when i don't get the AFT popup window, enbhost.exe never grows in size. it will just CTD 1 second after i click Continue. when the AFT window pops up, it's like whatever's happening in the background is paused until i click OK (ie: tesv.exe and enbhost.exe memory usage does not change). after i click OK to that popup, enbhost.exe will begin to inflate in memory usage and my save will load normally. again this leads me to believe something with the enb or some constant outside of the skyrim core files or my mods is causing these issues, since i have tried replacing all of those files and the issue remains (ie enb brute force still doesn't work on a brand new ENB install v 0.404 in a brand new skyrim install fresh from steam). i feel like if i can fix the brute force issue, it may also fix the issue with the modifier key not working in-game. 

 

i will try your suggestion of saving during an animation to check papyrus log as soon as i can actually get the game to load. from the few times i was able to load it last week though, i glance at the file size and it didn't seem like there's any excessive stack thrashing. filesize for papyrus logs were around 300kb, which is about normal for me considering the amount of mods i installed and removed from this save (save #4949). back on win7 when i do observe input lag due to active scripts, my papyrus logs usually go over 3mb in size from the stack dumps. 

 

thanks btw for taking the time to help with this

[GenioMaestro]

15 hours ago, gtcard said:

this is the exact same enb with the same enblocal.ini i was using in win7. so after switching to win10, the brute force command no longer works for some reason.

My only explanation is that the Bute Force of ENB not works in Win10 but i not see any reference to that exact problem in the forums of ENB, Redit, Nexus, Steam...

I can not verify it because i only have Win7. Another user with ENB in Win10 must make the verification.

Remember that ENB is not officially suported in Win10.

 

15 hours ago, gtcard said:

i am in fact getting CTD right now on save loads.

The game have a very well know problem that cause CTD when load the savegame but was solved a lot of years ago with Load Game CTD Fix.

But CTD when save the game only can be caused when you load a CORUPTED savegame.

 

Some specific CTD when load or save the game are caused by the main core libraries of the game like PapyrusUtil and JContaines. That libraries are used by the mods to store data inside the SKSE co-save.

Verify that you have the last versions and none other mod overwrite it.

Specifically, Campfire and Sexlab have OLD version of PapyrusUtil. Be sure are overwrited with the new version.

[gtcard]

On 1/24/2020 at 9:19 AM, GenioMaestro said:

The game have a very well know problem that cause CTD when load the savegame but was solved a lot of years ago with Load Game CTD Fix.

But CTD when save the game only can be caused when you load a CORUPTED savegame.

 

Some specific CTD when load or save the game are caused by the main core libraries of the game like PapyrusUtil and JContaines. That libraries are used by the mods to store data inside the SKSE co-save.

Verify that you have the last versions and none other mod overwrite it.

Specifically, Campfire and Sexlab have OLD version of PapyrusUtil. Be sure are overwrited with the new version.

i have tried those, but problem persists, and it's random. i can still load the save, it's just about half the time i can't. problem also occurs when i use 'coc whiterun' from the main menu. it'd randomly ctd with the "skyrim has stopped working" prompt

 

i'm going to try installing win7 back to another partition and run the game from a win7 environment to see if i still have these issues. i'd feel better to continue troubleshooting this once i can confirm that there isn't anything wrong with the game files i'm working with. on my win7 install i did not have any trouble loading this save, and the only thing that has changed was the upgrade to win10. it's the same save i'm loading from with the same mods and same skse co-save, same enb. everything is the same except the windows version. in fact, i didn't have any of these issues, with modifier keys not working, enb brute force not working, and the ctd, until after the win10 upgrade. which is why i keep suspecting it's maybe something happening at the OS level, maybe win10 handles memory or processes differently. if i can launch the game again from a win7 install, then i can assume it's some incompatibility win10 has with something in my load order.

[Grey Cloud]

36 minutes ago, gtcard said:

i'm going to try installing win7 back to another partition and run the game from a win7 environment to see if i still have these issues. i'd feel better to continue troubleshooting this once i can confirm that there isn't anything wrong with the game files i'm working with.

If you are going to go to all that trouble then you may as well rebuild from scratch with Win10. Or, as a compromise, uninstall all the mods to verify that things work with just the vanilla game.

Last summer I built a Win10 machine and for a laugh tried my last save from the old Win7 machine and it loaded without any problems even though there were mods in the save that weren't on the new machine. Since then I have had 3 or 4 big Windows updates (I put them off for as long as pos) and never had a problem with Skyrim or anything else.

 

[gtcard]

On 1/26/2020 at 12:35 PM, Grey Cloud said:

If you are going to go to all that trouble then you may as well rebuild from scratch with Win10. Or, as a compromise, uninstall all the mods to verify that things work with just the vanilla game.

 

i have tried vanilla mods with an empty load order via MO profile switch. the issue with enb brute force not working remains. i cannot test the modifier key however, since SL will not be in the load order. however i suspect it will also not work, since enb is half broken. that's the best way to describe the current situation, my game is half broken.

 

i do intend to reinstall win10 fresh at some point, but it's not an undertaking i want to do if i cannot be sure there's something wrong with my particular install of win10. more importantly, i need to be sure there isn't something wrong with my skyrim files. i did install win7 on another partition today and ran my game with the exact same files, with symbolic links to the save game directory. i do not have any of the issues i'm reporting here, so there's definitely something broken with my particular install of win7 upgraded to win10. 

 

so to recap, my mod organizer folder and steam games folders are on separate drives from the OS. 

 

booting into win10 on this system and running the game via MO leads to the issues i described in this post--high rate of CTD on save load, ENB brute force not working, modifier keys not working with any mods. 

 

running the game via the exact same MO executable from a win7 install in the same system, but on a different drive, does not have any of these issues. 

 

since i am sure my skyrim related files are fine and they aren't the ones at fault here, i will wipe the win7 install and put win10 on there to give it a go. if that works out then i'll do a fresh install of win10 on my main nvme drive.

[LittleVampire]

I had the same problem with modifier keys not working in SL after updating Faster-HDT-SMP to the current version 1.37. It seems fine again after reverting to 1.36 (tested in a fresh game only). Last known good in my game before that was 1.24.

 

Edit: And right now it has been edited on the nexus page to include a bug warning.