posherid

Hi Bob / Jim,an easy method to find out if the USB hub is giving the time out issue is simply to unplug the USB cable and plug it back in. If the goflight hardware comes back to life then you know it is a "time-out" issue. Note that in my case the hardware is behaving normally as far as speed is concerned, but it dies after a while, either unplug it and replug or restarting the goflight brigde bring them back to life. This affects GF-45,old P8, and GF-166.This issue did not exist in XP (even with hub 2.0), but started with 64-bits OS versions (Vista / Win 7).Patrick

Hi Jim,I had exactly the same issue you describe. It started with Vista 64 and is also present in Win7 (64 bits versions) and is due to the use of USB 2.0 hubs timing out after a while (mostly when the Goflight hardware is not used for a certain period). Only the recent GoFlight hardware are fully compatible with USB 20 hubs in these OS versions.The solution is either only use USB hubs version 1.0 (very rare these days) or when this happens to you, simply exit the goflightbridge program and restart it. You don't need to quit FSX or reboot your PC, the goflight hardwares should be fully functional again.Hope this helps,Patrick (EBBE)

Hi Carl,the fact that you can have network trafic during 3-5 minutes is a proof that your network configuration is good. I'm more inclined to either a possible harware malfunction of the network card (like trafic overflow) or bad network cables loosing the connection after a while.The first test you should do a testing the network with some heavy traffic between the 2 computers (like copying big directories/files) and see if you can maintain the connection active.Another possibility would be a periodic job severing the network activity while it is running (anti-virus scan ?)Have you checked also the systm events log to detect any malfunction ?For your info, my FS pc runs under Vista 64 Ultimate and the WideFS client runs under Windows 2000. No time-out issue ever encountered.PS: as another idea what protocol are you running with widefs ? I'm using the robust TCP/IP protocol (UDP protocol can loose network packets if congested).Patrick

Would you be happy to limit the 30" screens at the max resolution of 1680 x 1050, as this is the max resolution of the TripleHead2Go digital edition ? And what about your graphic card having to deliver 3 * 1920 x 1200 pixels per FPS ? We're far from that fantastic setup, I'm afraid,Patrick

From www.flightsimlabs.com/"This interface allows owners of Engravity's 737 and 747 CDU hardware to interface their CDUs with the PMDG 747-400X Queen of the Skies for Flight Simulator X. Purchaser must already own and have installed an Engravity 747-400 or 737 CDU in order to use this driver. Requires that the user also have installed the PMDG 747-400X for FSX line of products, along with the latest Service pack."A response is needed, thank you.

Could somebody confirm that the FS9 upgrade coming with the FSX version cannot be installed unless the 747 Freight version is previously installed ?Having installed this version (R12) under VISTA-64, the 747 cannot be loaded anymore (FS9 terminates), even when starting first with the Cessna and then selecting the PMDG 747. Before installing R12, it was working without issue. Other version of 737-900 loads normally and so does the FSX version.Also what would be the best method to uninstall version R12 without affecting the other versions (FS9 + FSX) installed ?Thanks in advance,

