Topic: Console command not working [wine] [semisolved] Read 3378 times

663409c0b1cfb

I tried the "shift+;" and then "shift+anythingelse". I changed keyboard layout to different ones, I just seem to not have any success whatsoever of getting the console (in shoot mode, of course). I tried left shift, right shift. I still have no idea. Has anyone of you experienced something like this before? This is my first time trying the console, so I've never seen it working before, but disabling mods doesn't seem to change a thing.

TL;DR: The file user.bnd in your shock directory has the line "bind : edit_command" (or very similar). Change it to something that doesn't need shift. For me "bind . edit_command" worked. Save user.bnd with the changed line. Console will now start, when you press ".", but the keyboard layout is still strange. Changing the layout to brazilian does work. _ is now at shift+ß (I have a german keyboard)

Code: [Select]

$ setxkbmap br

663409c0b211c

Quote by Colonel SFF:

I tried the "shift+;" and then "shift+anythingelse". I changed keyboard layout to different ones, I just seem to not have any success whatsoever of getting the console (in shoot mode, of course). I tried left shift, right shift. I still have no idea. Has anyone of you experienced something like this before? This is my first time trying the console, so I've never seen it working before, but disabling mods doesn't seem to change a thing.

Using the number pad?

663409c0b22ae

What sort of weirdo foreign keyboard are you using?

Whatever, if you look at an American or British keyboard layout, you'll see that the shifted semicolon character is a colon. So type a colon.

663409c0b2755

Quote by ZylonBane:

What sort of weirdo foreign keyboard are you using?

Whatever, if you look at an American or British keyboard layout, you'll see that the shifted semicolon character is a colon. So type a colon.

It's the one built in to my Laptop.
The layout is called German (Austria). English (UK), and English (US) don't change the fact that it's not working.

Quote by OmegaDeath:

Using the number pad?

I have neither a shift, nor a colon key on the number pad. But I still tried combinations with the Numpad. On and Off, yes.

663409c0b2871

Did. You. Type. A. Colon?

663409c0b295d

Try use the windows on screen keyboard.

663409c0b2c08

On a german keyboard you have to press shift+:

663409c0b309d

Quote by Olfred:

On a german keyboard you have to press shift+:

Quote by ZylonBane:

Did. You. Type. A. Colon?

Thanks, yes I did. I wish I was too stupid to try out , and . at first, because then the problem would now be fixed.

Quote by OmegaDeath:

Try use the windows on screen keyboard.

I don't see how I could do that.

663409c0b31c9

Sorry for late reply.
it should be under the windows 'accessibility' options.

But could be somewhere else what OS are you using sorry.

663409c0b332a

I guess it's more of a problem how you can input anything into it with a full screen game active.

I made a simple autohotkey script.

Code: [Select]

End::
Send {Shift Down}{SC034}{Shift Up}
Return

Whenever you press the End key it should open up the console.
Maybe you have some weird thing going on and you get an improper scancode, with this it should do the trick.

663409c0b379e

Quote by Olfred:

I guess it's more of a problem how you can input anything into it with a full screen game active.

That's what I meant, yes.

Quote by Olfred:

I made a simple autohotkey script.
Code: [Select]
End:: Send {Shift Down}{SC034}{Shift Up} ReturnWhenever you press the End key it should open up the console.
Maybe you have some weird thing going on and you get an improper scancode, with this it should do the trick.

Thank you for the effort. Unfortunately AutoHotkey isn't WINE supported.
This is a mystery to me. I also tried rebinding "bind : edit_command" in user.bnd to something else. (I don't know if that's even the right thing, but it looked promising.)

Edit few mins later: I tried rebinding "bind : edit_command" to something that doesn't need shift. It is now "bind . edit_command" and works like a charm. Problem solved.

663409c0b38af

Oh, yeah, forgot that you are on WINE. Autohotkey probably doesn't work on WINE because it intercepts the OS on a low level. The structure probably is different as it is some kind of API translator.

663409c0b3a37

Just as I thought. After being able to open the console I found out that my keyboard layout outside of SS2 doesn't change the one inside. Now I can't seem to find the "_" button.
"," and "." are the same, but adding shift will make then "<" and ">".
My "_" is a "/" when pressed in the console, and a "?" when I add shift.
Does anyone know that keyboard layout, and if it's possible to change it?

I'll make a screenshot of 1234567890 with shift pressed.
[Screenshot from 2015-12-31 02:27:59.png expired]

663409c0b3b1f

this community rocks i love you guys.

663409c0b3c08

Except the ^ being a lightning symbol and the parenthesis looking like brackets it seems to be the standard (US) layout.
Try pressing shift + ß for "_"

663409c0b3e76

Quote by Olfred:

Except the ^ being a lightning symbol and the parenthesis looking like brackets it seems to be the standard (US) layout.
Try pressing shift + ß for "_"

Nothing comes when pressing ß or ß+shift. Neither does it for "´" right next to "ß"

663409c0b3f7b

Then I have no idea what else to try. I have no idea about the usage of Linux or WINE.

Maybe as a makeshift until it's solved you can try to copy and paste the underscore.

663409c0b415c

Quote by Olfred:

Maybe as a makeshift until it's solved you can try to copy and paste the underscore.

Good idea, thanks, but ctrl+c/v doesn't seem to work either.

663409c0b42b1

Found something promising on the WineHQ Bugzilla and tried

Code: [Select]

$ setxkbmap deDoes not solve the problem however.

BUT(!): changing the layout to brazilian does work. _ is now at shift+ß (I have a german keyboard)

Code: [Select]

$ setxkbmap brWorks, but this is really just a temporary solution for people not on a brazilian keyboard.

Topic: Console command not working [wine] [semisolved] Read 3378 times

663409c0b1cfbJML

663409c0b211cOmegaDEATH

663409c0b22aeZylonBane

663409c0b2755JML

663409c0b2871ZylonBane

663409c0b295dOmegaDEATH

663409c0b2c08Olfred

663409c0b309dJML

663409c0b31c9OmegaDEATH

663409c0b332aOlfred

663409c0b379eJML

663409c0b38afOlfred

663409c0b3a37JML

663409c0b3b1fOmegaDEATH

663409c0b3c08Olfred

663409c0b3e76JML

663409c0b3f7bOlfred

663409c0b415cJML

663409c0b42b1JML

1 Guest is here.		New topic