Peter Clark

Electrical power from cold&dark is documented in the manual. Yes you can light everything up without the APU going.

Hm, I'll have to play around with that, but I've seen pretty good results on the NGX and 777 when inputting winds in the CDU. I was wondering how finely the winds data was entered, especially with a cross-continental jetstream in the way. But I havent' used the FMC to do fuel planning often, I go with FSBuild with ActiveSky exported winds for the most part.

If you input cruise winds. Otherwise it's zero-wind calcs. Maybe that's the discrepency?

There's a knob (left of the baro knob) that sets it when turned. The outer knob chooses between radio and baro alts.

OK, so I've seen a number of people post they have no true overcast (more like 90% broken instead) with AS2012, but I'm trying to figure out what I'm doing wrong here...Leaving KBOS, 3/3/2012, 10A local time, reported 400BKN 700OVC. Seemed alright (the usual 90% broken instead), but on the climbout, around 10K,I get the attached weather depiction. The METAR is reporting 200 overcast, I'm only (30?NM max) from Boston, and the weather system that is generating the low ceilings and rain spreads for miles and miles around. Certainly there should be no ground showing at all with the real world weather in place, and definitely not this much...Any thougts?8GB RAM, i7 975, 1GB GeForce GTS 240 video card (GTX 850 coming Monday, but this isn't a frame-rate issue).TIA for thoughts on how to fix...

I wonder how many who are 'reaching' the website have an ISP that has a transparant caching engine and are getting whatever the last version of the page it captured was? The site is still down hard from a DNS perspective. It's only 08:00 local on the US West Coast so I'm sure they're going to start working on it soon if they haven't already done so.

Now now, we don't know that's the case. Let's not jump to conclusions. Could have been Tucows who messed up. Plus if the email address on the contact is invalid who's to say it's the right phone number anyway?

That's what I've been saying without saying for a few hours now. I'd at least update the message to remove the guys addresses and phone numbers tho.

Probably are based on the domain registrations. Those who know how DNS works can figure out what's happened. I'm sure the official people will make an announcement of some sort when things are being worked on and when they believe it's all resolved.

Well, the correct entry is 72.51.39.176 (which has ICMP filtered to prevent ping, you can connect to port 80 on that site). The problem here is DNS delegation is broken. It's a relatively quick fix once started.

[root@c3po etc]# ping www2.hifisim.comping: unknown host www2.hifisim.com[root@c3po etc]#[root@c3po etc]# dig www2.hifisim.com; <<>> DiG 9.7.2-P3-RedHat-9.7.2-1.P3.fc13 <<>> www2.hifisim.com;; global options: +cmd;; Got answer:;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 17728;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0;; QUESTION SECTION:;www2.hifisim.com. IN A;; AUTHORITY SECTION:com. 851 IN SOA a.gtld-servers.net. nstld.verisign-grs.com. 1292242004 1800 900 604800 86400;; Query time: 0 msec;; SERVER: 192.168.168.2#53(192.168.168.2);; WHEN: Mon Dec 13 07:07:58 2010;; MSG SIZE rcvd: 107[root@c3po etc]#DNS for hifisim.com appears to be broken. Perhaps your ISP hasn't expired the records yet, but I don't think it's going to come back for the rest of us until the root issue is addressed.

This outage is different than the one previously reported, there's something seriously wrong with hifisim.* 's DNS setup. I attempted to email the listed contacts for the domain but the email bounced back.Hifi - if you need assistance troubleshooting/fixing all of this drop me a PM and I'll help you sort it out. I worked for an ISP for 10 years and do IT consulting now.

(duplicate for some reason?)

No worries. Some background in IFR procedures would be useful, but it's nothing that can't be learned along the way. Start basic and work your way up into the advanced stuff. Set up a flight plan in FS, manually enter those waypoints and the ILS/whatever in the LDS FMS, ignore SID/STAR and once you're good with that you can always add in SIDs and then STARs later. Think of it as building blocks, with enroute and basic IAPs first, then stick on the STAR, then stick on the DP. It'll make sense once you've done it a few times.Course, over a thousand hours IRL doing this stuff helps too ;) No, not in a 76....

Well, remember the STAR and approach procedure are different things. The STAR desends you down and gets you into the general airport area, the approch procedure (ILS, GPS, NDB, etc) are what sequence you into a runway (although some stars have transitions to specific runways, generally they just get you to within about 30NM of the primary airport they serve and ATC vectors you to the approach from there). If you get a planning app like fsbuild, you will export the plan to both FS and the LD aircraft. You then load that plan in FS's route thingie and get an IFR clearance. In LDS you load that route into the FMS using the company route line. Since the plans match FS's ATC will know how to deal with you. That having been said, I've been vectored into other aircraft on an approach by FS's ATC, so I never count on it for separation. Thankfully they modeled TCAS into this beastie.Have you looked on the LD owners forum about this? It's pretty FAQ over there...

Although I don't have a comprehensive list at hand (I'm sure the search function will find it), there are a number of functions and features of the real world G1000 missing from the default G1000 FSX implementation. It's good for it's intended purpose, but if you are looking for a proper G1000 for on-ground systems training the Garmin sim/trainer ($25 direct from Garmin - https://buy.garmin.com/shop/shop.do?pID=6420#accessoryTab ) is probably the best available until the Mustang comes out.

When you use a planner like fsbuild and build and export a flight plan to both FSX and LDS/PMDG, it will include the waypoints of the SID/STAR in the export so FS's ATC can handle it. FS's planner/ATC can't read/write to LDS/PMDG FMC plans, so you need to get the flight plan into both systems independently.With FS's ATC generally you will not end up using a STAR because you'll start getting vectored for the approach before you go through more than one or two waypoints in the STAR. I haven't tried FS's ATC with a DP recently, but as I recall the generic IFR clearance is "fly runway heading", so if you have a quick turn in the procedure before being handed off to departure and receiving the "resume own nav" things tended to get real wierd since it would start trying to vector you back to a previous waypoint which the FMC had already sequenced.For now I'd suggest getting used to enroute operations and once you're comfortable with them start adding procedures when dealing with ATC. Without ATC, play with them all you want.

I've found transplanting a hard drive can be easy, or can be a crap shoot depending on how much under the hood needs to change.The cleanest way I know is to start an upgrade install of XP, then when it's prepped the drive and is ready to reboot the system, power off when you see the bios screen, isntall the new hard drive, then let it come up and finish the install with the new hardware. Sometimes it's happy, sometimes it's not.Good luck.

With 1GB of RAM wouldn't it have issues with shared memory reducing overall system RAM available (don't understand the technicals behind it)?

