Military AI Works

I downloaded and installed the South Dakota ANG package from Marks Flight Simulator Paints. I had to create an AFCAD with parking spots. Once installed, no C Model F-16 aircraft shows up. I did see the D Model once sitting on the ramp. Same with the Kunsan package from Marks web site. Only 3 aircraft shows up at the terminal gates. I went through and assigned parking for these and no aircraft show up. I do periodically see a Kunsan bird sitting on a ramp at other airports/ air bases. I have the retro folder with the 181st and 183d Fighter Wing. I think this is one of Allans repaints. I did the same thing as I did with South Dakota and no aircraft shows up.
All files I've installed so far have been from the MAIW packages. I believe my the problem with no aircraft showing up maybe due to the flight plans. Just my opinion. Does anyone have any idea or any flight plans for these I can try?


Thanks,
Jack

jethomasjr wrote:I downloaded and installed the South Dakota ANG package from Marks Flight Simulator Paints. I had to create an AFCAD with parking spots. Once installed, no C Model F-16 aircraft shows up. I did see the D Model once sitting on the ramp. Same with the Kunsan package from Marks web site. Only 3 aircraft shows up at the terminal gates. I went through and assigned parking for these and no aircraft show up. I do periodically see a Kunsan bird sitting on a ramp at other airports/ air bases. I have the retro folder with the 181st and 183d Fighter Wing. I think this is one of Allans repaints. I did the same thing as I did with South Dakota and no aircraft shows up.
All files I've installed so far have been from the MAIW packages. I believe my the problem with no aircraft showing up maybe due to the flight plans. Just my opinion. Does anyone have any idea or any flight plans for these I can try?


Thanks,
Jack

Try making your parking spots a bigger radius.

Traffic % scale set?

Radius would be another issue to look at as mentioned. I'm running most if not all of Mark's paints with FP's posted in the Keep it Real thread. If you can't get it sorted let me know I can post them.

Victory103 wrote:Traffic % scale set?

Radius would be another issue to look at as mentioned. I'm running most if not all of Mark's paints with FP's posted in the Keep it Real thread. If you can't get it sorted let me know I can post them.

Thanks Chris. I am running my radius for the F-16 at 10.06 if that gives you an idea.


Jack

campbeme wrote:

jethomasjr wrote:I downloaded and installed the South Dakota ANG package from Marks Flight Simulator Paints. I had to create an AFCAD with parking spots. Once installed, no C Model F-16 aircraft shows up. I did see the D Model once sitting on the ramp. Same with the Kunsan package from Marks web site. Only 3 aircraft shows up at the terminal gates. I went through and assigned parking for these and no aircraft show up. I do periodically see a Kunsan bird sitting on a ramp at other airports/ air bases. I have the retro folder with the 181st and 183d Fighter Wing. I think this is one of Allans repaints. I did the same thing as I did with South Dakota and no aircraft shows up.
All files I've installed so far have been from the MAIW packages. I believe my the problem with no aircraft showing up maybe due to the flight plans. Just my opinion. Does anyone have any idea or any flight plans for these I can try?


Thanks,
Jack

Try making your parking spots a bigger radius.

Mark,

I have my radius for F-16 at 10.06. What should it be?

Jack

I'll check with Martin's AI Editor, but 10.06 was the standard. Prior to reading the wingspan vs. flight dynamics thread, I had changed all my F-16's aircraft.cfgs to actual RW wingspan size of 32.8/9.8m working with a spot size of 6 in ADE. I'll pull up my KFSD to confirm.

Victory103 wrote:I'll check with Martin's AI Editor, but 10.06 was the standard. Prior to reading the wingspan vs. flight dynamics thread, I had changed all my F-16's aircraft.cfgs to actual RW wingspan size of 32.8/9.8m working with a spot size of 6 in ADE. I'll pull up my KFSD to confirm.

Well I finally got some free time and made the wingspan to 14.00. I figured this should give it plenty of room. In the end I get the same result as to I only see the D model F-16 sitting on the ramp periodically. This baffles me.

Jack

14m is actually pretty large, as the original 10.06 is fine. Are the aircraft.cfg entries correct? One small, tiny typo can play havoc with ac not showing, it happens. Martin's AI Editor is a great tool to check everything out. I run new packages through it and AIFP2 to make sure.

If needed I can post my AFD file, although mine is modded.

Victory103 wrote:14m is actually pretty large, as the original 10.06 is fine. Are the aircraft.cfg entries correct? One small, tiny typo can play havoc with ac not showing, it happens. Martin's AI Editor is a great tool to check everything out. I run new packages through it and AIFP2 to make sure.

If needed I can post my AFD file, although mine is modded.

Modded is fine. I will check the aircraft.cfg. Do you have Buckley AFB and the F-16's? I have it just not the aircraft. I got what I could out of the Plains add-on but there were only two or three in that one. They don't show up either. I just added it today.

Jack

jethomasjr wrote:

