Nice post, John.

 

We are getting second thoughts about the Yaw Damper button. Apart from it being nice to have does the BT-67 actually have it?

Good question. I just saw the parameter in the aircraft.cfg, which then made me look for the switch.

 

Well, the rw DC-3 conversions at least offer the yaw damper option. http://www.turbinedc...rbine_dc3.html Should help the AP performing coordinated turns, while the manual flying won't be a problem without the YD. Don't know if the BT-67 design is prone to the dutch roll tendency, which would then be another thing the YD could help with.

 

She does need a lot of rudder in the turns though, so the convenience factor wins a lot with that YD option. Lazy sim pilots. :lol:

 

Revised Fuel Flow has now been added to the cabfile in the Bugfix zip (url in post 156).

Thanks. This renders my King Air gauges to be redundant. Good work.

 

It's OK, the current DIY model still has the two 3D Garmins. But I am not sure what poster KOXR means by removing bezel and knobs

I guess he means what Ray and I showed on the screenshots with the yellow marked areas. By getting rid of the 3D model for the Garmins, the 'flat' RXP units would show up in the VC with their knobs and switches, not only their screens. This would allow for a VC operation but also render the panel to look very flat. Hence my note on being an optional step.

Some pre upload texture thumbnail testing

I'm preparing the textures for upload right now and got some thumbnail image problems.

 

There are 3 ways to add a thumbnail image to FSX:

 

1) Add it to the texture file "thumbnail.jpg" (only working if the texture uses only one thumbnail, not possible here!!!)

 

-> 2) Add it to the plane's root folder and add a ui_thumbnial= entry to the aircraft.cfg (thumbnail option 1)

 

-> 3) Add it to the plane's root folder and name it after the title= aircraft.cfg entry (thumbnail option 2)

 

Here's the test Alfred-Wegener "Polar 6" texture

https://dl.dropbox.c...C-GHGF_test.zip

 

Both options working for me, I need some others to test this!

Feedback: PM me!

 

Thanks, Daniel

As the refered spec sheet said the yaw damper is an option. Sure we could add it and the fact that I had put it into the aircraft.cfg was just at a time I did not know if the Basler has it or not.

So we have two option and we need to decide. It only makes sence if a dedicated switch to activate it is there too.

 

I will have another look into rudder authority. Maybe tweak it a bit further, but what I heard from a DC-3 owner, a DC-3 needs to be propperly flown with wheel and rudder to keep the ball in the middle.

 

Work for the weekend....

So we have two option and we need to decide. It only makes sence if a dedicated switch to activate it is there too.

I like it like it is now. And the guys already took care of that extra switch. After TO, my YD comes on. Before landing, it goes to off. As said, happy as can be.

CoolIP, Alexander - I guess if the Dodson Turbo has YD then so does the BT-67 - being the more sophisticated plane.

 

Sure the two Garmins can be removed altogether, but what size polys do you need in their place? No polys no RXP, no? or are they as clever as to position themselves on their own?

 

Seems there is a test flight report in FLIGHT INTERNATIONAL 24 - 30 April, 1991 which also refers to YD in the Basler.

 

Daniel - not a good idea to clutter the root folder with ui thumbnails.

Note to Daniel. Both thumbnail options work fine here. I saw the methods on some Carenado repaints too, so I'm ok and the repaint looks nice. One just has to make sure to drop those thumbnails in the main folder, not the one of the repaint itself. But the readme explains it very good.

 

Same as mjahn, I'd say that the YD makes sense. Since it's already there, why not keep it? For the folks not wanting to fly with it, if can stay off or one can even disable the line in the aircraft.cfg so it will never engage.

 

Edited. On the sheer YD operation, perhaps Alexander can take a look. Seems like he mentioned this plan. Reason is that the turns with the YD engaged are still able to offset the ball for more than a moment. Could be just my system, but I'm turning rather civilized and the ball slowly goes towards centre but never reaches it.

With manual rudder, I can centre it without much trouble. Of course, she surely does induce some high amount of adverse yaw which, from my limited knowledge, is a typical DC-3 character trait and also adds to Alexander's statement on the stick and rudder work.

 

On the RXP stuff, I don't know and I'm actually happy with the 3D models as they are, even if they force me to operate the RXP via the popup window. They look great in the VC. Maybe the other folks looking for the flat GPS section can state their wishes to help you.

 

On a long shot, Marcel Felde helped you folks with some knowledge, right? Perhaps he knows how to make your nice 3D model work with the RXP units. He's used that tech on his Katana. Means that the VC knobs interact with the RXP GPS, if installed. I guess this would then be the first freeware to allow for some 3D RXP integration. B)

 

Don't worry, you folks are already top notch in my eyes. We're working on the cake's icing right now. More like on the second layer. :lol:

Do you want just two display screens, one for the 430, one for the 530? I'd need the dimensions for these and the VC_xx sections of the panel.cfg then, I guess.

 

Yes. It would be great to just replace the current 530 and 430 with the reality XP verisons.

 

Here is the panel.cfg entry from the Realiair Duke which has the Reality XP 530 and 430 gps.:

 

