Jump to content
The simFlight Network Forums

CyberAvia Assoc

Members
  • Posts

    8
  • Joined

  • Last visited

Posts posted by CyberAvia Assoc

  1. Good Morning

    I was out this afternoon, So, i just read this GOOD news !  it's very positive work you have made for association CyberAvia

    Quote

    I will remove that fiddle -- or rather make it conditional on seeing ".." not just ".".

    I understand ...thanks for explications ,       It's not always easy to be compatible with all situations , perhaps conditional is better waiting for  L-M corrective  ?

    Quote

    Then adding another .flt at the end of your strings will work.

    This will just be for P3D4 and FSUIPC5. Okay?

    ok, no problems,   I  will check versions to apply this condition (   .flt.flt  )   with next FSUIPC  with fix

    Thanks very very much for  time spend  to searching my problem   and for future corrective .

    Regards   

  2. Quote

    zero termination of strings is 0x0 ('\0'), not 0x30 ('0'). Try with that.

    I' have just tried, but NOT result processing;       I  thought  character  "zero"  (in  document)   means special code for FSUIPC , and was not  standard terminated string , this always used null (0x0) for my programming language by default for ASCII  string .

      I tested with   cybervol_IFR.flt          and with   cybervol_IFR.flt.flt                 ,   and      null   character  all other   positions

    In my previous log  FSUIPC.log        with                cybervol_IFR.flt.flt             I saw     =>        WRITE0[0]  3F00,   2 bytes: 00 00                                            ..
                       128609 Loading Flight "C:\Users\Dev_cip\Documents\Prepar3D v4 Files\cybervol_IFR"       I  shouldn't  see   the  first  ".flt"   , if only  the last " .flt"  is removed   by FSUIPC  ? 

    thanks you

  3. Good morning

    Quote

    All it does if find the last '.' character in the name, then if the string at that position is equal to ".flt", replaces that with a zero, as string terminator.

    I have made two tests ;  but  program NOT   processing  loading  ;       uploaded  2   files  result     upload  failed   and message  error  ??  can you open its    ?  

    -Second TEST  Log       "FSUIPC5.log  "          just write       cybervol_IFR.flt.flt      _    ( Document "FSUIPC4 offsets status  mentions"   at 3F04 : "There must be a zero terminator"  , but you said     program replaces    ".flt" with a zero 

    -First  TEST  , LOG renamed   "FSUIPC5.log-test1.txt"    program  write          cybervol_IFR.flt.flt0   ( I  add  zero terminated  )

    Attention , it's in ASCII string and      0 terminated   ASCII  is  coded  hexa  (30) Perhaps   it's the   problem  now   ? ( but not problem with OLD FSUIPC   4.9.39-  p3D4.1    4.9 which load  OK,  you can  believe me )

    Quote

    Can you enable "extras" logging

    setting via    P3D Menu  -> add-ons  -> FSUIPC   : Logging  ( extra..) ;   generated in FSUIPC.INI   LogExtras=Yes    ; is it correctly what you wanted ?    How can do  otherwise

    thank yo very much for your  time and help  

  4. Thanks for all  explications

    Quote

    Meanwhile, can you try adding another .flt at the end? eg. cybervol_IFR.flt.flt

    I tried, but NOT work !   

    Quote

    Shouldn't your program be updated to use FXML files?

    we have  many files ( nearly  1000 files)  made in format Flt , ready for flying   between any airport;  it's very  important work to  translate them  in FXML format and this affect more than one program  ;  we have to do this in the future 

    Quote

    FSUIPC5. A flag set in offset 3F00 (not just 0 to load a flight, but another value to load a "deprecated" .FLT file, or just leave the extension alone. 

    Is it possible for you ?     this will be  match  with  two  types of P3D scenario files  describe in SDK   ;     "legacy scenario flight file  format.FLT"   go on working in P3D v4,    I tested    load manually by menu  P3Dv4  ,     and have  tested   via  console command,    to run P3D flight pre loaded , it's work also   

      D:\P3D4\Prepar3D.exe "-flt:C:\Users\Dev_cip\Documents\Prepar4D v4 Files\cybervol_IFR.flt"    (for  my "soft" configuration) _  Only problem via offset FSUIP when pilot choose change currently flight

    Sorry , but now  it 's night in France,  I will continue tomorrow ;  thanks you for your attention and your  help ; regards

  5. thanks for reply and help

    the FSUIPC log,( monitoring 3F04 is cancel  size 80, but in log file, command WRITE is display for 252 caracters (953657 WRITE0[0]  3F04,  252 bytes: 63 79 62 65 72 76 6F 6C 5F 49 46 52 2E 66 6C 74  cybervol_IFR.flt0....  ..)-

    Quote

    “Something seriously wrong with your installations”  : the way you are using the offsets. The flight loading and saving facilities via the offsets are working fine ... saving facilities via the offsets are working fine ... I don't think P3D3.4 supports the old .flt format files.  Flight files are in XML

    -Same problem occurs for other installation of experimented virtual pilots .

    -I confirm processing NEW load via offset Works correctly for FXML file, in the same program ; problem limited for file format FLT ( excepted  FSUPC 4.9.3_)

    Perhaps format file FLT is not supported now in FSUIPC ? ; I have read extension flight file is not required since FSUIPC 4.97 , (  .FLT  discarded to process new fxml file ?);  I have tried with and without extension , same result . Forever, referencing repar3d.com/SDKv4/LearningCenter.php , overview, I thing "FLt" is not again obsolete  for P3d v4,  ( what time ?)

    There are two types of scenario files:

    • Legacy Scenario (Flight) Files which have the file format .FLT and are in the INI file format.
    • New Scenario Files which have the file format .FXML and are in the XML file format

    sed with P3D version 2, FSUIPC discards the .FLT part of any request to load a flight via offsets, so that the new XML format flight file may be loaded instead.

    It's very  important time to translate many file " flt"(with plan file) ,  created by Cyberavia;  Cyberavia Program is a freeware, wrote by Fabrice Erdinger( who died 3 ears ago) he was founder of French association CYBERAVIA ( www.cyberavia.org),  preparing and examining flight for virtual Pilot (FSX and P3D)

    Thanks for FSUIPC  log expertise , Regards

     

    FSUIPC5.log

  6. Morning,    I can't change currently Flight in P3D v3,4 when using FSUIPC offset in program . Occurs with P3D v3.4.22 -FSUIPC 4.971 and P3D v4.1.722 -  FSUIPC   5.14 and  5.13   -BUT the same CyberAvia’s Program loads, via offset, this file( format FLT) correctly in P3D v1.3, and FSUIP 4.9.39 ; Loading  this File “FLT”  using  P3D interface  menu( “LOAD”)is OK,  or via batch command  to run P3D with flt argument ; -the same CyberAvia’s program loads flight Files in format  “fxml” correctly via offset , in all of this version P3D.

    Execution: instructions to change currently Flight when aircraft is ready to fly, on the ground. CyberAvia ’s program provides name of the Flight  file (.flt)  at offset  3F04,  plus zero terminator, and load by writed at offset 3F00,  2 bytes (00 00 ) ;Windows of P3D  became black, sound of currently aircraft motors is still going , no load for changing flight  is processing ; waiting few minutes and  then ESC and “resume”  and P3D displays initial situation  aircraft .

    I don’t understand why no works on configuration FSUIPC/DP3Dv3-P3Dv4; l don’t find fsuipc v5 DSK,  but I think this offset is still available ?  I’m Cyberavia ‘s member ,developper, ( not virtual Pilote) , trying to update CyberAvia ‘s Program (named “Boite Noire”) to P3D v3 and P3D v4 _ Regretted Fabrice Erdinger  wrote this program for old FSx (?)  using IPC6  calling  FS98; I begin knowledge of FSUIPC ans P3D,  Can you help me to debug ?    Thanks  very much, regards 

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