Mario DANTAS

Members
  • Content count

    120
  • Joined

  • Last visited

  • Days Won

    1

Mario DANTAS last won the day on January 13 2016

Mario DANTAS had the most liked content!

Community Reputation

3 Neutral

About Mario DANTAS

  • Rank
    Advanced Member
  • Birthday 08/07/1975

Contact Methods

  • MSN
    mario_dantas@hotmail.com
  • Website URL
    http://fstrackr.net
  • Skype
    mariodantas

Profile Information

  • Gender
    Male
  • Location
    France
  • Interests
    Programming for FSUIPC in VB.NET
    Programming in LUA
    Programming in SIOC

Recent Profile Visitors

1,453 profile views
  1. Hi Pete, and once again many thanks for taking your sunday's time to answer my questions, these were only for understanding purposes, as my wideFS clients (2 PCs) are not executing the event.sim(CLOSE, "myfunc"), it seems that they can't catch the CLOSE order (or even the event.sim itself), that's why I need to understand the entries in the log file, but Pete, please, enjoy the sunday with your family, anyway I must say that you are the BEST SUPPORT (answering on sunday) for the BEST simulator related PRODUCT (FSUIPC / WideServer / WideFS), in the world. Have a nice sunday Pete.
  2. Pete, good morning, why this one below ?, why Auto send stopped before sending all data (0 of 47 sent) ?, what does it mean ? Cheers Mario Dantas
  3. Hi Pete, if you have only a few seconds to me, can you please explain the error lines from 5916703 ? I don't use UDP in WideFS configuration any thanks in advance see below: ********* WideServer.DLL Log [version 7.966c] ********* Blocksize guide = 8192 (double allowed) Date (dmy): 21/04/17, Time 23:40:18.579: Server name is PC-MASTER 15375 Initialising TCP/IP server 15375 Initialising UDP/IP server 16000 Broadcasting service every 1000 mSecs 17328 Incoming connection Accepted ok (skt=14252) TCP 17422 Restarting service due to zero reception! 17453 Incoming connection Accepted ok (skt=13792) TCP 17656 Connected to computer "PC-SLAVE-1" running WideClient version 6.999 (skt=13792) TCP 26516 Incoming connection Accepted ok (skt=15220) TCP 26719 Connected to computer "PC-SLAVE-2" running WideClient version 6.999 (skt=15220) TCP 5916703 Auto send stopped before sending all data (0 of 47 sent), Error=10013 (IP=255.255.255.255) UDP 5916703 Error 10054: client socket disconnected at Client: removing (skt=13792) TCP 5917000 Auto send stopped before sending all data (0 of 47 sent), Error=10013 (IP=255.255.255.255) UDP 5917203 Error 10054: client socket disconnected at Client: removing (skt=15220) TCP 5917313 Auto send stopped before sending all data (0 of 47 sent), Error=10013 (IP=255.255.255.255) UDP 5923250 Close signalled to clients 5924359 Closing down now ... Memory managed: Offset records: 7420 alloc, 7418 free Read buffer usage: 30270 alloc, 30270 free, max in session: 1 Write buffer usage: 420454 alloc, 420454 free, max in session: 1 Throughput maximum achieved: 58 frames/sec, 5055 bytes/sec Throughput average achieved for complete session: 23 frames/sec, 1715 bytes/sec Average receive rate from "PC-SLAVE-2": 0 frames/sec, 19 bytes/sec Average receive rate from "PC-SLAVE-1": 4 frames/sec, 194 bytes/sec ********* Log file closed ********* Cheers Mario DANTAS
  4. Sorry Pete for delay to thank you for your time spent with my case. Only to say that my lua saying "READY" was called from ipcReady.lua so when sim was really ready to fly, FSUIPC is your baby, you and only you do know his flow inside the sim so I am no one to ask you why those 12 seconds cannot be reduced. Thanks anyway for your precious help. P.S. Congratulations Pete, you have now a new BIIIIGGGG display with NatVis
  5. Hi Pete, sorry for bad post location, I think that we can get data like selected aircraft, aircraft position (lon, lat, hdg, alt) etc.. (while sim is loading terrain) In my own case I can measure more than 45 seconds from Ready to Fly status to wideserver message, wideserver, waiting for clients. I use wideclient remotely to start some software and start some lua scripts also, it means in my case that my sim hardware is really ready to fly after around 45 secs from sim software ready to fly. I create a simple lua script to put in sim rig that displays a message ("sim ready"), when FSUIPC is ready to process lua, after the message displayed I can wait around 45 secs before get the waiting for clients and then, the remote wideclients connect and start their own luas. Too many time in my opinion, but maybe this is related to my configuration ?
  6. MOVED FROM DOWNLOAD LINKS SUBFORUM! Hi fellows and Pete. This is for Pete himself; Pete, do you think that is possible to add an option to fsuipc.ini to allow users to launch wideserver before ready to fly ?, I mean when Sim loads FSUIPC module ???
  7. must be replaced with if val == 0 then
  8. You must use == instead of = in if statements to comprare
  9. Thanks for your help Pete, Sorry if I made you waste your time but I'm not the only one in this forum asking you things about FSUIPC system so if you delayed a release about 6 days is not my fault.
  10. Hi Pete, many thanks for your help, I didn't run the test yet, too busy in office tis week but I'm thinking about a thing. Look below require("simFunctions") All the 4 luas running and waiting for the CLOSE event (when triggered) have the above line of code and calls a function inside simFunctions.lua, it works well for many years but you have some time ago add a feature to threat each lua in a separate thread, isn't it related ?
  11. Hi Pete, ok when return from work I'll try with only one script but FYI the 4 lua scripts have all of them an event.sim(CLOSE So to answer one of your questions, yes, the scripts are all 4 waiting for the CLOSE event To quit the sim I use all times the same procedure as described below: ESC key Exit Prepar3D Are you sure you want to quit Prepar3D ???? Click YES That's all I log my lua separately and for each of 4 luas log I have at the end <<Thread forced Exit>> where before updating the sim I had my ipc.log saying "Closing program:" .. myProg myFunc is about a function that runs a looping ext.kill(oPrgHandler[nIndex]) until the last nIndex where oPrgHandler[nIndex] contails the programs opened by ext.run when launching the sim, with different nIndex of course. Anyway I'll try with one script tonight Pete and many thanks for your help.
  12. Those 4 lua scripts have event.sim(CLOSE, "myFunction") argument and a myFunction function of course
  13. Hi Pete, please see below, the lua script are killed and no close event is running 80046 Plug-in thread table check: 80046 1: Okay: "C:\P3DV3\Modules\settings.lua" 80046 2: Okay: "C:\P3DV3\Modules\initPrograms.lua" 80046 3: Okay: "C:\P3DV3\Modules\readytoflyPrograms.lua" 80046 4: Okay: "C:\P3DV3\Modules\pmd737sim.lua" 80062 Plug-in thread table check: 80062 1: Okay: "C:\P3DV3\Modules\settings.lua" 80062 2: Okay: "C:\P3DV3\Modules\initPrograms.lua" 80062 3: Okay: "C:\P3DV3\Modules\readytoflyPrograms.lua" 80062 4: Okay: "C:\P3DV3\Modules\pmd737sim.lua" 80062 Plug-in thread table check: 80062 1: Okay: "C:\P3DV3\Modules\settings.lua" 80062 2: Okay: "C:\P3DV3\Modules\initPrograms.lua" 80062 3: Okay: "C:\P3DV3\Modules\readytoflyPrograms.lua" 80062 4: Okay: "C:\P3DV3\Modules\pmd737sim.lua" 80062 Plug-in thread table check: 80062 1: Okay: "C:\P3DV3\Modules\settings.lua" 80062 2: Okay: "C:\P3DV3\Modules\initPrograms.lua" 80062 3: Okay: "C:\P3DV3\Modules\readytoflyPrograms.lua" 80062 4: Okay: "C:\P3DV3\Modules\pmd737sim.lua" 80062 Plug-in thread table check: 80062 1: Okay: "C:\P3DV3\Modules\settings.lua" 80062 2: Okay: "C:\P3DV3\Modules\initPrograms.lua" 80062 3: Okay: "C:\P3DV3\Modules\readytoflyPrograms.lua" 80062 4: Okay: "C:\P3DV3\Modules\pmd737sim.lua" 80062 Plug-in thread table check: 80062 1: Okay: "C:\P3DV3\Modules\settings.lua" 80062 2: Okay: "C:\P3DV3\Modules\initPrograms.lua" 80062 3: Okay: "C:\P3DV3\Modules\readytoflyPrograms.lua" 80062 4: Okay: "C:\P3DV3\Modules\pmd737sim.lua" 80062 Plug-in thread table check: 80062 1: Okay: "C:\P3DV3\Modules\settings.lua" 80062 2: Okay: "C:\P3DV3\Modules\initPrograms.lua" 80062 3: Okay: "C:\P3DV3\Modules\readytoflyPrograms.lua" 80062 4: Okay: "C:\P3DV3\Modules\pmd737sim.lua" 80062 Plug-in thread table check: 80062 1: Okay: "C:\P3DV3\Modules\settings.lua" 80062 2: Okay: "C:\P3DV3\Modules\initPrograms.lua" 80062 3: Okay: "C:\P3DV3\Modules\readytoflyPrograms.lua" 80062 4: Okay: "C:\P3DV3\Modules\pmd737sim.lua" 80062 Plug-in thread table check: 80062 1: Okay: "C:\P3DV3\Modules\settings.lua" 80062 2: Okay: "C:\P3DV3\Modules\initPrograms.lua" 80062 3: Okay: "C:\P3DV3\Modules\readytoflyPrograms.lua" 80062 4: Okay: "C:\P3DV3\Modules\pmd737sim.lua" 80062 Plug-in thread table check: 80062 1: Okay: "C:\P3DV3\Modules\settings.lua" 80062 2: Okay: "C:\P3DV3\Modules\initPrograms.lua" 80062 3: Okay: "C:\P3DV3\Modules\readytoflyPrograms.lua" 80062 4: Okay: "C:\P3DV3\Modules\pmd737sim.lua" 80062 Plug-in thread table check: 80062 1: Okay: "C:\P3DV3\Modules\settings.lua" 80062 2: Okay: "C:\P3DV3\Modules\initPrograms.lua" 80062 3: Okay: "C:\P3DV3\Modules\readytoflyPrograms.lua" 80062 4: Okay: "C:\P3DV3\Modules\pmd737sim.lua" 80078 Advanced Weather Interface Enabled 80218 Saving Flight "PMD737" (Descr "") 80265 Ext: Starting "C:\PMD737SIM\SayStatic.exe" 87359 Memory in use: 1707Mb, Avail=2389Mb, MaxFreeBlock=2030Mb 128671 Ready Flags: Ready-To-Fly=Y, In Menu=Y, In Dlg=Y 128671 Sim stopped: average frame rate for last 61 secs = 15.6 fps 128671 Max AI traffic was 0 aircraft 149328 === DLLStop called ... 149328 === Closing external processes we started ... 149328 === Getting Lua plug-ins to close ... 169828 === About to kill any Lua plug-ins still running ... 169984 Lua threads being terminated: 169984 1 = "C:\P3DV3\Modules\settings.lua" 170125 LUA: "C:\P3DV3\Modules\settings.lua": killed 170125 2 = "C:\P3DV3\Modules\initPrograms.lua" 170281 LUA: "C:\P3DV3\Modules\initPrograms.lua": killed 170281 3 = "C:\P3DV3\Modules\readytoflyPrograms.lua" 170437 LUA: "C:\P3DV3\Modules\readytoflyPrograms.lua": killed 170437 4 = "C:\P3DV3\Modules\pmd737sim.lua" 170593 LUA: "C:\P3DV3\Modules\pmd737sim.lua": killed 170593 === Closing global Lua thread 172593 === About to kill my timers ... 172796 === Restoring window procs ... 172796 === Unloading libraries ... 172796 === stopping other threads ... 172796 === ... Button scanning ... 172890 === ... Axis scanning ... 172984 === Releasing joystick devices ... 172984 === Freeing macro memory 172984 === Removing any offset overrides 172984 === Closing all WideFS threads 175406 === Clearing any displays left 175406 === Calling SimConnect_Close ... 176015 === SimConnect_Close done! 176015 === AI slots deleted! 176015 === Freeing button memory ... 176015 === Closing my Windows ... 176015 === Freeing FS libraries ... 177015 === Closing devices ... 177015 === Closing the Log ... Bye Bye! ... 177015 System time = 19/02/2017 19:30:31, Simulator time = 19:29:04 (18:29Z) 177015 *** FSUIPC log file being closed Minimum frame rate was 11.6 fps, Maximum was 29.5 fps Minimum available memory recorded was 2311Mb Average frame rate for running time of 61 secs = 15.6 fps Maximum AI traffic for session was 0 aircraft Memory managed: 88 Allocs, 87 Freed ********* FSUIPC Log file closed ***********