Hi,it looks to me that the issue you have is that your trying to climb with your cruising speed (most likely above mach .84 and at that speed don't expect miracles. Try to limit your speed to .82 and you'll quickly see the climb rate increasing (in VNAV mode). However at that level, a climb rate around 1000 fpm is not at all abnormal (if you're fully loaded). Typically also the initial flight level will be around FL290 - FL310 and you'll only be able to climb higher after having consumed some fuel (it can take easily 2 hours before you're able to step climb to the next level).

Hi,the solution is dead easy: edit the file scenery.cfg with notepad and delete the erroneous lines (left over from the scenery you removed) and let FS rebuild its indices. Next time it helps if you keep a backup of this file before installing something dubious.

Hi,You'll get nowhere with these complex aircrafts if you do not study the detailed procedures provided. Looks like your FMC initialisation is not complete. And surely you know that there is also a PMDG forum ?When you do that you'll not want to come back to default aircrafts.Always 3 greens.

Hi,this 360 orbit during a SID departure happens to me as well from time to time (in my case a WOBUN2G from EGLL (between BUR and WOBUN), i.e. well after passing the first waypoint (BUR) of the departure.I've the impression that it might be caused by having some fixes defined in the SID with different coordinates than the FMC NAV database.As you, I'm just selecting heading sel mode to go through and resuming LNAV after next waypoint.(see http://forums.avsim.net/dcboard.php?az=sho...ng_type=search)

Hi Jonathan,works perfectly for me since years, just use the right push button as a COM1/COM2 toggle in the goflight setup program.

Hi Jerry,with the current hardware possibilities, there is no way that you could have 3 windows in 3D mode for the left, front, and right views without a severe penalty on FPS.The options you have in my opinion are: - TripleHead2Go with one computer (already a vast improvement to the front view on one monitor), with optionnally the Track-IR software (for changing views); - 3 (or 5) computers connected in a network each one displaying one view with the wideview software (Left, Front, Right) or (Left, Front left, Front, Front right, Right) (website www.wideview.it)Hope this helps.

Hi Jonathan,the solution is dead easy: remove all reference to SID/STAR to runways 05 and 23 in the file EGLL.TXT and you'll be fine. Or better, download a more recent EGLL.TXT file...Patrick,

Hi,for me, I'd rather put it this way: if I could not use the Aerosoft MCP, then I'd have no reason to buy the FSX version... I'd fully happy to stay with the FS9 version.Of course, I'd understand paying for the upgraded version.

Hi Chuck,With Wideview, you need to have a main PC (called wideview server) running FS with all instruments and optionnally the outside main (forward) view and then "n" PC's connected on your LAN (called wideview clients). Each client needs to run its own copy of FS (in slew mode) and receives the FS data from the wideview server PC (via the network) and will have just one/two outside view(s) (different than the other PC's views).Eg with 3 PC's with one outside view each, you can have Left forward + Forward + Right forward views.You can also with powerfull graphic card and PC have 2 independent views for each PC.All the details can be found in the wideview forum :)Hope it helps,Patrick

Hi Alex,have you checked also the the goflight bridge is running (program GFDevFSX.exe)? It get minimised in the task bar. In my case, I've to start it manually before launching FSX.Patrick

Hi,in the WOB2G for EGLL, defined as follows: SID WOB2G RNW 27L KEEP HDG UNTIL 580 KEEP HDG UNTIL RADIAL 121 FROM NAVAID BUR NAVAID BUR NAVAID WOBUNa strange circle appears between BUR and WOBUN.It seems to have been noted already but I do not remember if a solution was found. For the moment I just press on Heading and resume LNAV after WOBUN. Any other solution ?Patrick

Hi,This is explained in the wideview documentation and wideview forum, but basically, you'll need these lines in your panel.cfg :3 MONITORS SETUP WITH WIDEVIEW(Here is my panel file for both the server and client)...[VIEWS] VIEW_FORWARD_DIR=0.0, 0.0, 0.0 VIEW_FORWARD_ZOOM=1.0 VIEW_FORWARD_EYE=0.035, -0.210, -0.05 VIEW_FORWARD_RIGHT_DIR=0.0, 0.0, 45.0 VIEW_FORWARD_Right_ZOOM=1.0 VIEW_FORWARD_RIGHT_EYE=0.0, -0.210, 0.0 VIEW_FORWARD_LEFT_DIR=0.0, 0.0, -45.0 VIEW_FORWARD_LEFT_ZOOM=1.0 VIEW_FORWARD_LEFT_EYE=0.0, -0.210, 0.0...Once you have set up the layout you can save it as a saved flight that you will re-select to start a new flight.Hope it helps.In my setup the server pc has forward view and instruments (on 2 monitors) and the second pc has the right and left views.

Have a look at http://www.simhardware.co.nz/ for AVC tuner add on.Patrick O'Sheridan

Hi Michael,please donwload the latest FSUIPC from Peter Dowson. This has been solved. Alternatively add one line in the FSUIPC.ini file at the section [buttons]: Pollinterval=66This cures it.