In the past versions of the Tinmouse2 I've had the minor annoyance of the flaps not working...I know we only use the F6 and F7 keys (not F5 and F8) but occasionally hitting F7 will result in the flaps beginning to travel to setting "1", and then going back to stowed. For some reason this annoyance has gotten worse for me...3 attempts at starting a flight in the TM2, and my flaps won't work. This is new as my first 2 flights with 1.25 worked perfectly. Some things I've noticed...I used to be able to hit the attendant call button, if the sound didn't play that was my cue to restart the flight and reload the default as I had done something wrong. This no longer works as a cue to a loading problem. In the "problem" flights, my gear lights didn't load and I had to click the hot spot to see them...this is new from my first 2 1.25 flights. It seems to me to be a problem with the way I'm starting a TM2 flight or...maybe...an issue with the panel re-initializing when I go to full screen after I have everything set up? Here's my order (Windowed mode for start):1. I have my ADEU card already loaded in my CIVA folder.2. I have my FSNav plan exported to FS9.3. I start FS9 and load the default flight (Cessna at Seattle) NOTE, this is an untouched version of the default that I religiously leave alone!4. I move the Cessna to the departure airport.5. I set time and date.6. I download RW weather (with 15 minute updates).7. I switch to the TM2 aircraft of choice.8. The panel initializes.9. I set fuel and payload as desired.10. I start my VA's ACARS program.11. I load my FSNav flight plan.12. I go to Full Screen mode (the panel re-initializes).13. I perform the usual start-up (APU generators on, Packs, start the INS alignment, set lighting, get clearance from ATC, etc, etc.).14. Pushback.15. Start engines, engage main generators, close APU bleed, open engine bleeds, shut down APU, set pressurization to "flight", etc., etc.16. Set Take-off flaps....and the problem occurs.Somewhere, in there, I'm thinking, lies the problem. Another interesting point...on my first 2 1.25 flights the parking brakes worked as corrected in 1.25..."." would release and "CTRL+." to set. This is not so in the problem flights..."."would not release brakes? I'm doing something wrong and can't quite put my finger on it.

An update,I started FS9 in full screen and followed the basic order above with one change...I loaded the TM2 at Seattle and THEN set myself up at ETAR. On the panel initialization I had my "3 green" gear lights showing...they disappeared after going to the overhead and returning...but loading in full screen solved the flaps problem. I have no idea why I didn't lose flaps functions on my first 1.25 flights which I started in Windowed mode but now I do lose it if I start in Windowed mode and switch to full screen? Makes no sense...what changed? I haven't touched a thing since the 1.25 install.Is there any way to stop the panel re-initialization when switching view modes? I'm not sure that's the answer...as I said, switching view modes did not harm the flaps function on my first 2 1.25 flights, but I'm out of ideas.

Update 2.There is a definite correlation between "." not working to set parking brakes and the flaps (F6 F7) not working. The gear position lights may or may not be related. It is definitely tied to switching views from Windowed to Full Screen. I have no explanation as to why my first two 1.25 flights had no problems with view switching, as long as it was done before starting up the aircraft systems? All I can tell you is it doesn't work anymore...the entire flight had better be started in Full Screen mode or parking brakes and flaps don't work...for me, of course, don't know if others are experiencing this or why it changed suddenly?I can, of course, somewhat live with this new restriction, although why it's changed from earlier 1.25 flights will eat holes in my brain and cause worms to find shelter therein :( .

S-I-G-H! Another issue...multiple leg flights? I finished the first leg of a 2 leg flight. I shut down the TM2. I loaded the next leg's flightplan and saved the flight in FS9. Unfortunately the flaps don't work, even loading the saved flight directly to Full Screen. Bob, I have to admit to a bit of dissatisfaction with this issue? I will readily admit to not knowing what's involved in making the TM2 work...but I need some education as my payware addons do not exhibit these issues? It all seems to be related to the panel initialization? I could be way off on that, however. I can't figure out why a saved flight, at stop 1 of a 2 stop flight, would bring up the flaps issue again? I saved in Full Screen, I started in Full Screen...and yet the flaps issue returns. Also the parking brake issue..."." doesn't work to release brakes and this is a guaranteed indication that flaps will not work.Anybody have any ideas?I'm bailing on my VA's 737-200 flights until we figure this out.

For flaps, try going into FS and deleting the key assignments for the flaps in the FS control assignment menu. Could be that there's some doubling up going on.Alternative 2 is to assign two other keys to send the FSUIPC offset as in the manual.For brakes, have you tried assigning a button or key to the FSUIPC offset?The issues with initialization when switching to/from windowed and full screen mode have to do with FS running the initialization process again when that switch is made. The initialization is only supposed to run once, when the panel first loads. I'm a bit stuck in a quandary as to how to deal with that without making it so that parts of the panel won't initialize properly if the panel is re-loaded or the flight is reset.Have you tried going to full screen mode, and then loading the 'mouse, so that switching isn't needed?RegardsBob ScottColonel, USAF (ret)ATP IMEL Gulfstream II-III-IV-VColorado Springs, CO

When FS9 is switched between full screen and windowed mode, it runs the panel system through a cycle in the pre-install panel service mode. This forces the panel, as it's written now, to re-initialize like it's first being loaded. This is causing the internal hotkey table loaded into FSUIPC to be cleared somehow, so all the programmed hotkeys (F6, F7, "." and "/") stop working. The FSUIPC offsets that control the functions still work, though, as do the various panel clickspots. In the case of flaps, clicking on the upper-half of the flap gauge will move the flap handle up one notch, clicking in the bottom half of the gauge moves the flap handle down a notch.The brakes, similarly, will work with any input except the "." key once this happens. The best way to use the brakes, in any case, is to program your pedals or a button on the joystick, to send brake inputs in via FSUIPC.If the panel is loaded in either windowed of full screen mode and left there, no problems with any of this.So the workaround, until I sort through this, is to load the panel in the mode you will fly it in. If you switch between full-screen and windowed mode or vice-versa with the TinMouse panel already running, it'll cause problems.RegardsBob ScottColonel, USAF (ret)ATP IMEL Gulfstream II-III-IV-VColorado Springs, CO

OK, I found the problem, and it appears fixed in preliminary testing here. Turns out there's a bug in the MS SDK that's been around since at least FS2002...found an old post by Arne Bartels that explained it.I need to do a bit more testing, plus I found a bug in the pneumatic system logic that needs fixed.V1.26 with the fixes (gauge only) should hit the streets in the next few days.RegardsBob ScottColonel, USAF (ret)ATP IMEL Gulfstream II-III-IV-VColorado Springs, CO

V1.26 was just uploaded with this fixed. See the pinned post for more detail.RegardsBob ScottColonel, USAF (ret)ATP IMEL Gulfstream II-III-IV-VColorado Springs, CO