Jump to content
The simFlight Network Forums

FliteStar 9.5.2.1 (Build 15211) on W7?


Recommended Posts

Is there a way to get FStarRC to work with FliteStar 9.5.2.1 (Build 15211) on W7? I just upgraded (thanks to my employer) to 9.5 and it seems not to work with the latest. Thanks.

I'm using 9.3 on Windows 7 (64-bit) with no problems in FStarRC. Jeppesen keep changing things to mess me up, but not usually on minor increments. What exactly happens? Can you show me an example of the Report output format? FStarRC is dependent upon scanning the printer output so that's relevant.

I'm making inquiries now about updating my copy -- if it isn't too expensive I might get it. That might be the fastest way to sort it out.

Pete

Link to comment
Share on other sites

I'm using 9.3 on Windows 7 (64-bit) with no problems in FStarRC. Jeppesen keep changing things to mess me up, but not usually on minor increments. What exactly happens? Can you show me an example of the Report output format? FStarRC is dependent upon scanning the printer output so that's relevant.

I'm making inquiries now about updating my copy -- if it isn't too expensive I might get it. That might be the fastest way to sort it out.

Pete

Hello, Thanks for replying.

Nothing happens really. When I click print it just prints a log. Nothing come up regarding your FStarRC.

I created a sample flight for you. I just took a capture of the screen. If you need more let me know. I think it's like 70 for a upgrade. Not too sure though...

http://img201.images...02010050439.jpg

capture25102010050439.jpg

Edited by FlightLevel41
Link to comment
Share on other sites

Nothing happens really. When I click print it just prints a log. Nothing come up regarding your FStarRC.

FStarRC would save a log file too. You are using the latest FStarRC (2.10) aren't you? And using it to start FliteStar as per instructions? What was the previous version of FliteStar which it worked okay with?

I created a sample flight for you. I just took a capture of the screen.

Looks pretty much unchanged, although mine doesn't have 2 decimal places for fuel and distance values -- is that new or an option you've set? -- nor seconds in the timing, only hours and minutes. How does the printed Report compare with the last version you had FStarRC working with?

If you need more let me know.

You could setting "Log=Debug" in the FStarRC.ini file, then rerunning and printing a typical report. That'd produce a huge log. ZIP it and send to petedowson@btconnect.com. Can't promise anything though. I might have to wait to see if I can update my copy without too much expense.

I think it's like 70 for a upgrade. Not too sure though...

It'll be much more than that -- mine is a Worldwide Corporate FliteMap version (takes GPS inputs and operates as a moving map too). Last time I updated (Jan 2008) it cost a few hundred Euros I think.

Regards

Pete

Link to comment
Share on other sites

FStarRC would save a log file too. You are using the latest FStarRC (2.10) aren't you? And using it to start FliteStar as per instructions? What was the previous version of FliteStar which it worked okay with?

Looks pretty much unchanged, although mine doesn't have 2 decimal places for fuel and distance values -- is that new or an option you've set? -- nor seconds in the timing, only hours and minutes. How does the printed Report compare with the last version you had FStarRC working with?

You could setting "Log=Debug" in the FStarRC.ini file, then rerunning and printing a typical report. That'd produce a huge log. ZIP it and send to petedowson@btconnect.com. Can't promise anything though. I might have to wait to see if I can update my copy without too much expense.

It'll be much more than that -- mine is a Worldwide Corporate FliteMap version (takes GPS inputs and operates as a moving map too). Last time I updated (Jan 2008) it cost a few hundred Euros I think.

Regards

Pete

1. Yes. i am using 2.10 and using it as you readme file outlines.

2. The decimal places are just the options that I always use. I've used the same with the previous version 9.4.7. I cannot say or remember that I see any difference in the format of the display of the nav log.

3. The log is very small:

0 ********* FstarRC, Version 2.10 by Pete Dowson *********

0 Sending RC plans to: C:\Users\Stratox\Documents\Flight Simulator Files\

0 Error: no Base for for MFC42.dll

0 Error: no Base for for MFC71.dll

0 Error: couldn't hook DrawTextA

0 Error: no Base for for MFC42.dll

0 Error: no Base for for MFC71.dll

0 Error: couldn't hook DeleteDC

63024 ********* FstarRC Log file closed *********

FstarRC.txt

Link to comment
Share on other sites

The decimal places are just the options that I always use. I've used the same with the previous version 9.4.7.

So the change is from 9.4.7 to 9.5.2.1? That's odd -- such a seemingly minor step ...

