Jump to content
The simFlight Network Forums

MarkStallen

Members
  • Posts

    101
  • Joined

  • Last visited

Everything posted by MarkStallen

  1. It crashes like I found in the windows logbook (probably the applicationevents). Nothing in the taskabr after crash and process stopped working. found the FSUIPC_WASM.log FBW is installed with the installer with lastest version. Will try without Mobiflight WASM installed FSUIPC_WASM.log
  2. This the log with debug in WASM en trace under [WAPI] FSUIPC7.log
  3. Found this in windows.logbooks - System - Provider [ Name] Windows Error Reporting - EventID 1001 [ Qualifiers] 0 Version 0 Level 4 Task 0 Opcode 0 Keywords 0x80000000000000 - TimeCreated [ SystemTime] 2021-09-01T12:36:40.6028060Z EventRecordID 25579 Correlation - Execution [ ProcessID] 0 [ ThreadID] 0 Channel Application Computer stallen-server Security - EventData 1882757301474280260 4 APPCRASH Niet beschikbaar 0 FSUIPC7.exe 7.2.0.8 6128fe7c FSUIPC7.exe 7.2.0.8 6128fe7c c0000005 0000000000088cab \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERA686.tmp.dmp \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERA6E5.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERA705.tmp.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERA705.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERA716.tmp.txt \\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_FSUIPC7.exe_ee9a9e8f4e332381a339e4182165414f32fca_f355a881_3770d140-bb7d-428c-9d78-c47e1390b08e 0 b2aa5d11-f1f4-4930-8385-32be5be8cc8a 268435456 4edba0a7380417068a20e5ca58a5c344 0
  4. Problem persists. It's not visible in the taskbar en the process stops. Running the dev version of FBW. FSUIPC stopt working after update to 7.2.8.. Previous version was working with the same dev of FBW. Debug is on, but can't find FSUIPC_WASM.log FSUIPC7.log
  5. It's stops and isn't visible anymore. I can only restart with the same result. Here is the log with Trace. FSUIPC7.log
  6. It doesn't crash with an error it just stops . If I put in EnableWAPI=No then it works (offcourse without WASM)
  7. I also tried to go back with FSUIPC v7.2.0d (only the exe) , that works accept the LVARS-list is empty. (probably due to the change of fsuipc-lvar-module)
  8. I downloaded the new version of FSUIPC for msfs 2020 but now as I start-up it stops after initial load (see log). Previous version had no problems. ini has not changed etc. I provide the log-file and my ini FSUIPC7.log FSUIPC7.ini
  9. It's the A32NX FBW. I couldn't find an event or LVAR either. Previous version( I don't know if it's MSFS or the FBW Dev version) was working.
  10. Offset 0B46 seems not to work any longer with update 5 of MSFS 2020
  11. If I use SD and FLT32 or 0x and FLT64 then they both give 0.0000000 If I list the Lvars with FSUIPC then the value = 1576.3274 I really don't understand because all my other lvars are working, but as soon as it's more than one byte it doesn't. in my ini : [LvarOffsets] 0=A32NX_BRAKES_HOT=UB66C1 1=A32NX_AUTOBRAKES_DECEL_LIGHT=UB66C2 2=A32NX_AUTOBRAKES_ARMED_MODE=UB66C3 3=A32NX_MASTER_WARNING=UB66C4 4=A32NX_MASTER_CAUTION=UB66C5 5=A32NX_PARK_BRAKE_LEVER_POS=UB66C6 6=A32NX_ECAM_SD_CURRENT_PAGE_INDEX=UB66C8 7=XMLVAR_Baro1_Mode=UB66C9 8=LANDING_2_Retracted=UB66D0 9=LANDING_3_Retracted=UB66D1 10=LIGHTING_LANDING_1=UB66D2 11=LIGHTING_LANDING_2=UB66D3 12=LIGHTING_LANDING_3=UB66D4 13=A32NX_HYD_BRAKE_ALTN_ACC_PRESS=0x66D5
  12. Probably doing someting wrong In ini : 13=A32NX_HYD_BRAKE_ALTN_ACC_PRESS=SD66D5 If I list the LVAR with FSUIPC value=1576.3274 If I look at the LVAR (offset 66D5) in the monitor I get with SIF32 : 0.01953125 with S32 : 5 I tried several diferent assignements aswell in the ini file as in the monitor. I can't find the right couple.
  13. Yes sorry about that, was only looking in the PDF.
  14. In Simconnect there is a variable that's call autobrakes_active. Can't find that one in the offset-list. Is there a way to read this parameter?
  15. I made it so cheap and simple so in a few minutes, I can easily change aircrafttype. Only waiting for the paint and whitepaint markers to give the panels a paintjob.
  16. Milan, I was specific looking a the A320 FBW. You said "you can try outputting the MCDU trough web socket" , but where and how can I find this HTML/CSS/JS data. I've programmed a MCDU using VB6, FSUIPC and Mobiflight-events just to use it on the same PC as where MSFS is running on. For now I've to use the pop-out MCDU screen to see what my input is and I would like to control this myself so I'm free to place my MCDU where I want on my screens without opening, placing and resizing the popout. And in case I can use the MCDU via a websocket then in the future I could use the same technique to display the ND, EICAS etc as well. See my cockpit setup. If I have my MCDU (see concept second picture) running then it would be possible for me never have to go "inside" the virtual cockpit.
  17. Are there offsets which contain the lines displayed in the (M)CDU
  18. Found it and works, even with events from a evt list and HVAR's events for the WASM. Making my own A32NX MCDU with it
  19. I use VB6 to read and write offset, but is it also possible to send controlls?
  20. I'm using the DEV mod. You can see the LVAR with List LVARS. Im gonna try your solution 6=A32NX_AUTOPILOT_HEADING_SELECTED=66C7 . Standby
  21. I've this in my ini file : [LvarOffsets] 0=A32NX_BRAKES_HOT=UB66C1 1=A32NX_AUTOBRAKES_ACTIVATED=UB66C2 2=XMLVAR_Autobrakes_Level=UB66C3 3=A32NX_MASTER_WARNING=UB66C4 4=A32NX_MASTER_CAUTION=UB66C5 5=A32NX_ECAM_ALL_Push_IsDown=UB66C6 6=A32NX_AUTOPILOT_HEADING_SELECTED=UW66C7 if I try to read out number 6 then I got nothing. Tried every type UB-SD and every type with reading offsets in FSUIPC. Also tried other LVAR's off more than one byte .Number 1 through 5 are working fine. What do I do wrong?
×
×
  • 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.