Nervures

Hi Pete, After installing the latest version of FSUIPC the sim crash between 45' to 1h30 after takeoff with the FSUIPC5.dll error. I only fly with 777 PMDG ( up to date last release ) and never had this before with all 5.103 versions ( FSUIPC5.dll error ). Only ucrtbase.dll error. Event report at 23.44.05 04/08/17 Faulting application name: Prepar3D.exe, version: 4.0.28.21686, time stamp: 0x594a7255 Faulting module name: FSUIPC5.dll, version: 5.1.1.0, time stamp: 0x59804dd2 Exception code: 0xc0000005 Fault offset: 0x0000000000047fb3 Faulting process id: 0xaa8 Faulting application start time: 0x01d30d6139722b0a Faulting application path: C:\P3D4\Prepar3D.exe Faulting module path: C:\P3D4\Modules\FSUIPC5.dll Report Id: 08f4f635-795e-11e7-bf33-e03f491af142 Event report .NET Runtime at 23.44.03 04/08/17 Application: Prepar3D.exe Framework Version: v4.0.30319 Description: The process was terminated due to an unhandled exception. Exception Info: exception code c0000005, exception address 000007FED39D7FB3 Event report at 00.45.04 04/08/17 Faulting application name: Prepar3D.exe, version: 4.0.28.21686, time stamp: 0x594a7255 Faulting module name: FSUIPC5.dll, version: 5.1.1.0, time stamp: 0x59804dd2 Exception code: 0xc0000005 Fault offset: 0x0000000000047fb3 Faulting process id: 0x17e0 Faulting application start time: 0x01d30c9a7031d891 Faulting application path: C:\P3D4\Prepar3D.exe Faulting module path: C:\P3D4\Modules\FSUIPC5.dll Report Id: 6371ffd6-789d-11e7-925e-e03f491af142 Event report .NET Runtime at 00.45.03 04/08/17 Application: Prepar3D.exe Framework Version: v4.0.30319 Description: The process was terminated due to an unhandled exception. Exception Info: exception code c0000005, exception address 000007FED18D7FB3 The culprit is ? After the crash when the simulator restarts with my own LUA backup script I do not have crash anymore and I can fly 8 9 10 hours. Kinds regards. Francis. FSUIPC5 Install.log FSUIPC5sav.log

New screenshots. Francis.

Hi Pete, Best thanks for your answer. I use LUA script to send text into the "SimConnect Message Window version 5.11 " or "Message Window version 5.103". ipc.display("Situation sauvegardée sous "..nomt,1,10). Attached two screenshots. The first with 5.11 and the second, as I keep the previous versions, with 5.103. "sauvegardée" is correct with 5.103 not with 5.11. Kinds regards. Francis.

Hi Pete, I use french text, into the "SimConnect Message Window", with accents. Since 5.11 the accents have disappeared and are replaced by a "hieroglyph". Thanks for reply. Kinds regards. Francis.

Hi Paolo, cool. Have a good flights with 747. Francis.

No but since the release of P3D4 there are so many updates ( GSX FSUIPC EZCA LINDA P3D ) that when a simmer reports an issue the first thing to do is to check the updates. Maybe the HotFix will fix this issue ? rsrandazzo (pmdg) says: You must uninstall the 777 before reinstalling it. Maybe a bad install ? https://www.avsim.com/forums/topic/515035-current-best-practice-when-updatingreinstalling-pmdg-aircraft/#comment-366847 For the 777 offset 65A2 which remained at 0 version 5.103b only supports the offsets for the 747. You have released the 5.103e that works for me. Then 5.103.g doesn't work with my LUA script. You have released the 5.103j that works for me. Why ? I don't know. I try to help you as far as I can. Francis.

I confirm. See log. I confirm it works too with 5.103j. Log attached Francis FSUIPC5.103e.log FSUIPC5.103j.log

HI Pete and Paolo, two important links https://www.avsim.com/forums/topic/514807-13jul17-quick-update-from-us/ http://www.prepar3d.com/news/2017/06/114375/ CPF_PAOLO =>Prepar3D.exe version = 4.0.23.21468 last version is Prepar3D.exe version = 4.0.28.21686 Francis.

Hi Pete, fantastic these version works. FSUIPC5.log line 470 offset=1 :-)) PMDG777offsets=Auto You are GREAT. Thanks a lot. Francis. FSUIPC5.log

Hi Pete, run as administrator the new intaller. In the Fsuipc.ini the parameter => PMDG777offsets remains at Yes. Strange no ? Launch the sim and the offset reamains at 0 Modify the parameter to Auto: the same. To No: the same. Here is the file. Francis. FSUIPC5 Yes.log FSUIPC5 Yes.ini FSUIPC5 Auto.log FSUIPC5 Auto.ini FSUIPC5 No.log FSUIPC5 No.ini FSUIPC5 Install.log

Thank you very much Pete. At work for now. I will test in the evening. The parameter => PMDG777offsets= Auto or Yes ? Do you want I try both ? Francis.

Thank for the reply. Waiting for the test version. Have a good day. Francis.

I know you do not have the 777 pmdg but do you know where this setting is? Otherwise I have to look for exactly what ? " Hmmm. That's strange, because the log does show that the 777 offsets are enabled" My last log is with PMDG777offsets=Yes My settings are the same as for 5.103e. Yesterday I made a flight ( 5.103e ) of 15h without problems with the last update of the 777 PMDG. Francis.

