DeepDrummer

I prefer the feel of buttons and switches. I don't use the mouse and keyboard at all. A touchscreen certainly has been done. Don't ask me how. No such word as can't.

+1

Anything parked at spot 64 in Saint Pierre du Mont in Normandy will air start even with it set to take off from ramp. Even if parked alone. I tested this with the spitfire, p-51 and the 109 on the latest beta as of 3Mar2019. Is it a bug or did I mess up in ME? Miz attached. test pk 64 .miz

Anything parked at spot 64 in Saint Pierre du Mont will air start even with it set to take off from ramp. I'll go report that.

To add to that, I tend to highlight all the keyboard.html cells and paste it all into a spreadsheet which makes it quickly searchable and editable so I can track changes. I also keep one copy of my saved games folder somewhere else for a backup regularly after any changes.

Thanks for the information. I spent far too long trying to figure out what I did wrong in a whole campaign by using misleading parking spots. My # 2 (Spitfire) spawned flying off into the distance instead of start from ramp as I wished in Normandy from St Pierre du Mont. Any small aircraft parked in spot # 64 started in the air and did not respond to comms. I tried it with 4 spitfires and even with 4 christien whatever (tiny plane). Spots 63, 64, 65 and 66 were desired but I had to change parking locations. Maybe one spot should be removed or something needs to change there. I'd bet I couldn't even park my electric RC carbon cub in spot 64 as it stands today. Minor details. Many hours wasted trying of figure out what I did wrong. I will change spots quickly when that happens from now on. Thanks a lot. In this case there should either be only 3 spots available there or allow 4 small spits to park there. I'd call it a tiny bug. Good to know.

Considering the diameter of the rudder trim wheel, I think it is correct. It would react more for each bit moved of your hand.

Yes. It is still there.

Create a trigger zone by clicking the small circle with the x in it in mission editor left side. adjust the size and place it where you want or refer to a time, speed altitude where it can happen. There are lots of options. Create a trigger using the switch looking diagram in the mission editor left side. I use Audacity (free) to convert mp3s into ogg files and adjust the quality to make it smaller and adjust the length and volume and such. Pick the ogg file to send the sound at a trigger point. You can play at mission start or in a wide range of triggers. It saves into the mission. As has been said, watch the size. Refer to the pic attached.

Get the nose to where you want it to go and trim to hold it there. I just learned that if you trim to move the nose, you will always have to trim back again and this can result in see sawing and constant trimming. Man, I just had an amazing flight in the latest beta release. Nice in all respects from here!

This is not the best solution as you have already suggested but one thing that can help depending on other factors. Just a handy facility for adjusting keyboard and cursor rates and delay. They hid this version under bubble gum kiddie style useless crud but it is still there and can still be used for some. All that the following does for me is slow down the repeat rate a bit and put a bit of delay from the first to second step to ensure I only get one press if I only want a bit. I understand and agree, each step would be better if it was half the travel for sure. I hope we find a way. Doing this like this eased my mind regarding errant key presses. I was always wondering now I know. Fire up notepad and decide if your repeat rate is right for you and if not proceed to change things only after reading the following multiple times. I loaded up the older better way of adjusting keyboard profiles which is just an option to change or add the keyboard control profile to use the older way which I prefer. it may not work for you. Not tested with keyboard software running on my gaming keyboard. G901 This does not address the steps for each keypress and only the rate of repeating key presses and the delay from the first repeat to all the rest as well as the blink rate of the cursor. Use at your own risk Backup up your main.cpl from the Windows system 32 folder just cuz. I didn't and it's fine. You will still be able to bring up the mouse settings by typing main.cpl into the search bar or the command prompt and other normal ways. Make a copy of the main.cpl file that is found in your /windows/system32 folder and save it elsewhere so you could copy it back if you don't like the older better way. I can't guarantee it will save you. I don't think it changes to be honest but who knows. Back up your whole windows machine. There, I am off the hook if you mess up. Note that even after you change things, you can still get to the old way where main.cpl calls up the mouse settings by typing main.cpl in the search bar and pressing enter or of course typing cmd and manually typing it in there or right clicking the main.cpl file and picking open control panel and other ways so you've lost nothing. I do not use any keyboard software at all such as the logitech gaming software. Note this procedure allows your main.cpl (sortof) to use the older version of the keyboard utility which had more functionality than the one in Windows 10 now. If you want to change the repeat rate which will slow it down for multiple presses which happens when you hold the key, you can use the Keyboard control panel. This will not change the incremental actual step for a single keypress but only the rate the next step occurs if you hold it. It may help. It has a window to test your results as you go. One of the good things it does is adjust the delay from the first press to the next repeating bunch by adjusting the repeat delay. If you are constantly going too far beyond what one keypress gives it is useful. I have my delay set to about 75% which gives about a half second delay before it starts repeating. I slowed down the repeat rate only slightly. Remember it will affect any key held like the elevator trim which is based on the same repeat rates and delays. It will slow down even more if you slow the repeat rate. I often wondered if I was getting more than one press. Now I know I am not getting more for about a half second. The remaining presses are as normal and defined by the two top slider settings. A bit of delay ensures that the first press doesn't run into the second press so quickly. the rest of the presses are normal. Even the blink rate could be of interest. Play with it. This will change the main.cpl to always open the older better method. If you type: main.cpl @1 Into the search bar or from the cmd prompt, it brings up the keyboard control panel where you can adjust the repeat and cursor blink rates. They hid it in Windows 10 but it is still there if you convert it to the old way. Main.cpl is located in the system windows\32 folder. BACK IT UP. Don't blame me if you don't like it. I am just the messenger. My search brought me to this from here so blame him.: https://www.digitalwelt.org/en/tips/software/keyboard-speed-windows That one command changes the original main.cpl so again, back it up first in case you prefer the new style bubble gum kiddie type menus that MS THINKS we want.. It would be better if ED would cut each step in half for sure. As torque changes of course rudder trim must change. Torque is changing at most times as one picks up speed or changes one's AOA or any change in the demand for power and torque. I will consider the Spitfire complete only when there is a key binding for gun safety to safe and gun safety to fire. Just because someone says it is complete does not make it so. Yes I have a workaround for the gun safety which I have to re-apply every update (twice for each) and of course it doesn't pass the pure client test in some servers. I think. Unless they banned me for being too easy to kill. ;) Again after all that just type: main.cpl @1 In the cortana search bar or from the cmd prompt and press enter I made a shortcut from the main.cpl to the desktop and then edited the properties to include the @1 I have no problems with it but your results could vary. It doesn't address the issue of big steps for the rudder trim directly. I made shortcuts for joy.cpl, main.cpl and main.cpl @1 Joystick, mouse and keyboard for my desktop.

