OnCourse Software

How strange... sent it two days ago!

Anyway, I've attached it here... hopefully this will give me a little more info on the problems you're experiencing.

Once you've copied this into your main PF3 folder please remove the NoToolTips=1 option from your INI file or set it to NoToolTips=0, then recreate the problem of loading a bad flight plan, entering the FP adjustments page and hitting the Quick Entry option. Please let me know the exact error message received (if any)

Once you've done this test if you set the NoToolTips back to '1' again you will be able to load and use any flight plan again as you can with your current interim version.

No explanation on the why I didn't get the email, but here is the result of the test with the new version of PF3:

1. Select a flight plan: KIADEGLL12.pln
2. Hit Load a Flight Plan
3. Enter the Airport ICAO for the Alternate Airport: EGKK, press Enter
4. Hit Use Alternate
5. Get back caution about waypoints too close, hit OK
6. Hit Adjust Altitudes...for Selected Flight Plan
7. IMMEDIATELY the following error box appears when hitting the Adjust Altitudes... Button:

Please report the following to OnCourse Software!

frmFPAdjust(Load)-2147220990 - 38E

8. Hit OK and the Waypoint Altitude Adjustment panel comes up.
9. Hit Set END of SID/DP and get the usual:

Run-Time error '91':

Object variable or With block variable not set

10. Hit OK and PF3 'goes away'.

Have attached the two log files created by the run, startup.log and XDebug.log files as well as the offending flight plan. And for grins, I ran a Validate and it came back successfully, no problems.

Cheers,
George

Thanks for that George but please repeat but at step 9 please select the 'Activate Quick Entry' option, which is where the additional debug code has been inserted.

Sent from my mobile using Tapatalk

Sorry 'bout that.

9. Check Activate quick-entry mode the following error box shows:

Please report the following to OnCourse Software!

frmFPAdjust(CloseProc) 91-D2

10. Click OK and another error box:

Please report the following to OnCourse Software!

frmFPAdjust(QE) 91-46

11. Click OK and the final error box for the '91'
12. Click OK and PF3 'goes away'

I did try this on a 'good' flight plan and do not get any error as it worked as expected.

Cheers,
George

Thanks George... I now have enough info to see exactly where the problem is raising its ugly head, but why I can't replicate it here is another matter.

Watch this space and I'll hopefully get back to you later today.

Please know Dave, I very much appreciate your efforts...knowing FULL WELL, I may have inadvertently screwed something up. This FSX eco-system has so very many variables that to believe any of it works is truly amazing. Awaiting your next move.

Thanks,
George

Hi George

Please try the attached.

You can remove the NoTooltips INI file entry completely as this should now work for you with all flight plans

Dave,

You have appeared to nail the problem and fix the issue. Do tell what caused the problem? I've run five 'bad' plans and they appear to work. The final proof will be to do a flight with one of the plans but I don't expect that to be a concern.

Many, many, many thanks!
George

Well the problem would only occur if you selected an Alternate, which I initially failed to make a connection with, despite you having mentioned it previously. With an Alternate selected the initialisation code, when selecting 'Adjust Flight Plan' and where the tooltip objects are created,, would error when creating the tooltip to the actual Alternate airport. But then the error trap had a gaping hole and the code dropped out before being able to initialise the additional tooltip objects and it was those objects causing the problem when you hit 'Quick Edit' or 'Set DP', etc, because they didn't exist due to the initialise routine being exited before it was complete.

The fix for this will be in the next release and at that time you will need to either reinstate your original PF3.exe version 3.6 and then hit 'check for updates' to receive the official fixed version (3.7) or use the cumulative updates package using the link provided within the new release announcement post. Hope that makes sense, if not, just shout.

Thank you for being so helpful and patient with this issue George, I certainly do appreciate your time and trouble and apologise for all the inconvenience

Dave,

Interesting. Am greatly relieved that I didn't screw something up! Leave it to me to do what no one else had tried. No need to apologize. As I mentioned I used to do software support for a living and know the ups and downs. The key is patience by all parties and all will work out. If you ever need someone for testing, am again volunteering. I actually enjoy doing that sort of thing. And I do get the gist of what I have to do when the update comes out.

Again thanks,
George