Military AI Works • General MAIW Conversion Package issues - Page 4
Page 4 of 8

Re: General MAIW Conversion Package issues

Posted: 20 Dec 2018, 18:51
by md11driver44
I have the parking spots set for mil_combat (26.00). Is this to large?

Re: General MAIW Conversion Package issues

Posted: 20 Dec 2018, 19:11
by md11driver44
Now I am curious. I have two F15's from Portland sitting on stands, but still no aircraft from Mountain Home. Is the 389th, 391st and 428th from Mountain Home?

Re: General MAIW Conversion Package issues

Posted: 20 Dec 2018, 20:19
by Firebird
No the parking sizes are not set too large, although you didn't say if that is feet or metres.

Again, I come back to the question of what does AIFP show when you load the traffic file for Mountain Home.
For problem determination you have to start at the simple stuff, it is always going to be quicker than assuming that you have something unusual as the problem. You might have - but you have to eliminate the probable causes first.

Re: General MAIW Conversion Package issues

Posted: 20 Dec 2018, 20:29
by md11driver44
On my AIFP I show everything in black and a green checkmark above the aircraft names in my AIFP.

Re: General MAIW Conversion Package issues

Posted: 21 Dec 2018, 03:14
by pslinger
One other detail when checking the flight plans and aircraft with AIFP. Look on the left hand side and make sure the Target Version is set to FSX.

Re: General MAIW Conversion Package issues

Posted: 21 Dec 2018, 08:56
by Firebird
OK one question down.
So there are still two more to go from the ones I asked nearly a week ago.

Please confirm that you have BOTH sliders set to 100%.
That you have checked in AIFP that there are no FS9 traffic files.

I am also curious about the FSX scenery that you say you downloaded from here, as we haven't down any FSX scenery for Mountain Home.

***N.B.***
I think I know what your problem is but until those two questions are answered I can't be sure.

Re: General MAIW Conversion Package issues

Posted: 21 Dec 2018, 21:13
by md11driver44
Firebird wrote: 21 Dec 2018, 08:56 OK one question down.
So there are still two more to go from the ones I asked nearly a week ago.

Please confirm that you have BOTH sliders set to 100%.
That you have checked in AIFP that there are no FS9 traffic files.

I am also curious about the FSX scenery that you say you downloaded from here, as we haven't down any FSX scenery for Mountain Home.

***N.B.***
I think I know what your problem is but until those two questions are answered I can't be sure.
Everything is targeted to FSX and all MIL flightplans are set to FSX.

Re: General MAIW Conversion Package issues

Posted: 21 Dec 2018, 21:53
by Firebird
OK still not answered all the questions.

Do you have BOTH your FSX traffic sliders to 100%? I am thinking not, and I do have a reason why I think this.

Re: General MAIW Conversion Package issues

Posted: 21 Dec 2018, 21:58
by md11driver44
Sorry. Yes both FSX traffic sliders are set to 100%

Re: General MAIW Conversion Package issues

Posted: 24 Dec 2018, 06:51
by md11driver44
md11driver44 wrote: 21 Dec 2018, 21:13
Firebird wrote: 21 Dec 2018, 08:56 OK one question down.
So there are still two more to go from the ones I asked nearly a week ago.

Please confirm that you have BOTH sliders set to 100%.
That you have checked in AIFP that there are no FS9 traffic files.

I am also curious about the FSX scenery that you say you downloaded from here, as we haven't down any FSX scenery for Mountain Home.

***N.B.***
I think I know what your problem is but until those two questions are answered I can't be sure.
Everything is targeted to FSX and all MIL flightplans are set to FSX.
OK I have at least one FSX traffic slider at 100%. Not sure where the other one is.

Re: General MAIW Conversion Package issues

Posted: 24 Dec 2018, 10:25
by Firebird
The other slider for GA traffic is immediately below it. I am guessing that it is at 0%.