Victory103 wrote:14m is actually pretty large, as the original 10.06 is fine. Are the aircraft.cfg entries correct? One small, tiny typo can play havoc with ac not showing, it happens. Martin's AI Editor is a great tool to check everything out. I run new packages through it and AIFP2 to make sure.

If needed I can post my AFD file, although mine is modded.

Modded is fine. I will check the aircraft.cfg. Do you have Buckley AFB and the F-16's? I have it just not the aircraft. I got what I could out of the Plains add-on but there were only two or three in that one. They don't show up either. I just added it today.

Jack

I downloaded the flight plan again and ran it through AIFP. All aircraft show up in AIFP. I put it in the Scenery/World folder and I get the same result. I ran the flight plan from the Plains package through AIFP and loaded it into the Scenery/World folder. Those three aircraft listed for Colorado ANG and S.Dakota show up on the ramp now.

jethomasjr wrote:

Victory103 wrote:I'll check with Martin's AI Editor, but 10.06 was the standard. Prior to reading the wingspan vs. flight dynamics thread, I had changed all my F-16's aircraft.cfgs to actual RW wingspan size of 32.8/9.8m working with a spot size of 6 in ADE. I'll pull up my KFSD to confirm.

Well I finally got some free time and made the wingspan to 14.00. I figured this should give it plenty of room. In the end I get the same result as to I only see the D model F-16 sitting on the ramp periodically. This baffles me.

Jack

I think, from the way I have read this that you have got it the wrong way around. The aircraft don't appear if their wingspan is bigger than the parking spot size. The solution is not to increase the wingspan, that makes it worse not better.

You have to either reduce the size of the wingspan or increase the size of all the parking spots so that the aircraft wingspan fits into the spot. Taking into account that altering the wingspan alters the way the aircraft flys.
All afcads are produced, here, for FS9 which doesn't use the wingspan but a size built into the mdl. FSX ignores this and uses the wingspan parm. This is why You have to convert packages to FSX to use them properly.
Martin's guide covers all the aspects very well.

Firebird wrote:

jethomasjr wrote:

Victory103 wrote:I'll check with Martin's AI Editor, but 10.06 was the standard. Prior to reading the wingspan vs. flight dynamics thread, I had changed all my F-16's aircraft.cfgs to actual RW wingspan size of 32.8/9.8m working with a spot size of 6 in ADE. I'll pull up my KFSD to confirm.

Well I finally got some free time and made the wingspan to 14.00. I figured this should give it plenty of room. In the end I get the same result as to I only see the D model F-16 sitting on the ramp periodically. This baffles me.

Jack

I think, from the way I have read this that you have got it the wrong way around. The aircraft don't appear if their wingspan is bigger than the parking spot size. The solution is not to increase the wingspan, that makes it worse not better.

You have to either reduce the size of the wingspan or increase the size of all the parking spots so that the aircraft wingspan fits into the spot. Taking into account that altering the wingspan alters the way the aircraft flys.
All afcads are produced, here, for FS9 which doesn't use the wingspan but a size built into the mdl. FSX ignores this and uses the wingspan parm. This is why You have to convert packages to FSX to use them properly.
Martin's guide covers all the aspects very well.

Thanks Steve!

First: I only changed the size of the wingspan because Victory103 suggested it. I kind of knew this would not fix my problem, but I will take any advice into trying to fix the problem. I looked at the aircraft.cfg and could not find anything wrong with it. One thing I did notice is in the download it is only the textures. You have to add the AIR file and a couple of other things to make it work. I copied these from another F-16 file. The AIR file is for the F-16 D. I was moving things around and thought to myself could this be the problem? I went into the Luke aircraft file to see what AIR file is used. In there is the F-16C file. I copied and pasted it into the S. Dakota file and when I went into FSX the flight line is filled up with F-16D models and they are all black. When I go from one end to the other of the line and look down to the other end the about 4 or 5 aircraft textures show up. As I head towards them they turn black again. I replaced the AIR file with F-16 D and they all disappear.

Second: I copied the aircraft from the Plain States ANG ai_ang by Dan Borque. Did all file transforming from FS9 to FSX. Installed into FSX and the only aircraft I need are the Colorado ANG. I saw the S. Dakota ANG in there. I copied those also. They (6 aircraft) as in Colorado and S. Dakota show up on the Colorado ANG ramp. The S. Dakota aircraft (6) show up on the flight line at KFSD. Therefore, there is a problem with a file somewhere, I just can't put my finger on it.

I emailed Mark directly on his website a while back but didn't get an answer. So everything I do is trial and error on my part.

Jack

I both sets working fine in FSX. I initially only changed the wingspan in the "[airplane_geometry]" ac cfg to match what the conversion manual suggests, so all my Vipers went from 45' down to 33'. Using Martin's AI Editor, this gives me the minimum spot size for all the AFD's. I generally add 1m to be safe, so minimum 6m becomes 7m spot size for parking.

No airfile adjustments, and I have not seen any issues with the fighters, although it was documented there could be issues noted on other models, like the PAI KC-135's.

