cknipe

Almost immediately gave the error (no aircraft position)... http://a.tmp.ninja/lbZR8U1a3WOY.zip I am running ADSB under full debug instance too to see whether I pick up issues there, just FYI.

Not impossible that it's a bug my side. Will look into it, ty Nico.

https://a.uguu.se/jqvpwt.zip

@kiek Interesting observation for you that I've made now... 1) started the latest PSXT (64b, w10), and within minutes, I received the position report issue. 2) started the latest PSXT (64b, W10), but this time WITHOUT ADSB injecting aircraft (connected to 10747, but not sending any information to PSXT) - no errors what so ever. I am on the ground at VHHH, which has a lot of AI that needs to be injected. Just an observation, but isn't this perhaps related to PSXT pushing a lot of AI into the sim, and not being able to quickly enough respond to a 1 sec interval as there's too many AI to update? I've also noticed that since you took the 120 second down to 5 seconds, the error has been occurring a lot more frequently? Both logs at https://tmpfiles.org/download/65373/PSXseeconTraffic.zip EDIT: FYI but I personally am also more than happy to read position reports from the sim itself, instead of from PSXT. If RT can / want to do the same, then we may potentially remove the issue from PSXT all together. Just an idea, not sure how much you relay on this information in PSXT.

No aircraft position reeceived, tried 5 times https://tmpfiles.org/download/65309/Log.zip

Well that didn't take long LOL https://tmpfiles.org/download/65235/Log.zip

Running. PS: For what it is worth, since you changed the loop to use aircraft position, I've noticed that the AI movement is a lot smoother as well. Will post logs as soon as I get a crash again, it is -significantly- less on my side since you made the changes.

Same thing here - had to wait a VERY long time for this though 😞 https://gofile.io/d/ghCqsY No position update for user aircraft, this is w10 on x64.

FYI Kriek: Seems to be identical to the previous issue where you added the additional debug logging (this is still with 18.2 - will fire up 18.3 momentarily) FDX1528* N173FE MEM ->ROC B763 airborne not detected, no ON_GROUND msg received, no objectId.. is hanging ... FDX1528* N173FE MEM ->ROC B763 airborne not detected, no ON_GROUND msg received, no objectId.. is hanging ... Error 09:49:42 SimConnect problem: no 1sec system event I watched this one happen - no stutters 1) ADSB stopped receiving position updates from PSXT (TCP Port 10747) 2) ADSB reconnected after not receiving a single position report for over 60 seconds (this is coded in my app, it closes and re-establishes the TCP Connection if nothing was received for 60 seconds)) 3) The above occurred three times in quick succession 4) PSXT thereafter reported the heartbeat failure Now, SimConnect is one thing - why is PSXT stopping to advertise position reports? It would seem to be, that there is some kind of loop and/or thread perhaps that is terminating that is causing this. I understand what the 1s heartbeat issue is, I understand why it occurring. I don't understand what is triggering it. Given the below with position reports stopping, perhaps you are looking in the wrong place. Assuming this is SimConnect, when in actual fact the SimConnect is just a result of a deeper problem. It doesn't make sense to me why PSXT would stop transmitting position reports for over 3 x 60s (180 seconds), before eventually terminating due to a timeout on SimConnect. EDIT: will fix the no ON_GROUND message. it's just a boolean value that isn't initialized properly with a default value.

