Goran_M

I don't have the new one modeled fully yet, but I did model the old one a while ago. PM me if you want it.

Marc, This is far from the place to argue semantics over Gizmo and SASL. Especially for someone who hasn't even purchased the DC-3 These are support forums for us and customers of the DC-3. Seeing as you have not purchased the DC-3, please take this up in the appropriate places should you deem it worthy of your time.

The Aerosoft Airbus is, IIRC, a "lite" version. Javier is making an A320. Knowing Javier and Phillip, if they get the right team together, it'll be a damn good one! http://forums.x-pilo...30-airbus-a320/

To make a concorde for ANY sim is not as simple as some might think. Systems are one thing...and with the exception of the fly-by-wire, they are pretty straight forward when compared to the real challenge in a supersonic aircraft. Engine performance! X Plane can do an excellent job of simulating an engine travelling at subsonic speeds. But, in the real world, when you approach the speed of sound, very unusual things start happening to the engines. Jet engines perform most efficiently at somewhere around Mach 0.7. Each engine of a Concorde has 2 ramps, which are fully automatic, inside the intakes to slow the air down and create a shock wave as the air goes into the engine. X Plane, as far as I know, does not simulate this. Can a developer do this with plug ins? Most likely. But, coupled with the systems, to make an accurate simulation of a Concorde in X Plane would take quite some time (years). I'd still love to do one, and after the 747-200, it's a definite possibility because we can recycle some of the 747-200 code. But the engine modeling for a supersonic aircraft in X Plane is completely uncharted territory, and we would be, in a sense, "flying blind" when it comes to a time estimate for finishing it. And unfortunately, I don't think any developer has the resources ($$$'s) to dedicate all their time to make an accurate, or decently accurate representation of it. I'll probably start modeling it in my spare time and then cross the programming bridge when I come to it. Who knows what surprises X Plane 11 will have. Supersonic engine performance would be a HUGE plus!

Hi Hugh Engines spontaneously dying is a very unusual thing to happen. It should only happen under certain conditions. One thing to note, if the engine instruments are all in the green, you can still have an engine failure if your MP and/or RPM is too high.

Welcome to the world of "real" flying. Where navigation is actually a challenge. I'll have a look at the cruise setting with the fuel and payload weight you specified and double check.. At first glance, it seems like the figures and airspeed are correct for an approach, but definitely not for a cruise setting. Could you double check your configuration (Landing Gear up or down, Flaps up or down, etc...) With regards to the cowl flaps, you don't have to keep them all the way open or all the way closed. They can be adjusted somewhere inside the open/close range and then left at that position for however long is necessary. The same can be said of the oil cooler vents. IIRC, Cowl flaps should remain open on the ground and closed in flight. With regards to the Cylinder Head temps, the 175° mark is more of a guideline than a rule. In the real world, if you shut down an engine while it was running hot and it cooled too quickly, there could be a risk of cylinder head damage in one or both engines. For the purposes of the X Plane version, we didn't model an engine failure based on excessive shutdown CHT's.

Hi Hugh Correct, there is no OBS knob. Navigation is done using a very basic RMI. The larger needle on the left side is linked to NAV 1 and the smaller needle is linked to ADF 1. There is an identical RMI on the right side, except those needles are linked to NAV 2 and ADF 2. Each RMI has a DG which tells you what heading you're flying and the needles point to the navaid (if tuned). To land a tail dragger takes a bit of practise. Approach the runway like any other aircraft, but once you touch down, or maybe even shortly prior, deploy full flaps (for increased drag...but be careful not to pull the control column back too far as the extra lift will cause the aircraft to keep "floating"). DO NOT apply the brakes as soon as you touch down. You will forward-flip the aircraft. It has to slow down on it's own. Add as much drag as possible as it slows down by gradually pulling the control column full back, but only when the tail wheel settles down onto the runway. When you are below rotate speed, you can apply the brakes. It does take quite a bit of practice, but you will get the hang of it.

Try... Essco Aircraft manuals: http://www.esscoaircraft.com eFlightmanuals: http://www.eflightmanuals.com I think AVSIM also have a few very good manuals. Might have to do a search, though. Two other sites which are very decent are: http://www.smartcockpit.com/ http://www.avialogs.com/ Avialogs has only just come back online from a hiatus and I think they're still building up their old database.

Too much?

I don't want to go and point the finger at the x plane trim function just yet. There are so many models and so many variants of the DC-3, it's literally impossible to make it a "universal" version. I had a specific set of documents, and although there were some things I wanted to add/change, I had to stick to what was in front of me. SOME things were not explained in detail, so I had to improvise. (Case in point, the yokes not moving when the autopilot was on) I'll talk to Cameron and Theo about adding a wing leveling function to the autopilot once it is engaged. But only if it's certain that it was in the old DC-3's of the 1940's and 50's. It certainly isn't a difficult thing to add, so if it does get in, it will be a part of the update that hopefully includes the auto rich and auto lean functions. If wing leveling is not an option, I can slow the trim down to make it more finely adjustable.

