|
|
Post by connieguy on Jan 7, 2020 4:56:41 GMT -5
Tom. As I wasn't aware that the Ocean Stations featured in the gauge at all it is still well worth knowing  . Erik. Thank you. timeanddate is a valuable site but for the 1950s they are at the mercy of their historical information and I have known them be wrong. The present International Date Line is not a complete vertical and Daylight Saving Time introduces complications, but otherwise time is a function of longitude, and the PanAm timetables sometimes indicated time in that way. I think one of the best sources of information for our period is actually the airline timetables, which quite often give UTC and Local Time too. What the FS9 error on Fiji shows is the importance of always setting simulator time by UTC and ignoring Local Time if it is shown incorrectly. As I have pointed out before there is a Pierre Fasseaux clock which is not changed by crossing time zones and which can be set to the correct Local Time if FS9 is wrong. If you land in a different time zone it can be adjusted accordingly. Install two examples in a panel and the other can be set to UTC... Ken
|
|
|
|
Post by Erik on Jan 7, 2020 15:22:03 GMT -5
Roger all, Ken, thanks for the valuable tips!
Erik
|
|
|
|
Post by Jorge on Jan 31, 2020 11:26:55 GMT -5
Great topic. My apologies for bumping the three week old thread.
As a side note, in theory you can change the "range" of the NDB's with the "signal strength" option of the xml code in the gauge you are using. The code is ADF SIGNAL:1 or ADF SIGNAL:2, depending on the radio. If I remember correctly the default range (in meters) is about 200000, which comes out to about 108 nm. That's why the RR4 system can reach out to 100 nm like the real ones. This is in the DC3 default gauge for the ADF radio you tune. In theory you would be able to get an NDB to "reach out" farther if you increased the distance of the signal. For example, a range of 250 nm would be about 463000 meters. If you had 500000 meters, you would have about 270 nm.
I had some code I was messing with for the B314 panel I was working on. If anyone is interested I can post it here. I never had a chance to test it, though. It was supposed to be for FSX, but the xml code was in FS9 style so it should be usable in FS9. Any ideas?
Jorge
Miami, FL
|
|
|
|
Post by Tom/CalClassic on Jan 31, 2020 13:47:37 GMT -5
Hi,
The A: variables are generally read only, so those only report the signal strength when the plane is at its current location, they do not set the range (nor can you increase the signal strength). A few of these A: variables have been intercepted by FSUIPC and if you have the payware version you can set those within FSUIPC, but these aren't included. The maximum range is indeed 108 NM.
|
|
|
|
Post by Jorge on Jan 31, 2020 16:00:44 GMT -5
Thanks Tom. I wasn't aware the 200000 meters was "hard-coded" into the sim. Too bad FSUIPC doesn't include the signal strength as one of the variables.
Jorge
Miami, FL
|
|
. 
