airernie

Are the rear speakers set as a separate audio device? If so, you should be able to open vPilot, select Settings -> Audio and specify the source for the 'Output Device'. If the Soundblaster X7 is your only audio device (no internal audio device, etc.). Then it's a all or nothing thing. A more complete description of your current computer, OS, etc. might provide some additional insight. Ernie

Not sure if this is it, but if the airport/navdata on the G1000 doesn't agree with the airport/navdata of the FSX airport you may have the type of issues you describe. Remember, the FSX data is now 12-13 years old. In that time the magnetic heading of the runways, etc. will likely have changed. Depending on how the dates on your G1000 you may want to update the FSX data with something like the freeware FSX/P3D Navaids Update or the payware Navigraph and/or fsAerodata. I don't have Synthetic Vision, so best to wait for a Carenado user to chime in before making a purchasing decision if that's what is ultimately required. Ernie

It's the code that FSUIPC requires to display a VAS counter at the top left of the FSX screen. According to the docs it should work on either the registered and unregistered version. You can do the same thing on the FSUIPC logging tab by entering the appropriate codes in the 'Specific value checks' section of the tab. The code I gave you is just a shortcut. If you prefer not to do it using FSUIPC then there is a small app titled "VAS Monitor" that you can run. There is also one in the AVSIM library. If you have FSUIPC installed then it will create a sub menu entry under Add-ons.

I'm sorry that I can't answer your question. However if you can't get it working and you have Little NavMap, a user uploaded several maps, including the US sectionals that will give you the same ability. They just may not be the most current sectional. See the LNM forum for more info.. Ernie

Everything, except the Xbox 360 controller I use for ChasePlane and that is only defined in ChasePlane.

You won't see REX in the list of weather themes options. Texture direct is a replacement for the FSX cloud textures among others, so Clear skies, Building storms, etc. will use the cloud textures that REX installed versus the default clouds. The textures that are used is the set that you selected in the REX application's Theme option. So you change the 'look', but not weather scenario, by selecting different theme. Typically, replacement weather textures reflect best when used with an add on weather engine, such as Active Sky, FSGRW, etc.

Confused by 'default axis'. Do you have some aircraft using axis defined within FSUIPC and some using axis defined within FSX? IMHO, control axis definitions should be 100% FSUPIC or 100% FSX, but not a mix, I assign each class of aircraft a separate profile in FSUIPC, exp; ASEL, AMEL, iFly_737 ERJ_175-195, QW_757, etc. It may be overkill, but it allows me to assign different functions to an axis without conflict. Ernie

I'm going to make a suggestion for something I do. It may be the placebo effect, but it seems to help recover some memory. Of course, sometimes it also climbs right back up to the old number. I fly in Windowed mode and sometimes during the flight and on especially on approach I will hit the Restore down button which is the middle upper right button. FSX doesn't disappear from view, just reduces the window. I'll leave it that way for a few seconds until FSUIPC increases the VAS number. I then hit the same button, which is now titled the 'Maximize' button to expand FSX. To get the VAS numbers copy the following into fsuipc.ini: [Monitor] Display=5 Monitor0=0,024C,4,0 It may require the registered version of FSUIPC, but there's no harm if copying it into the unregistered version to see if it works. As I said, maybe a placebo effect, but it doesn't hurt to try it and even if it doesn't work you get a nifty VAS monitor at the top left of your FSX window. Good luck, Ernie

I realize that it's doesn't provide any help fixing the bouncing issue, but I do know that the iFly 737 documentation specifically states that it won't function correctly above sim rate 1. It's possible that some of the other add ons have a similar limitation.

Set up for that run tonight, but not able to finish it. Will give it a try tomorrow morning.

This morning I ran a test in my iFly 737-700. Washington X, NY X, and Flightbeam KIAD in addition to the FTX and Ray Smith and payware airports I have installed. Active Sky was enabled, but the clouds weren't real heavy, GSX installed, etc. Ready for takeoff at KJFK 31L according to FSUIPC I was sitting at 660240 remaining VAS. No issues with takeoff, flight or approach. On final to KDCA some of the ground textures or photoreal started loading slowly and I started getting low VAS beeps from FSUIPC. At point of touchdown I got a Windows OOM. Had I used SCE to trim some of my airports or maybe dropped Texture_Load from 2048 to 1024 I have no doubt I would have had a successful landing. BTW, as with Russell I only use FTX Global, Vector, etc. No FTX regions. Ernie

Who the cares what happens with another sim.. this is a FSX forum. Please observe the rules.

I'm not sure there is a simplest way unless you have a friend who can do it for you.. It really isn't hard, but preparation and knowledge is key. Start with research and reading. Especially about FSX SimConnect. There's a tool called SimConnect Config Tool that will help you create the proper entry. The Active Sky documentation has quite a bit of information networking that application to FSX. Create Static IPs for the two computers you want to network. I find it works much better than using names.

My guess would be that the user has to create this information themselves using the 'Aircraft -> New Aircraft Performance' or 'Aircraft -> Collect Performance for Flight'. I don't see, given his workload, that Alex will be generating this information. Of course I could be wrong. He has done some pretty remarkable things with LNM.

The copy of LNM on the FSX PC is necessary because LNM on the client doesn't have access to the FSX scenery files and therefore can't create (aka Load) the database. The database must be created on the FSX PC copy then transferred to the remote copy of LNM. BTW, you don't need to run LNM on the FSX PC while FSX is active. Run LittleNavConnect instead and that should connect to the version on the remote computer. Ernie

Ken, I honestly don't know, but if possible, I would bet that being in Steam would make it whole lot harder than with the standalone version of FSX. A partial solution might be something like SIMstarter, which would allow you to set up different scenarios, such as scenery subsets, etc. Hopefully someone else can provide guidance. Ernie

Would concur. I wear progressive lens and found it difficult enough maintaining focus that I abandoned TrackIR. I might also add that I used to fly real world GA and had similar issues with views out the window. Such that I switched to bifocals while in the air.

Most of the sources I have found online indicate that the LEBB runways are Asphalt. The FSX default LEBB lists runway 10-28 as Asphalt and 12-30 as Concrete. I wonder if 'Oil Treated' is how the authors interpreted 'asphalt'. Ernie

FSX considers Oil Treated Runways as soft. See http://www.simtours.net/runwaysurfaces.php. Ernie

Ray, I think those names are integrated into the map and can't be altered by LNM. At least that is the case with the Open Street maps. Ernie

The subject has been discussed in this forum, so a search should yield some fruit. Just remember, the database has to be created on the computer containing the flight simulator then copied to the networked copy of LNM. The remainder is a pretty straight forward process and the manual covers that.

A hearty +1. I don't go into a north side Chicago bar to hear about how good the White Sox are.

Probably better asked in the P3D forum.

I can say the same about my FSX installation. The tweaking of yesterday isn't necessary with today's systems.

Good to hear that then.. I don't really care about regions, but I do like the land class enhancements to my Global.