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.

Brian Mackie

Members
  • Joined

  • Last visited

  1. Why should mjrhealth or the rest of us "look in other" unspecified "locations"? Where are they? Your problems appear to be uniquely personal. Provide more evidence if you want to be helped. Or keep those problems to yourself and waste nobody's time.
  2. You may have been using something else in XP11. AutoHaze only got released this year. I'm a huge fan.
  3. You can. Easiest method is to create a duplicate copy of the program. If you do a fresh install, you need to copy over the preferences. Google AI says: n X-Plane 12, your joystick profiles and keyboard mappings are handled through a modernized system located in your main Output/preferences/ folder. Exact File Locations in X-Plane 12 Device Profiles & Joysticks: Output/preferences/control profiles/ Every time you create a custom joystick or hardware profile in X-Plane 12, it is saved as an individual .xml file inside this folder. Keyboard Assignments: Output/preferences/X-Plane Keys.prf This file stores all your global keyboard shortcuts. Active Layout Mapping: Output/preferences/X-Plane Controls.prf This file tells X-Plane 12 which specific hardware profile is currently active or mapped to each of your plugged-in devices.
  4. "Also odd that you refuse to offer specifics about why you retain Autohaze." says blingthinger. Where did I refuse to offer specifics? Nowhere. I merely said I preferred the AutoHaze solution to the XP beta's initial offering. Blingthinger, you could easily test AutoHaze yourself, and compare it with the LR beta solution, but you do not, excusing yourself as a confessed "plugin minimalist". This discussion seeks to involve users of AutoHaze who are testing the latest XP beta. It asks them whether or not AutoHaze remains relevant. Since you do not use AutoHaze, your comments are so far - at best - irrelevant, and - at worst - mischievous. You raise doubts about my experience as an aviator, and I quote "tossing out a claim of PPL (which everyone should think twice on because this is the world wide web with ai and all) does nothing to boost your credibility" but you did not search for the proof. Others will. I doubt that their findings will boost Blingthinger's credibility. With the greatest respect, you are coming across as an argumentative time-waster. I hope that a moderator will put this discussion back on track.
  5. I could flick you the last page from my flight log book, but we're not going into your rabbit hole. You can Google "Brian Mackie, New Zealand pilot" yourself. The headlined question remains: Is AutoHaze redundant now? I think that it is not. What do you think?
  6. You need to move Global Forests V2 down to beneath the Xworld listings. AEP probably needs to go above Global airports. OpenSAM Library should go below your Xworld stuff. Best to group libraries, for ease of viewing and checking. Your Sydney Landmarks may be interfering with your Sydney ORBX package. Try disabling the landmark. SCENERY_PACK_DISABLED Custom Scenery/X-Plane Landmarks - Saint Louis/ - cut and paste this with your other landmarks, just to be neat and tidy. Agree, those meshes were probably not helping. Meshes and overlays are usually not needed when running XWorld. XOrganiser is fine, but most useful with a good understanding of scenery.ini ordering. I recommend the ORBX Melbourne package, if you're into Oz. Great rendition. Add Live Traffic at your peril. Unless you really know what you're doing in a tubeliner, you'll be so busy you'll wish you'd stuck to a Cessna 172.
  7. Thank you. I had no involvement in the "smelling a rat" dialogue apart from flagging it as off-topic. Hopefully, the question I originally asked will continue to be debated. Sticking strictly to the headline subject helps to avoid misunderstandings, agreed?.
  8. I believe you, but I'm not sure what you were expecting in terms of help. Nevertheless, my most insincere apologies. As a realtime pilot since 1985, I know what to expect to see out the window. AutoHaze delivers it.
  9. Uncertain as to your question. Can I see the haze directly beneath the aircraft when above the layer, with AH disabled? Short answer is that the XP haze was so awful with AH disabled and just using the 4.4.4 beta, I stopped looking and re-enabled AH. Which looks much more realistic running in the beta. TBC, after your time away.
  10. Enough carping, please? This is getting off-topic. FWIW, I have tried XP 4.4.4 with and without Autohaze, and IMHO, Autohaze is superior. So it's staying put on my rig.
  11. Which begs the question asked elsewhere on this forum.
  12. In ‘What’s new in 12.4.4’, Marco states: "Visibility with Altitude Finally, a change you’ll notice on nearly every flight into marginal weather. Visibility previously faded from the ground-reported value to clear-air visibility over a fixed 5,000 to 15,000 ft ramp. It now uses a physically derived altitude band, estimated from the temperature and dewpoint spread, cloud layers, latitude and season. The practical effect: fog, mist and haze now stay in a realistically shallow surface layer, instead of hazing your view all the way up to cruise altitude. Departing into a foggy morning and breaking out into genuinely clear air is one of the more satisfying things in real flying, and it now works properly here." Does this render Autohaze redundant? FWIW, I kept Autohaze on the system and the beta didn't seem to affect anything; but it's early days.
  13. Yes, that's the correct file. Might be better to discuss this via a PM or starting a conversation via email. I am at [email protected]
  14. If you are seeing random trees etc where they shouldn't be, it's probably something amiss in your scenery.ini file. Post it here and we'll take a look.

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.