Been simming since FS1 and have never seen anything like this - I can only fly in full daylight!

I hadn't done any night flying for quite a while so I don't really know when this became a problem.

Here's what happening:

In anything but full daylight and with the aircraft parked it is bouncing up and down at about a one bounce/second rate.

If I am in the air and change from daylight to darkness, the aircraft enters a totally uncontrollable spin and crashes.

I've tried ActiveSky on/off with no change.

Thinking it might be something related to shadows or lighting, I temporarily changed those settings but that made no difference either.

Here's a link to video showing the problem:

https://youtu.be/C6C2jPNA93s

Ideas anyone?

 

Thanks.

 

 

 

Edited December 31, 20196 yr by Noell
Fix typo

Does this happens with all aircrafts? Or just this one?

Post a list of all your addons.

Simbol 

We found some addons add something like AFLT for P3D that is supposed to fix some kind of problem with P3D lighting (?) but it is very buggy and does things exactly like this.

I found the source for AFLT: https://www.fsdeveloper.com/forum/threads/aflt-now-generates-simobjects-for-custom-airfield-lights.440454/

Edited December 31, 20196 yr by downscc

It happens with all aircraft.

Don't have time right now to list my addons but will do that tomorrow and also have a look at the link provided.

Thanks, guys.

What's your default flight? 

Default flight is Carenado PA44 Seminole at KHQM (ORBX Freeware airport). This has been my default flight for a very long time.

As for addons, I have a lot of ORBX products: Global Base/LC NA/LC Eur/LC SA+Trees/Libs/Vector/Lights Config/TE GBsouth and a bunch of their payware and freeware airports.

In addition: FS Global Mesh / ActiveSky / EnvTex&EnvShade / REX HD Airports / RealTurb NA / RD Presets HD Bldgs / Chaseplane /  PrecipitFX / SpadNext / Real World Scenery NY State / Latin VFR KSAN.

Also have a load of payware aircraft and nav products.

I now have more info on the problem which just keeps getting stranger. The bouncing gets worse with the parking brake applied. You can notice this best by observing the nose wheel strut compression as the parking brake is set and released. Also, if you watch carefully as the bouncing is going on the aircraft slowly creeps froward. Another thing I only became aware of earlier today is that the pushback function no longer works. The following link to my latest YouTube video shows the amplitude of the bounce changing as I set and release the parking brake and also shows the slow forward creep:

https://www.youtube.com/watch?v=z5G43H0fflA&feature=youtu.be

Thanks for the input this far.

 

 

 

 

 

Edited January 1, 20206 yr by Noell
Typo

I know you said all aircraft but maybe try a default P3D one and make a new start scenario.

Edited January 1, 20206 yr by gsand

4 minutes ago, gsand said:

I know you said all aircraft but maybe try a default P3D one and make a new start scenario.

+1.

If it persist. Disable Spadnext and try again.

Regards

S.

59 minutes ago, gsand said:

I know you said all aircraft but maybe try a default P3D one and make a new start scenario.

+1.  That's where I'd start, a P3D default acft on a P3D default airfield, with the batteries and avionics switches on.

Also, if you go into slew mode and slew up a few feet, then back down to the ground, does the bouncing persist?

Tried with and without SpadNext loaded. Actually, the videos I posted were recorded without SpadNext.

Switched my default scenario to the default J3 Cub @ KHQM. No change in the problem.

Then changed the default scenario to the J3 Cub at an airport outside of any ORBX region. Still no change in the problem.

What about uninstalling/reinstalling the Content and/or Scenery components of P3D? Anyone think its worth a shot?

I don't know if this would have any bearing on my problem but thinking back to the latest update to P3D, I waited until all the goings on about HF1 and HF2 had died down before I updated. At that point I figured the hot fixes would have been integrated into the latest Client update.  Am I right about that?

Thanks again, everyone.

 

 

 

 

2 minutes ago, Noell said:

Tried with and without SpadNext loaded. Actually, the videos I posted were recorded without SpadNext.

Switched my default scenario to the default J3 Cub @ KHQM. No change in the problem.

Then changed the default scenario to the J3 Cub at an airport outside of any ORBX region. Still no change in the problem.

What about uninstalling/reinstalling the Content and/or Scenery components of P3D? Anyone think its worth a shot?

I don't know if this would have any bearing on my problem but thinking back to the latest update to P3D, I waited until all the goings on about HF1 and HF2 had died down before I updated. At that point I figured the hot fixes would have been integrated into the latest Client update.  Am I right about that?

HF1 and HF2 were not released as updates, but full releases of the sim--IOW, it's not a patch, but a full release version with the hotfix already incorporated into it.  The current version, 4.5.13.32097, is the latest, aka HF2.

Are you using something like EZ-DOK that might be making inputs, or an external load manager that may be messing with weights, etc?  What happens if you go into both dll.xml and both exe.xml files and disable everything?  If that stops it, re-enabling addons one-by-one should identify the culprit.

13 minutes ago, Noell said:

Tried with and without SpadNext loaded. Actually, the videos I posted were recorded without SpadNext.

Switched my default scenario to the default J3 Cub @ KHQM. No change in the problem.

Then changed the default scenario to the J3 Cub at an airport outside of any ORBX region. Still no change in the problem.

What about uninstalling/reinstalling the Content and/or Scenery components of P3D? Anyone think its worth a shot?

I don't know if this would have any bearing on my problem but thinking back to the latest update to P3D, I waited until all the goings on about HF1 and HF2 had died down before I updated. At that point I figured the hot fixes would have been integrated into the latest Client update.  Am I right about that?

Thanks again, everyone.

 

 

 

 

This must be caused by a 3rd party add-on. I will suggest disabling all your add-on's and test again. If it works then enable them one by one until you find the culprit.

S.

First of all, I am on Ver. 4.513.32097

An important breakthrough of sorts and too bad I hadn't noticed this earlier.

For a while now when I launch P3D a window opens minimized to the Win10 Taskbar titled AFLT (SimObjects) - Version 1.0..... with a Connect and a Disconnect button.

If I close that window (not minimize it) or click Disconnect my "bouncing" stops and the sim runs perfectly.  So it sure looks like whatever is causing this "AFLT" window to appear is at the root of my problem.

So at least now I have a workaround but I would really like to track down where this is coming from so I can fix it permanently.

Is it a matter of following Bob's suggestion to go into both dll.xml and both exe.xml files and disable everything and then enable one at a time?

Once again, many thanks everyone.

 

 

No need to disable all your add-ons, it's pretty clear you've identified the problem already.

You might try following the link Dan Downs provided (third post in this thread) and see if there's an updated version of AFLT (Airfield Lights Toolbox).  It's part of some sceneries...as to which, I have no clue.

Look through the dll.xml and exe.xml files (there are two of each) to see if there are any <Launch.Addon> blocks related to AFLT, and disable it/them by editing the line <Disabled>False</Disabled> in that block to <Disabled>True</Disabled>

If it's not invoked there, you may have to ask Don Grovestine, the author, how to disable it (e.g. if it's a simobject in its own right)

 

I keep a log of P3D addons and the last thing I installed was about three months ago was Dan Grovestine's CYYJ.

I'm pretty sure this created a folder named AFLT for P3D in Documents\Prepar3d v_ Add-ons containing the AFLT executable.

I followed the P3D uninstall instructions for AFLT on Airfield Lights Tool page of the stuff4fs website and that has fixed my problem.

Everything is now working as it should both day and night.

Thanks to everyone and especially to Dan and Don for pointing me in the right direction to get to the bottom of this.

Happy New Year!