phillroath

There is a utility that lets you set the spot view distance for each aircraft. Simple and very easy to use. Just click the link below and download the utility. http://www.fsdeveloper.com/wiki/index.php?title=RADItor Phill

Thank you, that's exactly the information I was looking for. Phill

First two replys to the OP seems to be about "themes" and importing real weather. However, the original question was how is the weather displayed in Prepar3d? How do low clouds look in hill or mountain terrain? Is there any amprovement from the default FSX weather graphics? This is something I would like to know. Thanks, Phill

Click on FORUMS and you'll find it there... Phill

Not sure if this would help, but I use DXTBMP to convert all the DDS files. Just load and save but make sure the "save MIPs" box is checked. I have shimmer problems both external and in the VC but after I save with MIPs all is well. I believe there is a method to do a batch conversion but I just don't use it. YMMV Phill

JustFlight has 737-100/200 under development - no release date yet.http://www.justflight.com/developProduct.asp?pid=865#

Look at MAY 2011 set, screenshot number 1 - that's an RV7? I believe that's the one in your shots.PhillEdit update: Looks like the RV-7A because it has the nosewheel.

Yep - did all that. Model shows fine in display but is gone in FSX.Forgot to mention previously, from spot view the navigation lights and beacons can be seen. They appear to be floating in air.

Gave it a try, but both the virtual cockpit and the external models are invisible. Only thing that shows is the 2D panel. Any idea what could cause this? if no answer I can just remove it with no loss.Thanks, PhillSystem: i7-2600 @3.40 GHz - 64 Bit OS - 8GB Mem - GT 420 1 GB mem and DirectX 11.0 capable

Don't know how familiar you are with the aircraft.cfg file but there is an edit that can help. What I did was to add a SMOKE section to the config file where I can activate the vclight separate from the panels light switch. Also needed to comment out the normal vclight found in the LIGHTS section. Here is what I have for the POSKY 737-600 using the default 737-800 virtual cockpit. With this setup I can just get the night lighting without the overbright lights and in addition, during the daytime just pressing the "i" key (normal for smoke) I get a much brighter cockpit for day flight. Works for me. Here's an example from my POSKY 736... [Views]eyepoint = 42.9, -1.34, 2.05 //(feet) longitudinal, lateral, vertical distance from reference datum [sMOKESYSTEM]smoke.0 = 42.9, -1.55, 1.9, fx_vclighth //Add vc lights for day usesmoke.1 = 42.9, 0.0, 2.9, fx_vclighth //Add vc lights for day use [LIGHTS] //Types: 1=beacon, 2=strobe, 3=navigation, 4=cockpit, 5=landing, 6=taxi, 7=recognition, 8=wing, 9=logolight.1 = 2, -49.500, 0.000, 7.000, fx_strobeh // Tail Strobe Lightlight.2 = 2, 1.70, 0.00, -4.90, fx_beaconb ,light.3 = 1, 9.10, 0.40, 9.55, fx_beaconh ,//light.4 = 4, 47.60, 0.00, 3.00, fx_vclighth , Hope this helps. Phill

Long time back, many had this issue and the answer was NOT intuitive. Look at your DISPLAY settings and set as shown in the attachment and see if that helps.Phill

OK - that makes sense. Guess I'm one of the rare ones, I load a new flight sim and see how much I can maximize it and then start to decide if that's good, or do I spend a little of my kids inheritance and get the latest in computers.I agree that those who keep an older system going like me should not complain if/when the new does not give super duper performance out of the box. Phill

I've read this several times and am curious. Are you saying it will make you happy for folks to be disappointed? Perhaps I did not read this right, and if so, I apologize. I hope Flight will run on XP even if I don't get all the bells and whistles. I look forward to this as to all of them.My first was some twenty five years back and over the years each release has brought me something new. My current computer is doing just fine for normal uses and runs FSX with many sliders way to the right. If it gets me some improvement and I can crank up the weather (now I really get low FPS with heavy weather) I will be happy.PhillPS - I may have fifteen years or only a couple of years left, so yes I hope it's released soon. :(

UPDATE: As of today, I am no longer getting the attempted file downloads and the Facebook links are still there so my "guess" was wrong. Don't know what happened but yesterday had the problem and today it's gone. BTW, I am using IE7 with XP (and all current updates from MS).Phill

Sim-Outhouse had the same problem in every forum and thread. They found it was links to Facebook and the admin removed all links to Facebook from their website and today that popup is no longer there. Probably the same here...Philledit: Just noticed the two Facebook links at the bottom of the page.

As I said above, I use fly the AOA with approach speeds of 135 KIAS and it works every time for me. I don't have pedals, just a joy stick button, but I still land and brake with no more ground loops.The raising of the realism settings worked for me and for others. It is a simple thing to try and I hope the OP will try it. This is a fine aircraft and a real joy to use.Phill Umberto,Little off topic but just wanted to say your VC on this aircraft made the cost of acceleration worth every penny (at least for me) so thank you for a fine product.Phill

