DeepDrummer

This as you suggested returned this in pics attached.: It worked perfectly with those additional instructions. Input from all is well appreciated and forced me to thrash out my understanding. Not an easy task. Well done! As I said before, It had to be me. I put it on the wrong line and then on another wrong line. Sometimes with an extra curly bracket or lacking one. We don't want to talk about me having to overwrite my users saved keyboard.diff. I must have saved the ED mods version to it or something. Minor detail. Both of you have rocketed me into customizing a few more toggles shortly. I can't thank you enough for the help and putting up with my coding incompetency's. I just lose it when that is toggled wrong and an opponent gets away. Right on! Thanks so much. :) I'll post the pics so I can remember if I have to redo it. I am the worlds worst coder. I am a Bramma Bull in Geeks clothing. I am heading into the wild blue with one huge smile. Awesome people here. Just awesome!

I will try to explain my point of view on all this. I do not play M/P for those who would consider chiming in saying I am a cheater. This is quite a place. Quite unique. No doubt I've messed something up. I haven't even gotten back to taking it out of the joystick file yet. I am so bad at looking at code these days. I was a whiz when I was a youngster but that is eons ago. I find it extremely stressful and bad for my health. lol. This is 5 am for me. at 5 am I just want to fly. I set the guns safe to a hat to the right this morning. I accidently hit it twice and toggled my guns to safe off. It ruins a half hour run when you have to go back around in a bit of a mission I made. I just modified my Target script again and set it back to a 2 position switch which is, unfortunately, both sides set to a toggle. That works perfectly with my checklist and preflight flow and as long as I only use ramp start, it'll do. I never get it mixed up. Gunsight turns on WITH the Gun to fire function. If my gunsight is on, my guns are set to fire. It never fails. Runway starts and air start of course have that reversed and so I need to toggle it back in those cases. If I toggle it in the normal layer with a momentary push button, I inevitably get it reversed without knowing. Runway start has the switch opposite (fire) for some super strange reason. If I flip my 2 position (both set to toggle) at that time, it toggles it off. That switch is programmed via MY script to do 6 functions. It works very well. When one is programming a joystick/device directly via the control settings page, one needs to have the devices combined for the Target script. That means when you try to set up that device in game and you move that control, you are actually asking DCS to perform 10-20 keystrokes most of which are with a modifier or 2. It was really simply a request to the developer to make the change so it would not revert biweekly. Hopefully they can use your examples and I thank you for taking the time. I'll try it again when I am in the proper mood for problem solving since I could type 2 brackets in a row without getting messed up most days. I never had any doubt that it was possible. I never had any desire to edit their .lua files nor any need and I am simply very bad at it. Especially when they name more than one file default.lua. sheesh. No damage done. I just want to turn it on and fly. It's not fun when one turns it on and an update has wiped all that kind of thing out. I have gone back to factory stock pristine install a few months ago and swore I wouldn't change anything ever again. Even if this discussion gets the next warbird released to be released with the proper availability of switch states, I would be happy. I mean, what you guys seem to be saying is that the developer won't change a couple lines in the stock default.lua to better reflect the proper switch operation in the airplane they sold me? I can't believe that. No doubt if your way works the developer can insert that into the default.lua which in itself can become confusing since there are a number of those files of the same name. I realize where they are and where they go and don't need a lesson on that as well. If you are not running a target script, we very well may be running down different roads. My 10,000 lines in some cases don't meld well with yours. Only axis are assigned to my devices in game. All fields for the thrustmaster combined are blank. It's a target thing. Target supplies the keystrokes and so keybinds are really the best way I have found in order to assign over 300 different possible commands with one throttle and one joystick. I am not going to stop running such a work of art for one errant switch state and I simply requested it be updated by the Developer as the title would suggest. I will revisit this thread and give some of your suggestions another go maybe someday but knowing it is possible and knowing it is easy only furthers my case to the Developers and it should not be necessary to edit the luas in the end and everyone can enjoy proper switch state options on this or if not this all new aircraft released. I do not ever need pre-made controller profiles and so I certainly am not asking the developer or anyone else to build a custom one for myself. I like my controller/device profiles blank. If it turns out that they have abandoned this aircraft and I don't believe they have but a suggestion in the future that no aircraft be considered out of Beta until such time as all switch states reflect the real life aircraft should be the rule. "Toggle" actions are for momentary push button style switches. I have been saying this for somewhere around 2 years. Thanks again for your time and for your suggestions. I will play with them someday again. OK Let's "Ramp Start" this thing for the thousandth time.

