Military AI Works

It's also crashing when I try to load it at dawn and dusk

andypoppens wrote: 10 Aug 2017, 23:02 How could it have been improperly installed

Do you see ramp lights at the airport at night and in the container yards? They aren't installed improperly then.

andypoppens wrote: 10 Aug 2017, 23:05 The file may be unsupported damaged or corrupted

Unless you used a program that specifically supports .dxt3 files, that's what I would expect to see.

andypoppens wrote: 10 Aug 2017, 23:13 It's also crashing when I try to load it at dawn and dusk

Without you getting a good Procmon reading, we really can't help you. It could literally be any of a thousand things

I just deleted the Kobe scenery and I'm going to re add it and see what happens

Andy, lets go back a step.
When you loaded up Procmon, did you successfully load up the filter? Did the main window look different after the filter loaded?

The reason I ask is that with without filters it will stream everything on your pc. Once the filter has been loaded it will only show you FS9 related stuff.

By the way Brent let's forget Kobe for awhile can you help me with the puma not showing up I installed it right

Plus can you add the Tokyo heliport to the library

Where does it not show up?
Does ACA2017 Light or the AIAE find any problems with it? If no have you done a thorough check using ACA2017 that will check your flightplans as well?

You see the problem is that we can't see your system nor can we access it so you have to narrow down the problem to be able to help you.

***EDIT***

When you say installed the package correctly, did you read the note that Brent added to the doc?

Yes I did

What's aca 2017 and the aiae

OK. ACA2017 is a util for checking for problems with AI traffic you can get it and other utils from here:-
http://aifs.pvdveen.net/.
The AIAE is Martins tool for checking for aircraft installation problems, The AI Aircraft Editor.net.

On the first answer, I would read the note again.
The reason I say this is that I just downloaded the package, installed the paints, installed the plans, made the change suggested in the note and hey presto all 3 appeared at RJTK. Afterwards, I checked the afcad and saw that if you didn't make the change then no aircraft would appear.

what change did you make

andypoppens wrote: 12 Aug 2017, 23:14 what change did you make

NOTE: In order to maximize comparability with the largest number of helicopter scenery, I suggest setting the model size to 9 meters

Using the AIAE I checked the model size and it is 13m. I made the change to 9m, as per suggestion, and when I checked their base afcad at RJTK I found that the vast majority of parking spots were 10.67m for the Chinooks.
This is most likely the reason that your aircraft didn't show.

Now as the afcad doesn't have dedicated parking spots for the EC225s you could add/alter some and change the parking size to 13m but you may very well have problems every well that they go, hence the suggestion by Brent.

Oh and in case you weren't aware as well as being able to tell you what radius the model is set to AIAE can also alter it.

By the way I loaded up procmon and I did load the filter I have a question how exactly does procmon work plus does it take long to exclude events

Well I am sure that you can find some exact definition somewhere but it must intercept all calls made to the system processor(s).
That is why without a filter you will see every call from every process. This is why it is a powerful diag tool but you have to know what you want it to report. That particular filter I spent some time building up. I started by only showing FS9.exe events and then showing only failed calls and finally removing everything that is really superfluous for finding missing textures like IO calls and registry calls or
looking for non-existant .dat files in every single aircraft folder.

Then the big thing is to only show what isn't successful. You are not interested in what it does find only what it doesn't. That is the only thing that can make it crash or report missing textures from objects.

What you showed get is very close to the end of the filtered output is a failed call to find a texture. If you then use a tool like Everything you can then search your PC and see if you can find it.

The only way to understand what each line does in the filter is to untick everything in the filter and see what extra shows up.

The answer to your next question is that the excludes are almost instantaneous. Again temporarily untick a category and then re-tick and you will see how fast it works.

As with so many things, if you find other things that can be filtered out then go ahead and include or exclude them. The worst case scenario is that you have to reload my profile again.

Can you show me a picture on how to do that

Plus I have a question why why can't I figure out how to fix this what is the issue