Tom,Lot's of us had that exact problem and a very simple fix was found and has been posted many times but it's usually ignored. When I was getting the un-realistic ground loops my simulation Realism was set to MINIMUM settings. At the advice of someone, I moved it up to a MID range setting and then it worked. Still have to be careful and watch what I'm doing but there is no FA-18 that requires 10,000 foot runways. It is so simple to test. Go to your realism settings and move them up. If it does no good, then set them back. I have told this to several FA-18 users and in every case it helped them. Just try it once. A few seconds to determine if it helps you or not.I like to use the AOA indicators to the left of the HUD. With flaps and gear down I usually approach at about 135 KIAS (keep the center light on) and as I cross the threshold deploy speed brakes. Touchdown for me is less than 120 KIAS and ease the nose down and then apply brakes. No tapping needed for me and just keep the nose lined up on the centerline and usually take the first exit.I regularly fly into airports with 5,000 ft runways and take an early exit. PhillPS - it is so simple to try: REALISM SETTINGS TO MID OR HIGHER.Edit to add link to FA-18 support: http://www.fsdreamteam.com/forum/index.php...1&board=4.0

Looks like a recent change to the defaults. I went to My Controls and under OPTIONS clicked the Board Settings. Changed the "Number of topics to show for each forum page" from default to 25 and now that's what I get.Phill LOL! You beat me to it by what appears to be seconds. :( Phill

I have a work around for you, but not everyone likes what I do. I use the SMOKE system to activate the old vclight fx files via the "i" keyboard assignment. Here are some examples but be sure to backup your original aircraft.cfg files first!This shows how one may get daytime VC lights and retain the night VC lights. After inserting the smokesystem (and make sure the VC lights are commented out under the LIGHTS section), then by using the "i" key in the daytime you get good VC lights. At night the Shift-L controls panel lights but both on are super bright, so just toggle the "i" key again to use only the night system. This way you get the best of both worlds. These are the six aircraft I've done this for.Goose Gruman, C206B Grand Caravan, Default B737-800, Default C172, Default Douglas DC3, and Maule M7 260C=============== Goose Gruman =====================[Views]eyepoint = -0.9, -1.35, 2.95 //Longitudinal, Lateral, Vertical (feet)[SMOKESYSTEM]smoke.0 = -0.9, -1.35, 2.95, fx_vclighth //Add vc lights for day use[LIGHTS]//Types: 1=beacon, 2=strobe, 3=navigation, 4=cockpit, 5=landinglight.5 = 1, -15.6, -0.26, 4.4, fx_beacon ,//light.7 = 4, 1.60, 0.00, 2.70, fx_vclight,================== C206B Grand Caravan =======================[Views]eyepoint = -12.5, -1.2, 2.19 //(feet) longitudinal, lateral, vertical distance from reference datum[SMOKESYSTEM]//smoke.0 = -10.5, 0.00, 1.19, fx_vclighth //Add vc lights for day usesmoke.0 = -12.5, -1.2, 2.19, fx_vclighth //Add vc lights for day use[LIGHTS]//Types: 1=beacon, 2=strobe, 3=navigation, 4=cockpit light.0 = 3, -16.72, -25.80, 3.85, fx_navredhlight.1 = 3, -16.28, 25.80, 3.85, fx_navgrehlight.2 = 3, -42.28, 0.00, 2.12, fx_navwhihlight.3 = 2, -16.90, -25.90, 3.85, fx_strobehlight.4 = 2, -16.45, 25.90, 3.85, fx_strobehlight.5 = 1, -40.10, 0.00, 10.01, fx_beaconh//light.6 = 4, -11.61, 0.00, 0.98, fx_vclight================ Default B737-800 =========================[Views]//eyepoint = 48.2, -1.55, 1.9 //(feet) longitudinal, lateral, vertical distance from reference datumeyepoint = 48.2, -1.20, 1.9[SMOKESYSTEM]//smoke.0 = 47.60, 0.00, 3.00, fx_vclighth //Add vc lights for day usesmoke.0 = 48.2, 0.00, 1.9, fx_vclighth //Add vc lights for day use[LIGHTS] //Types: 1=beacon, 2=strobe, 3=navigation, 4=cockpit, 5=landinglight.0 = 3, -24.20, -56.60, 3.90, fx_navredm ,light.1 = 3, -24.20, 56.60, 3.90, fx_navgrem ,light.2 = 2, -71.32, 0.00, 5.92, fx_strobeh ,light.3 = 2, -25.00, -57.20, 4.20, fx_strobe ,light.4 = 2, -25.00, 57.20, 4.20, fx_strobe ,light.5 = 2, -7.55, 0.00, -5.50, fx_beaconb ,light.6 = 1, 2.00, 0.00, 8.70, fx_beaconh ,//light.7 = 4, 47.60, 0.00, 3.00, fx_vclighth ,light.8 = 3, -29.50, -56.60, 3.70, fx_navwhih ,light.9 = 3, -29.50, 56.60, 3.70, fx_navwhih ,================= Default C172 =====================[Views]eyepoint= -3.95, -0.85, 1.9 //(feet) longitudinal, lateral, vertical distance from reference datum[SMOKESYSTEM]smoke.0 = -2.27, 0.00, 1.45, fx_vclighth //Add vc lights for day use[LIGHTS]//Types: 1=beacon, 2=strobe, 3=navigation, 4=cockpitlight.0 = 3, -2.76, -18.11, 2.97, fx_navredlight.1 = 3, -2.78, 18.11, 2.95, fx_navgrelight.2 = 2, -3.13, -18.31, 2.95, fx_strobelight.3 = 2, -3.11, 18.31, 2.95, fx_strobelight.4 = 1, -20.51, 0.00, 6.20, fx_beacon//light.5 = 4, -2.27, 0.00, 1.45, fx_vclight=================== Default Douglas DC3 ======================[Views]eyepoint = -6.495, -0.8, 3.25 //was 3.32//eyepoint = -6.495, -1.4, 3.26 //-6.495, -0.8, 3.25[SMOKESYSTEM]smoke.0 = -6.50, 0.00, 4.80, fx_vclighth //Add vc lights for day use[LIGHTS]//Types: 1=beacon, 2=strobe, 3=navigation, 4=cockpit, 5=landinglight.0 = 3, -27.20, -46.30, 0.65, fx_navredm ,light.1 = 3, -27.20, 46.30, 0.65, fx_navgrem ,light.2 = 3, -64.00, 0.00, 2.72, fx_navwhi ,light.3 = 1, -36.80, 0.00, 6.25, fx_beaconh ,//light.4 = 4, -6.50, 0.00, 4.80, fx_vclighth,light.5 = 4, -33.00, 0.00, 4.20, fx_vclighth,==================== Maule M7 260C ===========================[Views]eyepoint= -2.0, -0.75, 1.4 //(feet) longitudinal, lateral, vertical distance from reference datum[SMOKESYSTEM]smoke.0 = -2.24, 0.00, 2.20, fx_vclighth //Add vc lights for day use[LIGHTS]//Types: 1=beacon, 2=strobe, 3=navigation, 4=cockpit light.0 = 3, -1.23, -16.56, 2.68, fx_navredlight.1 = 3, -1.23, 16.56, 2.68, fx_navgrelight.2 = 3, -17.05, 0.00, 4.45, fx_navwhilight.3 = 2, -1.23, -16.56, 2.68, fx_strobelight.4 = 2, -1.23, 16.56, 2.68, fx_strobe//light.5 = 4, -2.24, 0.00, 2.20, fx_vclightWARNING! If you use this method, you loose the "smoke" capability, so it's just a trade off. It's a choice you have to make.Phill