"keybind" not device Captain. Like the pic attached: I send the keystroke from my device via the switch and Target software. I need a place to put the keystroke for on and the keystroke for off. Don't give it another thought. I'll come back when I learn this stuff better.

Entering the exact line in both the default.lua still returns a greyed out keyboard section. I DID figure that out and tried it. It needs an icommand in the keyboard section does it not? You know what? Let's just close this thread. The stress of figuring this out is bad enough without the B.S. demeaning remarks received from some. I'm out. Enjoy your day.

If there is no existing icommand, I cannot add one., Is that correct?

Yes. The keyboard field is greyed out. I want to insert a keyboard bind for on and one for off on two separate lines one of which turns the gun safety on (like the real plane. off and on and not specifically as a custom request from me). I need to be doing my editing in the keyboard default lua I think maybe. Probably messing with the icommand instead of the device command in the keyboard lua instead of the device.lua and assigning one line to 0 and one line to one which may allow me to insert a key bind for off and on and then assign those to the off and on of my switch. If having an off and an on option for a switch that should have an off and an on is a request for a change just for me then that is pretty sad indeed. Might as well put everything on a toggle. I am going to use what LeCuvier has suggested but I will apply that logic somehow to the keyboard.lua to an off and an on 0 1 lines. I should be able to add a keybind (which I will use to program my controller via Target)and that is what I needed to know. Thank you for taking the time. It is all helping. The bottom line is I could not have done this without you. It is not there yet but I see the light I think. I'll let you know but I have to take a break every now and then to let the hair I pull out grow back. Pullng your hair out = frustration in my part of the world.

I looked through the default keyboard lua file and I can see the difficulties to getting that done. I have edited my sheets and controls to use a momentary push button for the safety only. It's going to bug me every time. A momentary push button is a "toggle" A switch, lever, tang, really should have an off and on. The Pilot could feel the gun safety indicator and the tang that put it in and out of safe mode. We cannot. I bought and then stopped flying the p-51 because it had a "toggle" on the gear. I am pretty sure the mustang didn't have it's gear on a momentary push button or a mouse in the cockpit other than the ones that eat cheese. Maybe they will get the P-47 correct.

No luck with this. Same toggle behavior. { down = device_commands.Button_1, up = device_commands.Button_1, cockpit_device_id = devices.WEAPONS, value_down = 0.0, value_up = 1.0, name = _('Gun Safety Switch On/Off'), category = _('Stick')}, I took my own target controls back out to ensure and had no action then. *restoring things and never looking back* I'd fly the mustang but then there's this "toggle" on the gear. *sigh* That's enough for today. Thanks for trying. I really am the worlds worst at this sort of thing.

Thanks guys. I am trying. It is quite frustrating. The sim won't let me assign anything to the thrustmaster combined for gun safety so there we sit. I'll give it another 10 min before I get the sledge hammer out.

-- Safety Lever { down = device_commands.Button_18, up = device_commands.Button_18, cockpit_device_id = devices.WEAPONS, value_down = 0.0, value_up = 1.0, name = _('Input.SpitfireLFMkIX.safety'), category = _('Stick')}, Trying that.

ok wrong section. I'll probably end up with the prop on the tail. Working....

Here is what it is stock: -- Gun Sight Master Switch { down = device_commands.Button_18, cockpit_device_id = devices.WEAPONS, value_down = 1.0, name = _('Input.SpitfireLFMkIX.gun_sight_master_1'), category = _('Gunsight')}, { down = device_commands.Button_18, cockpit_device_id = devices.WEAPONS, value_down = 0.0, name = _('Input.SpitfireLFMkIX.gun_sight_master_0'), category = _('Gunsight')}, { down = device_commands.Button_19, cockpit_device_id = devices.WEAPONS, value_down = 1.0, name = _('Input.SpitfireLFMkIX.gun_sight_master'), category = _('Gunsight')}, I'll mess with button 19 I guess.

