dgeddesjr

Wow that is great work, I'll try it out! Thank you!

Position three would be useful for US operators that keep the last two characters the same. Many of them like to use their initials for the last two characters, like Virgin America for example who uses "VA". I'm enjoying your program immensely and thanks for all your hard work in putting it together. I understand why you don't want to check for a wildcard everywhere but using that third position will help a lot with US carriers. What has already been implemented at the last position helps with some of the non-US carriers and it works well for those.

Any plans to implement the use of * in the registration at other places other than the last character? So for example, N94*LR,N95*LR,N24*LR,N93*LR,N91*FJ,N92*FJ etc The regional jets in the US are a nightmare and often only report their registration to RealTraffic, and to make things worse you have several different operators for a specific type so the only way you're going to get the correct livery is to use registration. Unfortunately PSXSeeconTraffic ignores * if it's not the last character.

Looks like this is a widespread problem, I came here looking to see if anyone else is having the same problem and of course this thread is right at the top of the list! As stated, there is a workaround, which is to load the default F-22 first and then load the PMDG 747. I'm okay with that until PMDG/Lockheed Martin can get this sorted...4.2 was just released so let's give them some time.

Yes it's happening to everyone right now...it's a shame too because I just got P3D and the AI traffic with RealTraffic + PSXSeecon working great and now I kind of miss it.

Exactly how am I to edit them? What changes do I need to make? The AI_Liveries.txt format is quite straightforward and easy to figure out. VMRGenerator only tells me that a specific aircraft.cfg has an invalid aircraft code. There is no guidance as to what I should change in the aircraft.cfg so that VMRGenerator will be happy with it.

For Prepar3D v4 users you might want to consider using the AI models from MyTraffic as they are known to work and supported in P3D v4. When combined with some work in editing the AI_liveries.txt, I have been able to obtain 90% model matching at the airports I fly out of.

No, with DL off the F-22 nose landing light does light up the ground in front of the aircraft, but of course illuminates nothing else. It just looks like what we would see in P3D and FSX versions before DL ever existed in the platform.

Yes it does, I just tested it. Feel free to try it out for yourself. They are not extremely bright but the DL does work on the default F-22.

But it is possible...the default F-22 for example. The landing light will illuminate the ground with DL either on or off. With DL off, it clearly looks like what we would see in P3D v3 and earlier, even back to FSX. There is a difference between "it's not possible for us to implement when operating within the constraints of our current development staff and without having to add a bunch more code" and "it's not possible because the platform doesn't allow it". I can understand PMDG's position though if the real reason is the former.

Not enough information to really make anything other than an educated guess. If you're familiar with Windows debugging and can get a crash dump and stack back trace, you could post that and it would show what code is really executing at the time of the crash.

DL is a Prepar3D feature, it's something that PMDG chose to use. Correct me if I'm wrong and point out the post where PMDG stated otherwise, but they chose to use the DL feature in Prepar3D and haven't stated that there is any other workaround. So it's either LM did not provide an alternative in this situation (either use DL or your lights don't illuminate the ground) or PMDG chose to not allow their aircraft to fallback to any other lighting method. If a fix is going to come it has to come from one or the other. I'm not trying to blame anyone, but one of them has to change. It sure does seem that the fix should come from PMDG but I haven't seen any indication that they are going to do that.

If anything, I would hope a reasonable compromise can be found and implemented by LM where you can disable DL yet still have your lights illuminating the ground.

My advice? Move to Prepar3D v4 where soon all of those aircraft will be available. FSX is essentially a dead platform now that both LM and Dovetail games have released 64-bit sims based on the older FSX code. If you can live without PMDG aircraft you can also try AeroFly 2 and XP11, although PMDG is developing aircraft for XPlane now.

They've released the entire FTX Global range with the exception of Vector as they are waiting on some 64-bit code from a third party. Any of the airports that use objectflow are also not officially supported yet, but the majority of ORBX products are officially supported for Prepar3d v4.