tarakanbg

Just a heads-up that the DC-6 seems to be working in XP11 public beta 1 with only 1 bigger caveat: pressurization state and cabin altitude and rate of change are not picked up by the XP11 systems, leading to oxygen starvation and blackouts above 12000ft or so. In the following screenshot, taken in cruise at 15000ft the gauges display the a/c pressurization system set to the cruise altitude (15000) and the cabin altitude set and indicated to around 5000ft with zero rate of change, however the XP11 datarefs, displayed at the top right corner, bottom section, display a cabin altitude of 15000 with fluctuating vertical rate of change: Also as expected there are some minor graphical issues with reflections on the fuselage and gauges, due to the new PBR rendering system. Finally as XP11 is 64-bit only, I had to delete the 32-bit plugins from the "plugin" folder, as they caused random crashes. The 64-bit versions load and work fine. I know the devs are probably not soliciting feedback at this early beta stage, but just wanted to give some info to other users who might be wandering: the compatibility prospects for our favourite aircraft look quite good, hopefully it wouldn't be too much work to produce an update when the simulator is finally released. Here's another XP11 external shot: P.S. To preempt any criticism: I intentionally didn't switch the superchargers on this flight as it had a very short planned cruise at only 15000 and then descent

Hi guys, Really enjoying the DC-6 and new 1.10 update, thank you for the quick turnaround! I noticed (since initial release) that manipulating the audio selector panel and toggling between COM1 and COM2 radio does not affect/change X-Plane's internal dataref for selected transmission radio; i.e. COM1 is always selected for transmission regardless of the position and manipulation of the selectors on the audio panel. It remains possible to toggle between COM1 <-> COM2 by using a custom assigned X-Plane shortcut or joystick button, it's just not tied to the plane gauges. Can you please have a look at this, it's quite useful when flying online in a controlled environment Cheers and keep up the good work!

It's doable with FlyWithLua and a custom lua script that will intercept the throttle axis raw position and amend it with an offset. I'm using a similar approach to smoothen the values of my rather noisy throttle quadrants.

I'm not on my sim PC so don't remember all positions from memory, but this one for certain is on the left bottom side of the co-pilot's seat, at the floor level; it's a 3 position handle / slider with detents. All 3 detents are labeled.

Have you tried running one inverter on ON, and the other on the alternate position (as suggested in the POH). Does it make a difference?

Thank you for the article, Cpt. Randazzo! Incidentally, some "simmarisms" appear to be platform specific, i.e. the inherited notion among some X-Plane users that all prop planes have inherent lateral instability and those that are stable and can be hand-flown without dropping a wing and constantly juggling the aileron and rudder trim are "unrealistic": a notion that historically follows from the not entirely accurate roll dynamics and torque in earlier versions of X-Plane: a deficiency, that has been since overcome both by the internal development of X-Plane and the efforts of 3rd party addon developers that worked around it in their models. Hope you address that as well. Thanks for an awesome plane!

+ 1 for assignable datarefs on the AP turn wheel

The thing is in my observation: the X-Palne dataref only changes when both the left and the right (captain and FO side) transponder modes in the DC-6 are set to at least SBY mode: thereafter manipulating the left transponder mode selector will succefully change the dataref to ON/ALT. When starting from cold and dark and rotating only the left transponder selector manipulator, the dataref is stuck to "off".

I had the same thing happen to me also in Vegas today. The outside air temperature at the time was 37C. It happened with the aircraft powered off after landing, and after a replay so I initially attributed it to some systems not re-initializing correctly after the replay. The cowl flaps were fully open at the time

I can confirm all the artifacts have disappeared after the re-install. Thank you!

On behalf of all affected: thank you very much for identifying and fixing this so quickly! And thank you for this wonderful plane, I'm having a blast learning it!

I have a similar issue, although less pronounced. It's most obvious on the RPM, Man Presure and Water Pressure gauges, although visible on the OBS too. It's also visible on the panel surface just left of the RPM gauges, It's unaffected by shadow quality: looks the same with shadows all the way up to global (high). It's also more evident on higher cockpit light intensities: almost disappears with cockpit lighting set to "off" or "low". Here's a video: Specs: Windows 10, 64-bit Nvidia GTX 970, 4 GB VRAM Intel Core I7 6700K 16 GB RAM The rendering settings on the video are like this: http://i.imgur.com/ABCqLtq.png (deliberately upped the shadows to global high to test, normally I run with 3D on aircraft)

