Military AI Works

BadPvtDan wrote:FS9 or FSX?

Oops, sorry. FSX SP2, XP. I'm fairly experienced at this. Just kinda getting back into it, with winter here now. I'm actually going back and picking up packages I didn't have previously installed. This is the first one to throw me a curve.

The 10 10x10 runways located some distance away are probably related to implementing "crosswind runways" such that more than 1 runway can be active at a time.

The package was designed and tested (as are all of our packages) for FS9. I thought afcads for FS9 acted squirrely in FSX?

I'm running FSX Sp2 with UT-USA and can confirm the trees and buildings in inappropriate areas.

Give me a few minutes to fix it with AFX.. or not.

Note: I usually ignore a lot of "fault finder" errors so long as the aircraft takeoff and land regularly because afcad designers often deliberately leave/design such errors in for "visual" purposes.

Ford Friendly wrote:I'm running FSX Sp2 with UT-USA and can confirm the trees and buildings in inappropriate areas.

Give me a few minutes to fix it with AFX.. or not.

Note: I usually ignore a lot of "fault finder" errors so long as the aircraft takeoff and land regularly because afcad designers often deliberately leave/design such errors in for "visual" purposes.

True. I'm seeing that a lot. Thanks for the quick help.

Unfortunately, I can't attach the file with my quick fix in this forum. I'll pm it to you both and hopefully it can be added by a mod.

I saved it in FS9 format so anyone should be able to use it.

Edited to add... SENT

Ford Friendly wrote:Unfortunately, I can't attach the file with my quick fix in this forum. I'll pm it to you both and hopefully it can be added by a mod.

I saved it in FS9 format so anyone should be able to use it.

Edited to add... SENT

You're a peach. Thanks, and happy holidays.

Thanks for helping the user, Ford. Since the file works fine in FS9, we'll keep it to PMs.

Seems to be a missing flight plan for the following a/c
title=WoA_HTAI_C-130H_RCH_XX_156_93-1458
sim=AI Lockheed C-130H
model=wing_tanks
texture=RCH_XX_156_93-1458
ui_variation=USAF Seaboard
ui_manufacturer=Henry Tomkiewicz
ui_type=Lockheed C-130H
atc_airline=EPIC
atc_parking_codes=156A,C130
atc_parking_types=MIL_CARGO
atc_heavy=0
description=AI Lockheed C-130H Hercules by Henry Tomkiewicz.
Was this left out or do I have an old version?

Les

/shrug
It's 2 1/2 years old

I have had a look at the old plans, as Dan said, and saw that of the 5 schemes for NC ANG, one is used 3x, three are used 2x and one, 93-1458, is not used at all.

Now it would seem that the best way to fix this yourself is to decompile the plans into their three txt files, amend the aircraft txt file by adding this line:-
AC#464,340,"MAIW_HTAI_C-130H_RCH_XX_156_93-1458"
and then amending the flightplans txt file by altering one of the AC#460 entries so that the line begins:-
AC#464,931458, ....
Then recompile. That will solve your problem.

Now I am sure that the original flightplan author would wish me to tell you that decompiling/recompiling flightplans can create problems, each time you do it.

Now there are two two other options available here. One being to hope that we get around to updating the pack in the future to individual aircraft, as we do now, rather than representative ones, as we did with this one, or you can curse us forever.

Personally, I would prefer one of the first two rather than the third but its your choice .

Hope this helps.

you can curse us forever

ack ack ack ack
Curse you, RedBaron!
ack ack ack ack


***next line edited for clarity and proper emphasis***
Sorry *comma(pause..wait for it.. wait for it...)*
it's Friday.

Ford, don't apologize for the day of the week! We know that its completely outside your control, mate .

Steve,
I pretty much did that. I figured that would be the easiest to do.
I just take it with this being an early package there would be bugs.

Les

There will be bugs in the package we release tomorrow.

There better not be!!