[Solved: Not a bug] I have Shift NUM PAD ISSUE
-
Whilst attempting again to make a flyable profile that doesnt foul up, I switched to a fresh copied version of the BMS keypress file in the hope that the callbacks will be more up to date than the old Keypress file. Found that they were and got to work.
First job setup the TMS switch, entered sims setup, used that, clicked on No assigned key next to HOTAS TMS up assigned Shift + Num Pad 8 to it, checked it by pressing it, jumped to ICP 8, pressed it again jumped back to HOTAS TMS up and so on and so on.
Also doing it this way it doesnt appear to pick up on the fact the SHIFT key has been pressed in a combination as at the side of HOTAS TMS up, is now shown Num 8, not Shift + Num Pad 8 as was programmed in.
So i got a fresh copy of the BMS key file, renamed it and put it back in the config folder and tried again, saving it as soon as the modification went in. However on doing that it jumped straight to ICP Num 8 in the list and continued to bounce between the two on each press of shift 8.
Or is this profile purely for people who can have the shifted layer state on their HOTAS, say like Cougar owners and such.
-
Edit : because i am a dumb dev
-
Im not entirely certain of why you want TMS up on the numpad and not your stick?
In any event, you’ll find that with trying to set shift keys for the numpad, it can be done but takes a few tries through the UI. Either persist or just edit the keyfile. Not exactly a difficult task to set specific keyboard presses like Shift + Num 8 through the keyfile.
the shifted state layers have nothing to do with keyboard presses, so Im not sure why you bring it up. If you insist on using keypresses then I cannot help with shifted layers. If you use DirectX to map your stick, then you can set a shifted layer (but really shouldnt anyway).
-
First job setup the TMS switch, entered sims setup, used that, clicked on No assigned key next to HOTAS TMS up assigned Shift + Num Pad 8 to it, checked it by pressing it, jumped to ICP 8, pressed it again jumped back to HOTAS TMS up and so on and so on.
Also doing it this way it doesnt appear to pick up on the fact the SHIFT key has been pressed in a combination as at the side of HOTAS TMS up, is now shown Num 8, not Shift + Num Pad 8 as was programmed in.
Have you ever used Falcon4 before BMS? Except in F4AF, it has always been the same.
Am I wong?
-
Edit : dev can not give advices
-
you want to modify the keystroke in order to make it work from your KEYBOARD ? following your preferences on your keyboard setup ?
Well JP, I must confess that it is what I’ve been doing forever, and I ever never had any troubles or problems (excpect in the past with the 1st and 2nd trigger detent which is now solved in BMS)
Always doing it via F4 setup and not messing the .key which notepad.
Works fine for me!Maybe because I always keep things as simple as possible, using DX button as much as I can and rarely use key combination.
-
Well JP, I must confess that it is what I’ve been doing forever, and I ever never had any troubles or problems (excpect in the past with the 1st and 2nd trigger detent which is now solved in BMS)
Maybe because I always keep thing ver simple and rarely use key combination.
there are only a few Keys i use on keyboard : “G”, CTR K, SHF space (cat), and very rarely nozzle angle
i dont use any other…why do you?
-
Ah that explains it then, my apologies for trying to do what we have been doing in falcon for years. I missed the annotated heading in BMS.key that says // DO NOT MODIFY THIS FILE AT ALL. I shall of course refrain from using an inferior HOTAS on this sim immediately.
I shall go and buy a Cougar instantly,
My Saitek 52 cannot get at the shifted layers because it is set at device 8 in the USB devices list and only devices 1 to 4 can access the shifted layer state according to various manuals and postings regarding this.
So with this in mind I tried using Hard Decks profile, it didn’t work on my stick due to it being device 8. Tried Kolbe’s Profile, didnt work, device 8 problem again. Pinky switch on my HOTAS isnt picked up in setup at all and doesnt illuminate button 6 press in setup due to it being on device 8 in the USB list, that I cant find and cant seem to modify due to that fact.
Mav just exactly where is this Foxy profile for the x52 I would like to giove it a try?
As for
Foxy profile for instance :
BTN H2U /P KD(DX7) /R KU(DX7)
BTN H2D /P KD(DX9) /R KU(DX9)
BTN H2L /P KD(DX10) /R KU(DX10)
BTN H2R /P KD(DX /R KU(DXWhat runs perfectly, that isn’t even proper Falcon Direct x listing the ones below are out of the BMS.key file.
SimTriggerFirstDetent 0 -1 -2 0 0x0 0
SimPickle 1 -1 -2 0 0x0 0
SimPinkySwitch 2 -1 -2 0 0x0 0
SimAPOverride 3 -1 -2 0 0x0 0
SimMissileStep 4 -1 -2 0 0x0 0
SimTriggerSecondDetent 5 -1 -2 0 0x0 0
SimTMSUp 6 -1 -2 0 0x0 0
SimTMSRight 7 -1 -2 0 0x0 0
SimTMSDown 8 -1 -2 0 0x0 0
SimTMSLeft 9 -1 -2 0 0x0 0
SimDMSUp 10 -1 -2 0 0x0 0
SimDMSRight 11 -1 -2 0 0x0 0
SimDMSDown 12 -1 -2 0 0x0 0
SimDMSLeft 13 -1 -2 0 0x0 0
SimCMSUp 14 -1 -2 0 0x0 0
SimCMSRight 15 -1 -2 0 0x0 0
SimCMSDown 16 -1 -2 0 0x0 0
SimCMSLeft 17 -1 -2 0 0x0 0
SimCursorEnable 18 -1 -2 0 0x0 0
SimTransmitCom2 19 -1 -2 0 0x0 0
SimTransmitCom1 20 -1 -2 0 0x0 0
SimCommsSwitchRight 21 -1 -2 0 0x0 0
SimCommsSwitchLeft 22 -1 -2 0 0x0 0
SimToggleMissileCage 23 -1 -2 0 0x0 0
SimSelectSRMOverride 24 -1 -2 0 0x0 0
SimSelectMRMOverride 25 -1 -2 0 0x0 0
AFBrakesOut 26 -1 -2 0 0x0 0
AFBrakesIn 27 -1 -2 0 0x0 0Just in case you missed it I have a SAITEK X-52 HOTAS. I dont want a cougar, I want to be able to program in my own keypresses so they can be used in my own X-52 profiles. If this sim can only be flown by people that posses Thrustmaster Cougar Hotas only then that should be made clear in the Installation. As it isnt I would like some information on the first item in this thread. Ive absolutely no idea what that gibberish is youve posted, but Ive tried mixing Direct X with keypresses and on my particular setup it seems there is an issue that I would like some help from someone to resolve.
As for just making it DX, already tried to do it thats why I switched over to the BMS key file. I shall persevere with this problem and see if I can resolve it. I can see it is pointless asking questions now.
-
Edit : because i am a dumb dev
-
i dont use any other…why do you?
I am using very few keys actually, just like you.
But using an USB numpad as ICP and a real gear handle (Aker Barnes ckockpit) I have to remap the numpad for ICP functions, and also my gear leveller (CTL+PG UP/DW) using the CTL as a safety lock for the gear which is mapped on my Cougar AP Override (which has the both functions: gear lock, and AP Override …. I never had any conflicts since I have unmapped all unused key in my .key execpt the views and few others.)Works perfect!
-
Gentle warning once again Gyro, you are on a slipy way …
Ah that explains it then, my apologies for trying to do what we have been doing in falcon for years. I missed the annotated heading in BMS.key that says // DO NOT MODIFY THIS FILE AT ALL. I shall of course refrain from using an inferior HOTAS on this sim immediately.
…
If this sim can only be flown by people that posses Thrustmaster Cougar Hotas only then that should be made clear in the Installation.
… stay away from BS and sarcasm please … There are hunderds of ppl here using X-52 wihout problems.
Edit:
If you can’t be more kind with ppl trying to understand your problems and help you, I will prevent them to do it by supressing their answer, and will let you alone dealing with your shit.
Good deal?
-
Agreed i edit my answers
-
Please do not feed troll, he pissed off everyone every day, along with Tagman smashed this forum.
-
Please do not feed troll, he pissed off everyone every day, along with Tagman smashed this forum.
Correct. Ignore and eventually he will desist/go away. Well said Banita.
Alternatively, ban the prick and be done with it.
-
Aha Dee Jay you may have just the thing then. Would you do me a huge favour. Check your DX callbacks in the key file and see what device number is assigned to your USB num pad please.
-
No disrespect Mav but I too was once a developer, many many moons back. My efforts towards this program took up a lot of my time and I just didn’t have it to spare with bringing up two kids alone out in the middle of nomans land. So this profile then that foxy has where can I get it to try it out?
Oh and as a “Dumb developer” there is no such thing, I got accused of that in the past, however I made a career out of it. I could be a developer if someone would send me the code files, all Ive got for reference is Falcon 4 original, SP4 think its about version 1.2, its an early copy anyhow, and the source for freefalcon 6. Id like to get involved again but it would have to be in my spare time. Save me keep posting things on here and getting flamed for it and no answers. This USB shifted layer I think I have an answer to it, but ive got no frame of code reference to look at.
Im kind of old school DJ and its tough to kick the habit when i used to fly with a Microsoft Sidewinder 2 and the keyboard up till SP4 got going then I bought my Saitek x-52, which may or may not have had hardware changes since that time, so my version may in fact be old and outdated. Dont mind buying a new one but theres no way im paying a fortune for a Cougar or a Warthog or any higher make of Saitek stick.
I would delete the x52 profile you have in the joysticks folder, it doesnt work on my stick at all or load into the new SST software.
Anyhow offers there if you want it. Already ripped the callback set out of the EXE thanks so i can make my own profile. And Mav dont do yourself down. I went by a different callsign way back then but i doubt people would dig it now its just way to old fashioned.
-
Ah the page has just refreshed, by all means leave me to deal with my own problems, that way I dont have to bother worrying about how others get on with this. Have you fitted a close account button to this forum?
-
Dont bother with answers, Dee Jay could you please close my account and delete all my posts. I cant seem to find how to do it on this forum, I shall seek my own answers.
Regards Gyro
-
Now I have had a good look at where I went wrong. Once more Red Dog’s callback manual plus the Kolbe’s manual on keyfiles has provided and answer to all my issues.
I now have a fully functional profile for my Saitek HOTAS created NOT with the Controllers Setup, but with the a text editor, in this case Notepad. My profile consists of 3 parts. Key presses and Direct X inputs (for the first 32 Direct X commands, this includes the three MFD buttons used as function buttons and the clutch switch) and also a profile created just for the Pinkie + states in the latest SST software.
To find the keyfile you wish to modifiy, the original ones are in the Falcon…//User/Config folder, make a copy of them, rename it and put it back in the same folder. Start the game and click, click on controllers, then load, then on your renamed profile. This will set it to default each time the game starts. You can edit it in Setup, but it is not the safest way. Some of the callbacks are different names now so always check in BMS.key for the latest callback name, if it differs from yours then copy the one out of BMS and replace the one in yours. Always leave the original files as you found them then you have originals available to work from if you change your mind.
Direct x callbacks have 7 sections and are always listed at the bottom of the keypress file you chose, add yours in there only, not in the middle or the top.
It did involve the removal of the OSB button commands on the main keyboard to be replaced with DMS switch and CMS switch commands, TMS works just fine as it is. But I now have a working BMS profile. I didn’t realise at the start that the whole thing is now based around Laptop keyboards and not the standard Keyboard Layout. Doing the modifications to the keypress.key file ( always use a copy of the original file you work on so you have the original kept safe). Nor did I realise that the USB device number becomes irrelevant as BMS when saving a file converts all USB devices to device number 8 regardless of what device they actually are. It also alters the callback SimDoNothing to SimNextRadarTarget so if you add labelling to your keypfess file either by the SimDoNothing Method or by #–---- method, both either get overwritten or removed in the save process.
Any how, my thanks to Red Dog again, Kolbe, Dee Jay for making me seek my own answers, Mav for reminding me programmers are not dumb, and to everyone else for the inverted encouragement you have given. If anyone would like further informartion then get trolling the web the information, although dated in some cases is out there.
-
Good.
Now check this one and please confirm that there is not bug.