cap10jaf

Hi Folks, Maybe someone can help me understand what I'm looking for. You have convinced me to buy a 4K TV rather than a monitor. My situation: Saving-up $ as I go to buy one piece at a time and I did the i6700K/GTX1080 build. System will be used for P3D only. Not as a TV at all. No other games or video/picture editing. My desk can only handle up to a 43" display. My question: I understand for the most part what makes one computer monitor more expensive than another, but what do I gain for my application when buying a $650 43" Sony XBR43X800D vs. a $330 43" Hitachi LU43V809 ? If anyone has a different recommendation I would love to hear it as well. Thank you for the help, Greg

Thank you Gary. I was afraid Nick's bible was not up to date with M.2 and such. You really summed it up perfectly. If one large SSD is the best option I'll do that. I appreciate your input Kylan! I'm over budget already, but choose to buy in stages to get a good result. Vortex and Luke, Thanks for the all the information. I came to the right place to ask for help. You guys are the best. I appreciate your help. Greg

Greetings friends, I took the plunge and I'm leaving FS9 and 2D panel flying behind. I've done hours of reading and video watching to build a 2016 machine within my budget and I need some help with the last part, selecting and setting-up the drive/drives. This machine is exclusively for flight simulation and I want to run P3D V3+ and try X Plane. I read a theory about installing two different drives and where to put the OS and where to put the sims, but I cannot seem to find that discussion again. So far I have: i6700K Skylake Corsair H110i GTX ASUS Z170A Ripjaws V (2x8GB) DDR4 3200 EVGA 220-G2-0850-XR power supply Corsair Airflow 750D case and waiting for: EVGA GTX 1080 Non-reference Can anyone please offer some advice or provide a link on what drive or drives a best suited for this type of build and where to install the OS and sims? Thank you very much, Greg

Don't forget... http://www.frfstudio.net/downloads.html

Thank you both for the info. I'm fairly certain you've nailed it. I checked my CPU usage while flying and 99% is the lowest number I see! With FS9, FSACARS, FSINN, VATSPY and Firefox running this old system is tapping out. My WILCO planes seem to be the only ones that turn back to the previous waypoint, but it seems that's exactly what is happening. This old machine has been fun, and I have put countless hours into scenery and aircraft add-ons but I think I'm ready to upgrade. Now I need to decide if it's worth building an FSX/P3D rig or just a better FS9 version. Thanks again Gents, Greg D.

Alrighty then, This sounds promising! I'm glad I asked before giving up. I'll do some research an see what I find, then report back with the test results. Thank you very much, Greg Hi and thanks for the reply. The only problem with testing that is that I fly in windowed mode (better fps is what I was told). Curious what you are wanting to test though. Thank you, Greg

Greetings, I'm ready to give up. I have searched everywhere and tried everthing I know. Can some FS wizard out there diagnose this problem? This is only happening with three planes. Wilco 737, Wilco Regional Jets(ERJ-135 ECT), and Wilco Ejets (E-170 ect). I have contacted Wilco support and they claim all issues are resolved. When flying online (Vatsim), in LNAV mode the plane suddenly enters a full banking turn off course. Sometimes I go a whole flight without this happening, but it's rare. I was supecting real world wind shifts for awhile. I'm using REX and yesterday I purchased a registered copy of FSUIPC after reading about the smooth weather function. Tested it last night and after 20 minutes, hard banking turn to the right. I've tried coping the Autopilot features in the aircraft.cfg file (nav_proportional_control ect) from other planes. Didn't help. Another thing that is curious, it seems to happen much more frequently when I'm not watching flight sim. If I go to a website to download an approach plate, when I go back to the sim it's banking off course. This makes me think it's my crappy rig (which is old: Pent 4 3.2 ghz/Nvidia 1G GPU/ 4G RAM) but why does it only do this with WILCO. Never with iFly, LSH, PMDG, Dreamfleat 727 which all work fine? Any thoughts? Thank you in advance, Greg

Greetings all, Is the FFS Saab available to purchase anywhere? Thank you, GD

Merge the PSS with the Project Airbus model and don't look back.

Here are a few tips FWIW. VATSIM UNICOM texts are on 122.80 should include who/what you are, where you are, and what you are doing. Your callsign is automatic generated when you send a text, so no need to retype it. If you are using a smaller airport with other airports nearby use the City name and the airport ID. To a pilot holding short for takeoff, a Learjet or C152 on a ten mile final are not the same so say type aircraft. Keep in mind that other pilots don't always know where, let's say "WORMS" intersection is so give distance and direction info. Include Departure/Arrival ID and Approach type when applicable. Sample: AAY1066: Orlando KSFB traffic, type MD83 t/o RWY9L Northwest Departure to WORMS (SFB4) AAL1411: KMCO traffic, type A320 ~15nm Southwest at UNITY visual approach RWY35L (MINEE5) I like to type in notepad before pushback and decent, then copy/paste as it gets busy during takeoffs and landings. Hope that helps. GD

FSInn is worth the trouble. The mini control panel is my favorite part. You can hide it in the bottom corner of your screen and have instant access to connection status, transponder modes, nearby ATC online, adjustable radar range, and weather metars via individual pop-up windows. It takes a little more time to learn, but works great for me. GD P.S. It also allows you to fly shared cockpit in the LSH Maddog with one radar target for ATC.

I prefer the PSS merged with the Project Airbus models. The merges are available in the Avsim library. GD

So Trevor, Just so I understand, was the problem only with new aircraft you installed, or all aircraft? My SEE_SELF is at 1, and I only have the problem you described when I fly my Electra II. All other planes are normal. Thanks for the time, GD

