Military AI Works

Tirithon wrote:Maybe I've missed something, but looking at the AFCAD I noticed that the C17 parking spots do not match with the info provided by P3_Super_Bee here ?! Any reason for this?

Greg

Greg,

Welcome to the forums. Unfortunetly the AFCADs are a compromise between the real world and FS2004 world. The initial afcad that gets installed when you unzip all the files is meant to be used with the default PHNL airport scenery courtesy of Microsoft. The modified AFCAD that is also included is meant to be used with Bill Mechlair's PHNL freeware scenery as well as DBWsim's Hickam AFB freeware scenery. Some of the buildings placed in the DBW scenery prevented me from placing the parking where I wanted to. So as with every AFCAD there's always a bit of compromise involved. It is very hard to make an AFCAD that will work with every user's setup since we never know who has what scenery installed etc.

As always feel free to modify the AFCAD to your own liking for your personal use.

Thanks for the explanation Mike.

Oh, and welcome too!! (We joined the same day you know )

I have tried downloading and installing the C-17 package several times using the 2.4 installer on FSX but it will not work.

This is what I get:

See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.IndexOutOfRangeException: Index was outside the bounds of the array.
at WOAI_Installer.frmMain.ReadPackage()
at WOAI_Installer.frmMain.btnNext_Click(Object sender, EventArgs e)
at System.Windows.Forms.Control.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ButtonBase.WndProc(Message& m)
at System.Windows.Forms.Button.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)


************** Loaded Assemblies **************
mscorlib
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/WINDOWS/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll
----------------------------------------
WOAI Installer
Assembly Version: 2.4.0.0
Win32 Version: 2.4
CodeBase: file:///C:/Program%20Files/Microsoft%20Games/woains24/WOAI%20Installer.exe
----------------------------------------
Microsoft.VisualBasic
Assembly Version: 8.0.0.0
Win32 Version: 8.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/Microsoft.VisualBasic/8.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualBasic.dll
----------------------------------------
System
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Windows.Forms
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System.Drawing
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
System.Runtime.Remoting
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Runtime.Remoting/2.0.0.0__b77a5c561934e089/System.Runtime.Remoting.dll
----------------------------------------
System.Configuration
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Configuration/2.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
----------------------------------------
System.Xml
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
ICSharpCode.SharpZipLib
Assembly Version: 0.84.0.0
Win32 Version: 0.84.0.0
CodeBase: file:///C:/Program%20Files/Microsoft%20Games/woains24/ICSharpCode.SharpZipLib.DLL
----------------------------------------

************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.

For example:

<configuration>
<system.windows.forms jitDebugging="true" />
</configuration>

When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.

Looks like an installer issue. I would check with the folks at:
http://www.world-of-ai.com/
Please bear in mind that the afcads may not work right in FSX. The packages are not designed for, nor are they tested, in FSX.

Seems that decompiling the plans really screws them up (or less likely but possible they're screwed to start with).

Wondered why only 1 out of all the C-17's was showing up so did some digging and found things like some really bad time errors day 6-0-6-0-1 for example. Currently going through manually fixing them. Also discovered TTools Companion really doesn't like any flightplan type other than WEEK. A shame as its fantastic for helping to spot mistakes.

Hi Ben,

To use ttools companion, you need to copy the plans to a temp text doc, delete the TNG commands and then they'll test fine.

It's the TNG it does not like, as it was designed for Fs8 which did not have them.

Cheers

Stew

Decompiling/compiling causes all kinds of grief (of which we here are very familiar with).

Ah, that makes sense Stew cheers mate, will do that from now on. As for decompiling/compiling causing grief tell me about it. Perhaps in future packs you could include the txt files prior to compilation for those of us who do a manual install?

Include prior to compile txt files? Yes Please! Thankyou.

Ron

Is the jet turbine looking as it is supposed to be? The part in the middle where it looks like partly disassembled.

This is with FSX.

Thank you,
Martin


[/img]

Hi Martin,

Thats the way the model was built by the guys over at Project AI. When at rest it sits with the reverse thrusters open (I think).

Anyway, whatever the reason, it's meant to look that way

Cheers

Stew

Hi Stew,

Great news. I expected something like that, because it was not looking buggy, just ... different. Now I am curious and must check what happens when the C-17 powers up for flight.

Thanks a lot!

Cheers,
Martin

Í have B-1's, KC-135's, E-6's at the apron but no C-17's.....checked it at various dates/times

One problem I have is the C-17's are at the airport gates. If I could use 1HNL AFCAD, instead of PHNL, they would be on the proper side of the airport. Is there a way to install 1HNL in the flight plans ?

decompile and do a search and replace.

Thanks, I will give that a shot.

I made an AFCAD for PHNL, accurate for both military and commercial. PM me with an email address if you want it.



PS - It's for the default FS9 scenery

PPS - I also made flightplans for the resident KC-135 unit using a repaint from AVSIM. If you want it PM me also but I need to get the go-ahead to offer it since I didn't get permissions to re-offer it