Don Desfosse

Congrats! Enjoy this New Life!

My very strong suggestion is that if you cannot do the entire flight online, in attendance, DO NOT sign up for a slot and preclude someone who can actually meet the requirements of the event (which is indeed to be in attendance throughout, with allowances for short, say 5-15 minute breaks, IF approved by ATC, in the middle of the flight). All that said, it really depends on what you mean by break. If it means getting up, walking around within a few feet of your chair, keeping audio volume up (or wearing a wireless headset) so you can hear, run back to your chair, and respond to ATC, etc., that's in the spirit of attending your connection. If it means going upstairs and taking a nap, or going across the house to your favorite couch or armchair, that doesn't work.... In the event that your breaks are more significant than stretching your legs within a few feet, into the next room, etc., but you can still monitor audio and run (or jog) back to respond, I offer the following additional thoughts. If you're trying to get ATC at both the beginning and the end of your flight, my next suggestion would be to try to take of very early, perhaps 10-30 minutes before the first slot time, or very late, perhaps 2-2.5 hours after the last slot time, when your reconnection will not make such a huge negative impact on the controllers trying to work the swarm of aircraft. You're not guaranteed ATC outside of the "normal" event times, but I can tell you that just reconnecting "blind" in the middle of a swarm of traffic could easily get you removed from the network, and possibly even given a 24 hour suspension if you push the point with repetitive reconnects. Otherwise, if you are only really interested in a takeoff during the swarm, fly with the swarm for a bit, and then a disconnect, you could participate as a non-slot aircraft. Though we don't usually have extra delays for non-slot aircraft at Boston, VATSIM always warns non-slot aircraft to expect significant delays. Some facilities enforce the slot times for slotted aircraft rigidly, to the exclusion (read delay) of non-slot aircraft. Boston is much more capable and forgiving than most....

Ah, excellent Claude!

Claude, did you move your .bgl files to \addon scenery\scenery\ or to the program's \scenery\ folder? You should have moved them to \addon scenery\scenery\, and you should NOT have made any extra entries in FSX pointing to the RNAV update .bgl files. If you did make any extra entries in FSX pointing to the RNAV update .bgl files, you should delete them.

My pleasure, Claude. Just to confirm, all is working now?

\addon scenery\scenery means that under the \addon scenery folder, there is another sub-folder called \scenery The full path, if you were copying files via Windows, might look like: C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\Addon Scenery\scenery\ Herve's installation instructions, on the right side of the Fixes page, are very clear and simple. He even includes a link that takes you to a step by step guide. Bottom line: if you only put your files into \addon scenery\, FSX will not find them on its own. You need to move them to the \scenery\ subdirectory (e.g. C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\Addon Scenery\scenery\) for FSX to find them automatically. Alternatively, you could put them somewhere else, but then you'd have to add that new area within the FSX scenery library. I would recommend the former; make sure the .BGL files are in the \scenery\ subdirectory (e.g. C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\Addon Scenery\scenery\) (move them if necessary). Hope this helps.

Yes, you understood perfectly. If you put your BGL files in \addon scenery\scenery, I would have thought they would have worked. I also have not used FSX in a while and do not have it on this machine, so am shooting from (aging) memory. To be sure, though, you put your BGL files in \addon scenery\scenery, and not just \addon scenery, correct?

Great. And I apologize in advance for the next questions, but we've had folks download the update and not actually install it in their sim, not realizing it, so I'll ask.... 1. Which file(s) did you download and try to install? 2. Where (on your computer) did you put the .bgl file(s) that you downloaded 3. If you placed the file in a unique folder (i.e. NOT in /addon Scenery/scenery), how specifically did you install it in your sim? 4. Which sim are you using?

Hi Claude -- sure is, thanks. Hmmm.... So far, sounds like you've done things right, so not necessarily an easy answer. Can you give an example of which fix(es) on which procedure(s) you were not able to use? Are you sure you've downloaded and installed the most recent version (current cycle is AIRAC 1906, Effective: 23-May-2019)?

Hi Claude, A couple of questions to help troubleshoot -- 1. What is the B637? Who publishes it? 2. What navigation source does it use? 3. When you say you download a nav update, which nav update do you download?

Never Dispute the excellence of our students and training programs (and puns). Congrats, ND!

As is the norm for Boston, a great, great event by great, great controllers that did a fantastic job. Really impressive that with 3 airports in play, Boston still had 60-65% of the overall event traffic. That's really telling!

I just have to thank Perrone for having the OIs PN. As I get older, my ears would have a wicked hard time trying to separate BN and PN.... :) Congrats, PS.

Congrats, NU! Now it's time to get really smart in preparation for becoming an Instructor. NUthing teaches you more than when you are teaching!

Also, just checking, if you're concerned about the number of non-liveried aircraft, did you try the steps in the installation guide to troubleshoot? http://flaicdn.bvartcc.com/version/FLAi_vPilot_Post_Installation_Guide.pdf