Skip to content
View in the app

A better way to browse. Learn more.

The AVSIM Community

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

BillC

Members
  • Joined

  • Last visited

  1. As usual with Robert's updates, I'm looking at the a/c in the background and wondering what it is. Not that they've ever sneaked things into such preview shots before
  2. On redownloading the latest installers for the NGX I opened up the readme files (yes, I know that's an odd thing to do ) and spotted a rather nice typo which is a very Freudian slip considering the added complication (for PMDG) of the Steam release. There at the top of the Release Notes is a little one liner that simply says: "FSX-SE COMPLAINT FSX-SE" Nice one!
  3. The 757 is also HUGELY fun to fly thanks to being somewhat overpowered!
  4. I believe they overcame the B & S problem by using ATCO aero but adjusting the visuals to match B & S. The real issue was that they were struggling to accurately model the friction coefficient of the grass found in southern England which is more suited to the seam characteristics of the Duke cricket ball than for cylinder mower drag simulation.
  5. The simple answer to the question is: if you're given a frequency of 118.625 then just tune 118.62 and it will work. Simples. NB: As any Google search will confirm, I used to be the Director of the CIA. No security issues there then
  6. and not all volcanoes produce anti-aircraft ash! Gawd, the movies I've seen with impossible volcanoes in them....
  7. There might be more compliance if the rule were ENFORCED more often?
  8. I would suggest going to your stats on vatsim.net and review the flight in question since the stats server records every change to the flight plan and who or what made that change. This will help identify what is affecting your logged flight plan. On paper it would be impossible for FSInn to do anything with any file produced by ASN or the 777 and certainly not automatically.
  9. Scott, this happened to me a few times. If after typing the message and submitting it goes straight to the "new ticket" page then it seems your message hasn't registered and therefore no ticket number. I gave up in the end after several tries. A couple of other people have reported this and it seems that sometimes it works and sometimes it doesn't but I've yet to see an official response as to what's causing it.
  10. How did you fix it? This happened to me when the 777 was released and I never found a way round it.
  11. A fair few peoople in here havn't really read what the OP actually said and are assuming what the problem is. My emphasis below: So it's not your FSInn setup since it works ok with other planes. You also say below that FSInn recognises you're transmitting so you shouldn't need to go tinkering with FSInn, PTT's etc. First question is, can you hear the controllers? With mine you can't hear the controllers until the correct mic switch is on so if you CAN hear them then you've probably got the correct mic on and set to COM1 on VHF L. Can I suggest you pop up a screenshot of your radios panel?
  12. I honestly suspect that your problems with this lie elsewhere on your systems. I've been using FSInn with FSUIPC autosaves every 5 minutes with PMDG products (737 v1, 747, JS41, NGX, 777) for years and it's never ever kicked me off Vatsim nor indeed killed the flight in other ways. I wouldn't know where to start looking on your systems I'm afraid but I can promise you that there's nothing in this combination that automatically kills your flights or connections. I've not used SB for about 10 years though so can't speak for that.
  13. Will it have a 2D cockpit?
  14. If you use the cockpit in full screen try switching to windowed, load FSInn then go back to full screen. It works for some but it's a workaround for a problem somewhere else though. NB: Re the advice to load another a/c first, PMDG do not recommend loading other aircraft before one of theirs.
  15. I was getting this on every other flight but since doing a reinstall and rebuild of my custom panel state I've not seen it once. My original custom panel state was built from C&D but the new one was done from the default start-up state. I'm not saying I've cured it but it's certainly not (yet) happened across a number of flights so it's happening a lot less if at all.

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.