Jump to content

Mark Hurst

Registered Users
  • Posts

    438
  • Joined

About Mark Hurst

  • Birthday 09/14/1962

Personal Information

  • Location
    Bedfordshire, UK

Social Profile

  • Homepage
    http://www.youtube.com/user/keysounddotcom

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

Mark Hurst's Achievements

Community Expert

Community Expert (6/7)

  • Dedicated Rare
  • Week One Done
  • One Month Later
  • One Year In
  • Conversation Starter Rare

Recent Badges

10

Reputation

  1. 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.
  2. 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.
  3. 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.
  4. 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.
  5. On the assumption that you haven't already, you will need to install the appropriate driver software from here.
  6. 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.
  7. Try going to options/settings/display and selecting a new value for the full-screen resolution. It likely defaults to 1920x1080.
  8. 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.
  9. 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.
  10. 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.
  11. That version doesn't work on the Steam Edition AFAIK. You will need v1.331.
  12. 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.)
  13. 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.)
  14. 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.
  15. 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).
×
×
  • Create New...