Simconnect

[Bluestar]

The lights came on without having to recycle the disconnect/connect button.

Bill

 

[gadgets]

I thought they might. Thanks for reporting back.

 

[Bluestar]

Don,

I'm not sure if this is a Simconnect/AFLT issue or not.

On several occasions in the past week I have had a P3dv4 default aircraft crash while on autopilot where the aircraft just heads straight down and I can't recover it. The only way I have been able to stop this situation is to close the CONNECT/DISCONNECT box. A related issue is when I was at KLAW doing a test for KSPS the aircraft would not move or move and stop. Again after I closed the CONNECT/DISCONNECT box the situation goes away. Like I said I don't know if the situations are related to AFLT, but I thought I would pass this along to you.

Bill

 

[gadgets]

Thanks (I think) for passing that along, Bill. The fact that you are able to "stop the situation" (how do you know you've stopped it if it only happens occasionally?) by disconnecting sound suspicious. But AFLT places a highly-unusual workload on the system by injecting hundreds, perhaps thousands, of simobjects. When You disconnect, you suddenly remove all those simobjects. Since the issue doesn't happen under specific circumstances, there's no way of knowing what the trigger might be.

If you find a way to reliably trigger the issue, I'm happy to investigate. But, without that, I'd be looking for a needle in a haystack (that might not even exist.)

 

[Bluestar]

I have made progress in isolating the Simconnect/AFLT issue outlined above. I use P3d in Windows mode. When I downsize P3d and the CONNECT/DISCONNECT box is in DISCONNECT there are no issues. I flew under this scenario on a 3 hour and 12 hour flight with no issues. I flew 10 hours of a 13 hour flight with no issues, then I went to CONNECT with the screen downsized and with in 15 minutes the airplane was running along the ground. When I was unable to recover the flight using Autosave until I completely closed the CONNECT/DISCONNECT box. I will continue to try to pinpoint the problem and keep you informed.

 

[gadgets]

Thanks

 

[Bluestar]

Don,

The scenario outlined above has occurred again. I flew 15 hours, 13 hours and 5 hours with the Connect/Disconnect Box (C/D Box) in Disconnect. When I got within 30 miles of KSPS I turned the C/D Box to Connect and the aircraft headed straight down and the only way I could recover it was to close the C/D Box. This has occurred twice using a PMDG aircraft and a default C-172.

The aircraft acts like it has gone into slew mode.

Is there a way for my airfield lights to appear without using the C/D Box?

Please let me know if you think this is an issue related to my system and I will go to Plan B.

Thanks,

 

[gadgets]

I really wish you'd forget about Connect/Disconnect. It is not meant to be used mid-flight and when connect is clicked, the sim gets very busy servicing AFLT. (Perhaps it "forgets" about other things.) Incidentally, in your earlier reports, you only indicated you fixed the problem by closing AFLT (SimObjects).exe. In this case, you started AFLT (Simobjects).exe.

I'll check a couple things, but I'm not expecting any revelations.

 

[Bluestar]

My apologies Don,

The only way that I can get my PAPI and Strobes to be visible is using CONNECT. There is nothing I'd like better than to start my sim and not have the C/D Box not pop up.

I've probably get something installed incorrectly. If you like I will move on. Sorry.

 

[gadgets]

I don't understand. Connect is automatic. Are you not in "connect" mode when you start the sim? And, yes, if you are not connected, you wont see PAPI's and strobes (and perhaps other lights. depending on they are programmed). So, if you don't see them, then either they are programmed incorrectly (unlikely, since they show up when manually connected) or you've turned them off.

As I've told you before, and as noted in the user manual, I cannot prevent the connect/disconnect dialog from showing. It gets minimized; that's the best I can do. But, there is no role for that dialog in normal use. Just ignore it. As you've discovered (and I've confirmed), turning AFLT on or off in mid-flight is disasterous - presumably due to the instantaneous load on the sim.

No one else is reporting this issue. While it may be because you are, I'd like to think someone else would have said something if they were experiencing the issue.

If you are not seeing your strobes and PAPI's on startup, that's an issue needing resolution. But, leave the connect/disconnect alone.

 

[gadgets]

I have discovered that if AFLT overloads Simconnect, Simconnect essentially "forgets" about the user aircraft, returning its airspeed to 0 (hence the crash). Seems to suggest an incomplete design of Simconnect.

In addition to startup - when it shouldn't matter, AFLT can overload Simconnent at 4 events: i.e., click the Connect button, click the Disconnect button (both of which you've experienced), when the user aircraft approaches (15-20 nm ) an airfield and when the user aircraft gets beyond about 20nm of such an airfield.

SInce the Connect and Disconnect buttons are not intended for use in normal circumstances, I'm not going to change that area - at least for now. But, previously, AFLT attempted to process 100 lights at a time when approaching or leaving an airfield. It seems that was more than Simconnect could tolerate. I've reduced that number to 20 in the attached. (It's not clear there is any feedback from Simconnect that would allow in-the-moment metering. This may have to become a user-setting).

Please copy the attached file into your AFLT\P3D Files folder and either recompile your airport or also copy it into Documents/Prepar 3d v4 Add-ons\AFLT to P3D and give it a try.

 

[Bluestar]

I have discovered that if AFLT overloads Simconnect, Simconnect essentially "forgets" about the user aircraft, returning its airspeed to 0 (hence the crash). Seems to suggest an incomplete design of Simconnect.

In addition to startup - when it shouldn't matter, AFLT can overload Simconnent at 4 events: i.e., click the Connect button, click the Disconnect button (both of which you've experienced), when the user aircraft approaches (15-20 nm ) an airfield and when the user aircraft gets beyond about 20nm of such an airfield.