3. The log is very small:

... yet it looks as if they'd completely re-compiled it all with some newer versions of the standard Microsoft libraries.

MFC42 and MFC71 contain the routines I hook into to trap the printing output so I can get the plan data.

I'm afraid it is going to have to wait till I can update my copy. I've taken the plunge -- the cost is nearly 500 Euros! (Groan! :-( ).

Pete

Link to comment
Share on other sites

If your in need of a tester let me know. I'll be more than glad to help in any way I can. I'll just copy and paste the route into FSBuild2 until then. Is there a way to export to FSNavigator?

From what? FStarRC? It produces FS format PLN files as well as RC's APL and Squawkbox & PM's SBP form.

If you mean FSBuild, sorry I don't know it.

Pete

Link to comment
Share on other sites

Doesn't FSNav read FS PLNs? I've never been asked to support anything for FSNav before. How were you using FStarRC before?

Pete

FSnav does read PLNs'. I usally inport though FSnav with a PLN and then use FSnav to export to PMDG. I am looking to remove FSnav from the loop and just export from FStarRC to PMDG directly.

Link to comment
Share on other sites

I am looking to remove FSnav from the loop and just export from FStarRC to PMDG directly.

So, I don't understand then why you asked " Is there a way to export to FSNavigator?", which was where we started on this loop?

Anyway, I've no idea what format PMDG uses. Surely they can read FS .PLN format? It's a bit short-sighted of them not to support the format folks can have universally.

Regards

Pete

Link to comment
Share on other sites

I was looking for FliteStar to export to FSN directly as well as exporting a PLN file.

At least to my knowledge it doesn't read the PLN format. PMDG cannot read the PLN format, it has it's own RTE format.

Shame. Having their own format is all well and good, but they should support a common one as well.

My update to FliteMap arrived today, but I'm out now till next week so I'll look at it when I return. But at present I'm sorry but I'm not considering adding any new formats.

Regards

Pete

Link to comment
Share on other sites

Shame. Having their own format is all well and good, but they should support a common one as well.

My update to FliteMap arrived today, but I'm out now till next week so I'll look at it when I return. But at present I'm sorry but I'm not considering adding any new formats.

Regards

Pete

Thanks for looking into it.

Link to comment
Share on other sites

Is there a way to get FStarRC to work with FliteStar 9.5.2.1 (Build 15211)

Okay, done.

Version 2.11 if FStarRC works fine with FliteStar 9.521 build 15211. Tested here under Win7 okay. Download it from the Downloads subforum.

Hey, I like the new free internet weather facilities in this update to Flitestar, but do you know how to get the Wind data automatically inserted into the Report and used in the fuel and time and best altitude computations?

Regards

Pete

Link to comment
Share on other sites

Okay, done.

Version 2.11 if FStarRC works fine with FliteStar 9.521 build 15211. Tested here under Win7 okay. Download it from the Downloads subforum.

Hey, I like the new free internet weather facilities in this update to Flitestar, but do you know how to get the Wind data automatically inserted into the Report and used in the fuel and time and best altitude computations?

Regards

Pete

Hello,

Thanks for your work. That download link is giving me a 404 error.

I love the weather too. I don't know why it took them so long to get live weather inside FS.

In order to get the wind data implemented on a log make sure that you have "Get Winds from Jeppesen WX (Updates NavLog only; NOT a full WX briefing)" checked as well as the sub checked "Route Optimization for Winds (from Jeppesen WX) checked when you are building your routes.

For the best altitude computations: Use via the route-pack box or click on the route magenta line "Optimize Altitudes".

Regards,

Clarke

Link to comment
Share on other sites

Thanks for your work. That download link is giving me a 404 error.

Dammit. It's this new Forum software. It has separate links and viewable text, and I keep forgetting to edit both! Grrr. Please try again!

In order to get the wind data implemented on a log make sure that you have "Get Winds from Jeppesen WX (Updates NavLog only; NOT a full WX briefing)" checked as well as the sub checked "Route Optimization for Winds (from Jeppesen WX) checked when you are building your routes.

I managed, eventually, to get the winds and temperatures included -- I somehow had a ridiculous flight start time and date for the flight. I suspect it was because I started with one of my large library of plans. I can see I'll be re-planning my routes each time from now on! ;-)

For the best altitude computations: Use via the route-pack box or click on the route magenta line "Optimize Altitudes".

I always find it's optimised altitudes way out for my B737 or B738. I'm going to have to work through the aircraft files for them to see what's wrong -- they were supplied to me by one Stamatis Vellis (who I don't think is flying sims these days) a long time ago. I don't suppose you have any good advanced model B737 or 738 Jepp aircraft files?

