• There seems to be an uptick in Political comments in recent months. Those of us who are long time members of the site know that Political and Religious content has been banned for years. Nothing has changed. Please leave all political and religious comments out of the forums.

    If you recently joined the forums you were not presented with this restriction in the terms of service. This was due to a conversion error when we went from vBulletin to Xenforo. We have updated our terms of service to reflect these corrections.

    Please note any post refering to a politician will be considered political even if it is intended to be humor. Our experience is these topics have a way of dividing the forums and causing deep resentment among members. It is a poison to the community. We appreciate compliance with the rules.

    The Staff of SOH

  • Server side Maintenance is done. We still have an update to the forum software to run but that one will have to wait for a better time.

Update Douglas_C-47_Beta_V3.14 feedback and support topic

mjahn said:
Gooneybird, verify you have installed from file Douglas_C-47_Beta_V3.1406.zip, and to make double sure have a look at file panel\C47\Main.xml, where there should be a line defining the version number as

<Macro Name="VVC_version">3.1406</Macro>

If you have that line, Monitor should show that value (if you are flying a plane from that folder). Better also make sure you don't have different versions installed, as we have been using the same planes for all updates.

Best,
Manfred
Click to expand...

Sorry, Manfred, I am completely ashamed, the mistake is mine!
I did create an other panel folder in the 3.1405 version, duplicating the original one, and adding one gauge for flight time measurement, and my aircraft points straight to this modified panel folder... but I just forgot to update the content of this other panel folder with your latest data!
It is now done, and the display is as you mention.
Sorry again
Philippe
 
ncooper said:
No, it will not look like that, thank goodness.

You might like to try this

[lights]
//new MJ
//Types: 1=beacon, 2=strobe, 3=navigation, 4=cockpit, 5=landing, 6=taxi, 7=recognition, 8=wing, 9=logo, 10=cabin
light.0 = 1, -57.65, 0.00, 13.6, fx_beacon , //un-comment for c47_2 model
light.1 = 10, -5.05, 0.00, 2.3, fx_vclight_c47v3 ,
light.2 = 10, -16.00, 0.00, 1.0, fx_vclighth ,
light.3 = 10, -18.00, 0.00, 1.0, fx_vclighth ,
light.4 = 10, -20.00, 0.00, 1.0, fx_vclighth ,
light.5 = 10, -22.00, 0.00, 1.0, fx_vclighth ,
light.6 = 10, -24.00, 0.00, 1.0, fx_vclighth ,
light.7 = 10, -26.00, 0.00, 1.0, fx_vclighth ,
light.8 = 10, -28.00, 0.00, 1.0, fx_vclighth ,
light.9 = 10, -30.00, 0.00, 1.0, fx_vclighth ,
Click to expand...

Nick,

That was perfect and they looked great...however...I lost my "Cockpit Lights" (that Orange Glow) with this change so had to revert back to my saved .cfg file. When I put in the above and turn on the Cockpit Lights, they flash quickly and go out.
Can you tell me how to fix as it really looks good with the lighted windows.

Thanks,
 
Boy, have I been slacking. Better get my installing version up to date.

And then find a way to convince my wife that I really need to upgrade from FSX to P3D v4
 
triflyman said:
Nick,

That was perfect and they looked great...however...I lost my "Cockpit Lights"

Thanks,
Click to expand...

I suspect that you do not have fx_vclight_c47v3.fx in your effects folder.
The VC light should be red.
In case you haven't, I have attached a copy.
 

Attachments

  • fx_vclight_c47v3.zip
    580 bytes · Views: 2
triflyman said:
Nick,

That was perfect and they looked great...however...I lost my "Cockpit Lights" (that Orange Glow) with this change so had to revert back to my saved .cfg file. When I put in the above and turn on the Cockpit Lights, they flash quickly and go out.
Can you tell me how to fix as it really looks good with the lighted windows.

Thanks,
Click to expand...

That's a sign of too many light effects too close to each other, all based on computer performance, so it won't affect everyone. Maybe split up the aft lights for less overhead.

[lights]
//new MJ
//Types: 1=beacon, 2=strobe, 3=navigation, 4=cockpit, 5=landing, 6=taxi, 7=recognition, 8=wing, 9=logo, 10=cabin
light.0 = 1, -57.65, 0.00, 13.6, fx_beacon , //un-comment for c47_2 model
light.1 = 10, -5.05, 0.00, 2.3, fx_vclight_c47v3 ,
//light.2 = 10, -16.00, 0.00, 1.0, fx_vclighth ,
light.3 = 10, -18.00, 0.00, 1.0, fx_vclighth ,
//light.4 = 10, -20.00, 0.00, 1.0, fx_vclighth ,
light.5 = 10, -22.00, 0.00, 1.0, fx_vclighth ,
//light.6 = 10, -24.00, 0.00, 1.0, fx_vclighth ,
light.7 = 10, -26.00, 0.00, 1.0, fx_vclighth ,
//light.8 = 10, -28.00, 0.00, 1.0, fx_vclighth ,
light.9 = 10, -30.00, 0.00, 1.0, fx_vclighth ,
 
Thanks.

I tried your advice and saw no difference but I am sure you are correct.
I didn't see much less light either, so your way is also a viable alternative.
 
