September 16, 200619 yr First I have to say what an amazing panel, a real work of art. I'm still flying the the 737-200 FFX. When I upgraded to v1.1 the folder for the 732 FFX did not have an FDE file. Should I use the the the new FDE or the old one that came with the first tinmouse 2 download? Scott
September 16, 200619 yr There should be just an aircraft.cfg file in the folder. If it's not there perhaps you could try downloading again.By the way, Philip Foglar has just released a new FDE for the FFX 737-200 with his new USAir/Metrojet repaints. It uses Mike Baumann's FDE but with improved contact points (for each individual wheel) and more precise tyre smoke effects. There is also an option for wing and flap vortices.boeing_737-200_metrojet-kittyhawk.zipI find Philip's and Mike's updated FDEs a noticeable improvement on the original. If you do use the aircraft.cfg from the metrojet you may have to copy the radios entry from the .cfg provided with the tinmouse in order for them to work correctly.RegardsIan
September 16, 200619 yr Use of FM that is not that one that if finds in the original package can give abnormal behavior of the aircraft in the simulator, and wrong reading in the EPR gauge.you was informed.regards, Gustavo Rodrigues - Brazil
September 16, 200619 yr I would expect that you can transplant the contact points end effects sections into our aircraft.cfg without issue. But as Gustavo points out, the FDE supplied with the TinMouse II and a number of internal functions in the panel are interrelated, and your aircraft performance is likely to be badly affected by use of a different FDE (.air file and aircraft.cfg together make up the FDE).RegardsBob ScottATP IMEL Gulfstream II-III-IV-V L-300Santiago de Chile Bob Scott | President and CEO, AVSIM Inc ATP Gulfstream II-III-IV-V Sys1 (MSFS20+24/XPlane12+11): AMD 9800X3D, water 2x240mm, MSI MPG X670E Carbon, 64GB GSkill 6000/30, nVidia RTX4090FE Alienware AW3821DW 38" 21:9 GSync, 2x4TB Crucial T705 PCIe5 + 2x2TB Samsung 990 SSD, EVGA 1000P2 PSU, 12.9" iPad Pro Thrustmaster TCA Boeing Yoke, TCA Airbus Sidestick, Twin TCA Airbus Throttle quads, PFC Cirrus Pedals, Coolermaster HAF932 case Sys2 (P3Dv5/v4): i9-13900KS, water 2x360mm, ASUS Z790 Hero, 32GB GSkill 7800MHz CAS36, ASUS RTX4090 Samsung 55" JS8500 4K TV@60Hz, 3x 2TB WD SN850X 1x 4TB Crucial P3 M.2 NVME SSD, EVGA 1600T2 PSU Fiber link to Yamaha RX-V467 Home Theater Receiver, Polk/Klipsch 6" bookshelf speakers, Polk 12" subwoofer, 12.9" iPad Pro PFC yoke/throttle quad/pedals with custom Hall sensor retrofit, Thermaltake View 71 case, Stream Deck XL button box Sys3 (DCS/P3Dv4/ATS/ETS): AMD 7800X3D, MSI MPG X870E Carbon, Noctua NH-D15S, 64GB GSkill 6000/30, EVGA RTX3090 Alienware AW3420DW 34" 21:9 GSync, Corsair HX1000i PSU, 4TB Crucial T705 PCIe5 + 2TB Samsung 970Evo Plus, TM TCA Officer Pack, Saitek combat pedals, TM Warthog, TM RS300 FF wheel/pedals, Coolermaster HAF XB case
September 16, 200619 yr I'm sorry guys. I guess what I ment to ask was what .air file should I be useing. There was only the aircraft.cfg in v1.1 for the FFX model. Thanks again for all the help.Scott
September 16, 200619 yr Scott; The .air file is the same for all supported models (includes Terry Gaff's model and the FFX one)...they use different aircraft.cfg files, however.CheersBob ScottATP IMEL Gulfstream II-III-IV-V L-300Santiago de Chile Bob Scott | President and CEO, AVSIM Inc ATP Gulfstream II-III-IV-V Sys1 (MSFS20+24/XPlane12+11): AMD 9800X3D, water 2x240mm, MSI MPG X670E Carbon, 64GB GSkill 6000/30, nVidia RTX4090FE Alienware AW3821DW 38" 21:9 GSync, 2x4TB Crucial T705 PCIe5 + 2x2TB Samsung 990 SSD, EVGA 1000P2 PSU, 12.9" iPad Pro Thrustmaster TCA Boeing Yoke, TCA Airbus Sidestick, Twin TCA Airbus Throttle quads, PFC Cirrus Pedals, Coolermaster HAF932 case Sys2 (P3Dv5/v4): i9-13900KS, water 2x360mm, ASUS Z790 Hero, 32GB GSkill 7800MHz CAS36, ASUS RTX4090 Samsung 55" JS8500 4K TV@60Hz, 3x 2TB WD SN850X 1x 4TB Crucial P3 M.2 NVME SSD, EVGA 1600T2 PSU Fiber link to Yamaha RX-V467 Home Theater Receiver, Polk/Klipsch 6" bookshelf speakers, Polk 12" subwoofer, 12.9" iPad Pro PFC yoke/throttle quad/pedals with custom Hall sensor retrofit, Thermaltake View 71 case, Stream Deck XL button box Sys3 (DCS/P3Dv4/ATS/ETS): AMD 7800X3D, MSI MPG X870E Carbon, Noctua NH-D15S, 64GB GSkill 6000/30, EVGA RTX3090 Alienware AW3420DW 34" 21:9 GSync, Corsair HX1000i PSU, 4TB Crucial T705 PCIe5 + 2TB Samsung 970Evo Plus, TM TCA Officer Pack, Saitek combat pedals, TM Warthog, TM RS300 FF wheel/pedals, Coolermaster HAF XB case
September 17, 200619 yr Thanks for the quick follow up about the .air file. I did try the metro jet FDE. First with just the contact points and then the whole thing. What I found was that if you do use this file you need to also copy over the weight and balance or the aircraft will flip back on it's tail. How much the EPR is effected I can't tell. What I could tell was that the aircraft did taxi better and changing the pax weight as much easier. If any body could come up with a way to incorporate the contact points and weight and balance to the tinmouse 2 FDE and still get correct EPR values that would be great. Until then, I'm sticking with v1.1.
September 20, 200619 yr Hi guys,My first post here. Firstly, thanks for the developement of the Tinmouse II panel and packages as a whole, great work!!Something that just concerns me a bit that may need to be clarified some how. When you chaps refer to the "FFX" model I gather that you are in fact talking about the Kittyhawk model which is the later version of the 737-200 model that Erick Cantu made. The "FFX" model was released in early 2003 with the Kittyhawk model being released in 2004 for FS9.All the best,Philip.
September 24, 200619 yr Thanks for that clarification, Philip. I have to admit that I wasn't aware of the difference, but I was indeed talking about the Kittyhawk model. I assume that the alternative FDE supplied with the Tinmouse II, although designated FFX, is also intended for the Kittyhawk model? Further to my earlier post about using the FDE from Philip's Metrojet and it being pointed out by Gustavo and Bob that it would not be compatible with many of the panel's operations. Of course, they were correct and although it flew and landed smoothly the engine performance was a long way out and I didn't get the benefit of the improved Localiser locking.My present compromise is to use Gustavo's .air and .cfg file (for the 'FFX' model)but substituting the following sections from the .cfg file of Philip's Metrojet: Contact Points, Airplane Geometry, Flight Tuning. This keeps the engine performance correct for the panel but seems to give a slightly more stable flight and improved landings.I hasten to add that I am not an expert and this is not a suggestion, just a personal preference, so if anybody has any comments or advice (or abuse!) please fire away!Ian
Create an account or sign in to comment