The way it's supposed to be flown under autopilot control, is to trim the aircraft, as you have done, and to ensure it is flying straight and level for at least a minute or 2. The way you confirm this is to make sure the adjustable Heading Selector Gyro on the Autopilot Panel (The heading you wish to fly) is still aligned with the Directional Gyro after that minute. If the aircraft is on a slight roll, you will see the DG slowly moving out of alignment with the adjustable heading selector. If you are drifting, it's likely you haven't trimmed it enough. If you're satisfied with the trim, and the 2 gyro's remain aligned after about a minute or 2, then engage the autopilot. It takes a bit of practice. The early Sperry's, as far as I can see in the info I have, do not have a wing leveling function when activated (Although I could add one, but that would take away some realism). They hold the pitch, roll and yaw that the aircraft is currently flying. Regarding the yokes not being able to move while under autopilot control. When the Sperry Autopilot is on, the yokes have no control whatsoever over the aircraft. They also do not override the autopilot. Now, it's possible that in the old vintage versions of this aircraft, the yokes did move with the autopilot, but I have to say, in all the research I did, I was not able to find out for sure. What I could find regarding this is that "the autopilot, while operational and in control of the aircraft, cannot be overridden with the control column."

I've brought this up with Theo and he has looked at the code and knows what the problem is. This has been fixed and will be added to the next update.

This was an issue I was faced with in testing. The DC-3 in X plane moves far too quickly with the default friction co-efficient. Meaning that the take off and landing run was too short. This had to be adjusted to get the correct takeoff and landing run. IIRC, X Planes ground modelling on non-paved surfaces has been an issue with other aircraft as well. The friction co-efficient can be turned down, but then take offs and landings would be shorter. How short depends on the reduction of friction. I'll have a look at this some more and see what I can do with it.

Thanks, Chaps! Rhydian, that throttle console is actually somewhere in this very thread. I think a few pages back. I have to say, though, seeing it on Simflight kinda took me by surprise. I only went there to check after I read your post. The reaction from some people at FSDeveloper is, well, interesting.

Very strange. I'll get Theo and Cam to take a look at the code and see what's going on.

A lothas been happening around Theo and myself lately, most notably continuing Saab development and a fix or three on the DC-3. As both those projects are currently out of my hands, I fired up Blender and revisited the 747-200. Have to be honest and say I was not happy with how it looked. So I bit the bullet and decided to remodel all the panels (except the throttle console...something Theo was against). So...I started modelling the main panel from scratch a few days ago. Yes, it will be a high poly count when it's finished, but it won't compare to the DC-3 poly count.

Happy to see you got it sorted. I'll look into the Com radios. I was actually asked about the audio selector from 1 other person. As far as I can tell from the doc's I have, the very old DC-3's didn't have an audio panel for the radios. I also can't find any photos of an old style audio panel for the nav radios. No promises, but I'll look into it some more and talk to Theo about adding it. It all depends on what I can find in the way of photos and if we can fit in the texture maps (The audio panel would have to be modeled, textured, panel regions added and then animated.)

Seeing as they were originally working on your computer, but have now stopped, I'd say this is a system specific issue. Have you deleted any files in your x plane folder? Did you remove the Gizmo folder? Did you modify the DC-3 acf in any way? When you reinstalled, did you reinstall in the correct folder (X Plane ROOT folder. NOT the Aircraft folder) and the correct X Plane installation (X Plane 9 or X Plane 10)?

Excellent! Glad you got it sorted.

No problem at all. Apologies if I came across as confronting, but I hadn't had my caffeine fix yet and I was losing a bit of patience over the project I am working on. I'll definitely look into it because I think I know where this can actually be adjusted. I don't have access to X Plane right now (I'm on the laptop about 15miles from home so I cannot check this for myself) but try changing the angles for steering in XP10 from (as you highlighted in your first screenshot): Low Speed 40 to 0 and High Speed 25 to 0 and leave the check mark in "gear castors"

1. ADF 1 and ADF 2 are tied to the RMI's on the pilot's side and co-pilots side respectively. The indicator needle is the solid white arrow. 2. I'll check these, but they are using Gizmo and were specifically coded to burn fuel from the selected fuel tank. 3. All instruments were modelled from an actual photo of a DC-3 panel. 4. There is no text command to add the transponder, but you could assign button presses to it. Go into your Settings->Joystick and Equipment->Buttons: Adv->Transponder section and assign the buttons to the respective selections. 5. I can't say it will DEFINITELY be added, but we have been working on it and it looks promising.

The mod I posted tells x plane to allow the wheel to freely rotate around its axis without being directly influenced by the rudder. Its direction is only affected by where the aircraft is pointing while it is moving. The tail wheel lock is a separate dataref (piece of code) in x plane that tells the tail wheel to stay locked in the forward position when it's engaged. When it's unlocked (in the release version without the free castoring tail wheel) the tail wheel is under full control from the rudder pedals. As for the co-ordinated roll point you make, I have never piloted a real DC-3. I don't imagine many people have. I was in talks with someone down here who used to work for a company that ran DC-3 joyflights out of Bankstown airport and he gave me some valuable feedback and he was "very happy" with the final package. If it is an x plane issue, then there isn't much that can be done, but I'm not ready to go finger pointing just yet.

I was watching a couple of videos on the DC-3 that were posted on YouTube and saw these two in the sidebar. I never even heard of these guys, but they make some pretty good videos and have a very nice website. http://www.gudun.co.kr/