What is it that you want a picture of?

Secondly, just in case you haven't got any options set I have exported my procmon config and attached it here. So load that first.

1. So ensure that fs9 is not running.
2. Start Procmon. IF the filter window auto-opens along with the main window close the filter window.
3. On the main window select File > Import Configuration and then select the unzipped ProcmonConfiguration.pmc file and then hit open. A requestor will appear while it loads the filters.
The main window will remain blank but the number of events being excluded on the status bar will be continuously rising. This shows that the filters are doing there job.
4. Under File check that Capture Events is ticked.
5. Under Edit check that Auto Scroll is selected.
6. Under Filter check that Advanced Output is selected and then hit Filter and open the window again.
7. In the secondary filter window you will see a number of operations some with green ticks and some with red crosses. The ticks are includes the crosses are excludes. The top one will be Process Name is FS9.exe .
8. Now you can close that filter window if you want, especially if you only have one monitor.
9. Start FS9

It is important to note here that as Procmon intercepts all call from your PC that everything runs slower while it is running.

10. With FS9 starting up the main Procmon window will start to fill up with events that pass the filters, i.e. FS9 process failures. None of these are critical.
11. Once you get to the FS9 options window you will notice that the output to the main window stops but the events in the status bar is still rising.
12. In FS9 create your flight by selecting your start location and some time in daylight, as that is where you have the problem, and then click Fly Now.
13. FS9 will now attempt to load your chosen aircraft and the start location and the events window in procmon will start again.
14. At some point FS9 will hit your problem and will terminate.
The procmon window will show all failures related to FS9 activties.
Obviously the cause of the crash will be near the bottom of the list.
15. To make it easier to find select Filter > Highlight. Another small window will open with green ticks in. You can delete them all or leave them it is up to you, but I would leave them at the moment as a guide to you creating your own highlight.
16. In that highlight window select the options at the top to 'Path' 'Contains' and in the box part of the path name to where the scenery you have just loaded resides e.g. 'Kobe' if that is appropriate. Then ensure that 'Include' is selected as the last option and then click add and then apply

What you should now have is all failures relating to your scenery folder highlighted. The last one is very probably the missing texture.

Now really I don't think I can make it any plainer than that. That is a step by step guide using templates I have already created.

You see that nobody else has this issue so it is not a scenery fault, it is an individual problem that you have and therefore only you can work out the issue.

Now when you do this what textures are reported as missing for your scenery, i.e. highlighted failures for your scenery folder?

I'v been meaning to tell you this Procmon is too complicated

Maybe you need to come out where I live so you can help me

Well to be honest it is not the simplest tool in the world to use, but then again diagnostic work never is. I have spent my career diagnosing computer problems and fixing them and I would agree that its not going to tell you what the issue is. You have to work out what you want to know (the Filter system) and then diagnose the results (the Highlight system).

The key thing here is that it if failing due to something missing. You can't guess like if a rogue scenery is causing a failure. With that you can keep deactivating/activating sceneries until you find it. You have to use a tool that looks at all calls your computer makes.

So, did you load it up successfully and see a blank window, then a window full of stuff as you start FS9, and then get highlighted messages once it fails.

1. Tell me first what scenery you were checking at.
2. Then tell me the path name of the folder/directory that the scenery is held in.
3. What did you set the highlight to.
4. What were the textures that were highlighted.

Now one thing to help here is that under File menu there is a Save option. When you click that you have two categories.
Events to save and Format.
The easiest here is to select Highlighted events and CSV output and save the file.

Now you have the opportunity to load the output into excel and can study them.
So what I would ask is that you save one file as stated, and then alter the Events option to Events displayed using current profile with Also include profiling events ticked and save again.
Now zip up both outputs and attach them here or if they are too big pm them to me.

I will check your findings but have a look yourself at either the highlighted output in excel or in the procmon window and tell me what you think it is highlighting as the problem.

maybe you need to come out where I live so you can help me