Jump to content
The simFlight Network Forums

draci

Members
  • Content Count

    48
  • Joined

  • Last visited

Community Reputation

0 Neutral

About draci

  • Rank
    Advanced Member

Profile Information

  • Gender
    Male
  • Location
    Switzerland

Recent Profile Visitors

1,007 profile views
  1. The airport GOBD (Dakar, Senegal) was not originally implemented in FSX and at the time of creation of the latest MyTraffic 6 schedules(2015) was not open yet, so there are currently no flights to/from this airport in MyTraffic. I know that I can add my own traffic using the various MyTraffic Subapplications. What I would like to do is to add autogenerated flights to/from GOBD without changing the other world wide schedules I currently have. I do care too much whether they are realistic, but the airlines should be correct (a lot of air Senegal, I suppose).Can anybody describe quickly what I would have to do? Any help greatly appreciated. I've already dumped the airports.txt and created myairports.dat, but what next? Any help greatly appreciated, draci
  2. Hi to all, thanks to my latest discussion with Pete I'm playing around with FSUPIC offsets and event intercepting and currently I want to try out whether an engine-blow out can be prevented when for example flying in icing conditions (eg. inside a TS) as some add-ons (like FS Captain) trigger an engine blow out if the anti-icers are not turned on. In the FSUPIC offset status list I found the offset 0B6B which seems to control the fail mode bitwise for each engine. I'm testing on the PMDG 747-800i (the old version, not the QOSII) in FSX. My idea is intercepting the status change of this offset when it occurs and immediately reset it to 0 (which means all engines ok). Then I expected no more engine failures to happen or at least to see them being reset after a few seconds. But somehow this doesn't seem to work. Can this be aircraft specific (PMDG is always a little bit tricky)? or can it be that this procedure doesn't work in general (as suggested by ?SimC and ?SimE)? or am I intervening at the wrong offset? Or is my code simply wrong? function failure(offset, value) if value ~= 0 then ipc.writeUB(offset,0) end end event.intercept(0x0B6B,"UB","failure") Any help is appreciated, kind regards draci
  3. Hi Pete, log checked, lua.script tested successfully, it's in fact simply a null string being written. Thanks for your help and every thing you've done and are still doing for the community, we all owe you a lot. draci
  4. Great, thank you, I'll do a flight tomorrow and report back! draci
  5. Sorry to bother you once again, but I don't have much experience when it comes to lua programming and I'm not at my FS Computer right now. Can you please quickly confirm that the following code does what I'm trying to achieve: function flightplan(offset,value) if value ~= "xxx" then ipc.writeSTR(offset,value) end end event.intercept(0x0130,"STR","flightplan") where I replace XXX by the value which I can get from the FSUIPC logfile that EFB2 tries to write to the offset position 0x0130. The idea is to simply block the flightplan being deleted by EFB2 but still allow other add-ons to set any flightplan (and also the user via FSX menu). I appreciate your help. Best regards draci
  6. Thank you Pete, of course, your guess is right, it's EFB2 I guess the file is simply removed from use, so I will try to investigate the log file, thank you for pointing me in the right direction, I will report back. draci
  7. Hi to all, I have the annoying problem that one of my add-ons deletes the GPS flightplan loaded into FSX default GPS after landing by sending an appropriate termination command to FSUIPC as soon as the gear touches down (according to the author). Unfortunately many of my other add-ons rely heaviliy on that flight plan and therefore cease working as soon as the landing gear touches down, but, of course, I need them until the end of the flight sim session. The author is working on a solution but meanwhile I need a workaround. So that's the reason for my rather peculiar question: is there a way to make FSUIPC to ignore the command of flight plan deletion it gets from a code to which the user of the program has no access? Maybe FSUIPC could subsitute the flight plan by another (identical one) as soon as the other is deleted? Or maybe the executing program can be tricked into thinking that the flight plan was deleted by sending an appropriate command back? Any help appreciated. Best regards draci
  8. Thanks again for your reply, Simon. Here is what I would like to have: For all AI flights listed on the board (no matter whether they ever materialize) let's say 30 min before departure time the board displays "preboard" and 20 min before dep time it changes to "Boarding" and let's say 5 min before departure time it says "Final Call", at Departure time the state changes to "taxi" and let's say 15 min after departure time the state changes to "departed at xx:xx" and - very importantly!- then the flight is REMOVED AUTOMATICALLY from the board. This more primitive version of STB would work for imaginary aircraft and nevertheless look very realistic although I use VoxATC. There is no reason for the"cancelled" message and the fact that the flights never get removed from the board, right? The same would work for landing aircraft: 5 min before scheduled landing time the state should change to "landing" and at landing time the state changes to "landed at xx:xx". Perhaps you could even add some small random variation such that flights do not always depart and land exactly at scheduled times and some get delayed with a "delayed" message etc. This much more primitive version of STB dealing with imaginary flights taken from the traffic.bgl should be easy to implement from the code you already have. I would be willing to pay for it and I imagine that there would be more users interested in such a version of STB since many don't use default FSX traffic or UT2 which hasn't been updated for years now. What do you think?
  9. Hi Simon, after a whole week of testing the disconnection problem can finally be considered solved! No more disconnects in 20h flight time. Hence changing the "transferMode" eventually did the trick. I also achieved that no more cancelled messages appear in the board by changing colors (displaying the messages in black on a black background :-D) But still the board looks boring, since I get no state changes for the listed AI airrcaft. So once again my question: Would it possible to adapt the code as I outlined in an earlier post in this tread to automatically trigger state changes at fixed times although they never materialize? That should be easily be possible given the code you have. Thanks for alll your valuable help so far. Cheers, draci
  10. Hi Simon, thank you for your revelations. I was not aware of any network problems since all my numerous other add-ons work flawlessly. Of course, I can do what you require: I will do a longer flight on Thursday and report back. My latest discovery might be worth telling you: I tried playing with the network config files on STB-DS and STB client again a little using these settings: (changes in black) closeTimeout="00:01:00" openTimeout="00:10:00" receiveTimeout="00:10:00" sendTimeout="00:10:00"transactionFlow="false" transferMode="Streamed" transactionProtocol="OleTransactions" hostNameComparisonMode="StrongWildcard" listenBacklog="10" maxBufferPoolSize="2147483647" maxBufferSize="2147483647" maxConnections="10" maxReceivedMessageSize="2147483647" And you won't believe it with streaming instead of buffering not a single disconnect in 1h 30 minutes flight time! I will try a transatlantic crossing on Thursday without Vox to verify whether it won't disconnect for 9h and to collect the data you require. I keep my fingers crossed... Thanks again for your precious help, patience and time. I appreciate your support. draci
  11. Thanks for your reply, Simon. But this would mean that I don't see any traffic on the board except myself which would make STB pretty useless and unrealistic. I imagine it would be easy for you to adapt the code slightly such that it would work for my puropse. Here is what I would like to have: For all AI flights listed on the board (no matter whether they ever materialize) let's say 30 min before departure time the board displays "preboard" and 20 min before dep time it changes to "Boarding" and let's say 5 min before departure time it says "Final Call", at Departure time the state changes to "taxi" and let's say 15 min after departure time the state changes to "departed at xx:xx" and - very importantly!- then the flight is REMOVED AUTOMATICALLY from the board. This more primitive version of STB would work for imaginary aircraft and nevertheless look very realistic although I use VoxATC. There is no reason for the"cancelled" message and the fact that the flights never get removed from the board, right? The same would work for landing aircraft: 5 min before scheduled landing time the state should change to "landing" and at landing time the state changes to "landed at xx:xx". Perhaps you could even add some small random variation such that flights do not always depart and land exactly at scheduled times and some get delayed with a "delayed" message etc. This much more primitive version of STB dealing with imaginary flights taken from the traffic.bgl should be easy to implement from the code you already have. I would be willing to pay for it and I imagine that there would be more users interested in such a version of STB since many don't use default FSX traffic or UT2 which hasn't been updated for years now. What do you think?
  12. Simon, I've tried to raise buffer values in the config file on the client and obviously the disconnects seem to happen less frequent. They mainly happen if the board is full of cancelled flights. Can it be that it is a buffer overflow issue because the cancelled flights never get removed from the board although I've set this to happen after 5 minutes in the settings? Is this an STB bug that the cancelled flights never get removed or is this a problem specific to my setting? draci
  13. Hi Simon, since you obviously think that it is a port collision problem, I'd like to share with you the idea that came to my mind yesterday evening when playing with currports. Perhaps you chan quickly comment on this. Do you think it could help if I 1. set the port in STB-DS and STB-client to an arbitrary number (within the allowed port range, of course) like 8779. 2. configure the simconnect.ini on server and client to use this port. 3. on both computers (server/client) allow the local port 8779 only to connect to the remote port 8779 through the firewall. This procedure should prevent another program on another computer in my network from using port 8779 at least if I start STB-DS and client first before connecting any other add-ons to the sim or even before starting the sim itself. Right?
  14. So now I've just finished a six hours flight from SEQM into KDFW. Several disconnects. I can provide port and log information below: TrafficBoardFrontEnd3.zip StbDataServer3.zip
×

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.