Regards

Pete

Link to comment
Share on other sites

I always find it's optimised altitudes way out for my B737 or B738. I'm going to have to work through the aircraft files for them to see what's wrong -- they were supplied to me by one Stamatis Vellis (who I don't think is flying sims these days) a long time ago. I don't suppose you have any good advanced model B737 or 738 Jepp aircraft files?

Thanks for the updated version, it's working as it should.

As for the B737/8 model data files. I do have some but they are for our company BBJ's. I cannot give that kind of data out. have you used the Model Exchange service that Jepp has on their website?

Link to comment
Share on other sites

have you used the Model Exchange service that Jepp has on their website?

Not recently.There were no suitable files last time I looked, but I'll try again.

[LATER]

Still as it was several years ago -- the only shared Boeing files are for a 737-200 and a 747-100/20 with RB engines.

There's a "basic" model B737-700. Maybe I'll try that, but I fear it might be worse than the one I have already.

Regards

Pete

Link to comment
Share on other sites

  • 2 months later...

Okay, done.

Version 2.11 if FStarRC works fine with FliteStar 9.521 build 15211. Tested here under Win7 okay. Download it from the Downloads subforum.

Hey, I like the new free internet weather facilities in this update to Flitestar, but do you know how to get the Wind data automatically inserted into the Report and used in the fuel and time and best altitude computations?

Regards

Pete

Happy New Years, Peter.

Looks like Jeppesen broke it again with 9.5.3.0.

I running FStarRC 2.11 with FliteStar 9.5.3.0.

I can't find any .apl file in the C:\Jeppesen\FliteStar

The forum won't let me attach to log file for some reason. It appears from the log file that they moved MFC42.dll and MFC71.dll again.

Anything I can do to help.

Martin Green

martin.green@verizon.net

Link to comment
Share on other sites

Looks like Jeppesen broke it again with 9.5.3.0.

I running FStarRC 2.11 with FliteStar 9.5.3.0.

I can't find any .apl file in the C:\Jeppesen\FliteStar

I'm sorry, but it cost me over 400 Euros to update to the last one and I'm certainly not updating again so soon. Maybe in another 2-3 years.

The forum won't let me attach to log file for some reason. It appears from the log file that they moved MFC42.dll and MFC71.dll again.

It's nothing to do with "moving" things. The libraries are installed in windows. It's to do with which compiler they use to compile with.

And logs can easily be pasted into messages here. They are simple text files.

[LATER]

The log won't tell me what Library versions they use. You'll need to find out. If it is only that which is changed then I should be able to fix it easily enough.

Go to www.sysinternals.com and download ProcExp. When FliteMap is running, run ProcExp, find and select the FliteMap process in the list, and look through the list of DLLs it uses. You'll find the MFCxx.dll there. Let me know and I'll build an FStarRC for you to try.

[EVEN LATER]

Cancel that ... your log shows MFC90.DLL is the one, like the previous release that I now have.

Pete

Link to comment
Share on other sites

I'm sorry, but it cost me over 400 Euros to update to the last one and I'm certainly not updating again so soon. Maybe in another 2-3 years.

It's nothing to do with "moving" things. The libraries are installed in windows. It's to do with which compiler they use to compile with.

And logs can easily be pasted into messages here. They are simple text files.

Pete

Hi, Pete,

I'm not sure why it is costing you so much to upgrade but I have a subscription to NavSuite. Every 14 days, they send me two CD's which update the NavData, Charts AND program files. The latest CD's should upgrade your Flitestar version 9.5.2.1 to the latest version 9.5.3.0.

I would be happy to send the update CD's to you or, better yet, if you have an ftp site to which I can upload the files, I can do that too.

Also, if there is something I can do on my end to try and track down the information you need to rewrite the FStarRC executable, I would be happy to assist.

Finally, this forum software will not allow me to send you the entire log file as it tells me the post is too big. So, I am inserting the first part of the FStarRC.log file into this email below my signature.

Marty

martin.green@verizon.net

0 ********* FstarRC, Version 2.11 by Pete Dowson *********

0 Sending RC plans to: C:\Jeppesen\FliteStar\

0 Error: no Base for for MFC42.dll

0 Error: no Base for for MFC71.dll

