duckbilled

I'm really looking forward to this. To be usable, this tool will need to prevent installation of models that are not compatible with V4. BTW, I have been using some version of Ultimate Traffic since the program was in public beta (2003). Of course, things need to get updated faster than UT releases schedules, so I have always had a mix of UT and other traffic. There is no need to uninstall UTL to use BGL traffic. Just deactivate the airlines in UTL that you no longer need.

Perhaps some industry-wide authority could develop a license that could be adopted by all freeware authors, and maybe even require them to adopt the license if they want top upload their work to freeware libraries. Not sure who that industry-wide authority could be let alone one with a file library.

You can add FedEx and UPS using a package developed for UTL. There is a link to the package in the UTL forum.

I don't know how, but I do know how to identify them, in general. I used a program called TumbnailExporterX to scan the FLAI folder. I goes through and checks all of the mdl's. If they are "MDLX", they should work. If they are MDL8, they probably won't. I also see types like PV20 - I'm not sure what those are. I removed them. Anyway, if you could figure out a way to read the model type, that could do it. I'm sure there are many ways to do this, and I bet the folks at AIG have a lot more information.

Would it be possible to build in a check for V4 compatibility? That's one of the biggest unities for updating AI - making sure you have a compatible model. I believe there are also issues with night textures, but, I'm not sure what that is all about.

I suspected this could be an issue, so I approached this as a one-time boost to my assigned repaints. The main thing I really wanted was the FSX native models, so I didn't have to assemble them on my own, so I'll probably continue to use the FLAI folder structure for future paints, but I wont run the updater. I suppose I could also copy the modified ones to a new folder, change the titles and add new textures. I'm not sure if there are release notes for updates, but if it turns out that I decide to update FLAI, I'll dump the new version in a temp folder. Also, it is nearly impossible to work with assignments if you don't have UI_Manf organized well. I use FLAI Boeing, FLAI, Airbus... Aside from removing incompatible aircraft, that is the only change I have made so far.

I just moved them out of the P3d directory (saved them just in case). Now, I could be wrong about my list, so the folks at FLAI should have a more accurate picture. I do agree this is a big time saver. Back before I had kids, I was able to get UT2 down to a really small repaint list (was using some stuff as old as PAI for obscure airlines). Now, with the need for FSX compatible models, I just don't have the time to piece together all of the updated models and textures. This gives me a good start. Also, I see no reason why we can't manually add new textures to the FLAI folders. Still, i'm not sure how the auto updated will react if there are unofficial textures in their folders.

This sounds really interesting. A couple questions: If I have already modified assigned aircraft, will it ignore my new assignments? In other words, is it just searching for default textures in the assignments and re assigning them with FLAI paints when the paint matches the assignment? If so, will it include FLAI paints were no default paint is currently assigned? While it only works with FLAI aircraft, what if I install a new texture within the FLAI folders? Will it pick those up or ignore them?

I went through the mdls and came up with this list of included aircraft that are not compatible with P3DV4. These are listed by folder name. FLAi_A10 FLAi_A140 FLAi_A148 FLAi_A158 FLAi_AN72 FLAi_B462 FLAi_B463 FLAi_B703 FLAi_C140 FLAi_C17 FLAi_C46 FLAi_C5 FLAi_C510 FLAi_C550 FLAi_CRJ2 FLAi_DC10-10 FLAi_DC10-30 FLAi_DC87 FLAi_E140 FLAi_E145 FLAi_E45X FLAi_E50P FLAi_F15D FLAi_F16D FLAi_GL5T FLAi_GLEX FLAi_IL86 FLAi_IL96 FLAi_JS41 FLAi_K35R FLAi_KC10 FLAi_L1011 FLAi_PA31 FLAi_SR22 FLAi_SW4 FLAi_T134

I couldn't find a list. I went through the mdls myself and came up with this list of included aircraft that are not compatible with P3DV4. These are listed by folder name. FLAi_A10 FLAi_A140 FLAi_A148 FLAi_A158 FLAi_AN72 FLAi_B462 FLAi_B463 FLAi_B703 FLAi_C140 FLAi_C17 FLAi_C46 FLAi_C5 FLAi_C510 FLAi_C550 FLAi_CRJ2 FLAi_DC10-10 FLAi_DC10-30 FLAi_DC87 FLAi_E140 FLAi_E145 FLAi_E45X FLAi_E50P FLAi_F15D FLAi_F16D FLAi_GL5T FLAi_GLEX FLAi_IL86 FLAi_IL96 FLAi_JS41 FLAi_K35R FLAi_KC10 FLAi_L1011 FLAi_PA31 FLAi_SR22 FLAi_SW4 FLAi_T134

Just saved me from reading 5 pages. That was where I was at when I heard about the Md-11 and it sounds like were I will stay.

Does the package contain any models that are not compatible with V4?

Right, but I'm thinking of it from a origin/destination standpoint based on my personal preferences. My main goal is to utilize MEM and SDF more. I can't find any recent picks of 747's at MEM. At SDF, yes, but since I don't typically do cargo flights, and most of my flights are less than 5 hours, a 757 is better for me from a cargo standpoint. If the 747 package was a lot cheaper, I'd buy it, but for that price, I'm going to want to get a tone of use out of it.

I totally agree with this, but my explanation is a little different. In FSX, I had the NGX and their 777. Because of the cost, I didn't get the 777 for P3D, but I did re-buy the NGX. Most of my flight are less than 5 hours, so I didn't get a lot of use out of the 777. I did, however, buy the 787. I don't get a lot of use out of it either, but the price was right. It is a beautiful aircraft visually. I haven't had too many issues, but I do miss the way PMDG simplifies certain things. Unlike many, I do like the team at QW and I do believe they do their best to address issues. In addition, I know it is a lighter aircraft, but I really like their 757 in FSX, and I really want it for P3D. In the end, it is really about how much I'll use the aircraft and how much it costs. I try to do reasonably realistic flights (correct aircraft/destination/origin/airline), so I don't see an opportunity to use the 747 package very often. The 747-400 is being retired by many airlines and the 747-8's pax usage is very limited. I don't typically do cargo flights, but if I did, I'd rather see a 757, because it is used by UPS and FedEx.

You should still check to see if the default traffic bgl is active. It default traffic doesn't perform well and should be disabled - especially if you are you custom traffic.Also, keep in mind that NYC is one of the most traffic heavy areas with 3 major airports and lots of scenery/autogen. Run the live updater. He has fixed the issue.