I just loaded the Maule at EGPO and there are two approaches, LOC 18 and LOC 36, both on 110.90. That means a localizer only approach with no glide slope. Went to rnwy 18 and with slew checked and it's working OK. Did the same for rnwy 36 and it is also working.Phill

Yes - square brackets. Here is my SF-86 entry.[GPWS]max_warning_height = -10000No other entries needed.Phill

Here's a thread showing what to do. The GPWS lines are not in most aircraft.cfg files and can be added to the bottom of any aircraft. Then modify the line, for example make the following change:max_warning_height = -10000 <== the negative number disables it.http://forums.avsim.net/dcboard.php?az=sho...42213&mode=fullPhill

There is a known logbook corruption failure that will cause the exact symptoms you are describing. There is a utility that will correct it and allow you to load FSX again. Link below.http://library.avsim.net/esearch.php?DLID=...hor=&CatID=rootPhillPS - if this corrects it, it had nothing to do with alacrity.

>tell-fs Guys, too many people have made this mistake.>Could you please consider putting all templates in a specific>Template directory so as to avoid confusion in the future?>>Best regards.>>LuisLuis is so correct! This would be a great improvement in future releases. I second the motion.Phill

>Yea I to would like to have the default FSX VC clickable on>the posky 737, yes it is only the default VC but its better>than nothing on such on a great model.>>Anyone got any idea on how to get it clickable?>I have the POSKY 600 merged with the 738 VC and it's all clickable. The secret is in position. For example, when looking at the center console could I not tune the radios. But with a zoom in, they started working. I then opened the aircraft.cfg file and modified the camera x,y,z position to get the initial view closer.When too far away, there are walls, panels, etc... that are not visible to you but prevent click functions. That's the best I can say. Oh, and anytime you change the eyepoint line in the aircraft.cfg, odds are the various camera views will need to be readjusted.Phill