February 11, 201214 yr I'm flying a route on vatsim KSTL CARDS7 BDF BENKY1 KORDWith center I was assigned direct BENKY climbing out of KSTL (prior to BDF)...I selected that in my FMC, and then manually entered the crossing alt of 100 at BENKY. Unfortunately the rest of the altitudes didn't fill in like they normally do. They still say FL290 (my cruise alt)What happened and why won't they fill in to normal altitudes with a descent profile like normal?It's not really a big deal I just do the mental math on the descent to benky... but the FMC should recalc right? | My Liveries | FAA ZMP | PPL ASEL | | Windows 11 | MSI Z690 Tomahawk | 12700K 4.7GHz | MSI RTX 4080 | 64GB 6000 MHz DDR5 | 500GB Samsung 860 Evo SSD | 2x 2TB Samsung 970 Evo M.2 | EVGA 850W Gold | Corsair 5000X | HP G2 (VR) / LG 27" 1440p |
February 11, 201214 yr I'm flying a route on vatsim KSTL CARDS7 BDF BENKY1 KORDWith center I was assigned direct BENKY climbing out of KSTL (prior to BDF)...I selected that in my FMC, and then manually entered the crossing alt of 100 at BENKY. Unfortunately the rest of the altitudes didn't fill in like they normally do. They still say FL290 (my cruise alt)What happened and why won't they fill in to normal altitudes with a descent profile like normal?It's not really a big deal I just do the mental math on the descent to benky... but the FMC should recalc right?is that the first time that it's happening? Daniel choen
February 11, 201214 yr It should indeed calculate this. This bug was reported once before. Its a shame that a PMDG plane has the same vnav bug as a captain sim plane lol! Johan Pettersen
February 11, 201214 yr Author It's the first time I've seen it happen... but this was the first time I did the route... so I can't be sure of the cause. Perhaps a factor is that when I put the STAR in it never calculated the crossing restrictions. All of the lines were blank. It is an RNAV STAR if that matters... | My Liveries | FAA ZMP | PPL ASEL | | Windows 11 | MSI Z690 Tomahawk | 12700K 4.7GHz | MSI RTX 4080 | 64GB 6000 MHz DDR5 | 500GB Samsung 860 Evo SSD | 2x 2TB Samsung 970 Evo M.2 | EVGA 850W Gold | Corsair 5000X | HP G2 (VR) / LG 27" 1440p |
February 12, 201214 yr It's the first time I've seen it happen... but this was the first time I did the route... so I can't be sure of the cause. Perhaps a factor is that when I put the STAR in it never calculated the crossing restrictions. All of the lines were blank. It is an RNAV STAR if that matters...I fly in the UK so i can't tell you about US but, for me it's working fine, maybe someone else can help you, guy's help this guy(: cheers Ryan. Daniel choen
February 13, 201214 yr Author Could just be a fluke! I'll try to make it happen again... | My Liveries | FAA ZMP | PPL ASEL | | Windows 11 | MSI Z690 Tomahawk | 12700K 4.7GHz | MSI RTX 4080 | 64GB 6000 MHz DDR5 | 500GB Samsung 860 Evo SSD | 2x 2TB Samsung 970 Evo M.2 | EVGA 850W Gold | Corsair 5000X | HP G2 (VR) / LG 27" 1440p |
February 13, 201214 yr Its not a fluke, it happens on certain routes, it was even confirmed by Ryan IIRC. Its been a while since I saw that thread tho, and I'm not going to try to dig it up. But its a confirmed bug. I do think it happened before SP1 or perhaps somewhere around shortly after SP1, so it is kinda surprising that it havent been fixed in one of the latest hotfixes.EDIT: Who am I kidding, I had to dig it up I believe this thread describes the exact same symptoms that you were experiencinghttp://forum.avsim.net/topic/352907-descent-profile-incorrect-when-star-has-six-altitude-restrictions-user-suspects/ Edited February 13, 201214 yr by Sekstifire Johan Pettersen
Create an account or sign in to comment