Brian Mackie

Mr BitstFlyer can consult AI, three monkeys, chicken entrails, tea leaves or the Dalai Lama for all I care - what counts is the result, and with AutoHaze, he most certainly delivered. I don't see any helpful products coming from the knocking critics in this thread.

Thanks, Davehibes. Our author came back and clarified that existing users should install both files (helper and lua) when they upgrade, so the question was useful. The other issue - multi-screen related - is being studied by MrBitstflyer, too. The number of pages in this thread illustrates 1) the level of users' interest in AutoHaze and 2) the author's unusual focus on making it even better for us. I'm hugely impressed. What he has achieved will, I hope, be noticed by the folks at Laminar Research.

May we invite a moderator to terminate this "discussion", which has strayed way off topic and into the realms of near-personal attack?

Duped. Ignore.

Feel free to help me, Davehibes. I don't have an issue with installing the latest version. Dead easy, and I was merely asking the author about the helper file. But maybe you know something about the multi-monitor observation. If so, please share. That's what this thread is all about.

For the avoidance of doubt, is the Helper exe required to reinstall? I've done that anyway, Windows having identified a tiny file size change... One curious thing I observe is that when enabling two smaller monitors for pop-out G1000 displays, when I go to FWL Macros>AutoHaze Settings, there is no AutoHaze settings box appearing on any of the monitors. When I disable the G1000s and the small screens and go back to a single monitor, the settings box appears on the main monitor. This only happens when I've assigned a pop-out instrument to the small monitor(s) in XP.. So, running two subsidiary monitors with no popouts assigned still results in the AH settings box appearing on the main monitor. Odd...

Complicated to set up? I'd advise you to either read the very short and simple guidance notes, or avoid this plugin.

The advantage of Windows, of course, is that you can run MSFS and XP on the same operating system, side by side. And you can try XP12 for free - it is light years ahead of XP11 in many respects. Whatever you do, try for as much VRAM as possible and don't stint on the CPU either.

I was wondering the same as GoranM. My AO does a pretty good job with Australia and NZ, but the ini file is the key to success or abject failure. Our OP might like to try Lyndiman's NZ orthos, all in ZL17 and rusing XP12 bathymetry. I couldn't find anything useful or downloadable on Australia. https://lyndiman.com/lyndimans-new-zealand-ortho-photography-set/ And neither AO nor Map Enhancement have the XP water effects. AO is also a work-in-progress, and users should expect to do some work installing updates (which aren't always right first time).

No sign of any pauses on first 10-minute tests. Just a momentary flash as we begin to load a new flight, which I'd expect. Looks like you've cracked it.

Great! Thanks again. The version is showing as 1.9, rather than 2.0...

As others have reported, I've now begun to experience the about-five-second freeze in X-plane followed by the Powershell pop-out (flashes by) and another second or so before XP resumes. Using the 1.9 version, at 300 second interval between checks (now extended to 900 to reduce the bother)..

My firewall already excludes the entire X-plane installation and the three calls display for less than a second each. Hiding them would be nice, but it's no big deal.

The mandatory updating of ANY software is usually bad for consumers - just ask anyone using Windows 11 who woke up one day and found Microsoft had unilaterally broken their operating system with a faulty update. I'm not quite ready to ditch Windows (it's getting closer), but avoid products such as MSFS like the plague.

Working well with the latest changes, but it would be good to hide the Powershell calls. They're a little distracting.