wims
-
Posts
2 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Gallery
Downloads
Posts posted by wims
-
-
I have this strange issue when I'm flying into KMCO on the CWORLD2 arrival. Somewhere within 5 minutes of passing KCHS (my last 5 minute FSUIPC autosave was pretty much right above KCHS) either FSUIPC or my weather engine is causing me some troubles, freezing the winds at what it currently reads. If turn off my weather engine and switch to clear skies in FSX's weather settings the wind is reduced to 0 for a short while before it steadily climbs up to the windspeeds it had before I chose clear weather. Opening FSUIPCs interface does not work, it simply ignores my clicks in Modules->FSUIPC. This has happened to me twice, once with the Maddog MD82 and once with the LVLD 763. I'm using a beta weather engine that *might* be the culprit, altho its strange that FSUIPC hangs and turning off the weather engine and switching to clear skies does not work. I'll inquire them about it. Does anyone have an idea what might be wrong, other than the weather engine?
W7 64
FSX SP2
i7 rock stable at 3.6ghz
GTX260
FSUIPC 4.6a
FSInn beta for FSX
Blueprint KMCO
UTX USA
GEX USA
(pretty much a repost from AVSIM)
FSUIPC hangup flying into KMCO
in FSUIPC Support Pete Dowson Modules
Posted
The weather engine is from a group called Flight Xtensions. They havent released any product yet as far as I know, this is their first product. Its still in beta. I mailed them about it and they said it did not use FSUIPC tho.
None of the other menus in FS were hanging, at least not the ones I tried (I tried the Level-D menu under the Modules menu, it worked fine).
I unfortunately didnt think about checking FSUIPC.log, I disconnected from VATSIM, restarted FSX from the last autosaved location and finished my flight, altho this time without the weather engine running. The flight finished without any issues. The log file I have now is from that last flight.
I might try to fly that route again when I got more time later, so I can take a look in the FSUIPC.log file.
-Wim