September 30, 200916 yr Hello allFSBuild forum is down, so thought I would ask here.I am having a problem with FSBuild v2.3 (with the latest patches). I have processed a number of flight plans without hitch, however the following plan causes a crash to desktop when I hit the print button and it reaches the final page.I managed to avoid the CTD by de-selecting the "Append TELEX" option. Although now it will print without an error message, the resultant printout is scrambled. The flight plan along the top of the navlog does not wrap to the page (rather it continues off the page), and the following lines are all out of Tab.By playing around, I found out that it is the Atlantic coordinate waypoints that cause the problem. By removing them, the plan will print without a problem. I tried entering them in the following formats: 50N50, 50N050W, and 5500N/05000W. In all cases, the plan will process properly, the coordinates will show up as waypoints, but they will not print! Other trans-atlantic flightplans I have tried with coordinates further south have worked - could this be a problem?Here is the plan: EGLL CPT UL9 KENET UN14 MEDOG UL18 MIMKU UP6 OSBOX UP858 SUNOT 5800N/02000W 5800N/03000W 5700N/04000W 5500N/05000W OYSTR STEAM N220B TAFFY ENE BAF J77 PTW J48 MOL J22 VUZ JAN AEX DAS7 KIAHAny help greatly appreciated Rob BatesSimming since the age of 10 with MSFS 5.0 P3D v5.0 | 10700K (@stock) | EVGA GTX1080Ti SC2 | Z490-E ROG STRIX | 32GB 3600MHz | 970 EVO Plus M.2 & EVO 850 SSDs | H115i cooling | NZXT H440 Case | Samsung 32" CJG 1440p Curved Monitor | Virtual-Fly Ruddo & TQ3+ | Thrustmaster FCS Sidestick | Skalarki MCDU Ask me about (my most flown): FSLabs A320-X series | MaddogXIn the hangar: Majestic Q400 Pro | PMDG 747 | A2A C182, Cherokee, Comanche & Spitfire
October 1, 200916 yr Author enter them with the N then W firstso N58W020Thanks 413X3.But I just tried and the result was the same. The flightplan and coordinates processed correctly, but printing the final page with the TELEX option enabled crashed the programme (MFC Application Error), and the result when not including it was as follows (see attachment).I have tried it on 2 different computers and with different AIRAC data... same thing occurs. Rob BatesSimming since the age of 10 with MSFS 5.0 P3D v5.0 | 10700K (@stock) | EVGA GTX1080Ti SC2 | Z490-E ROG STRIX | 32GB 3600MHz | 970 EVO Plus M.2 & EVO 850 SSDs | H115i cooling | NZXT H440 Case | Samsung 32" CJG 1440p Curved Monitor | Virtual-Fly Ruddo & TQ3+ | Thrustmaster FCS Sidestick | Skalarki MCDU Ask me about (my most flown): FSLabs A320-X series | MaddogXIn the hangar: Majestic Q400 Pro | PMDG 747 | A2A C182, Cherokee, Comanche & Spitfire
October 1, 200916 yr Have you tried importing the current NATS and using those? I'm not at home right now, but have not had any issues in doing NATS and PACOTS tracks either through selecting the TAT or by lat/lon. I beat Ernie up on this before release too :) I probably ran hundreds Trans Atlantic plans of plans before he released the code.Tim
Create an account or sign in to comment