JASDF Bases

[andypoppens]

Brent if you had an assistant you could make more Japanese sceneries

[clickclickdoh]

I have a great many assistants here at MAIW, though assistant is the wrong word. Maybe, Co-conspirators. None of the projects I produce are a solo effort. All of the objects, AI models, textures and effects that are used in my projects are created by the hard work of a dozen other people.

[andypoppens]

Are you ever going to make Kagoshima Fukuoka Kansai Hakodate and can you make a scenery for Tachikawa

[Firebird]

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

Lets exclude that as a fiscal possibility.

What is the current difficulty?

You have Procmon.
You have my config file.
You have my filter file.
I know that you can load FS9.
I have explained what to highlight.
I have explained how to save the output.
I have offered to interpret the output.

I can't see how it could get any better for you, other than a physical manifestation or somebody taking over your PC remotely (which I personally would never recommend).

This is all I ask is the answer to 6 simple questions.
1. With my config and filter loaded and FS9 NOT RUNNING - Is the main Procmon window blank?
2. With my config and filter loaded and FS9 RUNNING - Is there output in the main Procmon window?
3. What is the path name of the scenery that you are having problem with?
4. Are you able to to highlight?
5. Are you able to save the output in the two ways that I described above?
6. Are you able to attach the output here or pm it to me?

[Firebird]

Are you ever going to make Kagoshima Fukuoka Kansai Hakodate and can you make a scenery for Tachikawa

Andy,
Lets get one scenery fixed before you worry about others.

[andypoppens]

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.

no I didn't see a window full of stuff as I started FS9 and then get highlighted messages it just remained blank plus how long does it take for the filter to exclude non FS9 events

[Firebird]

OK.
Well if it was blank from the start then you must have the filter on, otherwise you would have streams about everything on your system.
So if nothing is coming up when you start FS9 then one of two things is true. Either one of my filters also blocks your traffic or your FS9 proggy is not called FS9.exe.

Lets start easy, can you confirm that your proggy is called FS9.exe and can you tell me the full path to your FS9.exe?

*EDIT*

I have just had an idea. You don't have your FS9 install in the default location, C:\Program Files (x86)\Microsoft Games\Flight Simulator 9\, do you?
If you do it is not really a great idea as you can get a lot of permission problems, but any way if you do then you will need to amend one of the filters.

You will see that one is 'Path contains C: Exclude'. If you have FS9 installed on the C: disk then nothing will show up.
What you will need to do is untick that option and then add a new one, you can't amend one, and using the options at the top of the filter window set them, in order, to 'Path' 'contains' then type 'C:\Windows' 'exclude' and add it.

When you then press 'Apply' the main window will immediately fill up. The reason that the original filter was added is that FS9 does a lot of checking against windows directories and it just fills it with rubbish.

So to prove my case try making the amendment AFTER you have started FS9 up and you will see how quickly it works.
Then try to export the results that I asked for.

[andypoppens]

OK.
Well if it was blank from the start then you must have the filter on, otherwise you would have streams about everything on your system.
So if nothing is coming up when you start FS9 then one of two things is true. Either one of my filters also blocks your traffic or your FS9 proggy is not called FS9.exe.

Lets start easy, can you confirm that your proggy is called FS9.exe and can you tell me the full path to your FS9.exe?

*EDIT*

I have just had an idea. You don't have your FS9 install in the default location, C:\Program Files (x86)\Microsoft Games\Flight Simulator 9\, do you?
If you do it is not really a great idea as you can get a lot of permission problems, but any way if you do then you will need to amend one of the filters.

You will see that one is 'Path contains C: Exclude'. If you have FS9 installed on the C: disk then nothing will show up.
What you will need to do is untick that option and then add a new one, you can't amend one, and using the options at the top of the filter window set them, in order, to 'Path' 'contains' then type 'C:\Windows' 'exclude' and add it.