We won't talk about the fuel tank pressure on and off. *sigh*

Thanks Captain for your consideration. I am using Thrustmaster Target. Assigning on and off are as simple as a drag and drop. I could probably do that in parallel and allow DCS to control the actions of one switch but it would be with reluctance for sure. Things can get out of hand for me that way. Would that be yet another thing I would have to redo every time there is an update? All I am asking is for a factory stock keybind to turn the gunsight on and off. Maybe ED can paste your code into theirs and assign a key to it.. It could even be a hidden keybind (there are enough of those anyway). I completely refuse to edit the code of the company who received my money in order to make a non functioning simulated switch operate properly. ED edits the code to accommodate a key press which turns this item on and a different key press (not a toggle) to turn it off and then advise what that key press is. I then dial that keypress into my target script as in the pic attached. If they could find it in their heart to supply a key press for the switch on their throttle to turn it off, that would be the icing on the cake. I keep reading that if they have definitive proof of something, they will act on it. The proof is there. Act on it. I will give your idea a go. This is quite stressful. Can you imagine? I have to change lines in their code. Unbelievable. Thanks Captain. When my heart rate comes back down, I'll take another look.

Of course we already should know this from the manual. Pic attached. Note where the arrow for # 5 is pointing. Now that we have decided that people can update their DCS profiles manually instead of being forced to do so, can we ensure we are advised which modules have changed and when as they are posted? If I took the profile now, it would wipe my own with no changes to the available key bindings. No? That should be enough official confirmation that it is modelled wrong. I patiently await notice of the new Spitfire Key Binding availability to repair that one contentious switch. (and the one that comes on with the throttle needs a method other than mouse to shut it off). I will shut up now. I have done my part.

Personal story about why cannot always blame the DEVs. Back in the late 90s I decided to learn java programming. I was going to self teach myself with a package valued at 3000 By just following the training manual which was quite thick. I was doing great and then suddenly I hit a snag. Some text windows didn't work properly or something. I poured and poured over the code until curly brackets and colons looked little birds on the screen. I followed the manual over and over and just could not get it to function by doing step by step what they said. Note this was GUI based for the most part but one had to edit as well there. I even went back to the manual and started from page 1 and did it all the way back up to page 300 where I screeched to a halt. I gave up and tossed everything into the trash swearing never to code again. I found out a year or 2 later from one of the top guys in that company that there were a lot of errors in the training manual. There can be errors in the code for various GUIs in use to put the code together as well. Problem solving is one of the highest forms of stress there is and is seriously hard on your health. Never diss a DEV who is crazy enough to do that for a living. Respect for anyone who can look at script and code for any length of time and stay sane.

I was wondering if I should call this a bug and report it or something. For the first time in a while I forgot to turn on the fuel valve before priming the engine. I primed it and then started using the wobble pump. The light wouldn't stay out. Then I noticed my error and turned the valve on. I primed it again and then went to the wobble pump and wobbled. the light went off. Less than 2 seconds later the light came on. I could not get the light to stay off no matter how many times I wobbled it. I tried multiple times. I agree I should be punished a bit for priming with fuel valve off but I should be able to get pressure up once the valve is back on. So here I sit on the ramp hmmmm. I am going to turn on the electric pump and see what happens. Ok. Turning the pump on kept the light off but no start and the light came back on. I turned the pump back off and then wobbled with success and the light stayed off. I am going to file that under "I was being punished for being stupid and forgetting the fuel valve and wobbling all the fuel out of the line leaving a giant air pocket in the system." Well, that's what I am going to tell the Pilot anyway. ;) Should we call it a bug? On and off with the electric pump clears the issue anyway and you can prime and pump normally. Good to know. It kind of seems like it could be realistic too. A mistake like I made deserves a short sharp shock.

+1 Guilty as charged on the morbid tendency thing in a wide variety of ways. My Spitfire just oozes stress relief generally.