The only thing Vista32 SP1 did for me was eliminate some of my OOM crashes when hitting 72%+ RAM usage on a 4GB quad core system. It didn't seem to have any effect on FPS or anything else, just baseline system stability (which is what SPs are really for).

That's really unfortunate. Another great piece of FS addon code goes into the sunset. Good luck to Helge and whatever he moves onto from here.

And my point was that during that 20 miles the wind gradually shifts over that arc, it's not 000 one minute and then a new station loads and it's 180 the next, which is what causes problems in FS.

When flying real aircraft turbulence and other sudden windshifts make the ASI bounce with dependable regularity. The issue isn't that shifting winds make the airspeed change, but that in real life you don't cross a mythical border from station KBOS to station KORH (for example) and have a wind shift in the order of 50+ degrees or 30+ knots. As you fly between those two points the windspeed changes and the direction changes gradually so there's no sudden jump, like loading a new reporting station in FS. That's where FSUIPCs smoothing functions kick in. Smoothing out those changes makes it much closer to real life, but still not perfect.

If you dial down to negative numbers, eventually the selected minimum display (either baro or radio) will disappear. You select whether you're using the radio or baro minimum based on the type of approach you're flying.

Those lines are auto-generated when you click "trust this module" during loading so the system knows that you haven't changed them. I think it's some sort of CRC to identify changes so some .dll with the same name doesn't sneak in without permission.