When you then press 'Apply' the main window will immediately fill up. The reason that the original filter was added is that FS9 does a lot of checking against windows directories and it just fills it with rubbish.

So to prove my case try making the amendment AFTER you have started FS9 up and you will see how quickly it works.
Then try to export the results that I asked for.

I just did that but it's not filling up

[Firebird]

OK then in Filters untick everything EXCEPT the 4 green includes at the top of the list. That should should give you a lot of rubbish but it will only be FS9 stuff. If it is still empty then there is something wrong.

Please confirm that your FS9 process is called FS9.exe

[andypoppens]

Yes it's called FS9 exe

[Firebird]

OK did you untick everything except the includes and apply that?

[Firebird]

OK, I went back to the drawing board with the filter.
Rather than using the one that has worked perfectly fine on my PC for years I cleared it out and created a new one from scratch for you, which is far more generic.

So load up procmon and select the 'Reset Filter' option under the Filter menu.
What should happen is that the main window should spring into life. It will be constantly updating from all sorts of Process Names and the number of events in the bottom status bar will be rising rapidly.

Now again under the Filter Menu select 'Organise Filters ...'
When the small window opens click on 'Import' and then select the 'Filter FS9_2.0.PMF file that I have attached here and click 'Open'

Now to activate it. Again under the Filter menu, select 'Load Filter' and then 'Filter FS9_2.0'
You will then see a requestor titled 'Applying Event Filter'

What should happen then is that the window will go blank as the only thing we are including in the new one is anything from FS9.exe.

If you get to this stage then we should be on the right track and if you now start FS9 then the window will now fill up with stuff ONLY from Process Name FS9.exe

By doing this I have ruled out any possible local setup that I have that maybe different from yours.

You can now apply the highlight that you were going to before and can then save the output I requested before.

[andypoppens]

I did install that and I unticked everything but FS9 exe now the window is filling up with FS9 stuff but i don't know which file is which there are so many can you tell me how to read it Steve

[clickclickdoh]

What you are going to be looking for are the last few files that FS9 calls right before it crashes. If one of those is a call to a texture file, that's most likely to be your culprit. So, just let the program run until FS9 stops working, then find the last few files calls.

[andypoppens]

i think I got something Steve and Brent few of the Kobe files the result is FAST IO DISALLOW what does that mean plus I cant find the texture files

[clickclickdoh]

The best thing to do would be to take a screen shot of the last few results and post it here so that we can look at it.

[andypoppens]

I'll try Brent

[Firebird]

With that latest filter list you do not need to untick anything.

Also if you save the file, as I said some posts ago, it will be better than taking screenshots.
Under 'FIle' menu then 'Save'

Set the 'Events displayed using current filter' and 'Comma-Separated Values' and save it to your desktop. Then zip it up.

Do this again but select the 'Highlighted events' radio button and save with a different name.

***IMPORTANT***
When I was trialing the new filter last night there were 3.5M events with just the FS9.exe ticked. With all the new options set there were 795.
I can not stress enough that you MUST have all the new filter options ticked as it will be nearly impossible to save and send the output. Also you will probably not have the error on the last screenshot.

*** FINALLY ***
What is the path name of the scenery folder that is causing the problem?

===========================================================================================================

In simplistic terms if FS9 crashes then it will be because it can't find a file it is looking for the logical thing will be that it will be one of the last things it tried to find/load.

It is different when the scenery loads but there are white objects there. Then you use the filter to see what the textures it was trying to load from your scenery directory. All the ones highlighted are the missing ones.
What you may have to do in that case is slew your aircraft around the base to ensure that all missing textures are found.

[andypoppens]

On second though Brent and Steve when it stops loading at 55 percent it says loading terrain so it might be a problem with the terrain and not a missing texture

[Firebird]

It is still likely to be a texture. Everybody, but everybody that runs FS9 has had this issue. The point is that Procmon will highlight the issue.
Please just run the instructions and give us the output, AND the name of the scenery folder.