spokes2112 said:
That's a sign of too many light effects too close to each other, all based on computer performance, so it won't affect everyone. Maybe split up the aft lights for less overhead.

[lights]
//new MJ
//Types: 1=beacon, 2=strobe, 3=navigation, 4=cockpit, 5=landing, 6=taxi, 7=recognition, 8=wing, 9=logo, 10=cabin
light.0 = 1, -57.65, 0.00, 13.6, fx_beacon , //un-comment for c47_2 model
light.1 = 10, -5.05, 0.00, 2.3, fx_vclight_c47v3 ,
//light.2 = 10, -16.00, 0.00, 1.0, fx_vclighth ,
light.3 = 10, -18.00, 0.00, 1.0, fx_vclighth ,
//light.4 = 10, -20.00, 0.00, 1.0, fx_vclighth ,
light.5 = 10, -22.00, 0.00, 1.0, fx_vclighth ,
//light.6 = 10, -24.00, 0.00, 1.0, fx_vclighth ,
light.7 = 10, -26.00, 0.00, 1.0, fx_vclighth ,
//light.8 = 10, -28.00, 0.00, 1.0, fx_vclighth ,
light.9 = 10, -30.00, 0.00, 1.0, fx_vclighth ,
Click to expand...

That fixed it...thank you, to both, very much. I know this is a minor thing...but does make flying more enjoyable.

Now, off to finish my 1941 American Airlines "The Mercury", flight 3, from New York to Los Angeles...overnight with sleeper births.
 
Manfred-

If I could be curious, without being pushy, could I hesitantly ask if there has been any progress worth revealing, re. a new comprehensive installer for P3D v4?

As ever, obliged- Carl
 
Hello,

The only modification needed to make the aircraft model virtually P3Dv4 compatible
is the sound gauge which is linked to in this topic.
It is also pinned at the top of the SOH P3D forum.

There are a couple of other 32 bit gauges that mainly allow you to vary the fuel load
in the Control pop up.
You can still do this using the built in P3D fuel and payload function.
They have not yet been upgraded to 64 bit but are not crucial to the operation of the aircraft.

I would have said that for all but the most pedantic, the aircraft is already compatible.

For these reasons, I do not forsee a full P3Dv4 ready version for a while but as the sound
gauge update is so small and easy to do, this should not stop anyone from enjoying the C 47
in P3Dv4 now.
 
Douglas C-47 Beta V3-14 War Model Belly Beacon

Belly beacon is missed in the model 1 (War model)? How to restore?
Thanks
 
As FAIK the wartime planes didn't have a belly beacon. If you want one you can define it via the [lights] section in the aircraft.cfg.
 
Hello,

This should do it.

Aircraft.cfg file, [lights] section, copy and paste all of this over all of the existing light.6 line.

light.6 = 1, -35.75, -1.75, -2.9, fx_beacon ,

FSX

Untitled.jpg


P3Dv4

Untitled2.jpg
 
Last edited:
mjahn said:
As FAIK the wartime planes didn't have a belly beacon. If you want one you can define it via the [lights] section in the aircraft.cfg.
Click to expand...

There were no anti-collision beacons of any sort installed on aircraft during WW II. George Whelen invented the rotating anti-collision aircraft beacon in 1952. Factory installation of beacons on commercial aircraft began in the mid-1950's. In the late 1950's and beyond, many aircraft not originally fitted with a beacon had a beacon added.
 
Anachronistic VHF Antenna on C-47 Wartime Model

Manfred's C-47 Wartime exterior model has a VHF antenna just ahead of the astrodome. VHF Aviation
radio was not in use prior to 1960s on civilian aircraft and the military used and still uses UHF
and HF for commo. Military used GCA in lieu of ILS, and TACAN in lieu of VOR. The VHF Ominirange
system was developed in the late 50s and became widespread by the early 60s, as was VHF aviation
voice radio. A VHF antenna is as anachronistic on the wartime model as is a red rotating beacon.

One sees the VHF antennas on contemporary flying warbirds to permit use of civilian VHF radio COM
& NAV. The military uses UHF for most voice communications.

Perhaps the VHF antenna might be removed from the C47V3_1 wartime exterior model? It would be more
authentic in most cases. And perhaps it might be deleted from the C47V3_2 post-war as well?

And as noted, a VHF antenna would rarely be seen on a US Miliary C-47 in any era. Nor would it be
seen on a civil C-47 or DC-3 prior to the 1960s.
 
Hello,

In the interests of debate only, I have read that the European Air Transport Service began in 1945.
I see that the short description in the aircraft.cfg file reads description=VVC Beta V3.14 Civilian version,
that presumably being a description of the VVC, rather than the aircraft.

I can find only one picture of an EATS aircraft and it does seem to have the antennae.


eats.jpg


Given the huge variety in the surviving aircraft, it would be difficult to add models with all the variations and
there do seem to be many with these antennae, though it would be difficult to date them.

Airports are modeled for the flight simulator as a "snapshot" of how they were when the developer looked at
or photographed them, perhaps it is the same with the EATS model of this aircraft.

Here are a few more, some seem to be DC3s, interesting images in any case.

1.jpg


2.jpg


3.jpg
 
You must log in or register to reply here.
Back
Top