Hello!
I've been testing the same flight since some months and P3D always CTD at the same location (P3D 3.4.22, nvidia 378.33 recomended, windows 10 home 64, latest FsP and some addons. Specs overkill requirements, i7 3770K, GTX980ti, 32GB ram, 1500W power system).
The flight is from Buenos Aires to Heathrow and it CTD always when i am near Capo Verde islands and Tenerife island, near Mauritania coast, in the middle of the ocean. Unfortunately it simply closes to desktop, no event log.
At first i thought maybe it could be orbx products, expecially Vector, or anyway something about scenery or even AI.
But talking about Orbx i got europe and north america so it does not make sense thinking the culprit is Orbx, since i was flying near Africa, so no addons.
I also tried the flight with zeroed AI. Always with the same aircraft.
Every time the same CTD near the same location.
So i decided to make a run without FsP, even if it didn't made any sense to me.
Oh well... Against all my hopes it looks like it is FsPassengers. And the wrost thing is that this is even more sensless to me.
I did again (and again and again... for the 7th time or more now) the long flight without FsP (keeping all OrbX and other big stuff) and i was able to takeoff from SAEZ, cruise at 320 KIAS @ FL300, and land to EGLL after about 14 hours, with no problem. Also VAS was rock solid 1.35 GB left all time.
Now, my only explanation is that it is not about an exact place, scenery, geographical coords... It is more about time than the place, and after that exact time FsP makes P3D close to desktop.
This amount of time, is about 7 - 8 hours of flying, just there, near Tenerife as said.
Now i am even more clueless. :-(
Do you think there is something related between FsP, an exact location and long flights?
Any clue, hint or help please?
After all this i lost at least 10 years and i am devastated.
I've been testing the same flight since some months and P3D always CTD at the same location (P3D 3.4.22, nvidia 378.33 recomended, windows 10 home 64, latest FsP and some addons. Specs overkill requirements, i7 3770K, GTX980ti, 32GB ram, 1500W power system).
The flight is from Buenos Aires to Heathrow and it CTD always when i am near Capo Verde islands and Tenerife island, near Mauritania coast, in the middle of the ocean. Unfortunately it simply closes to desktop, no event log.
At first i thought maybe it could be orbx products, expecially Vector, or anyway something about scenery or even AI.
But talking about Orbx i got europe and north america so it does not make sense thinking the culprit is Orbx, since i was flying near Africa, so no addons.
I also tried the flight with zeroed AI. Always with the same aircraft.
Every time the same CTD near the same location.
So i decided to make a run without FsP, even if it didn't made any sense to me.
Oh well... Against all my hopes it looks like it is FsPassengers. And the wrost thing is that this is even more sensless to me.
I did again (and again and again... for the 7th time or more now) the long flight without FsP (keeping all OrbX and other big stuff) and i was able to takeoff from SAEZ, cruise at 320 KIAS @ FL300, and land to EGLL after about 14 hours, with no problem. Also VAS was rock solid 1.35 GB left all time.
Now, my only explanation is that it is not about an exact place, scenery, geographical coords... It is more about time than the place, and after that exact time FsP makes P3D close to desktop.
This amount of time, is about 7 - 8 hours of flying, just there, near Tenerife as said.
Now i am even more clueless. :-(
Do you think there is something related between FsP, an exact location and long flights?
Any clue, hint or help please?
After all this i lost at least 10 years and i am devastated.