carthorse

Thanks for looking at this!

The problem isn't just a cloud layer thickness. It is also with visibility. See my post above with images. SMP fails to limit forward visibility. This is a problem if you are simulating instrument conditions. You shouldn't be able to see something a mile away when the visibility is reporting 1/4sm.

Hi Mike, Same issue i've had with xp10 Unfortunately, i just turn skymaxx off if i want to experience a good foggy approach.

So, If I load up at an airport showing 1/4 mile visibility, it seems pretty realistic both with and without skymaxx. However, the default weather definately is less transparent than Skymaxx. The two screenshots below show 1/4sm Fog. What I've noticed is that when flying into an airport the weather doesn't appear realistic with Skymaxx, but during departure it is usually representative, as in this case. Maybe it takes a while for weather to be updated when flying enroute? Or it is updating from a location other than my destination? Current Weaher: PAKN 162054Z 00000KT 1/2SM FG VV003 01/01 A2970 RMK AO2 SLP058 I3001 T00060006 51012 RVRNO

Here are my settings. I've also tried HD Cloud Puffs and Dense Particles. If nothing else, i'd love to see the visibility accurately depicted: If the METAR says "1/2SM visibility", i'd love to not see anything till i'm close to half a mile. The standard x-plane weather does pretty well at this. I do not have real weather connector. Maybe this is part of my problem?

I've been noticing the same thing. For the IFR experience in general, If I turn off skymaxx, the default xplane weather does a better job at simulating lower clouds and visibility. I don't know if it makes a difference, but i'm letting xsquawkbox/vatsim drive the weather. If I want nice looking clouds enroute, I turn on skymaxx, if I want challenging weather during an instrument approach, i use default x-plane weather. I'd love to know if i'm doing something wrong. I've tried all of the settings I could think of within skymaxx.

I found this to be a conflict with using the latest version of xSquawkBox (1.3.3). I reverted to 1.2 and it solved my problem. I was using XP 10.51 and 1.7 of the CRJ.

That's pretty funny haha

thanks!

Can they be installed in paralell?

Excuse my ignorance, since it says 64 bit only -- after updating to 1.2 i will lose 32bit mode functionality, correct?

Are you guys running 32bit or 64bit xp when you experience this prob?

Thanks for looking at this Goran. Eagle: i've also noticed that you can lift the tail as if it were a cub. I flew on a DC-3 for a day once and i have to say there is no way you could lift the tail below 60kts. Also, when landing as the tail comes down, it's almost impossible to break so hard that you tip over on your nose. Also Typical approaches were made with 21" manifold 2000rpm easily maintaining about 80 to 90 kts with full flaps and gear down. Hope any of this helps, i don't expect the DC-3 to be exactly like the real thing. It's a pleasure to fly as it is, but the ground handling is pretty bad when you can't taxi at all on rough surfaces. Thanks!

Hi Eaglewing, I pretty much just don't use flaps. 1. with flaps down, there is so much drag you can hardly maintain approach speed with tons of power 2. with flaps down, it takes much more power to taxi 3. with a load in the plane, it is almost impossible to taxi on a non-paved strip (especially with flaps down). Another thing you can do is takeoff with minimum weight...then start your flight once airborn. But landing is embarassing on vatsim due to this issue.

Thanks for the quick reply Cameron, I used the default 172 to turn up the lighting, then switched back. No Change. I also mapped keys to "instrument lights up/down" and "panel lights up/down" and no change. I've tried both with HDR lighting turned on and off. What ended up solving the problem was uninstalling the aircraft and reinstalling. Prior to the reinstall, i did not have any serious errors in the log.txt file. Cheers!

Can someone help me understand why i can't see the radio stack and gps? I can see the numbers but they are blacked out and very very hard to read. XP 10.11 Win 7 64bit

Great! Thanks!

Thanks for the explanation, that makes sense to me too. If it helps any, when i flew on a DC-3 i took note of some of the performance numbers: Aircraft config Full Main tanks + 100gal in each aux tank. 6000lbs of cargo 1200hp twin wasp engines Climb Power: 35" manifold, 2300rpm Speed: 115 kts Rate of Climb: 400fpm Takeoff Power: 41" manifold - full RPM (36" used on longer runways) Distance: 1500 ft (we actually had 8000lbs payload for this takeoff) Surface: compact dirt Cruise Power: 30" manifold - 2200 RPM Altitude: approx 8,000 ft Speed: 125 kts TAS

I have found that two things play a part in this issue: 1. Flaps 2. gross weight The flaps in this model create a tremendous amount of drag. In fact, when loaded to 25,000lbs or so, i can't even maintain enough airspeed to make the runway at full flaps on a 3 degree glideslope. I have to either apply flaps short final or not at all -- this isn't quite realistic. So when on the ground and you are stuck...raising the flaps actually helps 'unstick' the aircraft and get it rolling -- the reduction is drag helps. 2. the weight of the aircraft has a large effect whether or not i get stuck on the runway. I fly with FSEconomy.com which loads the aircraft for me. I've flown in many different configs from empty to 28,000lbs (military's gross weight allowance). The lighter I am, the easier it is to get rolling -- the heavier, the easier it is to get stuck. Sometimes just one wheel gets stuck. Sometimes both.

Addition info: I have found that when the a/c is first loaded and flown -- selectors are on mains, and have not been moved, it burns only the main tanks. However, if you move the selectors, no matter what tanks i select, it always burns from all 4 tanks. I have experienced a similar behavior before where when u first load an aircraft it defaults to all tanks until you move the selector. Even if the aircraft doesn't have a "both" or "all tanks" position.

Thanks!

Hello, I reported what i thought was an anomolie before, where I didn't think the fuel selectors were working. I was experiencing it again, so i documented it below. Notice that all 4 tanks are losing fuel even though both selectors are on either "Main or Aux". Is it possible that x-plane is letting the fuel crossfeed between AUX and Main tanks? Let me know if there is anything else i can document to help investigate this issue. TEST 1: Mains selected mains selected few min later: TEST2 : AUX SELECTED test started few minutes later:

I have been experiencing a strange behavior where the DC-3 gets hung up on the surface. When this happens it takes 100% power to get it moving. It seems to consistently occurr when you are off of a paved surface. But occasionally when on pavement, it is very difficult to move...or it decelerates very quickly and noses over on landing. Anyone else experience this?

Goran, Sorry, i didn't explain myself very well. I did actually change Low Speed from 40 to 0 and High from 25 to 0 as you did in your tutorial. I had somehow unchecked "castor" on the tailwheel. I can confirm (with foot in mouth) changing the low and high speed to zero has the same effect in x-plane 10 as it does in x-plane 9.

I tested this mod in xp9 and it works great. I tried to implement the same mod in xp10, but some of the parameters are different. I did my best anyway...and i couldn't get the tailwheel to castor no matter what position the tailwheel lock was in. Here are the settings i changed: