il88pp

if 'fix it' means 'hide the text' then you could try: Close fsx Open fsx.cfg under: [MAIN] Add the line: HideInfoText=1 Close and save file. Start Fsx. That hides the infotext that fsx itself produces. Not sure if it will hide this joystick info too.

installl like any other sxenery create a folder, for example c:\fsx\Microsoft flight simulator x\addon scenery\FMX\Europe\Scenery\ or, if you prefer for example: E:\FMX\Europe\Scenery\ with the .bgl files inside folder "Scenery" (or drive D: of course,whatever you want) (not on external drive) ------ Then start fsx, and activate your new scenery using the "Scenery Library" menu. (PS, you can one install the single region or more, as desired. But you allways need to install and activate the "patches" folder as well.)

Install a free torrent client and use the torrents. See post 7 or 8 here, by Aviatormoser. (The creator of FreMeshX). https://www.avsim.com/forums/topic/516319-freemeshx-global-20-release-announcement/

maybe get one of those Dymo labelwriters.

Tristar35 The site is being worked on, see the reply here: https://www.flightsim.com/vbfs/showthread.php?338256-Server-Simultaneous-Download-Limit-Exceeded

maybe this: https://www.flightsim.com/vbfs/showthread.php?248567-How-do-you-keep-FSX-interesting&p=2156740#post2156740 something called: FltPlan Go! -(Not tried it myself.)

You're right. I see other files come up fine in the library. No prob. il.:D

I was looking for: fs2004interface-pack2.zip but get: No Search Results No Files matched your search criteria. still same issue with library? or has that file simply been withdrawn?

what Operating System is on the computer?

In the thread you linked that registry advise is about a different error message (1722). It does not apply here. Even if it would, using regedit in csse of 1722 would be very bad advice. this error, 1305, is about an unreadable DVD. (missing files on dvd). therefore trying to copy the files to disk first, copying the DVD, is the way to go.

make a folder on the pc. copy all folders and files from disk 1 to that folder. copy all folders and files from disk 1 to that folder as well. run the installer file from that folder. ------ or use your CD/DVD burner. make an .iso file of disk 2 and burn the .iso to a blank DVD. install from that.

different zoom level on the vr then on the screen?

perhaps you can create something like: read switch position if switch is in on position, read avionics state in FS if off --> toggle avionics (both on). if on --> do nothing. if switch is in off position, read avionics state in FS if on --> toggle avionics (to both off). if off --> do nothing. ------------------ to avoid situations like: 1=on 2=off flip switch and now 1=off 2=on. you may need to make the thing a little more complex. Using something like: read switch position if on read avionics 1 state if on do nothing then also read avionics 2 state if off toggle avionics 2 (so both are then on) + same for switch off position. (Note, I do NOT have FS2020. So I do no know if these variables like 'read_avionics_2_state' & "toggle_avionics_2" even exist in FS2020. (If not, you coild akso achieve "toggle_avionics_2" with ) In FSX K:Events (Key events ("commands" if you want)) such as toggle_engine_starter:1 1 and toggle_engine_starter:2 do occur in gauges and such. (maybe the exact K:Var-names are slightly different))

Sorry. That came out harsher then I meant it to sound. Your first post I see. Welcome to the Forum:D

yes, to make the aircraft follow the gps plan you need to activate VOR-LOC. You also have to set the NAV-GPS switch to GPS.

next time start a new thread for your question.

switch any time acceleration off.

Helicopter collective tied to one of the joystick axes perhaps?

may be as easy as switching multiplayer on. see here: https://forums.flightsimulator.com/t/online-status-is-always-offline-and-cant-change-server/429114

fsx works perfectly on Win 10. What causes those issues is something else. Fsx-settings, hardware, edits to those aircraft you had made in the old install now not being in those planes, etc, etc.

Hi. Here that logic in code. And combined with yours from post one. May be some typos in it. Cause made on phone. And not tested. Also see below the code. (A:Avionics Master Switch,bool) 1 == (A:Autopilot Heading Lock,bool) 0 == && ((A:Autopilot heading lock dir,degrees) (A:Plane Heading Degrees Magnetic,degrees) - ) (>L:VAR_A) (L:VAR_A) -180 > (L:VAR_A) 180 if: (L:VAR_A) (>L:VAR_B) (L:VAR_A) -180 if: (L:VAR_A) 360 + (>L:VAR_B) (L:VAR_A) 180 > if: (L:VAR_A) 360 - (>L:VAR_B) (L:VAR_B) -2 > 2 (L:VAR_B) -2 (L:VAR_B) 2 > I found a thread about the same "passing 360 degrees" issue on FSDeveloper. Note also: There a different variable is used to get the aircraft heading: (A:PLANE HEADING DEGREES GYRO,degrees) https://www.fsdeveloper.com/forum/threads/plane-heading-and-autopilot-heading-lock.83209/ Posting took few days. I ended up trying to make it into something more complex. >When 'AP_HDG_SET' different from 'AIRCRAFT_HDG' >Green arrow when AP_MASTER and HDG_HLD engaged. >Red arrow when not engaged. But.... there are more ways for AP to guide LAT navigation. (VOR_LOC, etc). It would get too complicated. So I took that part out. Also realised then. This gauge points to difference between 'AP_HDG_SET' and 'AIRCRAFT_HDG' only. With these A:Vars it will not point the right way if the aircraft is flying following a GPS Flightplan in GPS mode. (or when tracking a VOR or ILS.) To make a gauge that shows me where the plane is turning on autopilot (or where the AP would turn it) in all AP settings would take longer then I thought. For your gauge the other AP Modes are perhaps less inportant. The (A:PLANE HEADING DEGREES GYRO,degrees) variable may be worth looking at. #

Closing fsx renaming the fsx.cfg file and then restarting fsx. Means fsx will start without fsx.cfg file present. Fsx will then create a fresh fsx.cfg file while starting. with default settings. currently your settings are to high and the pc can't load the textures quicklu enough. (or the settings are just messed up.) (Don't worry about renaming the fsx.cfg file. You still have renamed file as a backup.:))

change 'm out for 3.5" flopy's:confused: :p:D

set your grapgics settings lower. use the menu. or better. close fsx. rename the fsx.cfg file to fsx_old.cfg (so there is no file named fsx.cfg any more) start fsx. you have a office pc. not a gaming beast. dont use very high settings. make sure your nvidia driver is installed and updated.

This is a good guide about installing in fsx. http://www.fstipsandaddons.com/how-to-install-addon-aircraft-in-fsx/ https://simviation.com/fsxaircraftinstall.htm Be aware, in Steam edition some people have to install things in the "DLC" folder. (not everyone, not sure why.) See this thread: https://www.flightsim.com/vbfs/showthread.php?299599-Issues-install-Honeywell-FMC&p=1982810#post1982810