• Please see the most recent updates in the "Where did the .com name go?" thread. Posts number 16 and 17.

    Post 16 Update

    Post 17 Warning old domain name stealing credentials

  • Special Server Maintenance

    Just when you think you have everything running some what better...

    You get a message from the Hosting company. Short story they need to move us to a new server. I have been working with them to plan a good date for all concerned. Here is what we have come up with as a schedule.

    1. November 4th 17:00 -5UTC shut off the forums and start backup proceedures. During this time there will be no access to the forums or the Resource Section.
    2. November 5th Continue with Backups and download same until complete.
    3. November 6th 7:00 turn over server to hosting company to move system to new server
    4. November 7th - 8th restore backups and upgrade forum software.

    If all goes well we should be back online on November 8th.

    To keep you updated we will post updates on AVSIM forums.

    Thank you for your support.

Getting FlyInside VR to work in Windows 11

K5083

SOH-CM-2024
I don't know if anyone else needs to hear this, but maybe there is someone out there who also has tried to get FlyInside VR working with FSX Steam Edition after upgrading/updating Windows 11. It took me a while to figure out the issue so I'm posting here to help any others.

If you upgraded to Windows 11 or updated Windows 11 after January 2024, and have since tried to run FlyInside, you probably got an error message like:

FlyInside Fatal Error Encountered (W:2)
Utils\Process.ccp: Line 1184

... followed by some useless stuff about posting your crash log to a FlyInside support forum that no longer exists. If you inspect your crash log, you'll find the last 3 lines are:
5.29848 Licensing\License.cpp 108 WMIC not found, reverting
5.29878 Utils\Asserts.cpp 48 FlyInside Fatal Error Encountered (W:2)
Utils\Process.cpp: Line 184

So "WMIC not found" is the issue. What is WMIC? It's the Windows Management Implementation Command-line executable, and it has been deprecated by Microsoft since Windows 10 v21H1; however, it was still available to the computer as a command-line executable until the Windows 11 update of January 29, 2024.

The good news is that as of this writing, WMIC can still be enabled as a "feature on demand" from within Windows settings. Here is a blog post about how to do it.

A caution about this is that it can take a long time, like 20 or 30 minutes, for Windows to install this little 600k file, so don't panic, be patient and let it finish.

When it is done, try FlyInside again. You should find that the error is cleared and you can use VR in FSX again.

That's the good news. The bad news is that at some point, Microsoft plans to eliminate the ability to enable WMIC at all. So any future update may brick FlyInside permanently. There's no telling whether there will be a workaround after that, such as someone offering a WMIC emulation utility. So, enjoy FSX in VR while you still can!

I assume that this also applies to FlyInside VR support for Prepar3d v1-3 before it got native VR support, but I don't own those so I don't know.

FlyInside is now given away for free, the support forums are gone, and we can safely assume that it will not be patched to do away with the WMIC dependency.

August
 
Back
Top