Perhaps to add, one needs that Cessna208B_XML.cab in the Basler's panel folder. So one must copy it from the C208's folder.

 

True. I put them in the FSX gauge folder so to use in other models instead of having to add to other model panels all the time.. But each to their own! Plus, FSP seems to look to the gauge folder for the XML bitmaps and not the panel folder.

 

A little twist on the AP. I very much like using the Stec55 AP. I dont need the DME display as there are already two DME device. The radio stack and the RXP GNS530 pages displays DME. Very nice fit.

 

 

Even better. Good point. The King Air stuff is done that way, I wonder why MS went a different path with the C208.

 

On something completely different. Don't you love it when testing something and then looking from the outside, seeing all those folks waiting for you? :lol:

 

 

'Don't worry, guys. The AP works now, I will take off soon (or just close FSX, killing you). Thanks for your patience!' B)

 

 

Erm, regarding that external view. The 3D lights seem to move around. I would like to describe it in more detail, but I can't. Perhaps just fly in the external view and alter the plane's pitch or bank to see it. Closest word could be rotating beams on that particle effect. Just happening here?

 

Whoa, I've just triggered a fire warning. Now how cool is that?! The extinguisher and fire panel worked as they should plus I had the engine on fire in the external view with some effects involved. Huge thumbs up, guys. Great detail!

 

Nice AP mod. Where's that gauge from? The only thing about the other DME gauge is that it's placed very low, so the throttles are in front with some power on. Perhaps I will move it a bit up.

 

On another level, I was thinking about setting up two RXP 530 where the radio stack is. Then use the current GPS gauge places for weather radar and fill the gaps with DME, ADF and things. There should be some place left for a small TV. :P

 

Or just leave the RXP where they are now, take the default radios out and use the space for the CS weather radar since the RXP GPS already handle the radios. WR down, DME and ADF up. Makes sense? The transponder and audio panel can also be replaced by RXP gauges.

 

I guess I will try that one later.

The transponder and audio panel can also be replaced by RXP gauges

 

The problem with that is the radio knobs are all part of the MDL.

 

Been discussing this at Buffalo Va. Old Joe actualy has one of his DC3 at Bassler being retrofitted at the moment. Luv to see a repaint of the most famous DC3 operator in a Bassler retro.

 

Right you are, I've obviously left the 3D model out of the equation.

 

Still, I like the idea and the audio panel and transponder are somewhat ok for me. Note the moved DME display, only causing slight 3D problems but staying clear of the throttles.

 

Cool livery indeed.

I just knew some gauge guru would save the day!

 

 

On those downloads. Could it be that you've only downloaded the SP1 but not the plane itself then? Sounds like. Find the initial release in Alan's post. http://forum.avsim.n...-dc-3-released/

 

The first fix is separate and can be found here. http://forum.avsim.n...25#entry2413230

 

Combine both and you should be set.

 

I downloded both, as you said, and installed. I was looking for the Navy repaint in the library when I ran across the SP1. It didn't have install instructions and looked like a stand alone file, so I un-installed the first one and installed the SP1 file. It didn't look the same, so I am confused.

 

Dave

I must admit that I don't know about the SP1 file from the Avsim library. I'll take a look.

 

Got it, Dave. That's the thing from Dirk Stuck you are seeing there. When sticking to the links from Alan and the authors of 'our' Basler, you should be ok. That Dirk Stuck thingy doesn't have anything to do with the plane we are raving about. Seems like she isn't available at Avsim so far.

 

But Ray's repaint is available, that's true. Repaint for the freeware Basler BT-67 Navy C40

More on suggestions made here -

 

Chock # 64 on ASI : The pictures of Basler BT-67 cockpits which I've seen (note that there are at least five different ones on airliners.net) all show an ASI with no red, yellow, green, blue or white arcs at all, but only the red stop mark at the VNE, beyond that, there appear to be no other marks whatsoever apart from the airspeed numbers.

 

Placard says 170 VMO, don't know whether/how that relates to VNE. Anyway, the new ASI will be a non-banded affair with just the red limit bug at 170 as in the real thing.

 

Fuel Flow will be tweaked, as suggested here (but tweaking the existing gauge).

 

AP annunciator - will do as suggested here but adding it to the local cab file.

 

CoolIP, #122: Erm, regarding that external view. The 3D lights seem to move around. I would like to describe it in more detail, but I can't. Perhaps just fly in the external view and alter the plane's pitch or bank to see it. Closest word could be rotating beams on that particle effect. Just happening here?

 

That is a bug whose cause we are still trying to find. The lights seem to swivel even though the object isn't animated. The temp solution is to create a copy of the default fx_landing.fx and calling it fx_bt67_ll.fx (or live with it as is).

 

 

 

CoolP, on 10 July 2012 - 03:18 PM, said:

The transponder and audio panel can also be replaced by RXP gauges

 

From what I see here it seems that many useful addons could be placed on the panel. Would members of this forum be interested in a DIY panel model unencumbered by those knobs and radios? If so, let me know what exactly you would want to see removed, and I'll see whether I can work it in. Best give me a picture (the way Ray does, that's most helpful).

Swivel, that was the word I was looking for. Thanks for posting (not only on the word). No big deal on the lights, it just looked funny in the external views at first. I won't delete the effect.

 

Placard says 170 VMO, don't know whether/how that relates to VNE. Anyway, the new ASI will be a non-banded affair with just the red limit bug at 170 as in the real thing.

Spot on.

 

On the panel. First of all, it's good as it is now. The tweaks with the gauges would be made easier if the 3D knobs wouldn't interfere, but I don't know the audience for those mods, so please don't change anything for all the other folks.

 

