No Available Departure Runway At Vancouver International Disable VoxATC message appears every time I attempt to load FSX at that departure location. I'm using Vancouver Plus and CYVR5+ addon scenery. The problem doesn't exist at any other aerodromes so far. I've been using Vancouver Plus for some years but the CYVR5+ is a relatively recent addition. I'm assuming there is a conflict there some place but where? I'm rather loathe to delete and re-install either VoxATC or CYVR5+ if there is a work-around.Seems to me there was a post on this subject some years ago but I can't find it now.Anyone know the answer to the problem.Thx.Sox.

Wow, I've never seen that, so I can only guess in the dark...What are the runway numbers that your scenery uses? If they've changed (e.g., if what is now 08L and 08R was 07L and 07R) then it could be that the available SIDs don't match the runways.Also, could you look in the scenery BGL to see if your runways are marked as not available for departure / landing? (I doubt this would be the case.)Regards,

Hi Fenric:Thanks for the input. I'll have a look at the rwy nos. Also, I agree with your thought on the BGL files. I'll be into the files tomorrow (too late tonight) and have a good look. My gut feeling is to uncheck CYVR5+ in the scenery files and see if that solves the issue. Of course, if I make any changes I'll have to re-run the VoxATC indexer. When I eventually solve the issue I'll post for your perusal.Sox.

There's a small tool located in the VoxATC folder which could address such runway heading based error sources. It's called RunwayNumberUpdate.exe.From the manual

Runway Number UpdateThe numeric part of a runway designation, for example ‘27’ in the designation 27L is assigned based on the magnetic heading of the runway (rounded to two digits). A runway with a magnetic heading of 273 will be assigned 27, one with a magnetic heading of 023, 02. Over time, the magnetic heading of a runway can change as the locations of the magnetic poles vary. This can require that certain runways must be assigned a new numeric designation. An example of this is EGSS (London Stansted). The default FSX scenery designates the runway at EGSS as 03/23. This has now been changed to 02/22.While irritating, this is not a significant until SIDS/STARS from the Airac cycle (Navdata) are used. Many of these procedures are assigned to particular runways using the runway designations. VoxATC may be unable to assign the correct SID/STAR if the runway designations have changed. To remedy this, you can use the Runway Number Update Utility.

Maybe it helps if the behavior you're describing just happens at some airports and not in general. So run the indexer and then the little tool to check for deviations.

From the manual

The default FSX scenery designates the runway at EGSS as 03/23. This has now been changed to 02/22.

02 / 22??Would that be the world's first boomerang-shaped runway? :(

There's a small tool located in the VoxATC folder which could address such runway heading based error sources. It's called RunwayNumberUpdate.exe.From the manualMaybe it helps if the behavior you're describing just happens at some airports and not in general. So run the indexer and then the little tool to check for deviations.

Hi:Thanks for the input. Sounds like that might do the trick. Unfortunately the tool you referred to does not appear to be in my version. Time to update anyhow. I'll update and see where I stand.Thanks,Sox.

Hi Guys:Thanks for the input. I upgraded to version 6.04 yesterday and now all is well. I guess we'll never know precisely what caused the problem but I suspect that if the "tool" had been in the earlier version it would have fixed the issue.Sox.

Sox, I have to apologize since I seemed to have interpreted your original post in the wrong way.Whatever the problem in the older VoxATC version was, it wasn't related to that tool in my eyes since "No Available Departure Runway" shows that there isn't any runway to use (in VoxATC's eyes), regardless of the actual rw heading. So maybe this update of yours fixed a bug or known problem with that scenery since the development from version 5 to 6 surely included fixes and improvements under the hood and without showing up on the "new features" log.That tool actually just helps you running a complete scan of the Navigraph descriptions and then scanning your scenery for misplacements (having the Navigraph data in mind). So it doesn't implement a new function (you could do this manually, it would eat up time though) but enhances the comfort of the usage by a big margin.So, as you see, it's clearly oriented on the version 6 only feature of using Navigraph data because a misalignment there can cause no SIDs or STARs to be available. It can't, by design, help you on the "No Available Departure Runway" issue and my misinterpretation of your post sadly left this fact out.But I'm sure you weren't harmed when going from 5 to 6 on VoxATC. The new version with Navigraph support really is an improvement in my eyes and you can still read my critics on #5 around here while #6 cleared them up and made me smile about that buy. Apart from flying online, I'm only using VoxATC and forgot about all other ATC addons of mine. I couldn't say that 100% of my offline flights work flawlessly but the amount is high enough to be confident about it and to investigate on the remaining issues then.Keep this forum section alive with posting about your findings. :(

Hi:Thanks for taking the trouble to reply. I guess I'll never know what happened there but then again I'm not technically minded enough to spend anymore time on it. All I really want to do is fly and leave the technical stuff to those who understand it.Interestingly, that particular issue only appeared after I rebuilt my system and updated the scenery files. I hadn't flown out of CYVR for some time so didn't notice the problem until recently. That issue never appeared at the other aerodromes. I did a long trip along the BC Coast and then inland, eventually landing @ Calgary....that problem never showed in any of the multitude of aerodromes (waterdromes)I used...and there were lots of them.Happy flying,Sox.