RichardW

I posted here http://forum.avsim.net/topic/402405-facetracknoir/ My initial enthusiasm has been tempered by some erratic behavior (possibly changes in the ambient lighting that need investigating). So I went back to TrackIR to make sure nothing else was going on, and haven't had a chance to get back to FaceTracknoIR. Richard

It seems to work just like TrackIR. I'm using version 1.6 and the Fake TrackIR protocol. The OpusFSX window that shows the connection to TrackIR shows exactly the same text with FaceTrackNoIR except that it finds the NP dll in the FTNoIR directory and the NP software is recorded as version 4.09 rather than 5.00. Time, which I'm out of for a few days, will tell. Richard

Just to note that I've installed FaceTrackNoIR ( http://facetracknoir.sourceforge.net/home/default.htm ) and so far, it works fine with Live Camera. Haven't yet explored the full parameter space, but it does seem to be a possible replacement for TrackIR, especially if you haven't purchased TrackIR but do have a web cam. The software is free (you can donate, of course). Richard

See http://forum.avsim.n...et-setup-guide/ for USB setup info.

If running Windows 7, "SnippingTool.exe" is available. You can make rectangular snips, window snips, full screen, and even free form snips.

Check out Opus http://www.opussoftware.co.uk/opusfsi.htm . A great deal of effort has gone into dealing with MSFS "notoriously bad" winds. ANd you get proper winds aloft and should you be flying from where you live, the weather in the simulator will match that out your window. Richard

If you are using the ATC within FSX, then you'll going to find all sorts of things wrong aside from your current problems. Take a look at PRO-ATC/X at http://www.pointsoftware.de. It costs a bit but these sorts of problems are being addressed by this excellent piece of software. Richard

When you create a view, you have the opportunity to assign a joystick or a keypress to be the command to activate the view while flying. So use whatever keypress you are having FSUIPC send to FSX as the keypress you assign when creating the view in Opus. Conceptually, your activation of the joystick is caught by FSUIPC which throws it away and instead sends a keystroke to FSX. Next in line, Opus grabs that keystroke and decides if it is a command to activate one of the views you've built. If it is, the view is changed to the relevant view. If not, the keystroke is sent on to FSX which does something with it if it is in the list of keystrokes (settings>controls>buttons (or whatever it's called)). If it's in the list, the action is taken. If not, nothing is done. The keystroke is discarded. Richard

What I wrote Kattz was: I've mapped my Saitek hat switch to views in Opus via FSUIPC. Inside FSX, bring up FSUIPC and click on the buttons/joystick tab. move the hat switch to one position and release. You should see a joystick name and switch number in the center boxes. If not, click on clear or reset (don't have it right in front of me), then again. When the hat switch is seen by FSUIPC, assign a key stroke of your choice (I use crtl-shift-0, ctrl-shift 1, etc) to the hat switch and FSUIPC will send this to FSX each time. You don't want repeat or release set. Same with the other positions. THen use those in OPUS to associate a view with a key stroke. In FSX, be sure under settings>controls that the Saitek hat switches are not assigned to anything. You don't want any conflicts with what FSUIPC will send to FSX. Richard

For a simple start, you could use OpusFSX and its Live Camera facility to drive one or more slave computers whose sole function is to provide the out the window views. Autogen and clouds might not be completely consistent if using multiple slave computers. 2D undocked windows on the main machine could provide the various cockpit displays. It's not ProSim737 but it's inexpensive if you have an extra machine in the closet and why wouldn't you use Opus for your weather anyway<g>?

3 per second? FSUIPC only saves at best once per second (if I recall properly). But if FSUIPC autosave is on, then you probably need to add some lines to the fsuipc.ini file in the autosave section or the panel states will accumulate without end. I have AlsoManage1=PMDG\PMDG 737 NGX\PanelState\*.FLT.sav AlsoManage2=PMDG\PMDG 737 NGX\PanelState\*.FLT.0.rte AlsoManage3=PMDG\PMDG 737 NGX\PanelState\*.0.rte AlsoManage4=PMDG\PMDG 737 NGX\PanelState\*.FLT.fmc Regarding the two .rte entries, I was having some trouble and once it all started working, I never went back to determine if I needed both.

I have the same problem. What I did was use FSUIPC to convert the hat switch data to keystrokes. ctrl+shift+0 through ctrl+shift+8 are unassigned in FSX and I used some of those as the keystrokes to trigger Live Camera views. A bit of a kludge, perhaps, but good enough for now.

the SDK does not install when you do the usual install of FSX. You have to find the SDK directory on Disk 1 (as I recall, it's in the root directory of the dvd .. just poke about with Windows explorer), go into that directory and then execute setup. You can determine which rev of the software you have via the control panel > Programs if it wasn't made obvious during the install. Then consult the web site I mentioned before to determine which service packs you need, download them, and follow the instructions on that web page. Richard

You need to have the FSX SDK software installed; that software is available on the FSX Disk 1 Deluxe or Gold or Acceleration packages. It's not included in Standard. For more information on the steps to go through to install the SDK and the necessary SP1/SP2 patches, see http://www.fsdeveloper.com/wiki/index.php?title=SDK_Installation_%28FSX%29 . I wish I had mentioned all this when I posted, but I'd gone through this dance some time ago and had completely forgotten about it. Richard

You might try the free Airport Design Editor http://www.airportdesigneditor.co.uk/ to change the frequency. File > Open Stock airport, KSAN, double click, go to Lists > Navaids, select ILS Runway 09, change the frequency. Save the airport for latter fiddling. Compile it to create a .bgl file. Copy that file into FSX\addon scenery or where ever you put such things. FSX should note the difference on startup if you use the addon scenery folder. Otherwise, you need to go into settings, scenery and give FSX a hint. I'm not sure how to change the heading to 93 ... I ought to read the manual some day! Richard

The problem was that I wanted to follow the tutorial but on initial startup of my new 737, all I had was pretty much cold and dark. If I understand you, I would have to know how to go from cold & dark to the state PMDG expects for the start of the tutorial and then save that state. Not plausible at my level of understanding (yet). Much better, in this case, to have FSX so set up that the state PMDG expects just happens.

PMDG support solved problem. ... In "My Documents/Flight Simulator X", remove the "Previous Flight" files.

Trying to follow the tutorial. Once the initialization finishes (green strip disappears), multiple trouble lights ... bat discharge, low pressure, "elec" and "fuel" on master display, engines spool down to zero. It all acts like it wants to initialize into some state where the engines are not running and so shuts down after a few seconds. I haven't changed any options in the FMC pages. I have installed a couple of liveries, and that's all. FSUIPC ini file removed but that didn't help. Should I just reinstall, or is there something else to look for? Feeling dumb! Richard