Normal response from any commercial developer, regardless whose fault it is (at least here in the US) - 'Yes, we will investigate and let you know".

We HAVE investigated, and the results were immediately offered to you, instead of the corporate-ish "we will investigate", which really means nothing, but sounds nice.

 

1st result of investigation, from my reply to you on our forum:

 

Of course, before replying to both of you, I reinstalled KFLL into P3D (just to be sure), and I cannot see any crashes, both when running KFLL, or when using it together with GSX.

 

 

2nd result of investigation, after Rob suggested it was AI-related, posted here:

 

Of course, after Rob's findings the crash happens only at Parking 102 GA, I immediately tried it, with 100% density (commercial, GA and airport vehicles), and left the airplane sitting at that parking for about 1 hour. And of course, no problems whatsoever.

 

 

Are you implying that you don't *believe* I took the time to "investigate" and do the test ? 

 

Do you want to have a Teamviewer session with me, and witness the installation of the KFLL installer (the SAME installer you have, since it hasn't changed since last February) which will happily run for as many minutes as you want, with or without AI ?

 

 

So, we HAVE investigated, but you don't want to agree with the results. Not only that, I asked you to try to install the bglmanx* files manually, just to be sure it wasn't another antivirus issue that got you the wrong files somehow.

 

I already told you on our forum that I just had a Teamviewer session with an user that had the dreaded stackhash CTD (it was FSX, maybe under P3D it manifests as a .NET error, because P3D DOES use .NET itself), but only with our modules active.

 

But when I tried copying them manually (the SAME files that are online for the installer to download), the CTD disappeared! The only explanation I got that, since he used the dreaded Norton antivirus, it was still tampering with the files, even if they were excluded from scanning, and we DID found in the antivirus LOG (only), they were red-flagged (without any visible warnings...)

 

That's why I asked you to try this. But haven't got any reply from you about this issue.

 

 

In the meantime I have a stable and well-running sim after I got rid of KFLL

 

But you haven't tried to what I asked about replacing files. What's the point of asking for support, if you don't follow our suggestions ?

 

 

Not only I disabled AI traffic, I also parked F22 at default KTPA and got the same string of CTDs (P3d unknown "module" + NET violation). In my case, KFLL installer affected not only KFLL area, but the entire sim.

No, you THINK KFLL affected the "entire sim", but it hasn't. Don't you think it's a bit unusual that you are now the ONLY one reporting this ?

 

As I've said, and has easily proven by the date on the installed digital signature (one of the features of a digital signature, is that a 3rd party is certifying the date of a file with no way to tamper it without making it invalid), the KFLL installer hasn't been updated since 6 MONHTS. We have thousands of downloads in such period, yet you are the ONLY one with this issue. Of the people that posted here:

 

- Rob seems to have isolated the problem being related to AI in some way.

 

- The other user that has posted here and tried KFLL, said he didn't had any issues with it.

 

I'm awaiting a report with the manually replaced bglmanx*.* files, as I suggested to you on our forum:

 

http://www.fsdreamteam.com/forum/index.php/topic,12149.msg92466.html#msg92466

 

Do you want to have a Teamviewer session to have a look at this together ?

 

Really: what ELSE you want me to do to be satisfied of the "investigation" and the level of support offered ?

Umberto,

 

I purchased JFK2 today and installed it without any problems. Modules seem to operate normally - co CTDs. I'd rather put FLL away for now - the purchased the product back in 2009, so it's naturally old for 2015 standards . Hope you will update it one day for new runaway config.

UPDATE: I ran some more tests Umberto suggested and I found NO problems with KFLL or MT6 AI, no CTDs.  All I did was uninstall KFLL and then re-install KFLL.  MT6 and FSDT KFLL seem to work fine now ... another unsolved mystery.

 

Cheers, Rob.