This just means that I would like a flat radio panel and transponder spot, while others will surely like the 3D knobs because they don't plan to change the gauges. So you folks may have to use two different 3D models, which is a thing I won't demand unless you are really comfortable with the idea. The plane already came for free, so who am I to demand anything more?

 

But I will show a screenshot, mainly to be looked at as food for thought.

The red areas mark the ones where one could place some weather radar or the other transponder and audio panel. It could also allow for another GPS setup. So leaving those areas free of 3D models, rendering it flat, will help the tweaking audience.

 

The flat part is important since the weather radar screen (the radar image itself) failed to show up with the 3D model in place even with excluding the other gauges.

 

The yellow part first of all is well done by you. Your GPS gauges are also pretty neat. So I guess just the guys switching to RXP GPS units could like a flat layout there as it would allow them to press the RXP buttons in the VC, which currently only works when using a popup window.

 

It would also allow to place a weather radar there and move the GPS closer to the pilot, to the radio stack (RXP units in mind). Various options.

 

I consider red as nice and yellow as very optional. However, if you guys like to deliver some normal and a flat panel version, those areas are the ones to look for in my eyes. Lets hear what others think.

 

 

On another occasion. You plane is currently listed under 'unknown' when sorting via the publisher's name. You guys shouldn't be unknown, so be proud of you and give it a name. B)

Vmo = Maximum operating speed

Vne = Never exeeding speed

 

So basically they are the same.

I guess some of our rw certified pilots won't agree there, Alexander. The turbine planes use VMO and if we were using the VNE value on the Basler, we would see some 228 kts (referring to the manual) and not the (in my eyes) more realistic VMO value of 170 kts for the redline limit.

 

Now I'm no pro on that one, but especially that turbine case lets me disagree with the statement of yours. However, I'm always open to be corrected.

 

I can see some VMO being defined for other planes and some VNE too (haven't checked the values though), being above VMO. So I wouldn't say that those two are the same while the spread itself is plane dependant of course. The planes in mind are, for example, the JetProp and the turbine Duke, being former piston engine powered ones and now incorporating a VMO well below the former VNE. Same as our DC-3 which now is the BT-67 I guess.

 

Getting certified with a piston engine may involve the VNE (and no VMO), while the turbine and jet stuff receives a VMO and no VNE, so perhaps that's where you are coming from.

 

I guess some of the rw flying fellows explained the aspect on the certification and the loss of the yellow arc range in more detail, which would then fit the BT-67 case.

 

Perhaps to add, in case anyone wonders. Those speeds are certification limits, not necessarily structural ones. I guess even the rather restrictive Airbus stuff allows for a slight VMO overshoot before the FBW triggers countermeasures and the test pilots will also exceed any VMO on flutter tests and things, to get closer to the structural limits of the plane.

 

Also, some other limits may involve the max. airspeed the windscreen can handle or just the one exceeding structural limits if a 'standard' bird strike occurs. The prop planes may also run into trouble on the prop rpm when diving, to give some examples.

 

On Hollywood planes though, a single knot over the red line will inevitably lead to an explosion of the plane. Sorry. Same goes for somebody shooting in the rough direction the plane is parked at. Believe me, I saw it.

 

 

First of all, thanks for your work on the Basler, Alexander. You are the man behind the nice FDE.

I looked into my data again and it does not say Vmo but Vno and you are right they are different but could be the same for planes.

I think the following is an explanation:

 

Vne (never exceed) maximum speed an aircraft should not exceed. This seems to be 228 for DC-3 types. The reason here is mostly the speed of air over the wing reaching either mach levels or strain on wing/fuselage parts that would brake just from aerodynamic forces.

 

Vno ( normal operation) maximum normal operation, which means up to this speed you can use full controls deflection without reaching acceleration values beyond the structiual limits.

 

If Vne > Vno than the delta is marked as yellow band indication of caution during manoevers that may lead to too high strain on fuselage or controls.

 

But Vno could be the same Vne if the controls and the accelleration from full deflection would be sustained by the structural strength of controls and wing/fuselage, thus no reason for indicating it.

 

A Vmo (maximum operating) maybe as high as Vne but it may also be set lower due to that the certification is set to a lower value based on age of construction, as we have here or many additional external equippment which would be damaged at higher speeds which can be applied on the Basler.

 

So maybe the fact that the original ASI on the Polar5 has only one red line at 170, this may be a result from the fact that they use skies and often other external measurement devices and to avoid any problems with high speed caused turbulences, flattering or just to high aerodynamic forces, the certification just use one limit which is significant lower compared to the DC-3 Vne data and would not hinder theri typical usage.

You are right, the manual lists VNE and VNO. That 170 kts VMO limit came from the placard in the cockpit. Good point on the ski ops.

Vno ( normal operation) maximum normal operation, which means up to this speed you can use full controls deflection without reaching acceleration values beyond the structiual limits.

Makes sense, but the placard also has some VA on it, so how to handle that one? It's way lower.

 

Not to be read the wrong way, my questions on the speeds are nitpicking and only arise from interest, not because I think that important items are affected on that beautiful plane.

How does this look (given the resources at hand)? We are also thinking about replacing the ASI.

 

 

 

May be like this one?

Everything is visible, a stopwatch, RMI, HSI, Radio Altimeter.

This is how it looks now, I think I'll leave it at that. Note sharper placards and new ASI. This is going to be part of an Update package. There are some other things we have to iron out still. Thanks everybody for the suggestions made here.

 

 

Very good. Is it possible to place the stopwatch above OMI indicators?

A request to our dear and respectable painters, there were several DC-3-65TPs (DC3-65ARTP) flying for the ICRC. I would be very gratefull if you repaint this BT-67 like them. Or is it a bad idea to repaint BT-67 like 65 at all?:)