I'm not finding VOX's log file showing ATIS info (just whatever is in %appdata%\Internal Workings\VoxATC P3D 5i), but perhaps the steps to reproduce the problem will be of use to you:

1) Logon to SimBrief and create a flight plan for KDEN to KMSP as follows:   

KDEN CHUWY1 CHUWY..KD75A..SSWAN TORGY3 KMSP

2) Use SimBrief to export the flight plan to P3Dv5 format (PLN);

3) Start P3Dv5 and load the flight plan, placing yourself at Gate C24 (any gate will likely do the trick, except VOX's taxiway instructions to RWY 07 will be different).  Not all current RW gates may not all be available with stock scenery.  Again, I'm using FlightBeam's KDEN;

3) Set weather (manually via P3D, if necessary) with winds out of the east;

5) Start VOX, listen to ATIS indicating RWY 07/08 are active for landing and departures, run thru the instructions, and then upon receiving taxi instructions, notice that, rather than being assigned RWY 08 (which is called for with a CHUWY1 SID), RWY 07 is assigned "via charlie sierra hotel alpha...".

As originally stated, at least with AIRAC 2010 (EDIT: same situation with AIRAC 2012 rev 1), CHUWY is not an available departure for RWY 07.  You can verify this by checking VOX's Procedure Pronunciation Editor showing RWY 07 is not an available runway for CHUWY1.

If I can be of further assistance, please let me know!

-Tim

Btw, I do notice that at least I can press 0 and request a different RWY than the one assigned by VOX.  That'll work for me in the meantime.

Edited November 17, 20205 yr by tjahns

If you want to separate logfiles for every comm frequency at all nearby airports and all AI aircraft, you need to turn on logging in Advanced settings. 

22 hours ago, tjahns said:

the steps to reproduce the problem will be of use to you:

Tim

I'm curious enough to "check" what I can, if only to "prove" my thoughts on how Vox does or does not assign SID's at more complex airports than my regular's.

Will be a week or so as I'll need to "re-install" FB's scenery etc.

 

I guess I should add (for completeness) that the .PLN file I loaded (for CHUWY1) included SID waypoints for departure to the north (not east), i.e. the waypoints CAAZZ, then YOKES, then LNGWD, and then CHUWY before continuing on to KMSP via KD75A, SSWAN, etc.  As stated above, the flight plan I used was generated by SimBrief.  If I interpret VOX's documentation correctly, intermediary waypoints do not matter, only the waypoint at the end of the SID (i.e. in this case, CHUWY)?

39 minutes ago, tjahns said:

intermediary waypoints do not matter

Tim

I'm not sure of that ..... I have never included SID / STAR  legs given one can have different SID's to the same en-route fix (start) from the same or different runways at many airports (& should weather be different to expected).

Including legs may thus be confusing for SID assignment ....... others may know more though.

Edited November 18, 20205 yr by vadriver

From the VoxATC "Help" manual...

Flight Planning and SIDs and STARs
To be assigned a SID or STAR, your flight plan must have some waypoints that correspond with
waypoints in the SIDs at your departure airport and/or STARs at your destination. The assigned
procedure may vary depending upon the runway in use.

Apparently "intermediary waypoints do matter" is supposed to be true, as long as (according to the Help manual) the flight plan contains "some waypoints that correspond with waypoints in the SIDs".

On a related note, I had another frustrating experience last night departing out of FB's KMSP.  Initially I was assigned RWY 12L for SCHEP 9 SID.  For what I think is more realism (see another post on this topic re parallel runways earlier today), I pressed 0 (I had to read back taxi instructions first) and switched to RWY 12R (the longer, closer departure RWY, which has the same SID waypoints as RWY 12L), which has the same SID waypoints.

Now, Clearance Delivery gave me SCHEP 9 (per the waypoints in my .PLN) but after takeoff I was given "Proceed Direct" ATC instructions to each of the SID waypoints, and (even more frustratingly) I was never cleared to climb above the initial altitude of 6,000.  (So there I was cruising along at 250 kts for about 50 miles at high speed not to far above the terrain before I closed my simulator).  It's possibly relevant to the problem that SCHEP 9 begins with a vector to the initial waypoints?

I dunno, I really want to use VOX, but these glitches are really killing my sense immersion.  That, and I'm constantly having to repeat myself (and this is after numerous voice recognition training sessions).  Sometimes screaming obscenities at VOX will get it out of a stuck loop and continue along to the next step, particularly with taxi instruction readbacks.  Perhaps it's just FB's scenery causing these issues, but that's what I like to fly, i.e. highly detailed airports (and I've got a "monster" rig that will handle it)!

-Tim

On 11/17/2020 at 12:17 PM, jabloomf1230 said:

you need to turn on logging in Advanced settings. 

Tim

the log file is "err.log"

5 hours ago, tjahns said:

That, and I'm constantly having to repeat myself

I'm surprised you are not using the pnf (copilot) feature in the B737.

Seems like the problem that occurs after requesting a different runway with a previous SID assignment. Do you get the same problem if you depart on the originally assigned runway? Get in touch through the VoxATC.com contact form if you're still having trouble

Could have just been a glitch with FB's KMSP because I just now departed KPHX on KEENS2 with a different (parallel) RWY than assigned (I requested RWY 07L instead of the assigned RWY 07R) and proper altitude assignments were given by VOX.  I guess I'll report any further difficulties via the contact form.  Thank you.

 

5 hours ago, tjahns said:

Could have just been a glitch with FB's KMSP

Tim

I believe you are "correct".

Many including me have noted that when an "originally assigned runway" SID includes "above altitude" restraints higher than the +6,000'agl initial altitude called by VOX, further step climbs are significantly delayed. Deleting those restraints from VOX's airac solves the "anomaly".

There is also an "anomaly" if the SID has an "at altitude" restraint higher than that initial altitude (despite the VOX departure clearance assigning the SID without an initial altitude ..... ie one expects to climb to that  "at altitude" before further steps to TOC), in that VOX reverts to issuing step climbs below that when one contacts departure.

& yes, VOX needs a "strategic tweak" at the moment to work fluently ....... but maybe, using an airac written for Vox & not an aircraft would be a solution (it's essentiallly what I do when you think about it).

Edited November 21, 20205 yr by vadriver

On 11/17/2020 at 9:09 AM, tjahns said:

the steps to reproduce the problem will be of use to you

Tim

Have some "tests" to report after a "fresh" install of FB's KDEN. ........ where the afcad has all runways open to both take-off & landings.

So using the plan without SID's & a 130^oT/04 wind, ATIS called 07 departure. 08 arrival, accepted a clearance to match & departed / maintaining runway heading for about 40nm before a "direct to chuwy" by Vox. (did expect a heading to set on the take-off clearance though). AI were using those runways appropriately & none of the others.

Then I tweaked the afcad to stop 07 departure / 08 arrivals. That "flight's" ATIS called (with the same wind) what I expected, 08 depart, 07 arrival.

Bottom line remains my believe that with afcad tweaks, Vox will respect & give you what you "prefer", even downwinds ..... even to the point of saying Vox "needs" user help to manage these large hub airports  (much as you can read about at AIG for any ATC engine)