sigh - here we go again playing games and running around in circles Sims hang, Sims have stutters, it's unfortunately the nature of the beast. IF that even is the problem. Regardless of whether that is the problem or not, ALL other addons, accommodate those pauses and stutters, PSXT apparently doesn't if what you say is true. Regardless of that, you've got a bunch of people here that would LOVE to use your software. You're making it incredibly difficult for us to do so. Arguing, pointing fingers at other things, that's not helping. You can't expect everyone to change everything (let's say is HF causing this, for arguments sake - do you seriously expect us to use PSXT without weather now?) just so that your application works. Find a fix, find a way around whatever the problem is. If it is HF, wouldn't the better thing be to contact HF and try work out what is happening with them, and find a solution? We don't have access to the code, we can't tell you what is / is not happening, nor can we tell you what the problem is. Only you can. May I remind you, that on versions 17.x, this was *NEVER* an issue? Same PC, same Sim, same addons... 17.x works fine, 18.x does not. Do you still want to tell us that the problem is the sim? May I remind you, 18.1 was initially only for p3d5 (64 bit version) - you said so yourself. Mysteriously, all off a sudden after you pushed a fix, 18.1 (64 bit version) all of a sudden worked in P3Dv4 even though you again at that time stated, no changes was made to simconnect? We can play these games and have these arguments all you want. The fact remains that you are the only one that can either fix this, or implement a workaround for it. You can choose to deny and argue, or you can choose to fix it.

So why doesn't this happen with *any* other addons?

i.e. it doesn't start up? starts, and closes? starts but does not connect to psxt? If it doesn't start at all, please check for errors in the windows event log.

Very rarely happened in 18.1, now happening quite frequently again in 18.2 - mostly when on the ground. Also had another instance of the aircraft slewing all over the place. I find it funny that no other addons has this problem, but only PSXT. If the other addons does have such problems, at least they automatically reconnect and continue. They don't just abruptly stop working. Extremely frustrating.

64bit connects to my p3dv4 now - seems to be fine with SimConnect and datafeeeds... Cruising so no AI around currently, but I'll see what it does once there's some traffic.

Hi Kiek, Is 18.1 compatible with P3Dv4, or any possibility of porting the change to 17.6 too?

@kiek - a ADS-B user just contacted me with -exactly- the same thing (v18.0, P3Dv5) The destination airport is LFMN "FLAi_FSX_PA28 N700MS" could not be created 10:21:19 Live: 6, Parked: 0 QNH=1021 C525* C525 airborne not detected, no ON_GROUND msg received, change status to ACTIVE Error objectId in update 0 10:23:51 Flight not running ... 10:23:51 Flight Simulator no longer connected, PSXseeconTraffic will stop ... UPS=26 Exiting: SIM WAS CLOSED QNH Reader has stopped Traffic Reader has stopped No error, no nothing. PSXT just closes... PS: Also experiencing the warp issue myself, on 17.6. Even I thought it was something else until I started seeing other PSXT users reporting the same thing. Don't be surprised if you don't get a lot of reports about it, it is very deceiving. 09:55:42 Live: 23, Parked: 25 10:00:42 Live: 17, Parked: 25 10:05:47 Live: 21, Parked: 25 10:07:49 Flight not running ... 10:07:58 Flight resumed 10:07:58 VHHH is at 23.9 nm, parked aircraft removed 10:07:58 No more parking at VHHH (HKG) User on the ground at airport ZGSZ, standing still The parking airport is: ZGSZ (SZX)

17.6 gave an "expired" error, forcing me (and others I guess), to upgrade to 18... Now only to find that 18 doesn't support P3Dv4?

It's coming, soon (tm)

If a weather program is used, then the weather program can be time shifted as well to match the weather... METARs will always be current unfortunately. Either way, timeshifting is still on the todo list, as is the configuration menu. Can (and more than likely will) add settings to enable/disable various aspects of the program. The only real difference is that I don't necessarily take the QNH at the closest Airport (METAR), but I take the actual pressure reading at the user's aircraft.

ADS-B Live Traffic version 2020.06.16 Build 9 has been released. As always, it is available at https://psxt.flightsimtechnologies.com/ADSBSetup.zip Change log: 2020.06.16.9 (2020-06-16) Settings now saved in INI file %APDATA%\Flight Sim Technologies\ADSB. IP or Hostname as parameter is still accepted as command line parameters on console application. Connects to Simulator via FSUIPC for accurate pressure readings only if FSUIPC/WideFS connection is available (this is optional but gives better accuracy). You'll notice the pressure change between the METAR received and actual QNH setting User Aircraft is detected via FSUIPC as well so that the correct aircraft icon for the user aircraft can be used on the maps. Redone automatic updater to automatically update application to the latest versions - previous release had problems with automatic updates. WinForm application launched with basic interface (expect more changes in the coming days). Settings screen, Radar screen, and time shifting still to be done. Installer package integrated into solution Installer package now enables TLS1.2 by default on Windows 7 machines Exception clean-ups and better error handling What started more than a year ago as a few lines of code just thrown together to see whether I can personally use an alternative to RealTraffic, has now turned into a fully fledged application, consisting of more than 17,000 lines of code! I have a few things still to implement, but I am confident that we will have a mature and stable application within the next few months that will stand the test of time going forward. Thanks for all the users, and continued support! It is appreciated. More than 1.4 million HTTPS requests has been served by our servers, providing data to users over the last 30 days!

I need to look at this in a bit more detail, especially in terms of how to implement this in a "console" application, but I can confirm we will be able to do time shifting for a period of 7 days as well. I am toying with the idea to change the basic data feeder to a Windows Service (always running in the background, the overhead is minimal), and then perhaps doing a WinForm for settings (settings has already been migrated to ini files in current beta builds), time shifting, and perhaps a little radar screen. it's all possible, just need to -do- it 🙂 -- Chris.

New version published. If you have previously downloaded the ZIP file with the executable, please delete and download the proper installer (URL is the same, alternatively use https://psxt.flightsimtechnologies.com/ADSBSetup.zip). Installation is a few clicks and you are done. Change Log for version 2020.05.19.6 (Build 6, Released 2020/05/19) Increased ADS-B Position Receiver timeout (ADS-B incorrectly timed out the connection to PSXT when no data was received for more than 2 seconds) Simplified initial connection to PSXT not to cause confusement to users (now clearly states when it is unable or waiting on PSXT to connect) Implemented automatic software updates on launch (you'll always run the most up-to-date version automatically) Created base installer package -- Chris

Didn't know that! 😃 Let's see if we can take the competition on!

Hi Michael, Can definitely change some stuff to handle the initial connection to PSXT better - will work on it today / tomorrow. There's a few other things that I want to add / change as well. I'll more than likely do another release in the next couple of days. In terms of time shifted traffic, it really isn't very easy to do. It's virtually impossible to take a snapshot of some 6000 aircraft in the air, 24x7 with like 1 second intervals. I think this is partially why Real Traffic also dropped it. Thanks for the feedback, and I'm glad to hear it is working well!

Just a quick update. I've made a new version available, 2020-05-18-01. Brief changelog: - Parameter now supports both IP address or DNS name of the computer where ADS-B Live must connect to, ie. "ADSB.exe mycomputer" /or/ "ADSB.exe 192.168.1.100" - Improved exception handling, errors are automatically reported. If there are any unhandled exception errors, please post them so that they can be addressed. - Some cosmetic changes to the console window's GUI I see quite a few people did download the data provider since my initial post. I would obviously, love to hear feedback, suggestions, and/or complaints 🙂 -- Chris.