Let's hope for no rejected takeoff

For the ruby crowd (only pulls once per 2 minutes, don't want to hammer the servers too hard). Waits for the price to drop below $120 (presumptions, presumptions....): Source: https://gist.github.com/tarakanbg/3831a7cad97fb622f8c6447226e6c9ff

Have a look at this thread in the iFly support forum and follow the steps there for proper axis assignment for the spoilers. I have Saitek throttles as well with the spoilers assigned to one of the axis and have no issues and it seems to work fine for the other users as well.

"Zulu" is one of the trigger words in the communication with the de-ice team when you're using de-icing. It's described in the manual.

The only way to get realistic ground steering is to have rudder pedals. Conventional control of nose steering via traditional joystick or even yoke with the "autorudder" option enabled in the flight simulator's settings will always produce somewhat wider turn radius compared to real world :)

Sure, I see your point, but it's the internals, the systems that are the plane. They're not the rest of the plane. What we are bring offered now is a mere wrapper. What I said in my previous post is I don't care about the wrapper. Ideally its quality should match that of the internals, just to give the whole thing a nice overall finish. The idea of separately marketing empty wrappers for non-existing products is what I find strange, to say the very least.

This whole "exterior" thing is laughable to me.Dear customers,Today we're selling coconut shells at exclusive price!There's no meat and juice in them yet, so nothing to eat, but eventually there will be and on a discount!Oh yes and I can also offer you at special price that glossy paperback cover for the book I haven't written yet!Enjoy!

LK is lock: it's meant to lock the window to avoid hiding it when switching views. The Hard Mute is HM ;)

Thanks for the answer, Bryan!I thought that might be the case. The thing is the controls people use for simming are seldom that realistic and a voice callout can resolve the lack of enough or convenient buttons to push for these actions. Not sure if enough people are interested in this to justify the extra work to add it as a feature, perhaps create a separate topic/poll investigating the extra features or fixes people want? I'm not particularly concerned about this frankly, it's so minor compared to what you've given us. I'm more interested in seeing the radio COMM problem resolved as the voice dialing of the radios is really a big thing, especially when flying online and these 25hz frequencies are often used by controllers.Cheers! :)P.S. In response to the previous poster: I can't confirm the engine problem: done 4 flights so far, each time engine switches are set to continuous correctly.

Here's some feedback after a short round trip. I tried to test as much as possible from the callouts, not all of them though. Excellent overall experience, the aircraft does come alive!One bug I noticed and hopefully people will try to reproduce it: voice callouts for dialing the COMM radios work fine, except when asking for 25hz frequency increments. For example 122.725 is a legitimate COMM frequency (displayed as 122.72 for brevity in most aircraft radio stacks, including the 737). However asking the FO to dial in either 122.725 or 122.72 or any other frequency that has an increment of 25hz and not 50hz does not work. The speech command gets fully recognized by the speech recognition engine and is displayed as pronounced in the green bar. If the requested frequency consisted of 3 digits after the decimal point it gets abbreviated in the green bar, i.e. asking for 122.725 is recognized as asking for 122.72. The requested frequency however is not dialed in the COMM radio. This problem only happens with the 25 increments. 50 and 100 increments work just fine.Another thing I noticed: there are no voice callouts for switcing on/off the autothrottle and no voice callout for disengaging the autopilot. This might be intentionally by design? I think though at least for the autothrottle that a callout might be handy.Other than that it's a very rewarding experience and I'm off for another flight right now!Be safe! :)

I got it and reading the manual right now, I must say I'm impressed with the number of possible voice commands, many more than other voice editions I guess? Even a speed restriction from the FMC can be deleted by a voice command and the ability to "dial" even the COMM radios by voice is absolutely wonderful and great convenience for online flyers. Still haven't flown with it but what I see in the documentation exceeds expectations, congratulations! From the top of my head the only routinely used function I don't see is a voice command for setting the squawk and changing transponder modes, but then again this kind of functionality would only be considered appealing for some online pilots.Thank you for yet another great product!

You can select which callouts you want/don't want from the iFly Config manager.

The 767 is Level-D indeed, it's a clear winner, one of the top payware aircraft of all times.For 757 PSS had a reasonably good model, dunno if it's still sold officially, as PSS went bankrupt a while ago. From the current ones QW is good one, although some systems are simplified or not modeled, so it's not quite on par with the LEVEL-D.