0 1: Looking for Address 764DB056 = DrawTextA in USER32.DLL

0 [1] Unprotecting 39C000 bytes from 6DAF0000 (need to write to 6DAF1878)

0 [1] Written 610087A0 to address 6DAF1878 in MFC90.dll

0 Okay, MFC90.dll hooked DrawTextA (type1)

0 Error: no Base for for MFC42.dll

0 Error: no Base for for MFC71.dll

0 1: Looking for Address 77075876 = DeleteDC in GDI32.DLL

0 [1] Unprotecting 39C000 bytes from 6DAF0000 (need to write to 6DAF1230)

0 [1] Written 610070D0 to address 6DAF1230 in MFC90.dll

0 Okay, MFC90.dll hooked DeleteDC (type1)

78 [DEBUG] type=10, cap=1, fmt=41 [51,17] "W A R N I N G - - A L T I T U D E O F C L O U D T O P S N O T K N O W N"

94 [DEBUG] type=10, cap=1, fmt=1056 [0,0] "OnRte"

94 [DEBUG] type=10, cap=1, fmt=32 [7,143] "OnRte"

94 [DEBUG] type=10, cap=1, fmt=1056 [0,0] "VHHH"

94 [DEBUG] type=10, cap=1, fmt=32 [146,159] "VHHH"

94 [DEBUG] type=10, cap=1, fmt=1056 [0,0] "LEVEL"

94 [DEBUG] type=10, cap=1, fmt=1056 [0,0] "START"

94 [DEBUG] type=10, cap=1, fmt=1056 [0,0] "VMMC"

94 [DEBUG] type=10, cap=1, fmt=32 [1275,159] "VMMC"

94 [DEBUG] DeleteDC(-1476324570): DCtype=10, DCcap=1

234 [DEBUG] DeleteDC(-2130631662): DCtype=10, DCcap=1

312 [DEBUG] type=10, cap=1, fmt=41 [51,17] "W A R N I N G - - A L T I T U D E O F C L O U D T O P S N O T K N O W N"

312 [DEBUG] type=10, cap=1, fmt=1056 [0,0] "OnRte"

312 [DEBUG] type=10, cap=1, fmt=32 [7,143] "OnRte"

312 [DEBUG] type=10, cap=1, fmt=1056 [0,0] "VHHH"

312 [DEBUG] type=10, cap=1, fmt=32 [146,159] "VHHH"

312 [DEBUG] type=10, cap=1, fmt=1056 [0,0] "LEVEL"

312 [DEBUG] type=10, cap=1, fmt=1056 [0,0] "START"

312 [DEBUG] type=10, cap=1, fmt=1056 [0,0] "VMMC"

312 [DEBUG] type=10, cap=1, fmt=32 [1275,159] "VMMC"

312 [DEBUG] DeleteDC(889266204): DCtype=10, DCcap=1

8518 [DEBUG] DeleteDC(1510024540): DCtype=10, DCcap=1

8518 [DEBUG] DeleteDC(1526801756): DCtype=10, DCcap=1

8518 [DEBUG] DeleteDC(1543578972): DCtype=10, DCcap=1

8518 [DEBUG] DeleteDC(1560356188): DCtype=10, DCcap=1

8518 [DEBUG] DeleteDC(1577133404): DCtype=10, DCcap=1

8518 [DEBUG] DeleteDC(1593910620): DCtype=10, DCcap=1

8518 [DEBUG] DeleteDC(1677796700): DCtype=10, DCcap=1

8518 [DEBUG] DeleteDC(1694573916): DCtype=10, DCcap=1

8518 [DEBUG] DeleteDC(1711351132): DCtype=10, DCcap=1

8518 [DEBUG] DeleteDC(1728128348): DCtype=10, DCcap=1

8518 [DEBUG] DeleteDC(1744905564): DCtype=10, DCcap=1

8518 [DEBUG] DeleteDC(1761682780): DCtype=10, DCcap=1

8549 [DEBUG] type=10, cap=1, fmt=41 [51,17] "W A R N I N G - - A L T I T U D E O F C L O U D T O P S N O T K N O W N"

8549 [DEBUG] DeleteDC(-1929304830): DCtype=10, DCcap=1

8549 [DEBUG] DeleteDC(1291921088): DCtype=10, DCcap=1

8549 [DEBUG] type=10, cap=1, fmt=1056 [0,0] "OnRte"

8549 [DEBUG] type=10, cap=1, fmt=32 [7,143] "OnRte"

