Jump to content


RTW Race Team
  • Content Count

  • Donations

  • Joined

  • Last visited

Everything posted by spokes2112

  1. Prior to selecting the procedures tab of the search window, right click on the airport you select on the main search window & select "Show all Procedures" ( CTRL+SHFT+R ) , the procedure tab will now be populated with the airport procedures you desire.
  2. Downloaded and took a look at it. All it takes is a little "nudging" of the ALT & VSI gauges in the VC. All 2D panels are OK. The 2 were overlapping while the VSI had a -1 for the initial X coordinate. (usually not good) In the panel.cfg (make a backup if wanted) under the [Vcockpit02] section change these 2 entries : gauge02=oh23!altimeter, 65,104,66,66 gauge03=oh23!VSI, -1,100,66,66 To this : gauge02=oh23!altimeter, 68,104,66,66 gauge03=oh23!VSI, 1,100,66,66 That should do it for you.
  3. One other thing to consider. Are you actually trying to track a localizer? or trying to track a VOR? Some APs treat the 2 the same, good ones don't. If you really are trying to track a LOC then get closer, much closer, <= 20nm out, The AP should track it then. If you are using LOC mode to track a VOR then it really should work.
  4. Since this probably an advanced aircraft ( I dunno, do not have ) it may require >= 30° intercept heading to the desired NAV1 crs for the AP to engage the NAV. ( the Maddog & others act this way ) Set everything up as shown above ( 109.6, crs = 74° )then set the heading bug ( and actual heading ) to no greater than 043° or from the other side, no less than 105° to intercept the NAV radial. If the AP engages NAV then you will know that this aircraft requires the 30° difference. Good luck.. Yes, this was typed up on a Chromebook 😉
  5. Some short reading material prior to your weekend flights - Don't be this guy! HERE It was mentioned that this article may not be available outside the U.S., scared of spreading the "rona" or soomething - HA! You may have to try a VPN with your source being the U.S. -OR- stop on over to my dropbox and get a copy. Shhh, don't tell anybody. HERE
  6. Just fly the climb at the speed you would like adjusting the AP rate of climb to keep that speed. Do not use IAS speed hold, although if the AP has N1 hold, use that,. If the vertical speed becomes too low then use a lower reference speed. That takes care of almost any fuel or payload.(OFC within realistic limits) Hand flying the AP VS like this is the same as if the AP had a FLCH mode. If the sim aircraft has a FMC, the FMC computes the required speed itself but basically flies the aircraft the same as above if on the FMS / VNAV mode. A "general" climb schedule that works for almost any airliner : < 10,000 feet, adjust vertical speed to maintain 200 (terminal area) to 250 knots > 10,000 feet to transition altitude (18,000 feet in the US), adjust vertical speed to maintain 300 knots > 24,000 feet adjust vertical speed to maintain MACH 0.70 At cruise altitude adjust throttle for for cruise speed / fuel rate or engine EPR .
  7. Ron, unless my eyes are serving me wrong, I would revisit this. Just for kicks I compared the 2. 👀 Yes, the area (country) idea is the same, some POI's could be & perhaps 1 or more images / descriptions "might" the same but the flight plan itself is not, not even close. Just hoping to keep that expired can of worms sealed.. 😉
  8. That or right click on the sim screen. (quick sim menu)
  9. @coldhoist There are 2 binary files that if corrupted, can cause FSX not to start, the logbook & the wxstations. For the logbook just search here or google for something like "FSX logbook fixer". For the wxstations just delete the "wxstationlist.bin" file & let FSX rebuild it. It is located in C:\Users\<user>\AppData\Roaming\Microsoft\FSX No harm in giving these a try. Better than reinstalling windows. Throughout the lifetime of my FSX install I have the logbook fail a couple of times & the WXStation list fail when trying new, freeware WX programs.
  10. Maybe give this a try, FSX closed, change in the FSX.cfg [Trusted] section : C:\Program Files (x86)\Steam\steamapps\common\FSX\SDK\Environment Kit\Traffic Toolbox SDK\TrafficToolbox.dll.haliznhicbbaunokrtzwbrizaleqnrinhtiaenwe=0 -- change to -- C:\Program Files (x86)\Steam\steamapps\common\FSX\SDK\Environment Kit\Traffic Toolbox SDK\TrafficToolbox.dll.haliznhicbbaunokrtzwbrizaleqnrinhtiaenwe=1 Start FSX and see if you have the FSX Menu --> Tools --> Traffic Toolbox. If so, you could optionally set the Traffic360 version to 1 too. ( if you still use it )
  11. Your XML looks good and parses fine. The menu is located at : FSX Menu --> Tools --> Traffic Toolbox Check to see if the .dll is there, follow the path given in your xml above If it still doesn't work try checking the FSX.cfg under the [Trusted] section and see if it is listed there. Maybe, by accident, you didn't trust it when it first loaded.
  12. Check your fsx settings. Perhaps in your old sim you had "airspeed, display true" and now in this one you have "airspeed, display indicated". "Indicated" is always the preferred setting. Indicated airspeed = what instrument shows from air data on the pitot / static systems ( what the pilot sees in cockpit, reference speeds for the aircraft are shown in indicated ) True airspeed = Indicated airspeed + outside temp, humidity adjustments.. IE air mass ( this is what a wiki / google will show for max speed ) Ground speed = True airspeed + any winds affecting flight.( GPS / FMS will display this, used for time calculations ) Edit - Using an online calculator for a standard day. 350 kts indicated @ 38000 ft yields a true airspeed of : 607 knots Add some tailwind and you are cooking along nicely.
  13. A good brain teaser to go with the morning coffee. ☕ The answer? It is hard coded in part of the AP system gauges. Instead of directions on how to modify yourself I just made a little kit to try yourself. Default up = 1500 fpm, default down = -1000 fpm. [Install] Download the kit here. Unzip & place the GAUGE_PA31TAP.cab file in both the Airplanes\Carenado PA31T_Cheyenne_II_LITE\panel & Airplanes\Carenado PA31T_Cheyenne_II\panel folders. Do NOT install into the FSX\Gauges folder! [Uninstal] Delete the GAUGE_PA31TAP.cab file from both the Airplanes\Carenado PA31T_Cheyenne_II_LITE\panel & Airplanes\Carenado PA31T_Cheyenne_II\panel folders.
  14. Have done the same thing, since FS9.. This sheet has been continuously updated and hardly ever changed in regards to assignments. After years and years at my side it is rarely referred to except maybe during gauge/lua coding sessions. All the keyboard keys in the image refer to FSUIPC/Lua commands whereas the text keyboard commands are the only remaining sim commands with very few having the stock key assignments. On the joystick image there are 2 solid black buttons, using these gives me 3 alternates for each of the remaining buttons although not all buttons have 3... Yet. Printed out & contained in a plastic protector to prevent stains from the occasional coffee spillage.
  15. If this is the stock 737 / 747 then no, there is no way to select AP nav source other than NAV1 & GPS. Only the most advanced payware aircraft have the ability to select NAV2 as the AP source.
  16. I believe the online activation is no longer available. From this post you can look in the FSX root folder for "Phone Activation.xml", call the number that is associated with your country or the US. If the phone activation does not work you can try this or this ( same procedure, written differently ). Note.. It requires registry editing (advanced) but it has been successful for many.. Phone activation list shown here for ease :
  17. Good news that the sim is showing now. One thing I would do prior into looking into the Ox80004500 error is start the sim, have the aircraft ready to fly, then, shut down the sim so everything gets written back as it should on a clean shutdown. ( FSX.cfg, FSX temp files, prefetch, other cfg / log files etc..) A computer restart at this time wouldn't hurt either. Then, as for the Ox80004500 error, it is from windows and any subsequent hints are clear as mud.. ( from an internet search ) Sorry...
  18. You might want to try this.. What I suspect is that you are directly going into the flight, bypassing the opening screen where you are able to adjust things. One of the adjustments is going to directly into full screen on load. With a plain text editor open up the FSX.cfg & check these settings : FSX boxed, Steam should be similar - C:\Users\<USER NAME>\AppData\Roaming\Microsoft\FSX\fsx.cfg These will get you into the opening screen so you are able to adjust things and, after that, run the sim in windowed mode. [STARTUP] LoadWindow=1 SHOW_OPENING_SCREEN=1 [Main] Maximized=2 As described above, make sure you are running FSX in the Win 7/8 compatibility mode and also as an administrator.
  19. Yes, exactly... 👍 In the FSUIPC dialog it is very easy to be in the wrong Lua section, IIRC there are 6 lua sections ( take with a grain of salt, from memory ) : 1) Lua [filename] - This will run the lua, "R" 2) LuaKill [filename] - This will kill the lua, "K" 3) LuaSet [filename] - This will set the flag provided by the param, "S" 4) LuaClear [filename] - This will clear the flag provided by the param, "C" 5) LuaToggle [filename] - This will toggle the flag provided by the param, "T" 6) LuaValue [filename] - This will send a value to the lua variable ipc.param via the UI param, "V" You can modify your .ini while the sim is running, save it, then go to the FSUPIC dialog, keys tab, press "reload all keys". That should do it :) If it does, ofc delete the pesky K & L assignments.
  20. Ideas.. - Review your key settings for numpad 2 & 5 in FSUIPC keys tab, the right side.. Confirm they are correct, matching exactly to what you have with the K & L keys. - Try removing 2 & 5 from the default commands as a test. You could also post only the [Keys] section of your FSUIPC.ini file, maybe a second set of eyes looking at it may help.
  21. This is just an idea on where to start. MSCTF.dll is a windows OS file dealing with Text Services.. Look for something dealing with plain text files. My idea? If the MD-11 is PMDG or an advanced aircraft with a FMS & uses database files (usually a plain text type) then maybe try setting your windows "Region and Language" settings. Control Panel | Region and Language | Formats tab | Additional Settings button --> Customize Format | Numbers tab | --> have Decimal symbol set to "." period & List separator set to "," comma. Reboot computer & try the flight again.. Again, just an idea. If that doesn't work you can always revert back to your previous Windows regional settings.
  22. I built a few gauges many years ago that have the same problem. Tried over & over again to rectify the situation with no luck. A thought just occurred... Have you tried doing the undock/move panel with the sim paused or the aircraft in a stationary state (IE preflight) ? Haven't tested yet but I think what is happening is that when the panel is undocked and is starting to be moved a value on the readout is updated/changed during that move. At that time the monitor(s) w/h size, w/h ratio may change and as the readout string is written the references to screen size/ratio are all wonky being saved as a reference to future readout updates. Just an idea, going to test this on my next sim session.
  23. These 3 are custom events using L:Vars. You can control these using either FSUIPC L:Var Macros or LINDA. For reference - (L:Stall_Heat, bool) < 0 = off, 1 = on > (L:fuelVentHeatL, bool) < 0 = off, 1 = on > (L:fuelVentHeatR, bool) < 0 = off, 1 = on >
  24. When using FS title bar, it will show the last offset listed of the 4 available. So make sure that either 024C is the only one in the list or it is in the last slot.. OFC have hex unchecked if you want a standard number output.
  • Create New...