Goran_M

Now we're getting into some complex territory (blue flame) I'll see what we can do about the glass. No promises.

I'm in total awe and envy at what Leen is capable of and completely appreciative of what he is doing. He has done all these repaints at his own bequest. I have never asked him to make any of them. Actually, after the first few, I asked him if he wants to texture all my future projects in a paid position. He said it was just a hobby and he wants to keep it that way. Some hobby!

Theo's gone on a well deserved vacation. I'll see what we can post when he gets back.

Just the default Garmin. I also made a KLN90 about a year ago for Dennis over at the org. Not sure if it was freeware or payware. He did something for me so I returned the favor. As far as I know, it was coded in SASL so it won't work with the current version of Gizmo (the DC-3 is coded in Gizmo).

I'll have a look at the autopilot issue with the steep pitching up behaviour. I'm not really sure why it would do this, but I'll have a look.

What's the matter? That thing too hard to navigate without a GPS? To add the Garmin is very easy. We already have one modelled and textured, and we can just throw it in there. I'll probably add it for the next update. I'll see what I can do about the localizer and flight director.

We're working on a few code fixes atm (including auto rich and auto lean). Hopefully, by the time that's done, X Plane will be a little more stable and we'll get to a few other things as well as the working electrics with a dead bus. I actually found it easier to work the radios with click spots. Manipulators were a little dodgy, especially when it gets a little bumpy. But I'll revisit this and see what happens.

This project has actually been passed on to me a few weeks ago. I really want to get it finished but I have to clear my current workload. Let me wrap up what I'm doing over the next few months and I'll see where I'm at. If I can squeeze it in as a side project, I definitely will.

Try to relax. You'll fly it for a little while. Try not to give the yoke a death grip (Trust me...the first few times, everyone has an iron grip on the yoke when they hold it with one hand and the other hand is on the throttle.) Instructors are there to help you. Not intimidate you. Ask questions. No question is a stupid question. Based on the experience of many others that I know of, including me, DO NOT tell the instructor that you have flying experience in X Plane or FSX. That does not impress them. What knowledge you do have based on simming, use it as a supplement to what the instructor tells you. Don't look at the panel and the gauges. You're not flying IFR. Look outside and kill 2 birds with 1 stone by enjoying the view as well as flying VFR. If you don't feel comfortable with anything, tell the instructor. He/she will take over the controls and you can then relax. Don't panic. Have fun. Ask questions and you'll enjoy the experience.

I was speaking to Theo about this repaint you did just yesterday. I really like it. It really looks old and adds a lot of character. There are different markets for different types of aircraft. We're still very happy with the response it has received.

Thanks for the comments! Regarding the issues you are having... The ammeter was deliberately "broken". I wanted at least one thing to not work in an aircraft from the 1940's that has seen a few 100 thousand air miles. I'm not sure what's causing the autopilot issue. This was not a problem when it was released. I'll look into it and discuss it with Cameron and see if we can find out if we can duplicate this behaviour.

Correct. It depends on the POV. The trail position is something I have not come across in the documentation I have. It most certainly may very well be in some old radial engines, but even if we did try to make it, going by what is available on the development side of things, it would mean quite a large amount of programming to make it work correctly because its movements and effects would be dependent on weather, temperature, air pressure, speed of the aircraft, altitude of the aircraft and all of that would affect many engine variables. So whereas it would be good to see, the amount of work needed to make it work properly, (if we COULD make it work properly within the sim) would be quite significant. We were going to make a clickspot for the yokes to disappear but figured they don't really obstruct much in the way of panel views. It isn't that we couldn't do it. We actually did it in the Duchess. We may add a clickspot in the update. Issues with the DC-3 have actually been very minimal. When it comes to pinned topics, that's all Cameron. Thanks for your comments! Goran

