Fsbuild-2 Flight Planner

There have been some unreleased updates to ver 1.8.

http://isgsim.com/dl/isg185.exe

Since this is still considered Beta, you should backup your original isg1.gau file.

Note: These updates will not work without the full 1.8 version being installed first.

Regards.
Ernie.

I think my ability to enter route offsets has been lost in the latest v1.8 updates. For example, flying to KORD I'm able to select the ILS32 approach with the FMC (with Navigraph updates), then insert waypoint MUNDY before waypoint INDDY as shown on the approach chart here: http://skyvector.com/files/tpp/1401/pdf/00166IL32R.PDF. However, if I then try to enter offset waypoint MUNDY120/08, the FMC reports the waypoint as not found (same result if I try the format MUNDY/120/08). The offset feature worked fine before the update. Can anyone confirm the issue?

Hi,

actually i have run into the same issue. Whatever VOR / bearing / distance waypoint i want to define, it tells not in database. The place beaing / place bearing feature gives a waypoint, but that is not at a place where i would expect it.
I use the latest hotfix 1.84 annd navigraph cycle 1313. I must confess, that i am pretty new to this product and still messing around with settings, cfgs etc. and i don't know if it worked in earlier versions or with other cycles.
I have just experienced a situation where it would have been useful to have that feature. I am overall very pleased to have that peace of avionics to improve all kinds of freeware and simple payware planes. Anyhow, it would be nice if that small feature were about to be in there, or a solution to that issue could be found.

Thank's for reading my post

Regards

I am looking into your ISG (Smiths and GNSXLS) for the TinMouse II 737.

I noticed the ISG Beta version 1.8 started June of 2011 but is not completed yet.

Does 1.8 beta have any improvements for the Smiths and GNSXLS?

Am I ok with the current ISG download version from SimMarket for use with the TinMouse II 737?

_________________
Vaughan

This is regarding the above posts by flibinite and Benny, describing difficulty entering offset waypoints after applying the 1.84 fix. I too was getting the “Not In Database” message when using the place-bearing/distance method to enter offset waypoints after applying the fix. Quite by accident I stumbled on a workaround. I’m not sure why it works but it seems to work consistently, at least for me. In flibinite’s example, above, he is trying to enter the MUNDY120/8 offset waypoint on the LEGS page, and “Not In Database” appears in the scratchpad. When this happens, press CLR to remove the “Not In Database” message. MUNDY120/8 returns to the scratchpad. Now use the CLR key to remove all of the extra characters so that only MUNDY is left in the scratchpad. Insert the waypoint where you want it to go on the LEGS page. (If there is more than one waypoint with this identifier you will now need to select the correct one.) The offset waypoint MUN01 will now be entered on the LEGS page, with the correct offset bearing and distance from the preceding waypoint. Again, I’m not sure why this works but it does seem to work every time. (I have not tried this with place-bearing/place-bearing offsets but I suppose you could try it.)