ark

Members
  • Content count

    675
  • Joined

  • Last visited

Community Reputation

67 Good

About ark

Flight Sim Profile

  • Commercial Member
    No
  • Online Flight Organization Membership
    none
  • Virtual Airlines
    No

Profile Information

  • Gender
    Male
  • Location
    Colorado, USA

Recent Profile Visitors

555 profile views
  1. On the FSW webpage there is the following suggested update for the C441. If you haven't tried it, it may be worth giving it a shot to see if it helps with the altitude hold issue by increasing the trim limit from 15 to 20 degrees (maybe the AP is running out of trim authority at high engine torque). The aircraft.cfg file is in your main C441 folder. Increase elevator trim range Until our next update changing this value in the Aircraft.cfg file using notepad will increase the elevator trim distance and this ensures that the autopilot will not use the entire range to keep the nose down during high torque. [airplane_geometry] elevator_trim_limit = 20.0 //Degrees Also, there is a 11Sept2017 patch available there to install the Com2/Nav2 radios if you are using a single GTN750 and the radios are missing from your C441 panel . http://flysimware.com/website/Cessna441.html Al
  2. Great ! I wonder if the key was redownloading the GTN750 to get the latest updates? Al
  3. Steve, If you don't find a solution here, suggest you try the Natural Point Track IR5 forum at: https://forums.naturalpoint.com/viewforum.php?f=60 Mike, from Natural Point, often responds to posts. Al
  4. Reybred2. If you are still having problems, suggest you read through this thread on the Fligh1 F1 GTN/GNS Series Support Forum at http://www.simforums.com/forums/gtn-complete-v2-04_topic59024.html. It seems a number of folks are having some problems similar to yours with the GTN750 and P3Dv4.1 with a variety of different a/c. Some things to try are suggested throughout the thread by a Flight1 rep (Tiberiu); perhaps you may find something there to try. If not, suggest you post your issue in the thread and I would expect Tiberiu will respond. And of course, you could also open a support ticket directly with Flight1. I'm afraid I'm out of ideas on things to try for now. Al
  5. If you do decide to try reinstalling the GTN750, I would first uninstall your current GTN750 setup to help make sure all files are updated on the reinstall. Al
  6. Ryebred2, What version of the GTN750 are you using, and what version of the GTN Configuration tool? Another thing we can check is the GTN entry in the panel.cfg file. Using a text editor like Notepad, open the panel.cfg file which is inside the panel.RDR_GTN folder inside your Lear35 directory. At the top of the file there is a [Window Titles] section which should have a GTN entry similar to this: [Window Titles] Window00=CONTROL_PANEL Window01=AIRCRAFT_OPTIONS Window02=Flight1 Garmin GTN750 U1 Window03=WX Advantage Radar Window04=START_INSTRUCTIONS Window05=DOOR_INSTRUCTIONS Window06=PAYLOAD_MANAGER Window07=WIND_GAUGE Window08=TEST_PANEL And then further down the panel.cfg file there should be a corresponding window entry like this [Window02] Background_color=0,0,0 size_mm=937,887 VISIBLE=0 ident=14401 window_pos= 0.310, 0.160 window_size= 0.340, 0.580 zorder=99 gauge00=F1GTN!GTN750, 0,0,937,887,UNIT1.POP These entries are set up by the GTN Configuration tool, which is why I asked what version of the tool you are using. There have been issues where the window entry has been corrupted, and Flight1 has updated the Configuration tool a number of times over the past year or so. Al
  7. Ryebred2, Put your mouse cursor on the GTN's blue memory card in the upper left corner of the GTN box and make sure the tool tip says the Nav source is GTN 750 Gauge Unit 1, and not GTN 750 Gauge Unit 2 or Flight Simulator GPS (which is the sim's default GPS unit). If you had more than one GTN750/650 installed, this is how you could switch the Nav source between the different GPS units. (Ref: Pg 16 of the Flight1 GTN Series User's Guide). Al
  8. Ryebred2, Does the GTN750 Nav work with any of your other aircraft? Al
  9. You are most welcome -- glad to be of some help. Yes, while FSUIPC does have a learning curve, in my opinion it is a wonderful addon program the provides the user with many options that otherwise would not be easily available. Al
  10. The GTN 750 has a world-wide database. Al
  11. "Let's hope my intervention will not be required for the 50." Stated that way, I have to agree. However, being realistic, I’m sure there will be opportunities for improvements. In this case we have someone who has been working on a complex simulation for over a year essentially single handedly. In contrast, it is not uncommon, but in fact rather the norm, for larger developers like PMDG, MILVIZ, and FLIGHT1, etc, to have to put out updates and fixes to their products. So I won’t be shocked if the same thing happens with the FSW Falcon 50. While I’m sure inputs in support of improvements will be appreciated if needed, no one should feel burdened or obligated to participate in that process. My 2 cents. Al
  12. My understanding is the bulk of the systems modeling is done, which was a big task. I think the goal is to have things competed by late Dec or sometime in Jan at the latest. Mark has to deal with some unpredictable health issues which slow him down at times. The Falcon 50 is FSW's most complex undertaking. It is a lot of work for one guy, especially given the level of systems depth he wants, which is greater than currently in the Lear35. Al
  13. Turns out FSW did contact Ernie a while back, but there was only limited response. I'm also told Ernie's Facebook page has been inactive for quite a while now, which makes me wonder if he is still 'active' as far as new sim products go. Al
  14. And how exactly do you adjust that rate if you could explain? Thanks :-) As you can see from the picture below from the FSUIPC Offsets Status document, FSUIPC offset 0BC0 is the elevator trim offset with values that range from -16383 (full down) to +16383 (full up). Then under the FSUIPC Buttons and Switches tab the Offset Sword Increment and Offset Sword Decrement controls are used to change the trim value. Increment increases nose up trim and Decrement does the opposite. The 16 in the parameter 16/16383 means each push (or repeat) of the trim button represents a change (increment) of 16 out of the total range from -16383 to +16383. Or said another way, you dividing the -16383 to 16383 range into 32766/16=2048 steps (one step per trim button push or repeat). Increasing the number of steps by decreasing the 16 value gives you finer (slower) trim control, and decreasing the number of steps by increasing the 16 value speeds up the trim action. The same idea holds for the down trim step size, and note the negative sign on the Decrement parameter 16/-16383. By making these values profile specific (specific to particular a/c), you can have different trim rates for different a/c. Note the box "Control to repeat while held" needs to be checked. The text below is from the box on pg 31 of the FSUIPC Users Guide: Al Offset Increment/Decrement Controls The increment/decrement controls operate on signed (Sbyte, Sword) or unsigned values (Ubyte, Uword), and have a more complex parameter that specifies both the increment/decrement (always positive) and a limit, thus: <increment value> / <limit> This allows things like Trim adjustments to be programmed to be whatever speed you like, or even multiple speed if you have enough buttons or levers to spare. Taking Trim as the example: The elevator trim is a signed WORD at offset x0BC0. For this sort of information you'd need the Programmer's Guide in the FSUIPC4 SDK. Its range is –16383 (full trim down) to 16383 (full trim up). So, when programming your button/levers: 1. Select the "Offset SWord Increment" control to program the nose up trim. 2. Enter x0BC0, or just xBC0 into the offset edit box. 3. Enter 256/16383 in the parameter box. The 256 is the increment and 16383 is the limit. This will give 128 steps between – 16383 and +16383 inclusive (32768 / 256 = 128). If you want a faster, coarser trim adjustment specify a larger increment, and of course vice versa for a slower, finer adjustment. 4. You'll probably want it repeating whilst held, so check that too (but never set repeat for rotary switches which can be left in an ‘on’ position, nor latching switches). 5. Do the same for the decrement, with a parameter of 256/–16383 (–16383 being the lower limit). Note that the decrement is still positive—you can only provide positive numbers for this part. It is the definition of increment or decrement which controls the addition or subtraction. 6. When reviewing such assignments you may see the parameters showing in hexadecimal (preceded by ‘x’). This is an optional way of inputting these in the first place, just as with the offsets. Note: This tmethod can also be applied to the rudder & aileron trims. Select "Offsets sword increment" with 256/16383 as the parameter to trim to the right, and select "Offset sword decrement" with256/-16383 as the parameter to trim to the left. Enter x0C04 for rudder trim or x0C02 for aileron trim into the offset edit box, and then proceed as 3 to 5 above
  15. I can't answer your question (you could email FSW and ask), but my guess would be that at this late stage of development any FMC capability would have to be via an addon FMC by the user, such as the freeware Honeywell FMC by Garrett Smith or the vasFMC, or a payware FMC. However, I don't have a feel for how well they would work, or whether such addon FMCs require the a/c to have an integrated autothrottle capability which the FSW version doesn't have. Might make for an interesting do it yourself project though for those so inclined. Al