Why do I suspect this? Because I downloaded the package you used and looked at the aircraft.cfg file

The reason I am making this assumption is that under FSX/P3D if you do not have each aircrafts "atc_airline=" parm set to something then aircraft is automatically a GA - General Aviation - aircraft.

The package you used has no callsigns.

So if it as I suspect you either have to bump up your GA slider to 100% or transfer the callsigns from the aircraft.cfg files from our original package and the aircraft will show up.

I suggest that you move the slider first to check if this is correct.

Re: General MAIW Conversion Package issues

Posted: 24 Dec 2018, 13:40
by gsnde

Firebird wrote: The reason I am making this assumption is that under FSX/P3D if you do not have each aircrafts "atc_airline=" parm set to something then aircraft is automatically a GA - General Aviation - aircraft.
I did not know this, Steve! Cool piece of information.

From mobile hence short


Re: General MAIW Conversion Package issues

Posted: 24 Dec 2018, 19:04
by Firebird
Whilst I have never been described as cool, I am happy if any info I have is.

Re: General MAIW Conversion Package issues

Posted: 25 Dec 2018, 00:24
by md11driver44
It worked for Mountain Home, but I'm still not seeing other AI aircraft. I will give you the list of who I cant see after Christmas.

Re: General MAIW Conversion Package issues

Posted: 25 Dec 2018, 08:50
by Firebird
OK I am glad that we got to the bottom of this problem.
So to wrap that up either you need to keep your GA slider up at 100% or you need to ensure that each aircraft you add to FSX/P3D needs to have an non-blank atc_airline parm.

Whilst this could have been rectified over a week ago I am glad that you didn't assume that every issue you had was due to the same thing. It is a common mistake and can lead to some very protracted trial and error work.

So we deal with one error at a time, and maybe that fixes other issues. It is the only way to do it.

Re: General MAIW Conversion Package issues

Posted: 29 Dec 2018, 05:39
by md11driver44
OK. I have aircraft at every military base with the exception of Hickam, Charleston and Altus. I have no C17's showing up at these bases. Parking spots and named for each but still no aircraft.

Re: General MAIW Conversion Package issues

Posted: 29 Dec 2018, 06:43
by Firebird
OK.
Well pick one base and start the simple checks from the start. If you have a problem with the aircraft when you fix that you will fix them all.

So lets choose Hickam, as it has other types there. Please confirm that you see other mil traffic there i.e F-15s.
So we can eliminate the sliders chek as we know for sure that you have moved it to 100% and part of your earlier checks you checked for FS9 traffic files. So 2 down.

Next up do you have scenery installed and active?
Now when you load the traffic file into AIFP what colour are the aircraft?

Re: General MAIW Conversion Package issues

Posted: 29 Dec 2018, 22:13
by md11driver44
Firebird wrote: 29 Dec 2018, 06:43 OK.
Well pick one base and start the simple checks from the start. If you have a problem with the aircraft when you fix that you will fix them all.

So lets choose Hickam, as it has other types there. Please confirm that you see other mil traffic there i.e F-15s.
So we can eliminate the sliders chek as we know for sure that you have moved it to 100% and part of your earlier checks you checked for FS9 traffic files. So 2 down.

Next up do you have scenery installed and active?
Now when you load the traffic file into AIFP what colour are the aircraft?
I think I read somewhere in here that AI Aircraft for P3D cannot be used in FSX. Is this correct?

Re: General MAIW Conversion Package issues

Posted: 29 Dec 2018, 23:47
by gavinc
md11driver44 wrote: 29 Dec 2018, 22:13 I think I read somewhere in here that AI Aircraft for P3D cannot be used in FSX. Is this correct?
Correct - Aircraft compiled for P3Dv4 are not backwards compatible.

Gavin

Re: General MAIW Conversion Package issues

Posted: 31 Dec 2018, 01:52
by md11driver44
OK that explains why I was not seeing any C17's.