June 25, 200520 yr I have been widely using RC3.1 2272 but lately I have noticed that when getting near approach (not all the time) it very weirdly directs you in a -90
June 26, 200520 yr Moderator Pedro,My guess is that you are not reaching the crossing restriction in time. Unless you are at 10,000ft, 40 miles from your destination airport you will be given a heading change which effectively puts you into a turn until you reach 10,000ft. Remember to adjust your altimeter when descending through 18,000ft. That will make a difference.Can you upload your flight plan so we can try it? Does it happen with all your flights or only with KDTW-KORD?It isn't necessary to include a VOR as your final waypoint. Anyway, let's see your flight plan and we can take it from there.Cheers, Ray (Cheshire, England). System: P3D v5.3HF2, Intel i9-13900K, MSI 4090 GAMING X TRIO 24G, Crucial T700 4Tb M.2 SSD, Asus ROG Maximus Z790 Hero, 32Gb Corsair Vengeance DDR5 6000Mhz RAM, Win 11 Pro 64-bit, BenQ PD3200U 32” UHD monitor, Fulcrum One yoke, Fulcrum Throttle Quadrant. Cheadle Hulme Weather website.
June 26, 200520 yr Thank you for your responseHere is the plan (I have also uploaded):flightplan]title=KDTW to KORDdescription=KDTW, KORDtype=IFRroutetype=3cruising_altitude=24000departure_id=KDTW, N42* 12.43', W083* 20.55',+000640.00departure_position=3Ldestination_id=KORD, N41* 58.46', W087* 54.15',+000666.00departure_name=DETROIT_METRO_WAYNE_COdestination_name=CHICAGO_OHARE_INTLwaypoint.0=KDTW, A, N42* 12.43', W083* 20.55', +000000.00, waypoint.1=DUNKS, I, N42* 25.38', W084* 11.39', +000000.00, J70waypoint.2=ALPHE, I, N42* 26.09', W084* 30.35', +000000.00, J70waypoint.3=PMM, V, N42* 27.55', W086* 06.20', +000000.00, waypoint.4=PIVOT, I, N42* 20.13', W087* 06.56', +000000.00, waypoint.5=PAPPI, I, N42* 16.11', W087* 36.25', +000000.00, waypoint.6=KORD, A, N41* 58.46', W087* 54.15', +000000.00, I indeed respected the restriction I was at 10000 before PIVOT which is more than 40 NM from KORD. In any case I did not received any remark that i did not respect that restriction. I also changed the the QNH when at 18000. I will re-do the flight and check very precisely. I will add ORD in myflight planIt hasalso ocurred with other flight plans
June 26, 200520 yr Moderator Pedro,I'm about to start this flight so I'll get back to you once I've landed at KORD.Cheers, Ray (Cheshire, England). System: P3D v5.3HF2, Intel i9-13900K, MSI 4090 GAMING X TRIO 24G, Crucial T700 4Tb M.2 SSD, Asus ROG Maximus Z790 Hero, 32Gb Corsair Vengeance DDR5 6000Mhz RAM, Win 11 Pro 64-bit, BenQ PD3200U 32” UHD monitor, Fulcrum One yoke, Fulcrum Throttle Quadrant. Cheadle Hulme Weather website.
June 26, 200520 yr Moderator Pedro,I've now completed this flight without problem. I am using RCv4 but the only difference in regard to the approach is the altitude you are required to reach 40 miles from the arrival airport. In my case it was 12,000ft.It may help to see the route I flew. The first JPG shows my departure from KDTW and you can see I flew the runway heading until I was given a change to fly to the first waypoint - DUNKS.The arrival route may help you see what's happening. Before reaching PAPPI I am under Approach Control and am given a heading change for radar vectors to KORD Rwy 32R. I fly the headings given to me by App and as you can see they vector me correctly for 32R.I crossed PIVOT at 12,000ft which equates to your 10,000ft and as you say you didn't get told off for missing that restriction then RC was happy with your altitude.I hope this helps you. If you have any questions please get back to us.http://forums.avsim.net/user_files/120712.jpghttp://forums.avsim.net/user_files/120713.jpgCheers, Ray (Cheshire, England). System: P3D v5.3HF2, Intel i9-13900K, MSI 4090 GAMING X TRIO 24G, Crucial T700 4Tb M.2 SSD, Asus ROG Maximus Z790 Hero, 32Gb Corsair Vengeance DDR5 6000Mhz RAM, Win 11 Pro 64-bit, BenQ PD3200U 32” UHD monitor, Fulcrum One yoke, Fulcrum Throttle Quadrant. Cheadle Hulme Weather website.
June 27, 200520 yr Thank you Ray:That is indeed a very well done support, Thank you very much.I think your first response iscorrect itmight be that the previous times I did not respect the crossing restriction asI re-did the same as you without adding ORD in the FP and did not have any problem as before so that might be the reasonNevertheless I suggest that problem needs to be adressed in the new version as it is quite possible not to fulfill the restriction and in that case the program gets lost. I am waiting as much as the other fellow users of that marvelous program for the new version, By the way I am a user since RC99.....Thank you againPedro
June 27, 200520 yr Moderator Hi Pedro,I'm glad the JPGs helped. Sometimes they're easier than trying to describe everything :-)I don't have v3 installed so I can't check what happens if you can't make the crossing restriction. There might be an option to advise you can't make it and if there is one then use that. Otherwise if you're less than 1,000ft above 10,000ft just ignore the heading change and once you're at 10,000ft you should be handed over to Approach. I'll check what happens with v4 in this situation. I always make my CRs of course ;-)We are progressing well with v4 beta testing but the decision as to when it's released remains John's of course :-)Cheers, Ray (Cheshire, England). System: P3D v5.3HF2, Intel i9-13900K, MSI 4090 GAMING X TRIO 24G, Crucial T700 4Tb M.2 SSD, Asus ROG Maximus Z790 Hero, 32Gb Corsair Vengeance DDR5 6000Mhz RAM, Win 11 Pro 64-bit, BenQ PD3200U 32” UHD monitor, Fulcrum One yoke, Fulcrum Throttle Quadrant. Cheadle Hulme Weather website.
Create an account or sign in to comment