Fsbuild-2 Flight Planner

Never had this problem before, Ernie, and it's a bit hard to explain, but I'll try.

The jist of the problem is that FB is not calculating cruise correctly now for some reason.
Firstly, my build settings :


Using the stored flightplan EGLL-ORD I get :




As you can see, I have set it to 38000, however I get 33000 across the board, with no climb or descent profile!

With winds aloft included I get this :



If you notice the current action box, it is stuck on attempting to retrieve a wind value. At this point I can build again, as though the action were complete.
On one occasion I could see FSB building again and again with different FL's, finally settling on 240! Something wrong there! You can see from the image it has stopped at 280.

If I take out all the variables from my build options I get this, I finally get 380, but still no climb/descent profiles:



As yet I have not been able to build a correct flightplan since this morning, on ANY route tried. I have tried different aircraft, with all kinds of settings, without any luck.

Any ideas, Ernie? Oh and yes, I've tried re-installing!

Cheers

_________________
Cheers

Gottfried

Hmmm still can't create the problem so far.



In your screenshot I do see something strange. The 'Freq' for all the waypoints is '359.00'. As you can see from my screenshot that is the freq for the 'YAZ' waypoint.

So maybe that is an indication of some sort of memory issue. Maybe some holdover from whan the autogenerator initially generated the route.

Something to try would be to autogen the route, then copy/paste the route from flight plan box, to a text file or someplace temporarily. Then shut down the Fsbuild program, and restart, then paste the route back in the flight plan box, and 'Build' the route (not autogen). And see if the result is any different.

But without being able to re-create the problem, it'd be next to impossible to provide a solution. You said it never happened before, that might indicate a recent system change might be the catalyst for this. I think there was a Windows update pushed out by MS earlier this week. Could that have triggered this ? Maybe, who knows.

But really I'm just guessing, it could be anything, it could even be caused by another program in memory. It could be anything.

You can also try and force it to use a certain cruise altitude for the step climb by manually entering a cruise altitude in the left cruise box. That would override any cruise altitude determined by the autogenerator.

Regards.
Ernie.

OK, Ernie, I've just finished 12 long hours at work, come home and set to try to solve this issue. I may have gotten somewhere with it, thank goodness, it's 1:15am now!

I tried installing again from scratch, 2.1 - 2.3 - 2.3.7.4 - 2.3.7.5

I thought at first it was fixed, and so it is, but only partly. There's still a slight bug somewhere... probably in Vista.

I ran the installers for 2374 and 2375 but found when I ran FSB the header still showed 2.3.1. I ran the istaller to a pseudo directory and copied the new fsbuild2.exe to my fsb directory which successfully updated the program.

I ran the previously built routes and they worked fine, until I tried CYVR-YBCS. This gave me two waypoints WAY off route. So I deleted them from the waypoint table and checked the "Build from waypoint table" option. This once again gave the crazy flight levels.

I tried this option on other routes and obtained the same results. The cruise level jumping all over the place and no TOC/TOD points.

UNcheck the "build from...." and it's back to normal. Well, except for the CYVR-YBCS... maybe that one was too long for the aircraft (767-300) to fly and maybe that was to blame somewhat.

By the way, I had already tried manually entering a cruise, and that hadn't worked.

Hope this gives you something to go on.

Steve