+1 I think it is grease in mine. It generally only happens on the first press of the day cold. When I say cold, I am talking around 15c. This is near where I start my day as I wait for the fire to warm the room. After the first press, it tends to work perfect all day long. I may try the silicon you suggested. I suspect it will work perfectly. I think the grease is simply thickening in the cold in my case. My stick has been doing that since new. I spent around 20 years twisting wrenches for a living. I used grease often to hold things in place during assembly like uncaged bearing rollers. Grease between 2 flat things that come together indeed tend to stick a bit when moving them apart. I may try a bit of silicon spray when I get some in stock. Good idea! I saved that great pic for possible future use. I often wondered how it looked internally. Thanks for that. :)

I finished the book yesterday. I cannot find the words to describe how good it truly is. It is a great read indeed. One of the best pieces of literature I have ever picked up.

I use the asset pack every single day when making missions and campaigns. I would certainly miss the things it brings to the table like flak and guns, soldiers, B-17G. The cost of admission is great value and a must have for WWII simulations. No regrets here. It is the cost of 2 pizza pies. Well worth it.

I can confirm that this happens with alt-printscreen and shift printscreen as well. Even clearing the dimmed key-bind does not prevent the saving of screenshots to the screenshot folder it makes. It is not a problem but something to be aware of and in fact, it may save me some time not pasting to a paint program. The stock behavior is a nice touch in fact. One can get a folder full of pics without knowing however it until now. Now I know. Thanks for the help Ramsay. I guess I am old enough and type well enough, I never noticed what year they added SYSRQ and never noticed it before.

Awesome! and... you are very brave.

Ahhh I see. Like the old days. Thanks. I will remove the binding from my other copy as well.

Ahh thanks FragBum. I just now figured out how to check my old posts.

That was when I removed it. It scared me to death. I re-installed it yesterday after a thorough cleaning of files. I had the saved games folder saved in 4 different places. that took a fair bit of room. I am now Down to 93 GB. free. What should I consider the minimum? I can't buy another drive for a while yet but it is in the long range plan.

One has no choice but to be a snowbird. Ottawa is balmy compared to some places I have lived.

Anything WWII. era mostly. It is and will be hard to keep up to what is coming in that era but I will try. The 2019 plan suits me fine in every single respect. The progress since I joined in late 2015 is quite amazing compared to any other sim or game I have been involved with in this age. I would buy a Tempest in a heartbeat. 24 cylinders breathing fire. Oh yeah!

The automatic ATC responses that clutter the comms at critical times such as Abort takeoff, abort landing and Takeoff after landing was really bugging me and since I do not want the AT deciding what I broadcast next, I found a way to prevent that which I am sure most know already but to share here is what I did.C If you hit F11 to go back one level in the menu and then hit F12 to exit the comms the canned choice in the comms menu is no longer active at that time. Hitting F12 of course takes it off the screen but it still lurks behind the screens. For instance, if you were to hit F1 for cockpit view after hitting F12 to clear the comms, the hidden canned ATC comms will execute the hidden command and call off your landing etc. If one can make one keybind like a virtual stick as in perhaps joytokey or easily in target, one button press can do those things. I hit that combination F11 and then F12 usually at least 3 times during a mission. Twice when on the ground landing and taxiing. Not handy. The current methods are totally unrealistic in my opinion. The pilot should be able to decide the next transmission with a clear slate. I would vote for removing the ability of ATC to anticipate your next command in any case. Obviously, I am in no rush to see it happen since I have my own temporary fix however many folks do not have the ability to chain two commands together with one press. Even with my fix, it is still quite annoying.

Can someone explain what SysRQ means as a keyboard binding for Screenshot? I had a folder full of screenshots and just wondered what I hit to make those. For now I cleared the field of that binding but I sit here wondering what it was that I was hitting to make those files. I have taken screenshots using shift+Printsceen for a full scrrenshot and alt + Printscreen to take a shot of the active window which copies the shot to the clipboard and worked with it from there.

+1 I concur.

Spitfire has channels A-D as in the pic attached.