SInce the Connect and Disconnect buttons are not intended for use in normal circumstances, I'm not going to change that area - at least for now. But, previously, AFLT attempted to process 100 lights at a time when approaching or leaving an airfield. It seems that was more than Simconnect could tolerate. I've reduced that number to 20 in the attached. (It's not clear there is any feedback from Simconnect that would allow in-the-moment metering. This may have to become a user-setting).

Please copy the attached file into your AFLT\P3D Files folder and either recompile your airport or also copy it into Documents/Prepar 3d v4 Add-ons\AFLT to P3D and give it a try.

No joy.

I started flight at KLAW RWY18 using default Cessna Caravan. When starting with default daylight, the aircraft starts OK, but when I change to dusk at KLAW the aircraft barely moves. If I Disconnect then it will move. I flew in this mode until approximately 30NM from KSPS, then pushed the Connect button and the airplane heads straight down. Basically there is no change for me. One thing that will also cause a crash even when I do not touch the C/D button is to change from Day to Dusk/Night. Each time I came back to the aircraft it was headed straight down.

Since I am the only one reporting this issue it is obviously a problem with my setup. I think the best plan for me is to use the AFLT RWY/TAXI lights and use the ADE Approach/Strobe/PAPI lights.

 

[gadgets]

I think the best plan for me is to use the AFLT RWY/TAXI lights and use the ADE Approach/Strobe/PAPI lights.

You can do that, but I suggest you don't give up just yet. We know (or at least I'm pretty sure) these "crashes" are due to a momentary overload in Simconnect. (At day to dusk, for example, there are a lot of lights changing state. AFLT currently tries to do it all at once, and that's "killing" Simconnect.) I am currently investigating ways that AFLT can "meter" these sudden, numerous changes. It's going to take me a couple days, but I'm reasonably sure I can avoid Simconnect doing whatever its now doing.

 

[Bluestar]

You can do that, but I suggest you don't give up just yet. We know (or at least I'm pretty sure) these "crashes" are due to a momentary overload in Simconnect. (At day to dusk, for example, there are a lot of lights changing state. AFLT currently tries to do it all at once, and that's "killing" Simconnect.) I am currently investigating ways that AFLT can "meter" these sudden, numerous changes. It's going to take me a couple days, but I'm reasonably sure I can avoid Simconnect doing whatever its now doing.

Take your time Don,

I don't mind waiting, just wanted to get the message to you of a potential problem.

 

[gadgets]

I have now (almost) fully metered the launching and deleting of the simobject lights. Please give it a try (but stay away from the Connect/Disconnect buttons; they are not fully operational yet). By metering, I mean Simconnect controls the pace. Consequently, you may see a slightly longer startup at an AFLT airport

As before, please copy the attached file into your AFLT\P3D Files folder and either recompile your airport or also copy it into Documents/Prepar 3d v4 Add-ons\AFLT to P3D.

 

[Bluestar]

I have now (almost) fully metered the launching and deleting of the simobject lights. Please give it a try (but stay away from the Connect/Disconnect buttons; they are not fully operational yet). By metering, I mean Simconnect controls the pace. Consequently, you may see a slightly longer startup at an AFLT airport

As before, please copy the attached file into your AFLT\P3D Files folder and either recompile your airport or also copy it into Documents/Prepar 3d v4 Add-ons\AFLT to P3D.

I will give it a try and report back.

I need a little clarification about your "stay away from the Connect/Disconnect buttons" statement. When P3dv4 starts the C/D buttons appear automatically. Do you want me to delete the button when it appears or just leave it in the default position when it loads with P3dv4?

 

[gadgets]

I mean don't click anything on that dialog. Just run PV4 (or whatever) and see if Simconnect is adversely affected as you approach and an AFLT-lighted airport from >25nm out or fly away from an such an airport after about 20nm

 

[Bluestar]

Good Afternoon Don,

I made three different flights leaving KLTS to KSPS, about 60 miles in the Jahns C-47 using P3dv4.5 starting with default startup.

1. Set up in the day at KLTS flew direct to KSPS without any issues. About 40 miles from KSPS switched to Dusk setting, immediate zero airspeed.

2. Set up with Dusk setting at KLTS, couldn't get the aircraft to move more than 3 seconds and it would stop.

3. Set KLTS using sim time of about 11 A.M. local. Departed without any problems and flew to KSPS without any problems. The PAPIs and one strobe were working at KSPS. Did a go-around and landed. Reset the sim to Night without any issues on the ground. Departed on runway heading and flew at about 3,500 feet. I went to outside view to watch the airport. Shortly after the airport disappeared from sight, the airspeed went to zero.

Didn't touch the buttons.

When it's good, it's really good. The lights are looking great as I get the brightness adjusted.

Again since I appear to be the only one having issues I don't mind putting this on hold.

 

[gadgets]

1. Please check the date-stamp of the file AFLT (SimObjects).exe in Documents\Prepar3d v4 Addons\AFLT for P3D and ensure it's dated yesterday, ie., May 2 or later. If its not, then you are not using the most recent version. The symptoms you describe occurred for me in the old version, but are now history.

2. If you are using the most recent version, how old is your computer and what version of Windows are you running?

 

[gadgets]

Now I'm almost certain you didn't use the latest version, because it should have thrown an exception when you left the airport area. So, please limit your checks to approaching the airport from > 25 nm.