Jump to content
The simFlight Network Forums

Nervures

Members
  • Posts

    54
  • Joined

  • Last visited

Posts posted by Nervures

  1. Hi,

    Since the version EZCA v3 the changes of views via the command ipc.keypressplus are not always functional.

    Some work as before and others not as described below.

    Here is my code that to work must be sent twice:

        ipc.control(66508,414)-- 66508 = PANEL_ID_CLOSE FO ND
        ipc.control(66508,420)-- 66508 = PANEL_ID_CLOSE FO CDU
        ipc.control(66508,402)-- 66508 = PANEL_ID_CLOSE CPT CDU
        ipc.control(66508,415)-- 66508 = PANEL_ID_CLOSE FO PFD
        ipc.sleep(4000)
        ipc.keypressplus(49,11,4)      FIRST
        ipc.sleep(500)
        ipc.keypressplus(49,11,4)    SECOND

    This is the CTRL + SHIFT + 1 (main keyboard) combination to switch from the cockpit view to the exterior view.

    The culprit is my code or EZCA v3 ?

    Prepar3D 4.5, EZCA v3, FSUIPC 5.152.

    Thank you in advance for your replies.

    Francis.

     

  2.  

    Good morning Pete,

    Unfortunately the simulator crashed 5 hours after the take-off. Flight YPPH-FACT (12h45 ).

    You said: " Previous crashes reported in that DLL have been eventually attributed to other problems in P3D."

    I know you can not do anything.

    It's just to keep you informed.


    Event viewer report:

    Faulting application name: Prepar3D.exe, version: 4.0.28.21686, time stamp: 0x594a7255
    Faulting module name: ucrtbase.DLL, version: 10.0.10586.788, time stamp: 0x5879ab76
    Exception code: 0xc0000005
    Fault offset: 0x000000000000443a
    Faulting process id: 0x1608
    Faulting application start time: 0x01d3150293632fce
    Faulting application path: C:\P3D4\Prepar3D.exe
    Faulting module path: C:\Windows\system32\ucrtbase.DLL
    Report Id: d5acde7b-8128-11e7-b7ec-e03f491af142

    Launch the simulator from backup.

    After landing when I closed the simulator it crashed.

    Event viewer report:

    Faulting application name: Prepar3D.exe, version: 4.0.28.21686, time stamp: 0x594a7255
    Faulting module name: ntdll.dll, version: 6.1.7601.23807, time stamp: 0x5915fdce
    Exception code: 0xc0000374
    Fault offset: 0x00000000000bf3e2
    Faulting process id: 0x22f4
    Faulting application start time: 0x01d31535ff1812b8
    Faulting application path: C:\P3D4\Prepar3D.exe
    Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
    Report Id: aee83b42-8169-11e7-b7ec-e03f491af142

    Francis.

     

     

    FSUIPC5 crash.log

    FSUIPC5 close.log

    UCRTBASE 1.PNG

    UCRTBASE 2.PNG

    Close P3D 1.PNG

    Close P3D 2.PNG

  3. 1 hour ago, Pete Dowson said:

    How did the FSUIPC5.LOG end

    It was late and I restarted manually my backup which has overwritten the file . My backup is corrupted (first time it does not work).
    I'm flying at the moment on an identical flight and I scheduled a backup of the FSUIPC5.log if a crash occurs. I know you save it but if I am not in front of the screen at the time of the crash the restore of the backup is done automatically and overwrites the file.
    I keep you informed.

    Francis.

  4. 3 minutes ago, Pete Dowson said:

    But the undocked values should be screen coordinates, with negative values for screens to the left of the default, as so on. That seems to work pretty well here but needs more testing.

    I confirm. Work pretty well here too.

    9 minutes ago, Pete Dowson said:

    I'm going to be very busy with other things in the next 3-4 weeks, so I might disable this new facility for now so I can make a release with the Lua fix which you are testing so ably for me!

    No problem Pete.

    I can fly and this is the most important.

    Francis.

  5. 1 hour ago, Pete Dowson said:

    1. Are you running P3D4 in full screen?

    No.

    1 hour ago, Pete Dowson said:

    2. If not full screen mode, if P3D4 maximized?

    Yes.

    1 hour ago, Pete Dowson said:

    3. Do you have other screens where you move undocked windows to?

    No.

    1 hour ago, Pete Dowson said:


    So far I cannot make any docked or undocked saved window parameters go wrong.

    While waiting for a solution I delete all saved parameters from the three windows before starting the simulator. It works very well.

    20 hours ago, Pete Dowson said:

    I assume those other entries are in the [LuaFiles] or [Macros] section? They just list the files you have in your Modules folder. Looks like you made copies of those listed there!

    I found a lua file in the Modules folder that was not added => Sauvegarde_Auto_777.lua. Why ?

    I added it manually.

    Francis.

  6. Hi Pete,

    12 hours ago, Pete Dowson said:

    These are where FSUIPC records the size and position of the different types of SimConnect window, so it can restore them in the next sesion.

    I have some difficulties to understand how the parameters of windows are recorded.

    1 I deleted all the parameters of windows:

    [Window.Message Window]

    [Window.SimConnect Message Window]

    [Window.SimConnectWindow]

    2 I launched the simu:

    [Window.Message Window]
    Docked=194, 925, 15994, 234
    [Window.SimConnect Message Window]
    Docked=1057, 1450, 14268, 690
    [Window.SimConnectWindow]

    Red parameters are perfect.

    3 I opened GSX menu ( CTRL+F11 ):

    [Window.Message Window]
    Docked=194, 925, 15994, 234

    [Window.SimConnect Message Window]
    Docked=1057, 1450, 14268, 690

    [Window.SimConnectWindow]
    Docked=6609, 6962, 3173, 2749

    Still perfect for the three windows

    4 Resized [Window.SimConnectWindow]

    Docked=6609, 6962, 3173, 4365

    Still perfect.

    5 Undocked the [Window.SimConnect Message Window] and [Window.SimConnectWindow]

    [Window.Message Window]
    Docked=194, 925, 15994, 234
    [Window.SimConnect Message Window]
    Docked=1117, 1851, 14259, 676
    Undocked=3028, 616, 554, 276
    [Window.SimConnectWindow]
    Docked=67, 414, 16248, 15859
    Undocked=2634, 552, 391, 417

    Undocked, position and size ( from linda.gui.ini ), are perfect.

    Why the [Window.SimConnect Message Window] and [Window.SimConnectWindow] Docked parameters changed ?

    I undock these two windows from my main screen to my second screen by using mouse.move mouse click.

    ipc.display("Tests",1,5)
        ipc.sleep(1000)   
        mouse.move(329,109)
        mouse.click(2)
        ipc.sleep(200)  
        mouse.move(379,121)
        mouse.click()

    When I restart the simulator, as positions are not good, I cannot any more undock these windows. It's as if another program modified these parameters.

    Francis.

     

     

     

     

     

     

     

  7. Hi Pete,

    9 hours ago, Pete Dowson said:

    I assume those other entries are in the [LuaFiles] or [Macros] section? They just list the files you have in your Modules folder. Looks like you made copies of those listed there!

    I understand now. Before entries were manual.

    Yes backup copies.

    Yesterday I made the same flight with the crashes => no crash during flight (6h) and no crash when the sim closes.

    I continue the flights this weekend.

    Francis.

  8. Hi Pete,

    I have just looked at my file FSUIPC5.ini and it was modified. I suppose by the new .dll.

    Can you tell me if it seems to you correct ?

    New entries:

    ConsoleWindow=25,25,702,384

    38=777COM - Copy
    39=777NGX - Copy
    40=Demauto - Copy
    41=GSX - Copy
    42=GSX_Arr - Copy
    43=Autobrake - Copy
    44=choix - Copy
    45=Followme - Copy
    46=RAAS - Copy
    47=RWstart - Copy

    [Window.Message Window]
    Docked=389, 4130, 15927, 234

    [Window.SimConnect Message Window]
    Docked=1438, 1105, 14183, 690
    Undocked=3028, 616, 553, 275

    [Window.SimConnectWindow]
    Docked=67, 414, 16248, 15859
    Undocked=2634, 552, 391, 417

    Francis.

    FSUIPC5.ini

  9. Hi Pete,

    thank you so much for your answer.

    20 minutes ago, Pete Dowson said:

    One thing I should ask: why are you opening and closing the same file every second? Why not open it once at the start and close it at the end? (You should also check that file is not nil after the io.open).

    It was a deceased friend who wrote this code. I am a beginner in programming LUA.

    What I can tell you is that it is in the backup ( Sauvegarde in french ) function. Here is the code:

    function Sauvegarde ()
        Mod = ipc.get("Mod")
        pbk = ipc.get("pbk")
        RW = ipc.readUB(0x7003)
        stage = ipc.readUB(0x7001)
        dem = ipc.readUB(0x7000)
        nomlog = ipc.get("nomlog")
        nomlog2 = ipc.get("nomlog2")
        icaoI = ipc.readSTR(0x66E3,4)
        icaoD = ipc.readSTR(0x700A,4)
        DP = ipc.readUB(0x7004)
        voxatc = 0
        kml = ipc.get("kml")
        Pistpref=ipc.readSTR(0x700E,3)
        lonpist = ipc.readUW(0x66D1)
        lat2 = ipc.readDBL(0x7300)
        lon2 = ipc.readDBL(0x7308)
        PMDG = ipc.readSTR(0x7005,5)
        nomvar1 = {"Mod","pbk","dem","stage","mont","FRC","fin","baro","RW",
                "nogsx","tp","metper","tpv","chkl","prop","Chemin","FSXchem",
                "typ","AES","cd","cg","nomlog","nomlog2","icaoI","icaoD",
                "Chemlog","Chemsav","DP","voxatc","kml","Pistpref","lonpist","lat2","lon2","gmt","PMDG","Lastwp"}
        valvar1 = {Mod,pbk,dem,stage,mont,FRC,fin,baro,RW,nogsx,tp,metper,
                tpv,chkl,prop,Chemin,FSXchem,typ,AES,cd,cg,nomlog,
                nomlog2,icaoI,icaoD,Chemlog,Chemsav,DP,voxatc,kml,Pistpref,lonpist,lat2,lon2,gmt,PMDG,Lastwp}
        local count = 0
        for _ in pairs(nomvar1) do count = count + 1 end
        file = io.open(Chemlog.."Linda777.log", "w+")
        for i = 1 , count do
            if valvar1 == nil then valvar1 = "nil" end
        file:write(valvar1)
        file:write("\n")
        end
        file:close()

    This function is called by the Timer function.

    46 minutes ago, Pete Dowson said:

    Anyway, none of this explains why FSUIPC crashes in P3D4 but not P3D3.

    Yesterday I made a long-haul flight (8h with P3D4) without crash. Only the crash when the simulator is closing.

    Event report 10/08/2017 02:27:56

    Faulting application name: Prepar3D.exe, version: 4.0.28.21686, time stamp: 0x594a7255
    Faulting module name: ntdll.dll, version: 6.1.7601.23807, time stamp: 0x5915fdce
    Exception code: 0xc0000374
    Fault offset: 0x00000000000bf3e2
    Faulting process id: 0x1e04
    Faulting application start time: 0x01d31126f7632cb4
    Faulting application path: C:\P3D4\Prepar3D.exe
    Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
    Report Id: c13264e4-7d62-11e7-a1f1-e03f491af142

    Kinds regards.

    Francis.

     

  10. Hi Scot/Pete,

    35 minutes ago, Scotfleiger said:

    I would suggest you disable all your add-ons and enable each in turn to find out which one is causing your crashes.

    I use LINDA EZCA AS16 and IVAP.

    For Scot ( Pete already know ):

    a friend, now deceased, has developed a co-pilot of 777 in LUA programming (12 scripts ). Like Fs2Crew but much more complex. This programming needs AS16 LINDA and EZCA. I have some basics in LUA but not enough, I think, to reprogram without these add-ons. I'll try it anyway. If I can not do it two options: return to V3 which works without any crash or accept crashes in v4 (when I restart the simulator with my backup it does not crash until the end of the flight (8 10 12 hours)).

    I'll keep you informed.

    Thank you both for your help.

    Kinds regards.

    Francis.

  11. Hi Pete,

    That night same flight as the previous ones with the Scott's recommendation. The sim crashed: DINPUT8.dll instead of FSUIPC5.dll.

    Event report:

    Faulting application name: Prepar3D.exe, version: 4.0.28.21686, time stamp: 0x594a7255
    Faulting module name: DINPUT8.dll, version: 6.1.7600.16385, time stamp: 0x4a5bdecf
    Exception code: 0xc0000005
    Fault offset: 0x000000000000a909
    Faulting process id: 0x2340
    Faulting application start time: 0x01d30fc8a177a157
    Faulting application path: C:\P3D4\Prepar3D.exe
    Faulting module path: C:\Windows\system32\DINPUT8.dll
    Report Id: 31776d02-7bce-11e7-802e-e03f491af142

    I await the opinion of Scott.

    Kinds regards.

    Francis.

  12. Hi Scott,

    sorry for this late response but I was busy all day.

    13 hours ago, Scotfleiger said:

    I would strongly recommend you move your code to a file named user.lua

    I move my code to the file named "user.lua" in the same folder C:\P3D4\Modules\linda\aircrafts\PMDG 777.

    I deleted the "actions.lua" and replaced it with the one in the zip PMDG_777_v_1_3 => Best practice from this moment is DO NOT MAKE ANY CHANGES in original actions.lua file.

    FSUIPC5.log => 84522 LUA.3: LINDA:: [USER] User's modifications script is loaded...

    13 hours ago, Scotfleiger said:

    ........ It will also allow us to isolate the problem.

    I have to make a new flight with LINDA verbose logging ?

    Kinds regards.

    Francis.

     

     

     

  13. Hi Scott,

    Thank you for your help.

    19 hours ago, Scotfleiger said:

    I suggest you temporarily remove some of the extra functions to isolate the issue.

    Which extra functions ? For me they are all necessary.

    Under P3D v3 no crashes. V4 and 5.11 FSUIPC.dll error and Pete said: "Looks like something to do with LINDA" .

    19 hours ago, Scotfleiger said:

    I would also suggest you turn on Verbose logging in LINDA to see whether it is at fault as Pete suggests. 

    It's done. Attached two FSUIPC5.log. Same flight as the previous one.

    In the reports I left empty lines to make it more readable.

    FSUIPC5_prev.log => From the beginning to the crash.

    FSUIPC5.log => From the crash to the end of the flight.

    21 hours ago, Pete Dowson said:

    I cannot really progress this any further. It needs someone from LINDA to take a look, probably with the Lua debug/trace option enabled.

    I enabled the Lua debug/trace but this greatly slows the action of the keys programmed in LINDA.  I will try to use the keyboard.

    19 hours ago, Scotfleiger said:

    I do have one issue as one of your LUA add-ons uses a file called actions.lua. This is also the name of the key LINDA aircraft module code and may result is some unknown adverse effects.

    Same file. My LUA script is inside your actions.lua: C:\P3D4\Modules\linda\aircrafts\PMDG 777.

    Kinds regards.

    Francis.

    FSUIPC5_prev.log

    FSUIPC5.log

  14. Hi Pete,

    20 hours ago, Pete Dowson said:

    The "successful" log doesn't terminate correctly. It is still waiting for SimConnect to tell it to close down. Did the sim hang?

    Yes. APPCRASH Prepar3D.exe Fault Module Name: api.dll.

    Since P3 I always have a crash when closing the simulator. StackHash_b8ce, StackHash_e561, api.dll, KERNELLBASE.dll ........

    20 hours ago, Pete Dowson said:

    Would it crash again in exactly the same place?

    No. I did the same flight and the crash happened later.

    20 hours ago, Pete Dowson said:

    What about other flights, different routes? Do all crash?

    Yes with 5.11 six flights and six crashes with FSUIPC5.dll error.

    With 5.103j sometimes but never FSUIPC5.dll error. Only ucrtbase.dll.

    P3D v3 no crashes :-))

    21 hours ago, Pete Dowson said:

    probably with the Lua debug/trace option enabled.

    I enabled the Lua debug/trace but this greatly slows the action of the keys programmed in LINDA.  I will try to use the keyboard

    Kinds regards.

    Francis.

  15. Hi Pete,

    5 hours ago, Pete Dowson said:

    So you are restarting the sim, so LINDA starts agan too. So everything is the same as before, but no crash?

    Yes. LINDA but AS16 ASCA IVAP too.

    Two FSUIPC5.log attached.

    1 FSUIPC5sav.log => the sim starts at:    System time = 04/08/2017 22:35:40   and crashes after the waypoint KUSVA ( 3903660 LUA.6: OK KUSVA ). SITPO (3597337 LUA.6: OK SITPO ) is the waypoint before KUSVA.

    Crash at: Event report at  23.44.05   04/08/17

    2 FSUIPC5.log => the sim restarts at:    System time = 04/08/2017 23:44:51 and the first waypoint is SITPO ( 342718 LUA.9: OK SITPO ) then KUSVA ( 3903660 LUA.6: OK KUSVA ) to the end of flight without crash. Autosave every 15'.

    18642353 LUA.5: Landing checklist complete.

    20171771 Sim stopped: average frame rate for last 19990 secs = 41.6 fps
    20171771    Max AI traffic was 0 aircraft
    20174345 === Closing session: waiting for DLLStop to be called ...

     

    In the reports I left empty lines to better see the important points.

     

    5 hours ago, Pete Dowson said:

    What else have you changed?

    Nothing.

    Kinds regards.

    Francis.

     

     

     

    FSUIPC5sav.log

    FSUIPC5.log

  16. Hi Pete,

    1 hour ago, Pete Dowson said:

    What exactly is the difference -- what is "my own LUA script"? An alternative to LINDA?

    My LUA script is like your Autosave. If the sim crashes the LUA restarts the sim to the last save. LINDA saves flights ?

    1 hour ago, Pete Dowson said:

    unless you can enable Lua debug/Trace in the FSUIPC Logging options and tolerate the huge log you'd get

    Busy tonight I will do it tomorrow night.

    1 hour ago, Pete Dowson said:

    Did you jump direct from 5.103 to 5.11, with no interim updates?

    No. 5.103,b,e,g,j. Same for LINDA3.0.0 614,664,673,678,689 and 3.0.1.

    1 hour ago, Pete Dowson said:

    Can you report with all the details to LINDA support.

    I'll do it but late tonight.

    1 hour ago, Pete Dowson said:

    To that end I'll edit the title to refer to LINDA. Okay?

    Okay. Thanks.

    See you tomorrow evening.

    Francis.

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