Hi Pete, Unfortunately I just test and the offset still remains at 0. The same with the parameter=No. Here is the files. Francis. FSUIPC5.ini FSUIPC5.log

Hi Pete, here is the files. Regards. Francis. FSUIPC5.ini FSUIPC5.log

I finish my flight between OTBD (ex OTHH) NZAA (5.103e). Arrival scheduled for 1630z. I will run the simulator with the 5.103g and I will send you the fsuipc.log. I will also test other offsets. 1 when there is text in the scratchpad. 0 when empty. It remains at 0 and my LUA script wait 1 to continue. Francis.

Dear Pete, thank you very much for your quick answer. Oftset 65A2 remains at 0 ( see my previous topic ) with 5.103g as 5.103.b. As you do not have 777 pmdg how i can do to help you. Regards. Francis. 777 PMDG last up to date (13 july )

Hi Pete, I monitor many offsets in my LUA scripts for 777 PMDG. As in the version 5.103b the offset 65A2 doesn't work with 5.103g. Can you confirm that the 777 offsets are supported in the 5.103g as before ( 5.103e ) ? In advance, thank you for your answer. Regards. Francis.

Hi Pete, offset 65A2 works as before. Thank you very much for the update. Best regards. Francis.

Dear Pete, thank you very much for your quick answer. Continue with 5.103. Best regards. Francis.

Hello Pete, I use the offset 65A2 (777 PMDG) in my LUA scripts. This offset = 0 when there is no text in the scratchpad of the CDU. 1 when there is text. Since version 5.103b the value of the offset remains at 0 when text is present. As this blocks the programming progression I came back to version 5.103 which works well. Can you check what is wrong so that I can continue to use your latest updates. My two .log (with 5.103 and 5.103b) that show the issue. FSUIPC5.log v5.103: line 310 to 460 offset=0 then offset=1( very nice :-)) ) FSUIPC5.log v5.103b: line 311 to the end offset=0 (I ended the flight ) W7, P3DV4 Hotfix1, Linda 3.0.0 for P3D 64-bit, EZCA 2.5. 777 PMDG up to date. Best regards. Francis. FSUIPC5 v5.103.log FSUIPC5 v5.103b.log

Hi Pete, perfect. All sounds work. A big MERCI. Francis

Hi Pete, I use LINDA 3.0.0 Beta Build 678. handlers-hid.lua function SHIFT_MODE_SET (m) if ipc.get('RUNAWAY') then buttonRepeatClear(jid) end SHIFT_MODE = m if m == 0 then sound.play("modereset") else sound.play("modechange") end _log("[hHID] SHIFT MODE = " .. m) end modereset.wav and modechange.wav are into C:\P3D4\Sound FSUIPC5.INI: [Sounds] Path=C:\P3D4\sound\ Device1=Haut-parleurs (3- C-Media USB Headphone Set ) Device2=Périphérique audio principal No sound when I use the SHIFT_MODE_SET( 0,1,2 ). With v3 I have the sound. sound.play from LUA Library works with V4 ? Best regards.

Hi Pete, I have just sent you a mail to your address. Regards. Francis.

Hi Pete, For the moment it is the only offset that is problematic. I monitor the FSUIPC offsets with linda. FSUIPC4.log version 4.959: 270802 LUA.2: LINDA:: [O] Offset: UB 0x6C1C = 0 273360 LUA.2: LINDA:: Watching new offset: 6C1C:UB:DEC:*1/1 = 0 882747 LUA.6: PLVfin. PLV 777 annonce.lua. 882809 LUA.2: LINDA:: [O] Offset: UB 0x66D3 = 0 909579 LUA.7: GsxDep = 1. Valeur <4 ou 5. PBR du GSX.lua. 909579 LUA.7: key PBR = 49 909641 LUA.2: LINDA:: [O] Offset: UB 0x66C5 = 1 911701 LUA.7: Pushback nose right demandé. PBR GSX.lua. 911716 LUA.7: GsxBoard = 5 PBR GSX.lua. 911716 LUA.7: GsxDep = 1. Valeur <4 ou 5. PBR du GSX.lua. 996284 LUA.2: LINDA:: [O] Offset: UB 0x6C1C = 1 996456 LUA.2: LINDA:: [O] Offset: UB 0x66D3 = 1 1008312 LUA.2: LINDA:: [O] Offset: UB 0x66D3 = 0 FSUIPC4.log version 4.962a 183270 LUA.2: LINDA:: [O] Offset: UB 0x6C1C = 0 184018 LUA.2: LINDA:: Watching new offset: 6C1C:UB:DEC:*1/1 = 0 774420 LUA.6: PLVfin. PLV 777 annonce.lua. 774498 LUA.2: LINDA:: [O] Offset: UB 0x66D3 = 0 787773 LUA.8: GsxDep = 1. Valeur <4 ou 5. PBR du GSX.lua. 787773 LUA.8: key PBR = 49 787929 LUA.2: LINDA:: [O] Offset: UB 0x66C5 = 1 789911 LUA.8: Pushback nose right demandé. PBR GSX.lua. 789911 LUA.8: GsxBoard = 5 PBR GSX.lua. 789911 LUA.8: GsxDep = 1. Valeur <4 ou 5. PBR du GSX.lua. Stop programming. Offset does not go to 1. IRS aligned in the 777. Regards. Francis.