Mark Hurst

It seems very unlikely to me that this is an FS Recorder artifact, since FS Recorder doesn't play any part in rendering. Most likely however you are using FS Recorder it is somehow exacerbating a problem that is there all the time but that you usually don't notice. I would suggest looking at your vsync settings, as screen tearing is a consequence of vsync being off.

Yes, go to Views/New View/Cockpit/Virtual Cockpit, which will open a new window. Assuming you are in full-screem mode, just drag the window to a new screen. If you are in windowed mode you will need to right-click on the new window and select 'undock window' before you can drag it to another screen. You can now manipuate the views independently to set view direction. zoom, etc. The main limitation is that you will not be able to save the positions of the windows, so I think you will need to do some of these steps every time you want to fly. This is all documented in the Learning Centre, BTW.

My suggestion is to go to Options/Settings/Display and make sure to select the 'full screen resolution' to be correct for the Surround display (presumably 5760 x 1080 if they are 1080p monitors). It most likely has reverted to 1920x1080 while you were fiddling. If that doesn't help, go to fsx.cfg and delete any sections with names that look like this: [DISPLAY.Device.NVIDIA GeForce GTX 670.0]. These will be regenerated when you restart FSX. Then make sure the full screen resolution is set correctly as above. I am confident one or both of these steps will sort you out.

Assuming you have the older version, it looks like you need to change settings in aircraft.cfg to adjust it for different aircraft. Look at the bottom of this page for the specifics. If you have the later version, it looks like it works differently.

On the assumption that you haven't already, you will need to install the appropriate driver software from here.

Yes, this is entirely possible with FSUIPC (or indeed, without). You can find the appropriate event ids in the SDK documentation here. I have done this for a complete implementation of the GNS530 in my Twin Otter cockpit, which is essentially the default FSX GPS with a veneer to make it look like a GNS530. I used Leo Bodnar BBI32 boards, which appear to FSX as collections of simple buttons, with up/down actions. I also used LINDA to make the programming easier. LINDA makes Lua programming more accessible, although for the GPS you do't really need Lua. There are lots of videos on my YT channel about programming the GPS, including . You can see the GPS in action in various videos, including (start from about 3:10)You can find LINDA code for the GPS at my forum (linked from the YT page), although you shouldn't really need it.

Try going to options/settings/display and selecting a new value for the full-screen resolution. It likely defaults to 1920x1080.

LINDA is the most flexible, and free. But it needs paid version of FSUIPC. SPAD.neXt is in some ways easier to learn but is not as flexible. It's also paid-for and has a subscription model if you want updates.

All versions of FS Recorder should work with the boxed FSX, but you should get the latest one (2-181a), which is in the library here. If you're having problems you should probably start by installing the legacy SimConnect DLLs. See this other recent thread.

It should be on the Addons menu. The only think I can think of is it may need a particular version of Simconnect. You have to install all the legacy versions. You can get them here, among other places.

That version doesn't work on the Steam Edition AFAIK. You will need v1.331.

If you have a window stuck off-screen or partially off-screen, you can generally rescue things by pressing ALT+SPACE, M (ALT+SPACE+M also works) and then using the mouse or arrow keys to move the window. (ALT+SPACE is opening the window's control menu and 'M' is selecting the 'move' option from it.)

Have you tried it in full-screen mode? (I am assuming you are in windowed mode, as you said you need to undock the windows.)

I presume you are talking about events that are only exposed as toggle functions (e.g. toggle landing gear instead landing gear up/down). Yes, this is a pain. You can often work around it by peeking at sim variables to see what state the thing in question is (gear, lights, fuel pumps, etc.) This will require some experimentation, a list of the SDK variables, a third-party tool of some kind and a bit of an understanding of programming. SPAD.neXt is probably the more accessible option as you can do everything from menus. FSUIPC is more poewrful but you really need to learn about Lua programming to make best use of that.

Aerosoft makes Honeycomb's software. But again, the Alpha yoke doesn't require any special software unless you are determined to use the mag switch. There are several well-established third-party solutions available that will let you do that (FSUIPC, SPAD.neXt, Axis and Ohs).

Open up your fsx.cfg and delete entirely any sections that look like this: [DISPLAY.Device...] blah blah Then start FSX again. In my experience this can fix a multitude of sins.

Those zoom settings are about the same, but your eyepoint position is different. You might want to look at this discussion, which might be the same thing.

Or you could just turn them off.

Good grief, he doesn't need FSUIPC to solve his problem. Most likely all that's going to do is leave him £25 poorer with more of a headache than he has now.

Assuming you are talking about the 2D cockpit, your only recourse is to resize the 2D panel itself to be in the correct proportions (it is a window with no borders). And obviously it won't fill the screen, but you could put it in the middle and have additinal view either side of it. If yuo do this, I think you also have to resize the outside view to fill the whole screen, otherwise it just fills the top half. I'd think you would be better off using the virtual cockpit, which will resize correctly for any display.

Assuming your 'full screen resolution' parameter is set correctly in the options/settings/display/graphics page, FSX has likely gotten confused. Shut down FSX, then open fsx.cfg and delete any sections labelled [display.device...]. When you re-start FSX it should work properly.

The OP is a complete novice but you're directing him to watch a tutorial for a sim he doesn't have, about how to use a piece of software he doesn't need, on the basis of your Google search for a product you don't have. I don't think it's going to help.

That's for X-Plane.

Okay, I will try to address some of that helpfully. The good news is, you can get most of the functionality without special Honeycomb software and with a little bit of patience. The problems you have described are common to most other flight controls too, so once you understand what's going on you should be okay. I would suggest that for the moment you put aside any Honeycomb software. When you plug the yoke and quadrant in FSX will see them as joystick controllers and apply default control mappings for them. This will be hit and miss, so as you have discovered, often the main analogue axes (pitch, roll, maybe throttle) will be correct but the button mappings will often be wrong. You need to go through each control one by one and map them to the correct things. You do this in the Options/Settings/Controls screen, and there are separate tabs for analogue axes, joystick buttons and keystrokes. The Honeycomb Configurator program lets you map the controls in a different place (an external program) and somehow inserts these mapping into FSX, which for now is just going to be confusing. This is why I suggest you figure it out using the default way to program controls first. There should be detailed instructions on this in the Help Centre, available from the FSX main screen. You will find that there are certain things you can't program directly from FSX. These include (from memory) the three right-most positions of the Magneto switch on the yoke, and also the black switches on the quadrant. This is because FSX uses an older way of interfacing to joysticks that limits the number of buttons to 32. You will also not be able to use the two rotary knobs on the quadrant for controlling the autopilot, as this needs functionality that isn't built into FSX. (This is one of the reasons you will eventually need to figure out the Honeycomb program, or use an alternative way such as FSUIPC or SPAD.neXt. But don't go looking for those now or you'll really get confused!) And, of coruse, you won't get lights on the autopilot or annunciator displays on the quadrant without the Honeycomb software. You will be able to program the autopilot buttons just fine, but it may take a bit of head-scratching to decide what to map them to. See if any of that helps for now...

The support forum is here. You will find a lot of chatter about this in there.