I purchased the MV-22B Osprey via Orbx Direct quite sometime ago. In fact, I probably bought it shortly after its release for MSFS. I flew MS FSX for almost 10 years and among the ridiculous amount of money that I spent on addons, (from aircraft to terrain, and weather to mesh… $$$$$ ), one of the aircraft was an MV-22 Osprey.
I can’t recall exactly which developer created and/or sold it, (maybe Virtavia?), but it was a fun, if not so precise, rendition of the plane. FSX’s notorious, processor-demanding code often hogged a lot from my custom-built system. The CPU back then (an i7-4790K OC’d to 4.9 GHz), could hold a solid 30fps but for the times, (circa 2014/16), the FSX MV-22 got along in that sim platform very well.
I don’t recall seeing very many updates for the FSX MV-22 back then but this Miltech MV-22B for MSFS 2020 seems to be getting an update every single time I open and log into my Orbx Central!
Seriously, I’m not at all exaggerating when I say that the MV-22B called for an update at least once everyday, since at least October 21st! Then today, (10-24-23), about 30 minutes ago, I opened ORBX Central and there was a notice for yet another MV-22B update!
I’m holding back because even though I know the daily updates were since 10-21-23, I really think I’ve had to update the MV-22B everyday since October 19th! However, I can’t be sure enough to stand on that date.
I’m beginning to wonder if maybe the update is simply repeating itself for some reason. Has anyone else noticed these daily MV-22B updates via the Orbx Central system?
Rich
I had a similar issue, even though I completed the Orbx update, then every time I switched on it told me I need to do the update again.
I had recently moved my community folder to a new drive and I think it may have been related to that …I had no other Orbx products with an update …so not sure if they would have been affected to!
I can’t now remember how I cured it !..sorry!
I am sure I must have removed it and a clean install of the MV-22 or something!
Some time ago, there was a small mistake made in the Orbx Osprey installer.
It was corrected some time ago as well.
Uninstalling and then removing any remaining Osprey folder before reinstalling
will fix the issue.
Anyone with this issue - Please uninstall the MV-22 completely, delete any folders in the community folder associated with the MV-22 and re-install. Indeed it seems something was changed on the backend that is resulting in this issue.
), one of the aircraft was an MV-22 Osprey.