very-short
Members +
Hi Guys ,
Im a big fan of the free VASFMC software the sad part is that the last version released did have a fuel bug in it and it would hang when calculating the fuel in the INT page I have found the problem seems to be related to the flight plan waypoints so here is a possible fix that I have tried and seems to work well .the problem occurs when two way points seem to be to close to each other eg
NZAA|-37.0080560000|174.7916670000|0||ADEP||cfl=320;fnr=ANZ516;croute=NZAANZWN306;adep=NZAA;ades=NZWN
AA|-37.0046390000|174.8136390000|0|DCT||..................Problem line #1
LIMES|-37.5716670000|174.6386950000|0|H384||
KARRL|-37.9766670000|174.5122220000|0|H384||
NP|-39.0072500000|174.1839440000|0|H384||
AKAVI|-39.9996670000|174.2638030000|0|H384||
SWUTH|-40.7697220000|174.3275000000|0|H384||
TR|-41.1858440000|174.3623780000|0|H384||
BAXOV|-41.2411830000|174.5276830000|0|H235||
WN|-41.3372220000|174.8169720000|0|H235||............ Problem line #2
NZWN|-41.3272220000|174.8052780000|0||ADES|
The problem begins with the two lines I have highlighted ..... the waypoints seem to be too close to calculate the fuel required Thus causing VASFMC to Crash so a simple fix is to delete these two lines from the FP then re-save the FP import it into VASFMC . I have been doing this for a while now and it seems to work fine the fuel load etc is calculated and VASFMC runs fine pretty much 100% of the time .... I hope this helps anyone who uses VASFMC .... it was only by chance I stumbled across this fix but it seems to work I was able to narrow the problem down to the FP causing the problem because it was only sometimes VASFMC would crash so the only variable was the FP .
I hope this helps ,
cheers
Andrew W {aka Very-short}
Im a big fan of the free VASFMC software the sad part is that the last version released did have a fuel bug in it and it would hang when calculating the fuel in the INT page I have found the problem seems to be related to the flight plan waypoints so here is a possible fix that I have tried and seems to work well .the problem occurs when two way points seem to be to close to each other eg
NZAA|-37.0080560000|174.7916670000|0||ADEP||cfl=320;fnr=ANZ516;croute=NZAANZWN306;adep=NZAA;ades=NZWN
AA|-37.0046390000|174.8136390000|0|DCT||..................Problem line #1
LIMES|-37.5716670000|174.6386950000|0|H384||
KARRL|-37.9766670000|174.5122220000|0|H384||
NP|-39.0072500000|174.1839440000|0|H384||
AKAVI|-39.9996670000|174.2638030000|0|H384||
SWUTH|-40.7697220000|174.3275000000|0|H384||
TR|-41.1858440000|174.3623780000|0|H384||
BAXOV|-41.2411830000|174.5276830000|0|H235||
WN|-41.3372220000|174.8169720000|0|H235||............ Problem line #2
NZWN|-41.3272220000|174.8052780000|0||ADES|
The problem begins with the two lines I have highlighted ..... the waypoints seem to be too close to calculate the fuel required Thus causing VASFMC to Crash so a simple fix is to delete these two lines from the FP then re-save the FP import it into VASFMC . I have been doing this for a while now and it seems to work fine the fuel load etc is calculated and VASFMC runs fine pretty much 100% of the time .... I hope this helps anyone who uses VASFMC .... it was only by chance I stumbled across this fix but it seems to work I was able to narrow the problem down to the FP causing the problem because it was only sometimes VASFMC would crash so the only variable was the FP .
I hope this helps ,
cheers
Andrew W {aka Very-short}