MAIW to FSX: Close, but no cigar....

[DaveB]

That's still a hell of an ask for someone who like me, has no interest in how these things work but just wants them to work as they should. The ideal solution is for someone versed in this field to say 'send me the two AFX files and I'll fix em for ya'. There are users out there who could do this in seconds and have em back 'by return'.

Fingers crossed for ya NC
ATB
DaveB

 

[rdaniell]

That's still a hell of an ask for someone who like me, has no interest in how these things work but just wants them to work as they should. The ideal solution is for someone versed in this field to say 'send me the two AFX files and I'll fix em for ya'. There are users out there who could do this in seconds and have em back 'by return'. Fingers crossed for ya NC ATB DaveB

Dave,

Please do not interpret my reply as being negative or rude in anyway. I have some experience with AI traffic and "fixing" someone else's traffic problem is not really that simple. The person attempting to "fix" it would have to have the same scenery and aircraft installed on their FSX for starters. Think of asking someone to do a repaint for you on a payware aircraft that they do not own.

Additionally, there have already been several members offering advice which apparently did not work for him.

Peace+

RD

 

[DaveB]

Dave,

Please do not interpret my reply as being negative or rude in anyway. I have some experience with AI traffic and "fixing" someone else's traffic problem is not really that simple. The person attempting to "fix" it would have to have the same scenery and aircraft installed on their FSX for starters. Think of asking someone to do a repaint for you on a payware aircraft that they do not own.

Additionally, there have already been several members offering advice which apparently did not work for him.

Peace+

RD

I didn't think that at all RD and appreciate that simple things can often turn out less so I have had similar problems with airports in the past and was able to pass them to 'a man who knows' who looked at the AFX file.. spoted the error and fixed it in two shakes of a lambs tail (that was a default airport too!!). I've tried fiddling with these things in the past with limited success but consider it something you really have to have an interest in. I much prefer them to work straight out of the box

ATB
DaveB

 

[scotth6]

MAIW packages quite often have other waypoint files that may be required for the aircraft to fly to. Maybe these haven't been installed correctly. You could try reinstalling the MAIW package, which usually has to be installed to a temporary folder and then installed manually in to FSX. In my experience MAIW airports should be OK out of the box as far as traffic movements go. After all it's what they are created for.

Also just to confirm, for Traffic tools to work you will need the following entry (with the path corrected to match your system) in your dll.xml file. This is in AppData/Roaming/Microsoft/FSX or FSX-SE, depending on which version you are using. The traffic tools should then be available from the FSX menu bar within the sim.

<launch.addon>
</launch.addon>See attached text file.

Cheers,

 

[Navy Chief]

MAIW packages quite often have other waypoint files that may be required for the aircraft to fly to. Maybe these haven't been installed correctly. You could try reinstalling the MAIW package, which usually has to be installed to a temporary folder and then installed manually in to FSX. In my experience MAIW airports should be OK out of the box as far as traffic movements go. After all it's what they are created for.

Also just to confirm, for Traffic tools to work you will need the following entry (with the path corrected to match your system) in your dll.xml file. This is in AppData/Roaming/Microsoft/FSX or FSX-SE, depending on which version you are using. The traffic tools should then be available from the FSX menu bar within the sim.

<launch.addon>
</launch.addon>See attached text file.

Cheers,

Scott, thank you for the file. I will take a look at it. Thanks also to Dave and RD for your suggestions. I do agree with you that it is much better to learn how to do this for myself, rather than have someone else fix the problems. AI is just something I have never learned how to manage, nor have I taken the time to work with ADEX. Other than placing a few objects in scenery with Instant Scenery (and very little time spent doing that either), I have merely played around with these programs. I know they have a lot of features, but do require considerable effort in learning how to successfully use them. NC

 

[mikewmac]

There has to be a way to get these AI moving around. I am not giving up this time, but it doesn't help that I still don't have a Tools menu with Traffic Tools. NC

What would be great if a SOH member, with experience with these things, could get connected with me via Team Viewer and maybe get this resolved!

Chief,

I can't help you via Team Viewer or with FSX SE, but I did check our MAIW download database and found that the only MAIW Whidbey Island package we ever released was named MAIW Whidbey Island Growlers_Desmond Burrell.zip released on August 29, 2015, so I assumed that this is one of the 2 MAIW packages that you were having trouble with in FSX.

I had never installed this package in FSX myself, so I just did to see if I had the same problem that you have and I definitely don't.

When I started FSX at NAS Whidbey Island today, Monday, 3-28-2016 at 18:00 Z, there are 20 EA-18G's parked with 9 scheduled to depart on Monday and 11 scheduled to depart on Tuesday. In addition there are 2 F-18C's, Expert 56 and 57, inbound from NAS Lemoore for a 18:10 Z arrival.

2 EA-18G's, Rampage 21 and 22, are receiving their IFR clearance for an 18:00 Z departure for NAS Fort Worth JRB before taxiing out to Runway 14 and departing as scheduled. At 18:18 Z 2 more EA-18G's, Scorp 21 and 22, receive their IFR clearance to the Olympic Alpha MOA, taxi out to Runway 14 and takeoff as scheduled.

After that there are additional flights scheduled for 19:50 Z, 21:00 Z and 22:58 Z. I didn't watch all of those, but I have no reason to believe that they wouldn't depart as scheduled.

If you are indeed using an ADE file named NAS Whidbey, then that is probably the source of your problem. The MAIW AFCAD2 file for NAS Whidbey Island that was included in the MAIW Whidbey Island Growlers_Desmond Burrell.zip file is named MAIW_AF2_KNUW_CUSTOM and is the one that should be used with this package. It does have quite a few "unconnected nodes" but they are intentionally unconnected for design purposes and have no affect on any of the EA-18G flights.

Hopefully this information will help you get the MAIW Whidbey Island Growlers package working properly.

 

[gray eagle]

I might add that the path to SDK needs to be spelled out a little better the the attached file i.e.,


..\Microsoft Flight Simulator X SDK\SDK\Environment Kit\Traffic Toolbox SDK\traffictoolbox.dll</path>


the above may work, but as you can see my SDK default installed in the C: drive hence:

C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X SDK\SDK\Environment Kit\Traffic Toolbox SDK\traffictoolbox.dll
in lieu of

MAIW packages quite often have other waypoint files that may be required for the aircraft to fly to. Maybe these haven't been installed correctly. You could try reinstalling the MAIW package, which usually has to be installed to a temporary folder and then installed manually in to FSX. In my experience MAIW airports should be OK out of the box as far as traffic movements go. After all it's what they are created for.

Also just to confirm, for Traffic tools to work you will need the following entry (with the path corrected to match your system) in your dll.xml file. This is in AppData/Roaming/Microsoft/FSX or FSX-SE, depending on which version you are using. The traffic tools should then be available from the FSX menu bar within the sim.

<launch.addon>
</launch.addon>See attached text file.

Cheers,