[VCockpit01]
size_mm=1024,1024
pixel_size=750,750
gauge18=rxpGNS!GNS530, 0, 570, 630, 454
gauge19=rxpGNS!GNS430, 0, 306, 630, 264

 

I can't find one that has the same pxiel_size as the Basler but hopefully this give the apporiate ascept ratio needed?

 

Would this work for the Basler panel.cfg if the DIY model had the 3d parts removed:

 

//--------------------------------------------------------
[Vcockpit04]
Background_color=0,0,0
size_mm=1024,1024
visible=1
pixel_size=750,750
texture=$basler_05

gauge00=rxpGNS!GNS430, 9, 1, 630, 264 // The pixel size and size mm have changed. Does that affect the first 9 and 1 in this string?

//--------------------------------------------------------
[Vcockpit05]
Background_color=0,0,0
size_mm=1024,1024
visible=1
pixel_size=750,750
texture=$basler_06

gauge00=rxpGNS!GNS530, 0, 0, 630, 454

 

I guess he means what Ray and I showed on the screenshots with the yellow marked areas. By getting rid of the 3D model for the Garmins, the 'flat' RXP units would show up in the VC with their knobs and switches, not only their screens. This would allow for a VC operation but also render the panel to look very flat. Hence my note on being an optional step.

 

Thanks CoolP, this is exactly what I am looking for.

Note to Daniel. Both thumbnail options work fine here. I saw the methods on some Carenado repaints too, so I'm ok and the repaint looks nice. One just has to make sure to drop those thumbnails in the main folder, not the one of the repaint itself. But the readme explains it very good.

 

Actually, the simplest way to handle the thumbnails is to place each livery's thumbnail.jpg in that livery's own ..\texture.n folder, and have no thumbnail whatever in the root ..\texture folder. In fact, the root ..\texture folder should only have common bitmaps that all liveries share, and all fuselage/wing textures should be in their own dedicated ..\texture.livery folders.

 

I would also point out that there's a error in the example texture.cfg files in the default aircraft, since fallback.3 actually is pointing to a remote machine at the former ACES studio! The corrected texture.cfg is as below:

[fltsim]
fallback.1=..\texture
fallback.2=..\..\..\..\Texture
fallback.3=..\..\..\..\Scenery\Global\texture

Right you are. But Daniel's trouble was that he has one livery with two options. Ski and no ski. So he was looking for a way to have two different thumbnails and only one livery texture folder. At least that's what I think was his trouble. But since he was testing the approach, he surely is interested in and reading the feedback.

 

On the other livery with the ski / no ski option, he used the same thumbnail for both and only the text gives the clues while the picture doesn't show the wheels.

 

 

With the current method of his, he avoids those ?. I guess that was his plan. Here's the shot with the correctly placed files. Note the thumbnails showing the skis or wheels.

 

First, I must thank and congratulate the designers for their hard work on this aircraft. What a great result!

 

Several others have commented on how well this thread reads, and I can only echo the same sentiment. It's a great example of what can be achieved by a group of like-minded individuals who are committed to making something good even better.

 

So, apart from my thanks, what can I add to this thread? Well, a few years ago I saw a DC-3 in the colours of RAF Transport Command at the Fairford airshow. I found the aircraft's textures for the FS DC-3 and that's what I load up when a fly a DC-3. So I thought, wouldn't it be great to have a BT-67 in the same scheme? Unfortunately aircraft painting is something I have never got into so it's way beyond my capabilitles. I won't be quite so cheeky as to ask if anyone wants to do it, but I thought I would post a couple of pics of the aircraft in question and maybe someone might think "that would be cool to do". If anyone takes this up, please let me know!

 

 

 

Beautiful plane and livery. Would be a nice one for the Basler for sure. Planning a RTW trip with her, Nick?

Unfortunately the Basler wouldn't be fast enough for normal RTW race legs but there are special flight legs where something else is required - the 2011 race kick-off event had DC-3s flying around the Caribbean. So you never know!

Unfortunately the Basler wouldn't be fast enough for normal RTW race legs

Oops, didn't know that. How about a jet conversion then? Agreed, it robs the style from that plane. It needs spinning props. I still run the DC-2 at times, just because she's so genuine and can land on a helipad.

With GNSs removed, DIY "_allblank" model is in

 

https://dl.dropbox.com/u/51024107/DIY_panel_01.zip

 

using panel.cfg data

 

 

//--------------------------------------------------------

[Vcockpit04]

Background_color=0,0,0

size_mm=512,512

visible=1

pixel_size=512,512

texture=$basler_05

 

gauge00=XXXGNS430XXX, 6,5,500,210

 

 

//--------------------------------------------------------

[Vcockpit05]

Background_color=0,0,0

size_mm=512,512

visible=1

pixel_size=512,512

texture=$basler_06

 

gauge00=XXXGarmin530XXX, 6,5,500,360

 

No self-illumination set, I am supposing RXP can do that?

No self-illumination set, I am supposing RXP can do that?

I'd say so, yes.

Edited. I've just tested the night stuff and the GPS spots stay black. That's although the RXP gauges usually include their night lighting. My guess is that the light map has to be altered to allow the RXP units to shine through. The day version works, but at night, even the displays stay black.