Goran_M

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.

Definitely needs a lot more "rumble" in the engines.

Thank you for those comments! The DC-3 has definitely been received well and has received some unexpected positive feedback from the various corners of the general flight simming community...including the MSFS crowd...not to mention it has opened up quite a few doors.

It's ok. I can understand peoples frustration because they just want a smooth, uninterrupted experience. I may be mistaken, but I have yet to see anyone complain to the SASL developers asking why SASL isn't it compatible with Gizmo. It's always "why isn't Gizmo compatible with SASL?" I would love to see Gizmo and SASL work well together. I think it'd make a lot of developers workload much easier. Having said all this, when I saw your first post after registration was a rant, of sorts, about Gizmo and SASL compatibility, it took me a bit by surprise...even though it was a reply to Cameron, it's something that I want to avoid in these forums. I don't mind answering questions about Gizmo, but I want to avoid confrontation and heated debates. ESPECIALLY with other developers. On a lighter note, I'm flattered to know you started following X-Pilot because of the Saab. Contrary to some peoples opinion who have asked me about it, it is not vaporware and has actually been heavily worked on for the last 5 months. There was a small break in its development last year, but I think, in total, it has about a years worth of programming already invested in it. Theo and I have taken that time opportunity to actually remodel and retexture about half of it. With regards to Ben and Cameron having their reasons for Gizmo being global as opposed to aircraft specific... I don't know all their plans, but I do know if they have future plans, then they must be big. And I can only surmise that these plans will benefit developers and simmers and will have a huge impact on the community as a whole. Cameron is a straight shooter, and will not crap on about something. His only interest is to make X Plane grow. It has been that way since he started XPFW.

Taken from the youtube description. First flight of Wilfried Wolterinck's scratchbuilt Boeing 747-200 in 1994. The plane is powered by four Ducted Fans using 15 cc glow engines. Span 3.7 meters, length 4.4 meters, weight 32 kilogramms. Here's the actual video...

Unreal

Thanks Jo Yes, I found that earlier today. The fix will make it in the next update. Maybe even earlier in some kind of interim update. I'll keep you posted in these forums. Thanks

I just checked in XP10 (I checked it in XP9 last night) and strangely enough, the indicator is moving out of range in XP10. I don't understand why, because for me, it works perfectly in XP9 and the objects are exactly the same with exactly the same animations. Weird. Joga, if what you are saying is correct, it looks like XP10 is reading at least the pitch trim dataref incorrectly. I'll look into it and if it is indeed X plane doing this, I'll send off an email to Austin, I'll get back to you guys.

With the trim, that's a weird one. No one else has reported this. I just tried it myself and the indicator worked normally. The only thing I can think of, unless you modified something in the acf (which I doubt) is something is corrupted in the installer. I'll let Cameron know and he can check the installer to see if something is wrong or there may be a few steps for you to do to determine if it is system specific. Regarding the lighting rheostats, IIRC, this is an issue within X Plane and how it reads manipulators in a 3D space.

No problem. Looks good!