Any taildragger is very tricky to land...especially using brakes. We obviously couldn't test how hard the brakes had to be applied before the aircraft flipped over because I don't know if any DC-3 pilot has actually done that, but I WAS told that it is VERY easy to nose over any tail dragger, and the DC-3 is no exception. To correctly approach the runway and use minimal brakes, you need to slow the aircraft down to just above stall speed, after touch down, do not use the brakes. Just let it roll to just above taxi speed, and then use the brakes. What you could do is adjust the brake sensitivity in the buttons assignment screen to "half pressure". With regards to the pinned posts, That's Cameron's doing. I'm guessing for organizational reasons.

Correct.

The ADF issue has been fixed and will be included in an update soon. In the meantime, make sure you load the aircraft with engines running. This will enable all avionics and the adf's will work. The tail wheel lock is not something that has been reported as a fault. Perhaps try to restart the sim or reload the aircraft. Goran

Like the title says. The DC-3 has received the PC-Pilot Classic award. I think it really says something when 3 add ons from the same publisher get reviewed in the same issue of PC Pilot. Goran

This is a known bug that has been fixed and is scheduled for the update. Goran

Rex I'll look into posting a screenshot of the Saab center console soon. I have to say, Theo has done some bad-ass texturing on it this time. We've settled into a nice groove now and big things are happening. I'll elaborate at a later date when we have off-loaded some of our current work.

LMAO!

So here's what's happening. The Saab is still being worked on. Quite a bit of work in the programming department has already been done on it, as well as re-modeling and re-texturing some of the cockpit that was done in the 2nd half of last year. I'll post screenshots soon. DC-3 update is in the works. Mainly updates in code. Flight model has had a few changes made along with a few cosmetic changes and bug fixes The 747-200 and -400 are still moving forward but they are long term projects and a lot has been happening on those in recent months. Don't want to elaborate on that just yet. I really want to, and plan on finishing the Hawker 4000, but it will need quite a lot of programming and an FMC. I was almost prepared to just add some kind of basic FMC, but after talking to Cameron and Theo about it, we all agreed it needs to be done properly. So the Hawker 4000 is just on hold until we can get it programmed properly. So, after making a bunch of prop aircraft, and while Theo was busy texturing the DC-3, I had very little to do, so I started work on a Cessna Citation II sometime in November last year. It's quite far along now and shouldn't take much longer to finish.

When I first modeled the DC-3, I mistakenly put 6 windows. It was baked, textured, and everything visual was done and we moved onto avionics, animations, coding, etc... Then it was pointed out to me that the vast majority of DC-3's have 7 windows. That's when we had a bit of a crisis, because I would have to modify the fuselage and risk messing up the appearance of the windows and the surrounding area of the fuselage. Needless to say, I managed to add the window without damaging the area around it. So the Fuselage texture has 6 windows, but there is a section of the mesh (the 7th window) missing, and that section has now been mapped onto Windows.png. The problem you face now is covering up that 7th window. This won't be easy, as the windows are set to be lit as a glass object in Planemaker and the actual texture for the window is a "sheet" of glass that has some Alpha in it. If you open Windows.png, you'll see what I mean.

It had to be put on hold for a little while. I've actually been working on the Duchess update as well as the Sundowner during DC-3 development. Both have had flight model adjustments and I've made several adjustments to the objects and their animations. Most of the Sundowner has been completely remodeled and re-textured. Recently, since the DC-3 has been released, both Theo and I have been VERY busy with other X Plane related duties. I can safely say the Sundowner and Duchess updates WILLbe finished...we just have to fit it in to what we're doing at the moment. However, we won't be restarting those until July. Once we get stuck back into them, they shouldn't take too long.

You're welcome. Happy to see you're enjoying it! Repaint looks good so far. Keep up the good work and keep us posted.

What Steve said. But also, this is the way the flaps on the DC-3 operate. At least the ones in the documentation I have. If it somehow conflicts with your hardware, you can always open up the acf file in Planemaker, go to Standard->Control Geometry->Controls and uncheck the box that says "Flaps are infintely adjustable between detents" This will not "break" anything in the DC-3. I have already added the degrees of flaps in the acf file for those that choose to have defined presets.