• 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 Tom Clayton has offered to post updates on AVSIM forums.

    Thank you for your support.

Simconnect

so just a thought...why not consider re-downloading your TacPack purchase from your VRS Customer Page... possibly updated, and re-install TacPack in your FSX-SP2/A or FSX-SE install; and perhaps the issue will resolve itself

per this thread, it appears simconnect was updated for FSX-SE: https://www.avsim.com/forums/topic/497361-fsx-se-installing-simconnect/ to v10.0.62615.0

and per this thread, it appears FSX-SP2/A has the simconnect you are struggling with: https://www.avsim.com/forums/topic/570908-the-bear-fsx-simconnect/ --> v10.0.61259.0 --> not the most up to date, and perhaps no longer compatible with TacPack??

cheers!
I'll give that a look & see if it helps, thanks.
 
And we finally have a solution!!

It seems W11 stores the simconnect.dll in a different place to W10; instead of it being C: ....... WinSxS it is now C: ....... WinSxS/Fusion! Quite why Tacpack struggled with that is a mystery. I copied the file over to FSX and ..... voila!

Thank you all for your help.
 
And we finally have a solution!!

It seems W11 stores the simconnect.dll in a different place to W10; instead of it being C: ....... WinSxS it is now C: ....... WinSxS/Fusion! Quite why Tacpack struggled with that is a mystery. I copied the file over to FSX and ..... voila!

Thank you all for your help.
Andy, do you think you could be more specific on the directories you copied the simconnect.dll from and to.

Thanks

Gary
 
Andy, do you think you could be more specific on the directories you copied the simconnect.dll from and to.

Thanks

Gary
I copied it from this path

"C:\Windows\WinSxS\Fusion\x86_microsoft.flightsimulator.simconnect_67c7c14424d61b5b_none_7a98ffdea9fe1e16"

directly in to "C:\Microsoft Simulator X"

It has only partially solved the problem as, when I tried to reinstall the F-18 Superbug it came with simconnect error again. I suspect the only sure way to fix this would be to move that whole x86.... folder directly into the WinSxS folder; however, as that is a systems folder I'll need administrative rights, which I will be looking at next.
 
Andy, I know nohing about either Tacpack or Simconnect, but I did wonder whether reinstalling the Superbug might have also installed another copy of Simconnect in another incorrect folder, and it was that copy that induced the error again.

Just thinking aloud - hope that might help . . .
 
I copied it from this path

"C:\Windows\WinSxS\Fusion\x86_microsoft.flightsimulator.simconnect_67c7c14424d61b5b_none_7a98ffdea9fe1e16"

directly in to "C:\Microsoft Simulator X"

It has only partially solved the problem as, when I tried to reinstall the F-18 Superbug it came with simconnect error again. I suspect the only sure way to fix this would be to move that whole x86.... folder directly into the WinSxS folder; however, as that is a systems folder I'll need administrative rights, which I will be looking at next.
Thanks Andy
 
Back
Top