Hello, I had a series of crashes at KMEM this morning, always while panning around the external view.  After this happened twice, i suspected an AI model was causing the issue so i turned off all AI and was able to takeoff without issue so that would seem to confirm a non-compatible AI model.  This is in p3dv4, i'm using a mishmash of free AI.

a few questions:

- are there any tools out there to help identify outdated models or otherwise what model is causing the crash?

- are there any commonly used models known to cause this issue?

- is v4 more sensitive to this than v3?  I never had this happen at kmem in v3, though it could just be the luck of what time I flew out of there, what AI was present etc.

any other advice/thoughts?

thanks

Dave

AIFP should be able to help, but I am still trying to figure it out myself.  There was an image converter, but it didn't help me.  It seems that the way to go is some payware so as to stop wasting time and just fly.

46 minutes ago, regis9 said:

Hello, I had a series of crashes at KMEM this morning, always while panning around the external view.  After this happened twice, i suspected an AI model was causing the issue so i turned off all AI and was able to takeoff without issue so that would seem to confirm a non-compatible AI model.  This is in p3dv4, i'm using a mishmash of free AI.

a few questions:

- are there any tools out there to help identify outdated models or otherwise what model is causing the crash?

- are there any commonly used models known to cause this issue?

- is v4 more sensitive to this than v3?  I never had this happen at kmem in v3, though it could just be the luck of what time I flew out of there, what AI was present etc.

any other advice/thoughts?

thanks

Dave

AIG has done it for you.  Go here:  http://www.alpha-india.net/forums/index.php?topic=25472.0

Shouldn't cause a crash though.  The FS9 models just don't show up or you'll see a tail but nothing else, or no landing gear.  

I use this to look for older MDL files, DasModel.exe. Checking the dev's website (http://www.supercell.nl/disposition/) it says it is available here, so look for FSModelChecker on AVSIM. But looking at my zip file it shows flyawaysimulation's blurb, so who knows where I found it...LOL

Here's the link:

https://library.avsim.net/esearch.php?DLID=114136&CatID=fsxutil

But it isn't going to tell you much more than which SDK was used to compile each model. P3D MDL formats show up as unknown.

it's a lot of work(time consuming)to recompile complete ai package to p3d v4. You can convert MDL, but then you need to add missing animations, and sometimes textures. I'm going to wait for some good addon

Traffic toolbox found in the sdk can be useful for finding ai aircraft that have black textures that show up in the sim

As some already said aig have a great page showing what works and currently does not in v4

Thanks guys.  I'm less concerned about the ones that are missing gear/textures etc, i have some of those too but they don't seem to cause a crash and i know most are being worked on.

Is it the outdated model that causes the crashing?

i wish there were a payware package that met my needs but unfortunately none i've tried cut it for me.  MT6 had some pretty bad models and unrealistic schedules, UT2 had way too many out of date liveries or missing liveries...sounds like UT Live is the same.

Have you considered creating your own? With aig plans 

Admittedly some models are not working in p3dv4 at the moment,but it is getting better as the older models get converted.

I'm back to having about 75% of what i have in p3dv3, and i have most schedules  are summer16 or newer

The way i have it set is all my models and plans are visible in p3dv4,p3dv3 and fsx all from one location

That's basically what I have in place right now.  Most does in fact work well, it seems like I have a gremlin model in there somewhere though.

Another way is to use Notepad + (freeware) right click on the *.MDL file and at the top you will see "MDLXMDLH " if it has an 8 and no X it is a fs9 model.

If your convinced its a model,why not try removing each model type from your setup at a time running the sim and see if all works then try the next batch and whittle it down to the faulty model for example 

If you have 40 models disable the last 20 and run sim if all works ok then the problem is in the last 20 disabled models so this time disable the last 30 models and then run the sim if it works then you keep halving the untested ones until you get the fail 

If it fails on the first attempt then you can do the same whittling but from the other way

Should only take around 20 mins to figure it out with any luck

Thanks, that's the kind of trial and error I was hoping to avoid but may have to resort to in this case.

do you have the camsim 787 installed ??

 

On ‎01‎.‎07‎.‎2017 at 4:50 PM, regis9 said:

so that would seem to confirm a non-compatible AI model.

...or an incompatible AI flightplan. IMHO that has a higher probability of actually crashing your sim.

An AI plane SimObject that can actually cause an exception would probably not have an issue in the 3D model (while that is possible). I would imagine that it might also have an incompatible "personality", as defined in the .air and aircraft.cfg file. Maybe P3D V4 is sensitive to certain kinds of wrong or incomplete definitions, for example for systems, geometry, contact points or the FDE parameters. The AI logic of the ESP sims is not simply moving 3D models around. These aircraft are actually really simulated, including the basic aircraft systems (electrical, hydraulics, engines => lights, gear, flaps, doors etc.).

Other than running a trial & error search I don't think that there is an actual tool for that. To check out the aircraft, you could use a tool that creates them as active AI at the press of a button, but I have no idea how to check out the flight plans. Maybe íf you can provoke the crash, you could proceed by exclusion, always cutting your AI library in half until you have narrowed it down.

Best regards