The stable is stable. It really feels like I am the only one running the stable version at times. Craziest thing I ever saw. Yes of course defects exist in multiple millions of lines of code. I believe they will get to it over time and if not, I have no problem reminding them every month or so what they forgot to do on it. If something takes me out of a flight I mention it. Over and over because I have no memory. Sometimes it is me and sometimes it is the code. I am not perfect and I don't expect anyone else to be. I will continue to remind them until it is fixed or they ban me.

As I sit here on the runway with the engine at idle and the canopy open Looking out over a beautiful day with the surround around my head cranked and all I can think of is that line from the Dunkirk movie: "That's the sweetest sound you'll ever hear out here George" Adding throttle Thanks for making my dream come true!

Use the Target GUI to make your first scripts. I have found there is nothing I can't do that I need in DCS that way. It saves searching through 10,000 lines of code searching for an errant curly bracket. I would highly recommend making a quick script to combine your TM devices before you set up your controls to save backtracking. Always pick advanced when you originally start the file. For the CF-18 I set up the backlight on the throttle to turn on precisely when the exhaust housing starts to flare a hair before the afterburners really kick in. Adding a ramp over physical device for that would ruin some of my aircraft. Kicking back and watching my very educational video regarding the Target GUI I made a while ago. I invented some other cool stuff later on. The GUI is definitely easier by light years than the script editor. I found only one instance where I had to go to the script editor and that was to take layers back out of the script. I uploaded a pic attached of that. My video is 1.5 hours and covers most of what is possible and how using the GUI. If you write code already especially C++ of course the script editor has merit. Watch the video. Take control of your own settings. Sorry for my "supposed" accent and bad impromptu video technique. Not monetized or anything. Just to help folks out. https://www.youtube.com/watch?v=WJv1pLWyxuE

Cams appear to be turned by the tang in the bottom cam protruding. This turns the cams which lines up the pins on them to enter into the buttons allowing them to travel inward and activate the trigger. When the cams are in the right position the buttons will not go in and the button can be pushed into place. The button simply holds the cams from lining up. It is not spring loaded or momentary. The bottom cam can be turned in both directions to allow locking and unlocking of the safe button. I am thinking the cam pops the button back up in one direction by a cam type action and opens the slot for the button to be pushed in effectively misaligning the pins and button holes and keeping the guns "safe". The cams are spring loaded back to center and the bottom one controls the top one for the button purposes and to line up the pins with the holes in the buttons. Critical no. Conjecture. Yes. It sounds good if you say it fast. My point is I should be able to "feel" that button up and it should be reliably guns free and safe when down. You can't "feel" a momentary spring loaded button but I can "feel" an off and on switch. Since ramp starts, runway starts and air starts begin with a default with different gun safe. I think a runway start should be guns safe but it defaults to guns free. Regardless, I promise to do my pre-fights better so I can toggle things back proper but I get a little grumpy when I forget. it's all my bad. Carry on. https://smnzone-scalemodellingno.netdna-ssl.com/wp-content/gallery/br-hurricaneexplored/12-ar-fig-2-pneumatic-twin-gun-firing-button.jpg

Step # 1 Does it happen with any other script? Check this>>>>>I went to get a pic of the save power sleep mode for hid devices to show how to turn it off and found windows had turned them all back on. Check out the pic. Apparently the last windows update changed it back. I will now uncheck all those allow to save power boxes for usb hid devices.<<important UNCHECK those boxes. I would uninstall Target and the TM Drivers and unplug them. Boot up. Reinstall the latest drivers plugging in the tm devices when it says to. Re-install the latest Target software (new version this summer). If you plug in and unplug hid devices such as other controllers or cams , it can mess with device ordering. I leave everything I use on my gaming machine plugged in. As an example, If I unplug my cam, over a reboot it will reorder things. It is a rare issue amoung users. I have noticed static electricity from my hand to my throttle can disconnect momentarily enough to mess things up as well. Nothing gets to touch the carpet now. Thrustmaster. A Love/Hate relationship. ;)

I made a full backup. Thought I'd share. It is my final since for me, it is flawless. Hitting enter before I time out... Spitfire Ultimate.zip