Problem with FstarRC 1.86 and FliteStar 9.x

[blave]

Happy new year Pete,

When I do a print of the flight plan in FliteStar, I get the following error in the APL file:

"Can't find or open the runways database (FStarRC.rws)"

I have confirmed that that file exists in my FliteStar directory, along with the other FStarRC files. Attempting to open the .rws file in Wordpad shows binary-looking nonsense, so I presume it is in fact binary.

The FliteStar version is 9.029, and it's the "IFR" version.

Thanks,

Dave Blevins

[Pete Dowson]

When I do a print of the flight plan in FliteStar, I get the following error in the APL file:

"Can't find or open the runways database (FStarRC.rws)"

I have confirmed that that file exists in my FliteStar directory, along with the other FStarRC files. Attempting to open the .rws file in Wordpad shows binary-looking nonsense, so I presume it is in fact binary.

The FliteStar version is 9.029, and it's the "IFR" version.

Can you say what has been changed to achieve this, or have you never used FStarRC before?

The runways database is binary. It contains a sorted table of all runways in all airports, but, alas, it is still based on FS2002. I have on my list to rewrite my scanning program for FS2004, but, though I think I now have the new AFD formats, it is not a trivial job and I haven't yet had time to do it.

I know it works well with version 9.xxx because there have been folks using this for a while now. I only just updated my FliteMap before Christmas, and am now running 9.04 (Build 7523). FStarRC works fine with it, still.

Regards,

Pete

[blave]

I have never used FStarRC before - just tried to get it working for the first time yesterday. I copied all of the files (except "if you cannot see the DLL.txt") into the FliteStar directory...

BTW I don't have FliteMap, just the subset FliteStar product. I just updated it with the updater available on the Jepp site today, to the same build that you have.... Still having the problem.

I know you're quite busy supporting all of the excellent utilities that you provide, so I don't want to take up too much of your time on this. I can get around this by using one of the FS2004-compatible planners... But I have to admit that when I found out I could use the planner I use for RW flying with FS2004 as well, I got kind of excited :D .

cheers,

Dave Blevins

[Pete Dowson]

I have never used FStarRC before - just tried to get it working for the first time yesterday. I copied all of the files (except "if you cannot see the DLL.txt") into the FliteStar directory...

Did you edit the FStarRC.ini file, to set your choice of paths and so on? I'm wondering if that may have anything to do with it.

The other thing to check is that you are running FStarRC.exe FROM the FliteStar folder, the one which contains the FliteStar program itself. If you have made a short cut to FStarRC make sure that the Properties show the same folder as the working folder.

Does FStarRC, when run, load and run FliteStar for you? If it does, then, since that is in the same folder as the RWS file, it should find that too.

Finally, you could set "Log=Yes" in the INI file, run it, then show me both the FStarRC.INI and FStarRC.log files.

FStarRC has been going now for years -- I first did it in the time of FS98 and FliteStar version 6 or 7. This is the first time any one has had such a problem.

Regards,

Pete

[blave]

SOLVED. But, I must say that my problem was due to something I've never seen before.

You said to check the shortcut's folder settings. Well, it turns out that when I did a WinXP "Pin To Start Menu" action on FStarRC.exe, it copied the executable to the Start menu, rather than a shortcut. So, of course it couldn't find the runway file.

I have used the Pin To Start Menu many times and have never seen this happen before with other executables.

Anyway, to work around this, I created a shortcut in the Flitestar folder and then pinned that to the Start menu.

Now, all is well, and thanks for *another* useful program to enhance my FS experience.

cheers,

dB.

[Pete Dowson]

SOLVED...You said to check the shortcut's folder settings. Well, it turns out that when I did a WinXP "Pin To Start Menu" action on FStarRC.exe, it copied the executable to the Start menu, rather than a shortcut. So, of course it couldn't find the runway file.

I bet it didn't start FliteStar either, eh?

To make shortcuts I just use the mouse, drag the EXE to the desktop bu press the ALT key before releasing. I think that works with all versions of Windows.

Regards,

Pete

[blave]

[quote name="I bet it didn't start FliteStar either' date=' eh?

To make shortcuts I just use the mouse, drag the EXE to the desktop bu press the ALT key before releasing. I think that works with all versions of Windows.

Regards,

Pete[/quote]

That's the weird thing - it DID start FliteStar, which seemed to work.

re: Shortcuts - I always used to do it the way you describe, but the Pin To can be done with two clicks and no dragging. You see, I'm really lazy!

dB.