Jump to content
The simFlight Network Forums

ahuimanu

Members
  • Posts

    43
  • Joined

  • Last visited

Posts posted by ahuimanu

  1. Hi Vic,

    I did remove the folder and re-install.  Given that SAM has moved to version 3.x, would that be a possible issue?

    Also, could you consider creating a dedicated 'scenery' folder here in your forums as that part of your business seems to have started to grow.

    Thank you sir.

  2. The PDF document entitled "FlightSim Commander Update 9.6 Rev. 9  Supplement to the Manual 9.x Supplément au manuel 9.x Nachtrag zum Handbuch 9" is not currently  included in the upgrade ZIP.

    The biggest requirement for P3D v4 users: Pete Dowson's FSUIPC 5

    The biggest limitation: the P3D v3.2 and v4.x Add-On.XML method for add on insertion (particularly sceneries) is not supported.

  3. First, required info:

    SIM: P3D 3.4 HF3 - 3.4.22.19868
    FSUIPC: 4.964 (1st March 2017)
    Network: NO
    FSC: 9.6.0.7
    FSCDbManager: 9.6.0.7
    Navigraph: 1703
    Download from FSCommander
    OS: Windows 10 64-bit
    Monitors: 2

    I am trying to use the flight recording and analysis playback, as indicated on page 95 in the FSC.pdf manual, but the airplane symbol doesn't not show when I am using the arrow keys for playback.

    What can I do?

    Thank you.

     

  4. I have made all purchases of FSC through simmarket over the years.  I paid to upgrade from 8 to 9 through simmarket as well.  Since I too have recently re-installed FSX (new drive), I had also attempted to reinstall FSC.  Here is what worked for me... the last full installer that I have is 9.1.  When i used that, and entered my registration details against that, then my registration information worked okay.  I was then able to upgrade/update to 9.2 and 9.3 just fine.  To be safe I went through each of the 9.2 and 9.3 updates.

     

    Hope that helps.

  5. Love the new window for NATS routes, that makes things SO MUCH easier. I tried to get PACOT and your internal window does not open, rather a web browser opens. That's okay, I thought, but https://www.notams.jcs.mil doesn't work either. I did test - https://www.notams.faa.gov/dinsQueryWeb/advancedNotamMapAction.do - and that makes your internal window come up, but that's not apparently a valid means of accessing the PACOT. So, it seems that until https://www.notams.jcs.mil works, this feature may be somewhat broken.

  6. What you basically get is a KML file as another of the Flightplan export types. You can then open this file in Google Earth and it shows the legs between waypoints. I did expect more Google Earth features, but that's about all I can see. There are cosmetic changes to the UI, but I'm not quite sure if they are improvements - it's subjective. I also see that transitions from STAR to approach are available as well.

    I also note the lack of a "what's new" document and feel that such a document would have helped. This is a worthy tool if you are new to FSC, but it is not certain that it is worth the upgrade at 20 Euros. It is true that there really aren't many new features that jump right out at you. It is possible that there are some hidden gems, but they aren't obvious. I still consider FSC a vital flight planning tool, but this feels more like 8.7 rather than 9.0.

  7. Perhaps I should also post this over at Navigraph, but I am not sure where the problem lies, so I'll try both places.

    The issue I am having is related to FSC not offering at SIDs at KDEN despite the fact that the Navigraph data does contain these SIDs. Is there something wrong with the data from Navigraph or something about FSC 8.5 that is preventing the SIDs from loading?

    UPDATE: I see from searching Navigraph that this is a known problem with 8.5 since April.

    http://forum.navigraph.com/forum/defaulsts&t=1085

    Is there any news on this problem?

    Thank you,

    Jeff

  8. Ai aircraft seem to exist in different states - departing, sleeping, arriving, etc. Remember that the excellent UT2 is "injecting" aircraft using SimConnect. This might create some differences from the traditional BGL-based approach. Use the UT2 monitor program and see if there is a correlation between the aicraft you see in FSC and the departure status of the aicraft you see in UT2's time-tables. I think you might see that many of those aircraft not showing up in FSC on the ground are aircraft not scheduled to depart in the near term.

  9. Hi,

    I found this thread after posting about a similar problem that I thought was due to the length of flight. I have the same issues described here and I am using FSUIPC 4.50. I tried to click the "L" to change the status from red to black and this still did not save the logbook. I too would like to see a manual close of the logbook so very long flights are not lost.

    Thank you,

    Jeff

  10. Hello,

    I've noticed for several versions (perhaps back to 7.x versions?) that a flight can be so long that the "Show Track" button runs out of little blue trail dots to leave. I noticed this on an KIAD-RJAA flight today in the PMDG MD-11F. However, what I am writing about is the logbook feature. While I got a red ATA for each waypoint, I did not see one upon landing at RJAA. Could this be why I lost the entire flight in terms of the logbook? Or, is it not possible to keep a log of such a long flight. From reading other posts I see that you write the logbook record from memory to a file on touchdown. While I had a normal touchdown, I did not get any of the flight saved to the log. I saw the entire flight's worth of red ATA times, but no long entry after the flight and after shutting FSC 8.5 down.

    Would you consider giving us a manual means for terminating and saving the logbook?

    Thank you,

    Jeff

  11. Hi Anonymous (names are sometimes useful for correct identification),

    Thank you very much for your observation. We will fix this bug for the next version/patch.

    The problem has, in fact, to do with the time format set in Windows control. We suspect that your current format is H:mm:ss; if you change this to HH:mm:ss, then everything will be fine. Of course, this is only a work around which, however, might help for the time being.

    Regards

    Sascha & Volker

    Oh, okay, so I should change my windows settings for this? I'll try that. I wrote a small program that fetches the file from NOAA and puts in the Database folder for FSC84.EXE to find and parse; the program then starts FSC84.EXE up. This is been a suitable work-around for now. Frankly, I don't mind showing the time in HH:MM:SS either. I'll report back with the results shortly.

    EDIT and FOLLOW UP:

    Sascha, changing to HH:MM:SS did the trick and the download works fine now.

    Thank you.,

  12. I think I see something wrong with my own protocol file:

    FSC  · Version 8.4.2 · Build:171208 - 12/30/2008 2:15:10 AM
    URL: ftp://tgftp.nws.noaa.gov/data/observations/metar/cycles/ 12/30/2008 2:15:25 AM
    WxFileName= 6:Z.TXT
    Looking up the IP address for the server.
    Found the IP address for the server.
    Connecting to the server.
    Connected to the server.
    Receiving a response from the server.
    Response was received successfully from the server, please wait...
    Requesting information from the server.
    The request was sent successfully to the server.
    Receiving a response from the server.
    Response was received successfully from the server, please wait...
    Requesting information from the server.
    The request was sent successfully to the server.
    Receiving a response from the server.
    GET /data/observations/metar/cycles/6:Z.TXT F:\FSC\database\fsc_metar.tmp
    

    You will see that the program is attempting to get a file called 6:Z.TXT from the server yet no file by that name exists. The files on the FTP site are actually called 0x.TXT where x is a number from 1 to 9. I don't know if this is a programming problem in translating to/from different versions of the OS. fsc_metar.tmp isn't being created as the URL for the current file from the FTP site is wrong. I have observed this across several hours this evening.

    Also, you might want to avoid FTP by using the HTTP access for the same files from NOAA:

    http://weather.noaa.gov/pub/data/observes/00Z.TXT

    All 24 cycle files are available by simply changing the file name to correspond to the correct hour in ZULU time. I have also noticed that FSC8.4.2 is programmed to fetch the last hour's file. I have written programs that have taken advantage of this resource from NOAA and I am familiar with the problem that causes the need to take data that is an hour old: incomplete files. If you write a program to fetch this data NOW, you'll find that NOAA might still be updating the file and, thus, the file is incomplete. In any case, Sascha & Volker might find that the HTTP method is more reliable; especially if the program has been trained to look for a file corresponding to the latest ZULU cycle - 1.

×
×
  • 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.