DC-3 Radio

[burcham8]

Guys --

If the DC-3 cfg.file [Radios] portion reads like this:

[Radios]
Radio Type=availiable, standby frequency, has glide slope
Audio.1=1
Com.1=1, 1
Com.2=1, 1
Nav.1=1, 1, 1
Nav.2=1, 1, 0
Adf.1=1
Adf.2=1
Transponder.1=1
Marker.1=1

WHY doesn't the *!&#%^ radio work?

Marc Burcham

[Tom/CalClassic]

You've got to be a little more specific than that...

The DC-3 radio does not have standby frequencies, so the Com and Nav lines should be 1,0, not 1,1.

Hope this helps,

[burcham8]

Tom --

I guess what I meant is that the radio won't operate. I can't use the mouse to change frequencies, etc.

-- Marc

[Tom/CalClassic]

And they won't until you change those numbers...

The correct Radio section should be:

[Radios]
// Radio Type = availiable, standby frequency, has glide slope
Audio.1 = 1
Com.1 = 1, 0
Com.2 = 1, 0
Nav.1 = 1, 0, 1
Nav.2 = 1, 0, 0
Adf.1 = 1
Adf.2 = 1
Transponder.1 = 0
Marker.1 = 1


Hope this helps,

[strat]

Hi Ho,

Further to this topic, when I/we/you select the frequency between 100-190, there is no dial, which is kinda weird. The adf still "works" and a frequency setting is visible on the mouse "call-out."

And furthermore, it doesn't select frequencies between 420 and 490 - although that is a code error and also an issue with the adf_dial bitmap - tricky if you're lurking around Budapest though.

I hope to have a solution in your Christmas stocking.

Santa's little helper.

[oldpropfan]

Strat, I believe the 420-490 freq range was blanked out because in the US it was reserved for other uses. Try this file from avsim : dc3_radio_improved.zip , and you can access the missing range.

Al

[Randy_Cain]

Hi,

Marc, this is hilarious! ;D

I just came to ask a question about this radio. I'm just beginning work on the VC for my Goodyear US Navy G-1 trainer and ran into this problem in the VC. This [DC-3 default] radio is perfectly clickable in both 2D and 3D environments in the default aircraft and others, but in MY VC, it isn't. What do I need to do in my FSDS model and/or the panel.cfg to get it clickable in both?....or is it something I can even get to work?

Here's a sneak peek:



Yours,


P.S. On a seperate but related note, I'm not getting any lights on the radio at night in the VC, but mousablity and lights are fine in 2D. What did I miss?

[Tom/CalClassic]

Hi,

Nice blimp.

Do you have it set up the same way, i.e. a popup panel, or do you have it installed directly into the main panel? Jens' Canadair DC-4m (for example) uses the DC-3 radio as a popup, and it works fine.

Do you have an electrical system defined in your aircraft.cfg file? You will need that for the lights to come on, AFAIK.

Let us know,

[Randy_Cain]

Hi Tom,

The answer to your question is "Both." I did find the answer by accident. After a I got a few gauges on my overhead (..the "main panel" in my ship) I found out that if your panel is at "eye level" or lower, you can get pretty close and still have mouse-overs (clickable w/tools), HOWEVER if you built it overhead, once your about 30 to 45 degrees beneath the panel, all the hotspots for frequency, navaids and stuff no longer work. In short, you can get close up in front, close up and higher, but NOT close up and under these gauges and still be able to use the mouse on them in a VC environment. Something else I got to learn the hard way.....and several clumps of hair later.

I was running around in active camera and suddenly discovered that on an accidental mouseover, a tooltip popped up. That's how I found out. I guess I'll have to angle the overhead down a few degrees to reduce that sharp angle to get to the panel....and maybe move it further forward to get it "clickable".

Not a big deal, since I'm having to cheat and make some stuff up. I have NO photos of a G-Class trainer, so this is all based on 2 very big and good photos, but no colors or interior details.

I guess getting the lights on the radio to "light" up is just a matter of getting the VC light effect just right, as they to get green when on, but with no difference in "brightness". (i.e. They don't "glow" at night...they just get very dark green )

Yours,


P.S. Marc, did you ever get your issue resolved?

[Randy_Cain]

Hi!,

P.P.S: Ok, I'm an idiot. I had my "view point" in a box that wasn't a reference part, so I could see it in FS9. OOPS!

I guess you can't click panels through a polygon, even if it's facing the other way (..the "head" view box, not the panel).

As for the above... uhm..."nevermind"