8549 [DEBUG] type=10, cap=1, fmt=1056 [0,0] "VHHH"

8549 [DEBUG] type=10, cap=1, fmt=32 [146,159] "VHHH"

8549 [DEBUG] type=10, cap=1, fmt=1056 [0,0] "LEVEL"

8549 [DEBUG] type=10, cap=1, fmt=1056 [0,0] "START"

8549 [DEBUG] type=10, cap=1, fmt=1056 [0,0] "VMMC"

8549 [DEBUG] type=10, cap=1, fmt=32 [1275,159] "VMMC"

8549 [DEBUG] DeleteDC(1593910290): DCtype=10, DCcap=1

8705 [DEBUG] type=10, cap=1, fmt=41 [51,17] "W A R N I N G - - A L T I T U D E O F C L O U D T O P S N O T K N O W N"

8705 [DEBUG] type=10, cap=1, fmt=1056 [0,0] "OnRte"

8705 [DEBUG] type=10, cap=1, fmt=32 [7,143] "OnRte"

8705 [DEBUG] type=10, cap=1, fmt=1056 [0,0] "VHHH"

8705 [DEBUG] type=10, cap=1, fmt=32 [146,159] "VHHH"

8705 [DEBUG] type=10, cap=1, fmt=1056 [0,0] "LEVEL"

8705 [DEBUG] type=10, cap=1, fmt=1056 [0,0] "START"

8705 [DEBUG] type=10, cap=1, fmt=1056 [0,0] "VMMC"

8705 [DEBUG] type=10, cap=1, fmt=32 [1275,159] "VMMC"

8705 [DEBUG] DeleteDC(1090594350): DCtype=10, DCcap=1

8705 [DEBUG] DeleteDC(318842502): DCtype=10, DCcap=1

8705 [DEBUG] DeleteDC(1308694721): DCtype=10, DCcap=1

...

77751 ********* FstarRC Log file closed *********

Link to comment
Share on other sites

I'm not sure why it is costing you so much to upgrade but I have a subscription to NavSuite. Every 14 days, they send me two CD's which update the NavData, Charts AND program files. The latest CD's should upgrade your Flitestar version 9.5.2.1 to the latest version 9.5.3.0.

I have only ever had a one-off version, Corporate Worldwide. When I first bought it it was a reasonable price, but it seems to double in price every year or two. The subscriptions have always been way beyond what I'm prepared to spend and they are not necessary for simulations.

I would be happy to send the update CD's to you or, better yet, if you have an ftp site to which I can upload the files, I can do that too.

That would certainly be a violation of your agreement with Jeppesen. I can't be really party to that now, can I, as a software publisher especially so. And I don't have any sites for uploads I'm afraid.

0 Okay, MFC90.dll hooked DrawTextA (type1)

Looks like the MFC90 one is okay, so it's something else they changed. That makes it much more complicated. I would have to buy the update to work that one out. Sorry.

You can send me the Log zipped up (it should actually then be smal enough to attach here) to petedowson@btconnect.com and I'll take a look to see if it's anything obvious, but when they've made changes to the print format or order of printing before it's been a complex job which is pretty well impossible without the program.

If I'd known there was another update so soon after I bought the last I would have held off!

Regards

Pete

Link to comment
Share on other sites

I'm sorry, but it cost me over 400 Euros to update to the last one and I'm certainly not updating again so soon. Maybe in another 2-3 years.

It's nothing to do with "moving" things. The libraries are installed in windows. It's to do with which compiler they use to compile with.

And logs can easily be pasted into messages here. They are simple text files.

[LATER]

The log won't tell me what Library versions they use. You'll need to find out. If it is only that which is changed then I should be able to fix it easily enough.

Go to www.sysinternals.com and download ProcExp. When FliteMap is running, run ProcExp, find and select the FliteMap process in the list, and look through the list of DLLs it uses. You'll find the MFCxx.dll there. Let me know and I'll build an FStarRC for you to try.

[EVEN LATER]

Cancel that ... your log shows MFC90.DLL is the one, like the previous release that I now have.

Pete

Pete,

In FliteStar 9.5.3.0 the version of MFC90.DLL is 9.0.30729.4148

ProcExp says that MFC90.DLL loads at address 0x6DAF0000 and has a mapped size of 0x39C000 bytes.

Does that help?

Marty

martin.green@verizon.net

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
 Share

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use. Guidelines Privacy Policy We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.