Jammer.

Oh ok, great! Thank you!

Thanks, but I already know. I wanted to have a status update on it.

Hello and thank you Heatblur for the amazing work you did on the F-14. I have some questions concerning carriers. I remember early in the development of the Tomcat, you made deck crew character models, and even showed some mocap. Will the Forrestal carriers have any animated crew, or is that plan scrapped since ED is doing that for the Super Carrier? Speaking of which, I noticed in the DCS patch notes a while ago, added features like "salute", "holdback bar" and such. Does that mean that you did your part on making the Tomcat compatible with the SC and that the rest is up to ED to finalize the implementation? Hope you don't mind the questions, thank you.

Theme sounds have been restored to all my modules, except for Normandy map.

Same for me. Error occurs on combat missions. I don't know if it's a coincidence but I started getting this issue after I installed the Flanker on the F-15 vs Su27 free weekend like 2 weeks ago.

I have the same issue. It happened to me quite recently, like 2 weeks ago, for the Flanker free weekend.

Interesting interview with Ian Black. Some quotes: "The Mirage 2000 is probably the ultimate fighter pilot's airplane." ".. you could do anything with it you wanted, you can point it in any direction and it would just keep flying." ".. and it was pretty foolproof really, you couldn't stall it as such, if you span the airplane you flicked the switch and it would come out of the spin. And you could pull 9.5Gs all day long." That sounds exactly like the Mirage 2000 I've read in books, seen on videos, doing all kind of maneuvers at airshows or else. We all know how agile, nimble and very capable the Mirage 2000 is IRL. Unfortunately, this isn't currently reflected in the module. I see that I'm not the only one to think that the Mirage isn't behaving properly. I have to admit that I felt reluctant to post in this thread. Concerns about the FM/performance being off have been raised before, but since no updates have been released for a good while, and obviously some people happy with it, or maybe just wanting to keep things the way they are, I felt that any complaints wouldn't make any difference. But I'm glad this thread came up. Being open and exposing the faults (while avoiding personal attacks) should lead into something positive. And since the issues will be addressed and prioritized for the module, it gives me hopes again. We'll see what happens. I've actually stopped flying it for some time now, as it's just not enjoyable to me. And I guess, as someone mentioned, it is a bit worrying that the Mirage is at this state so far after release, but it is what it is. The good part is that Razbam has good communication with us and that they have acknowledged the problem. CptSmiley gave us direct answers, and is working on it, so all I can say is that I look forward to the upcoming FM updates.

That's correct, it's not solved yet.

Hi Olivier! I guess you recognized your skins, nice job on the liveries. :) I was just having them as examples to highlight the lack of specularity in the numbering material. So disabling the spec maps doesn't solve the issue, but make it a bit less apparent I guess. What is needed is for the dynamic numbering to have specularity so that it matches the rest of the airframe's material, only then can the area around the numbers be truly transparent. Zeus said he'll let the texturer know, so hopefully it will be fixed. I just read some other parts of the plane didn't have spec maps either. I guess some of the materials need to be looked at.

I have no idea what font is used, but it seems to be different for the letters and numbers. You can check the files: M2KC_N1 and N2 in the liveries folders, you'll see how they look there.

Thank you very much! I find it rather important, so let's hope he can find the time. :)

I haven't received any reply on my previous request, if the devs or anyone involved could please let me know? My question in short: Could you add specularity on the numbering material? Would it be possible for you to look into it? Thank you.

In the mission editor, you type it in the "TAIL #" box. So on a french squadron you can change the last letter and the plane's number which you see on the tail. As an example for the 2/5 "Ile-de-France" squadron you will have on the nose "115-Lx" and a tail number "nnn". So if you type in the box "LA-123" you will get as result: 115-LA and 123 as tail number. You can also type AAA123 as recommended in the first post. You can just type and experiment for different liveries to have the results you're looking for. If you already knew that and wanted to have dynamic numbering on user-made liveries which don't have it, then it's more complicated because you need to have the texture match the placement of the numbering. If you don't know what I'm talking about you can just disregard this. :) I still hope this helps.

Maybe I wasn't clear before. So here are pictures to illustrate the issue. User made liveries: Default liveries: User made liveries: Default liveries: As you can see on a skin with a specific specular map, the polygons assigned to the dynamic numbering are really visible. You can see it on default liveries too, but it's more subtle. But I guess this is beyond our control. So could the devs please implement specular attributes to the material on the dynamic numbering polygons? That way, a specular map can be linked, and match the rest of the airframe's material. Thank you.

Yes I already know, thanks. I just used < and > as an example in the same way as previously in this thread. You obviously replace that and everything in between with the relevant filename.