I have asked about this once before. Apparently there was corrupted data before. I still cannot program VOR “ACO” Akron, OH, US, or program anything but visual approaches for KCAK. The approach data is available for nearby KAKR. I have the same issue regardless of aircraft or GPS.
Hi Nick,
I can confirm that you receive no signal for ACO VOR (on 114.40) at KCAK, but you receive a signal on KAKR. I have tested this with our dataset and also with the stock data from ASOBO/MS, and in both cases, the result is the same - no signal at KCAK. So, it appears to be a bug in the simulation. Please report this in the MSFS forum.
Your second report about the missing approaches for KCAK is not reproducible. I have all approaches available:
Awesome!! Thanks for checking it and responding so quickly. I do have an add on for CAK. I thought the ACO and other local VOR issues were related to the missing CAK approaches. I also thought that the AIRAC data took precedence in the community folder. I will disable my CAK add on and see what happens.
Again, thank you!!
Hi again Nick,
I will also create a ticket in the MSFS Development forum regarding the ACO VOR, as it appears to be a bit off.
To your 3rd-party scenery:
To rebuild the content file first (as in the FAQ) before removing the scenery. When this does not help, you can remove it afterwards.
Is this a freeware or payware scenery? Could you please provide the developer/scenery name? Then I can look if this is a scenery issue or any other issue.
I have researched and experimented a little. First, I just disabled the KCAK scenery in the library. Instantly all of the approaches were back in the database. The scenery I am using is the payware Fly2High KCAK airport. Based on some misc posts. This is a common issue with all of the Fly2High airports. I do not want to sound negative toward the company. Their airports are absolutely beautiful and realistic. I fly out of CAK and they nailed it.
Tonight I will let FS rebuild the context file and report back.
Thank you for your follow up.