Jump to content
The simFlight Network Forums

FSMP

Members
  • Posts

    11
  • Joined

  • Last visited

Posts posted by FSMP

  1. Geoff, to be honest: when you seriously think about using an AIRAC totally outdated, although I doubt there is one available, I seriously recommend you to use FSX without any addon: neither a scenery nor an aircraft. Most of them come with actual data, like airports with actual ILS frequencies which also will not fit to old FSX database, or modern airliner addons that will also rely on actual data.

    As Microsoft does not offer an update for FSX's outdated database, a very good solution can be found here: http://www.aero.sors.fr/navaids.html

     

    Thanks for the advice  & links.

     

    The way I see it,  one can either SIMULATE the world, as it was when MS frooze the FSX data,   and use Charts that match that period,  and hopefully a Matching AIRAC,

     

    or

     

    Be ever chasing to be up_to_date.     While there are updated AiRacs  (which is great), the problem arises when Airports (and their included navaid) change, and one is for ever  trying to find or produce updated airports bgl's  etc..

     

    ie  With Updated AIRAC,  try flying the ILS approach to " 1 left"  @  KIAD

    Everything is fine, till you get there,  only to find  in FSX,  that runway does had not been built yet, and you are landing in a field, because you did not know that in FSX, it was not correct, and you therefore had not searched and found a scenery update for KIAD that included that new runway.  (time to fly to your alternative !!)

     

    When you consider this in a Multiplayer situation, it becomes even more Chaotic  -- everyone is flying with differeing worlds, and differeing Nav data  !!

     

    I was just looking at the possibility of at least being able to define one Stable environment  -- ie   about 1994, which is about the time Aces seems to have stopped updaing their FS airports  etc.

     

    -------

     

    I see this as one of the bigger challenges facing any developer of a NEW Flight Sim....  option for automatic updates.

    However, when one looks at the cost to produce these updates, for a limited market, it is doubtful that such an update system would ever be workable.

  2. I am seeing strange instances of FSC not matching FSX.

     

    Note: No addon scenery or addon Nav data.  Ran the FSX databasebuilder.

     

    (1) KMTN.   FSX shows a NDB called MTN, a mile SE of airport.

        Does not show in FSX,  but other local NDBs  do

     

    (2)  Saratoga VOR   SRQ

       FSX shows freq as 117.00,  while FSX shows a different historic frequency.

     

    Note:  CURRENT real world  --  NDB MTN no longer exist.

              CURRENT real world  --  SRQ  is now 117.00

    So FSC dara is more up to date than FSX data   !!

     

    But FSX is meant to be getting its data from FSX bgl files, so how is it getting this newer UP TO DATE  info ?

     

    Examination of the BGL files, shows the expected FSX data,  and not what FSC is depicting.

     

    Once again, FSX database builder run sucessfully (at least without any errors displaying),  but still FSX & FSC do not match.

     

    ( scenerycfg.fsc is same as FSX's scenery.cfg)

     

     

    I had another owner of FSX & FSC look -- they see the same differences,  with FSC NOT matching FSX.

  3. Thanks Pete

    Ref: "The FSX Process Memory left"

    Is that the TOTAL amount of "Fragmented" memory left, or the Total of all the "CONTIGEOUS" blocks of free memory left, that exceed a given size ?

    From what I have experienced and seen, while there may be quite a lot of small Fragmented blocks of memory left, totaling an appreciable size, as the memory gets fragmented, there reaches a time, where there is not a big enough "Contigeous" block, to satisfy a FSX request for a new given size chunk of memory, and then one gets an OOM, ( when it is now too late for FSX to do much about the failure to get that memory).

    Geoff

  4. Pete,

    I recently saw this post on an Avsim forum

    For those that don't know, if you have the latest FSUIPC, you will get a windows "ding dong" to let you know you are close to getting an OOM. Give you a chance to save or continue.

    If you look at the fsuipc.log.txt, you will see low memory entries once you get near the 4gb limit. A great feature.

    I have a registered version, so not sure if it works in the freeware one.

    Looking through the FSUIPC documenation and this FSUIPC support forum , I see no reference to this.

    (maybe I missed it .. I'm getting old ! )

    Is this really a recent feature added to FSUIPC, or is the "ding-dong" coming from elsewhere ??

    Geoff

  5. I made some other changes to try to detect MP changeover (It seems I can't -- the requested events never arrive, like everything else, hence the "stall" diagnosis), but i also removed the "is Simconnect receiving from FSUIPC?" check. maybe that'll help in the crash case, as that was where P3D appears to be stumbling. It doesn't appear to like the Event State being changed whilst it is loading or reloading things.

    Try FSUIPC 4812f

    Regards

    Pete

    Pete

    I just tested it joining numerous times with my P3D Server.

    Client running FSUIPC version 'F' now connects without incident every time, and no signs of any errors in the FSUIPC Logs.

    When I joined and CRASHED THE PLANE, this time with Version "f" I was able select a repaired plane, and re-join the session, and when Pause was released, fly as normal, without any CTD>

    FSUIPC log did show a few EXCEPTION Errors :-

    Console Started ...

    1168015 LogOptions changed, now 60000000 0000001D

    1169015 Ready Flags: Ready-To-Fly=Y, In Menu=N, In Dlg=N

    1177297 Ready Flags: Ready-To-Fly=Y, In Menu=Y, In Dlg=Y

    1177297 User aircraft crashed!

    1209250 Exception 1 "ERROR", Ref 2459, Index param -1 on unknown request!

    1265125 Exception 1 "ERROR", Ref 2484, Index param -1 on unknown request!

    1286844 Ready Flags: Ready-To-Fly=Y, In Menu=N, In Dlg=N

    1289656 KEYDOWN: VK=80, Waiting=0, Repeat=N, Shifts=0

    1289656 .. Key not programmed -- passed on to FS

    1289672 *** EVENT: Cntrl= 65561 (0x00010019), Param= 0 (0x00000000) PAUSE_TOGGLE

    1289797 KEYUP: VK=80, Waiting=0

    1292422 **** SimConnect Data Stalled! Re-connecting now ... ****

    1292515 SimConnect_Open succeeded: waiting to check version okay

    1292562 Running in "Lockheed Martin« Prepar3D«", Version: 1.3.3708.0 (SimConnect: 1.3.0.0)

    1292562 Initialising SimConnect data requests now

    1292562 FSUIPC Menu entry added

    1293375 System time = 03/04/2012 11:56:36, Simulator time = 11:24:13 (15:24Z)

    Hope this helps :)

    ---------------------------

    Question: Are the changes made in "f" just for operation in P3D mode, or is the "checking" also removed for FSX ?

    THANKS for such a speedy resolution. You never cease to amaze me :)

    Geoff

    FSMP

  6. Running FSUIPC4812e

    Connection to MP completes, but if I CRASH the plane, and then try to fly again, I get a CTD when the Loading Progress bar reaches 100%.

    If I disable FSUIPC, I do not get this CTD.

    Tried two different PC as the SERVER, and two different PCs as the joining client.

    IDENTICAL, reproducable CTD in every case when FSUIPC was enabled.

    NO CTD when FSUIPC was disabled.

    FSUIPC4.Log ( Registration Info X'ed out !! )

    ******** FSUIPC4, Version 4.812e by Pete Dowson *********

    User Name="XXXXXXXXXXXXXXXX"

    User Addr="XXXXXXXXXXXXXXXX"

    FSUIPC4 Key is provided

    WIDEFS7 not user registered, or expired

    Running inside Prepar3D on Windows Vista

    Module base=61000000

    609 System time = 31/03/2012 09:34:04

    609 FLT path = "C:\Users\XXXXX\Documents\Prepar3D Files\"

    609 Trying D:\Program Files (x86)\Lockheed Martin\Prepar3D\Modules\SimConnectP3D.dll

    609 Found it: trying to connect

    640 FS path = "D:\Program Files (x86)\Lockheed Martin\Prepar3D\"

    1654 LogOptions=00000000 00000001

    1685 Wind smoothing fix is fully installed

    1685 SimConnect_Open succeeded: waiting to check version okay

    1685 Trying to use SimConnect Prepar3D

    6100 Running in "Lockheed Martin® Prepar3D®", Version: 1.3.3708.0 (SimConnect: 1.3.0.0)

    6100 Initialising SimConnect data requests now

    6100 FSUIPC Menu entry added

    6131 D:\Program Files (x86)\Lockheed Martin\Prepar3D\FLIGHTS\OTHER\Prepar3D.FLT

    6131 D:\Program Files (x86)\Lockheed Martin\Prepar3D\SimObjects\Airplanes\Mooney_Bravo\Mooney_Bravo.AIR

    98765 System time = 31/03/2012 09:35:42, Simulator time = 11:00:04 (15:00Z)

    98780 Aircraft="Mooney Bravo With G1000"

    99311 Starting everything now ...

    100403 Advanced Weather Interface Enabled

    112196 Weather Mode now = Theme

    365012 Sim stopped: average frame rate for last 180 secs = 7.1 fps

    937130 **** SimConnect Data Stalled! Re-connecting now ... ****

    937239 SimConnect_Open succeeded: waiting to check version okay

    937239 Running in "Lockheed Martin® Prepar3D®", Version: 1.3.3708.0 (SimConnect: 1.3.0.0)

    937239 Initialising SimConnect data requests now

    937239 FSUIPC Menu entry added

    938128 System time = 31/03/2012 09:49:42, Simulator time = 11:01:21 (15:01Z)

    993867 Sim stopped: average frame rate for last 57 secs = 9.7 fps

    993867 User aircraft crashed!

    1060932 **** SimConnect appears not to be receiving requests! Re-connecting now ... ****

    1061041 SimConnect_Open succeeded: waiting to check version okay

    Geoff

  7. Can you please report this to Lockheed Martin support. There's no change in FSUIPC -- only the Installer needed changing. L-M will need to work out what is going on. It will be something in SimConnect. (In any case I can only make one install of 1.3 so I cannot even test that multiplayer.mode).

    One thing you could try is removing the SimConnectP3D.DLL file from the P3D Modules foder to force FSUIPC to use the ESP one installed by L-M in the Windows WinSxS folder. But I doubt it'll change as the DLL is merely a wrapper for the calls into the SimConnect-proper part of P3D.

    Regards

    Pete

    Thanks Pete.

    FYI: FSMP runs a "Open to the Public" 24/7 P3D MP server, to aid developers, developing for Multiplayer applications.

    Currently, it is running the latest version of P3D: ( Ver 1.3 ) (FSUIPC not installed on Server)

    You (and any other developer) are most welcome to attempt to connect to it for testing.

    IP: 68.49.210.150

    I would be most interested to hear from anyone connecting, who has FSUIPC installed on their P3D Ver 1.3 client.

    Regards

    Geoff

    FSMP

  8. P3D Ver 1.3 + FSUIPC 4.812 - Crash in Multiplayer

    Host: XP Pro - P3D 1.3 ( Fsuipc Not installed)

    Client: XP Pro - P3D 1.3 FSUIPC 4.812 Installed

    Both running P3D as ADMINISTRATOR

    Client runs fine in Free Flight. ( with & without FSUIPC enabled)

    Client runs fine in Multiplayer, if FSUIPC is DISABLED,

    If FSUIP is Enabled, Client joins session, but a few seconds after coming off pause,:-

    P3D Application Error : Inst 0x0185a49a ref memory at 0x02c5f7f8 ( cannot read ).

    100% Repeatable: Every time FSUIPC is enabled in Clinet, it crashes after connecting, just after coming off pause.

    ------------

    This did not occur with P3D 1.2, and the earlier version of FSUIPC, that supported 1.2 (prior to 1.3 release)

    --------------

    Geoff

  9. Also note that I am still hopeful that FSUIPC4 can provide direct offset mapping for all the PMDG 737NGX data. The facility is already programmed. I am only waiting for PMDG's okay, because of the worrying EULA.

    Regards

    Pete

    We are ALL hopeful of that Pete. Thanks for looking to provide that. :razz:

    Will certainly make it a LOT easier for those who are not C++ Programmers.

    Geoff

    (Thanks also for the timely FSUIPC update for P3D 1.3 -- You are amazing )

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