I have an Electra II that drove me to drink with the same problem. I've been told it's a model issue. I don't think it can be fixed without a major rework of the aircraft model. I'll be checking back to see if you find a way. Good luck... GD

Did anyone ever find a way to update the Navdata on this plane? I tried the iFly B737 data but it doesn't work. Thanks, GD

Thank You! I'll give it a try.

What tool do you mean? Link please?? Thank you

Any luck?

Maybe wrong IP address then. I'm not at home so I don't know which one I'm using. I'll check in a few hours if you want. As far as Squawk box goes, default unicom frequency on VATSIM is 122.80, and text only with Squawkbox. You need to be in range of an online controller to listen (use VATSPY). When you are in range, you will see their frequency. When you tune it in, you will get a tone and enable text & voice both.

When you open the FSINN MCP (Main Control Panel) are you clicking in the VATSIM box in the left column? The box should turn green and you will hear a double chime. You will also get a chat message about connecting to VATSIM servers. GD

Hi HW, The night lighting can be easily edited. Open the panel.cfg with notepad and scroll to the bottom. Look for this enrty: Day=255,255,255 Night=100,99,72 Luminous=220,220,220 The numbers in "Night=100,99,72" are RGB (Red, Green, Blue) values: http://www.rapidtables.com/web/color/RGB_Color.htm Experiment with darker colors by changing values and saving (I use a dark blue on my version). You can test changes without restarting flight simulator by switching to the default cessna, then back to the Airbus. I've found that the problem with the Project Airbus landing and taxi lights is that they are pointing down at the ground. I don't know how to tilt the taxi lights, but the landing lights can be tilted up by doing this: First, turn off "Num Lock" on your keyboard. Now press "Shift+Ctrl+8" and you will see the lights flood a much larger area. Hope that helps, GD

Is this the order you're using? I use FSINN too, but I connect to the network, fill out flightplan then submit. cap10jaf

I'm not the person who will answer this correctly, but based on a simular issue I experienced I'm wondering if you have a registered copy of FSUIPC installed? The Tinmouse II FAQ section says it's now required. I don't have it, but only experience trouble after doing a turn-around when I leave power and APU running. If I shut off all power, things go back to normal. GD

Sorry to bump an old thread but I was searching for the same answer and want to share what I've found. Open the PMDG 737NG panel.cfg and scroll down to this: //-------------------------------------------------------- [Window01] // PMDG_MAIN_PANEL file=..\panel\737NG_Main_Background_1280.bmp file_1024=..\panel\737NG_Main_Background_1280.bmp size_mm=1280,960 position=7 visible=1 ident=20 window_size= 1.000, 1.000 window_pos= 0.000, 0.000 gauge00=PMDG_737NG_Main!MainBackLight,0,0,1280,960,MAIN gauge01=PMDG_737NG_Main!GearLever, 1198,635,83,223 gauge02=PMDG_737NG_Main!EFISDisplay, 50,670,250,250,PFD 1 gauge03=PMDG_737NG_Main!EFISDisplay, 388,670,250,250,ND 1 gauge04=PMDG_737NG_Main!EFISDisplay, 900,670,250,250,EICAS 1 gauge05=PMDG_737NG_Main!EFIS,369,398,181,113 gauge06=PMDG_737NG_Main!GearLights,1199,554,78,80 gauge07=PMDG_737NG_Main!FlapsDial,1114,549,71,74 gauge08=PMDG_737NG_Main!FlapsLights,1106,625,88,19 gauge09=PMDG_737NG_Main!FlapsReliefLight,1126,526,39,16 gauge10=PMDG_737NG_Main!MCP,550,383,730,130,MAIN gauge11=PMDG_737NG_Main!N1_Set,881,544,35,31 gauge12=PMDG_737NG_Main!SpdRef,971,545,35,31 gauge13=PMDG_737NG_Main!FuelFlow,899,597,65,60 gauge14=PMDG_737NG_Main!AutoBrakes,1015,551,99,74 gauge15=PMDG_737NG_Main!DSP, 268,558,170,86 gauge16=PMDG_737NG_Main!TestPanel,478,548,128,98 gauge17=PMDG_737NG_Main!MasterCaution, 140,431,216,66 gauge18=PMDG_737NG_Main!FireWarning, 89,431,50,66 gauge19=PMDG_737NG_Main!SbyADI, 683,563,166,122 gauge20=PMDG_737NG_Main!SbyAltimeter, 683,685,166,122 gauge21=PMDG_737NG_Main!SbyRMI, 683,807,166,153 gauge22=PMDG_737NG_Main!Whiskey, 1019,66,48,31 gauge23=PMDG_737NG_Main!MFD, 966,596,50,45 gauge24=PMDG_737NG_Main!PanelSwitcher, 41,617,221,24 gauge25=PMDG_737NG_Main!AutoBrakesDisarm,1052,531,41,15 Disable "gauge00=PMDG_737NG_Main!MainBackLight,0,0,1280,960,MAIN" by entering two forward slashes like this: //gauge00=PMDG_737NG_Main!MainBackLight,0,0,1280,960,MAIN Do the same for VC panel .cfg as well. Here are my results. Before: After: Just trying to help... GD

Just a final word for future readers of this thread looking for solutions. The two things that really jumped out were the fact that my FS9.CFG had settings for both old and new video cards. The ATI card info was way down the page near [OLD MODULES]. The other was my TEXTURE_BANDWIDTH_MULT=xxx setting. Mine was set in the high 200s rather than 80. Greg