I can post my traffic.bgls if needed for SD and CO ANG Vipers.

Victory103 wrote:I both sets working fine in FSX. I initially only changed the wingspan in the "[airplane_geometry]" ac cfg to match what the conversion manual suggests, so all my Vipers went from 45' down to 33'. Using Martin's AI Editor, this gives me the minimum spot size for all the AFD's. I generally add 1m to be safe, so minimum 6m becomes 7m spot size for parking.

No airfile adjustments, and I have not seen any issues with the fighters, although it was documented there could be issues noted on other models, like the PAI KC-135's.

I can post my traffic.bgls if needed for SD and CO ANG Vipers.

That would be great. That will tell me if the traffic.bgls I have are corrupted.

Jack

Both my CO and SD Vipers are in the same plans found in the FP thread, just be advised this is all ANG airframes:

I tried a little test.
From what I read it seems that you are creating two new folders, one for the F-16C and one for the F-16D.

So, I downloaded HT's original F-16 model package and copied the C D folders into my aircraft folder.
I then downloaded the flightplans from Marks site and placed into my scenery folder.
I then downloaded the two paint scheme packages from Marks site and placed the C schemes into the C folder and the D scheme into the D folder.
I copied the fltsim entries from the text in Marks C schemes folder and replaced the fltsim entries in the aircraft.cfg in that newly created F-16C folder.
Finally, I did likewise with Marks' D scheme text file over the fltsim entries in the new D folder.

I did nothing else, no deleting, no tidying up, no renaming, nothing.

I then used AIFP to check that the flightplan bgl was fine - it was and all aircraft titles were there. I then used Martin's AIAE to check that there were no problems with the aircraft folders I had just created and there wasn't.
I also checked what size spots were needed, using AIAE, and it is 8m for FS9 and 6M for FSX. So as long as your afcad spots are big enough for 8M then they should appear in either FS9 or FSX.

My supposition here is that if you do the basic of installations then the aircraft will show up, unless either there is a problem with your afcad spots or you have altered something somewhere from the process. It does sound like you have altered something.

What I would suggest is to download the original model package http://htai-models.com/downloads.html , clean up your current installation, and follow the basic method and see if they show up. Once you have them there then make any amendments you like.

Victory103 wrote:Both my CO and SD Vipers are in the same plans found in the FP thread, just be advised this is all ANG airframes:

Thanks Chris I appreciate the files.

Jack

Firebird wrote:I tried a little test.
From what I read it seems that you are creating two new folders, one for the F-16C and one for the F-16D.

So, I downloaded HT's original F-16 model package and copied the C D folders into my aircraft folder.
I then downloaded the flightplans from Marks site and placed into my scenery folder.
I then downloaded the two paint scheme packages from Marks site and placed the C schemes into the C folder and the D scheme into the D folder.
I copied the fltsim entries from the text in Marks C schemes folder and replaced the fltsim entries in the aircraft.cfg in that newly created F-16C folder.
Finally, I did likewise with Marks' D scheme text file over the fltsim entries in the new D folder.

I did nothing else, no deleting, no tidying up, no renaming, nothing.

I then used AIFP to check that the flightplan bgl was fine - it was and all aircraft titles were there. I then used Martin's AIAE to check that there were no problems with the aircraft folders I had just created and there wasn't.
I also checked what size spots were needed, using AIAE, and it is 8m for FS9 and 6M for FSX. So as long as your afcad spots are big enough for 8M then they should appear in either FS9 or FSX.

My supposition here is that if you do the basic of installations then the aircraft will show up, unless either there is a problem with your afcad spots or you have altered something somewhere from the process. It does sound like you have altered something.

What I would suggest is to download the original model package http://htai-models.com/downloads.html , clean up your current installation, and follow the basic method and see if they show up. Once you have them there then make any amendments you like.

Steve,

I followed your steps and it worked. I downloaded the original files from Marks website. I looked at the files I put together and they to were assembled like what you did. Now I have a full flight line with all of the South Dakota F-16's. Now I just need to find the textures for Colorado ANG unit.

Jack

Jack, glad that you have now sorted out your issue.
Now for the second part, go back to Mark's site and the very item below the SD ANG F-16's are the CO ANG F-16s.

Hopefully, you have kept the download of HT's F-16s so that you can create another couple of folders as before.

Firebird wrote:Jack, glad that you have now sorted out your issue.
Now for the second part, go back to Mark's site and the very item below the SD ANG F-16's are the CO ANG F-16s.

Hopefully, you have kept the download of HT's F-16s so that you can create another couple of folders as before.

Steve,

After fixing this last night I went back and fixed a couple of other F-16 units this morning before I went to school that were not showing up. Also, I did notice I had downloaded the CO ANG F-16 textures a while back. When I say a while back I mean 4-6 months at least just before I got laid off. After looking for something else in my download folder and seeing the texture zip I remember downloading them, but not having time to work on them. That fixed all of them. I appreciate your help with this.

Thanks again,

Jack