streakeagle

In DCS World, IFF generally works perfectly, which negates the need for Combat Tree. In reality, when you used IFF, if you got a response, you pretty much knew for sure you had interrogated a friendly. But if you didn't get a response, that could mean it is an enemy or it could be that the contact's IFF failed to respond for a number of reasons or that your IFF failed to detect the response. So, IFF only gave you one of two IDs: friendly or unknown. But with Combat Tree, if your intel was good, you could interrogate and get an IFF response from the enemy. No friendly could respond to Combat Tree. So, Combat Tree gave you one of two IDs: enemy or unknown. But as far as I can tell, Jester is 100% successful with IFF. If he says it is an enemy, it is, so you don't need Combat Tree to improve your odds of correctly identifying the enemy. Fast forward a few years and you have F-15s using NCTR: an advanced digital signal processor can tell the jet engine type from the frequency modulation of the radar return, much the same way a sonar technician classifies sonar contacts by demodulating their broadband signals to get screw/blade information and reduction gear ratios (I was a submarine sonar tech for 8 years and know all too well what you can do with blade/rate information). Now you don't need to emulate enemy IFF and have intel on his IFF settings. Just like Combat Tree, you either get unknown or positive ID: good enough to shoot.

The whole point is to have the original light ghost gray/dark ghost gray camo that superseded the original air superiority blue. It was the only camo scheme F-15A/F-15C Eagles used until the 1990s. A key point is the color of the canopy rails. They are some sort of metallic red. Many skinners miss this detail when converting to the original scheme. I wish there was an option in the mission editor to turn on "turkey feathers" for the exhaust nozzles. That would match the look of early F-15Cs and allow the F-15C to visually represent the original production F-15As.

That would make a lot of sense. I would really like an F-15A, but a 1980s post MSIP F-15C would be extremely useful for Cold War Germany and a bit more fair to those flying the period appropriate MiG-29A.

I was just attempting to place an A-10A in Spangdahlem using one of the stock SP skins only to discover that I couldn't and discovered others already found and reported this problem

It may have been fixed internally, but it did not make it into today's patch. So, the question is: will there be another small hotfix patch released very soon? Or is this problem here to stay until the next major patch?

Within seconds of starting an instant action mission, Jester is calling out "lost cabin pressure". I have seen others report the same on the Heatblur discord channel's F4 Discussion, including multiplayer, too.

The AIM-7s were very inconsistent. The nose cone could be beige instead of gray or white. The fins could be white (early AIM-7F), but later would be bare metal (the dark gray metallic color that sometimes almost looks black). I saw one photo where the front half had the white body of an AIM-7F, but the back half had the gray body of an AIM-7M.

I see the red-white-blue national insignia as late as 1987 in a group photo and the black outline that replaced it in a group photo from 1988. 1981 was the latest photo I found with the AIM-7 (AIM-7F?) in the gray nose cone/white body/dark gray (or black?) fins color scheme. Whereas I found a 1983 photo with the AIM-7 (AIM-7M?) in the white nose cone/gray body/dark gray fins color scheme. I would love to see the AIM-7s in correct colors for a given era just like the F-14A which has white AIM-7s when you fly 1970s paint schemes.

It would be real nice if the F-15C came with some 1980s 36th TFW Bitburg skins to match the new Cold War Germany map. Skins with overall light ghost gray, with dark ghost gray blotches, red metallic canopy rails, and red-white-blue stars and bars national insignia. There are some great photos of all three Bitburg squadron Eagles, many of them 1970s and 1980s paint schemes that I would love to see in-game: 22 Fighter Squadron – Eagle Country 53 Fighter Squadron – Eagle Country 525 Tactical Fighter Squadron – Eagle Country

I don't know who is right or wrong. I just know it is a loss for many owners/fans of Razbam DCS modules like me if this dispute cannot be resolved in a way acceptable to both parties. I not only want the existing modules I already own to continue to work for years to come but was looking forward to all of the Razbam products that were currently in development. I already got burned on the Hawk/P-40. This time, I will be losing a lot more aircraft/money as I own all of the released Razbam modules. If this doesn't get resolved, I will make sure I don't ever get burned again by not spending another dime on DCS World products despite my love for this sim and my desire for it to be around for many years to come.

Not all mods are causing problems. I have quite a few installed, but only the VSN F-4 was causing crashes. The VSN F-4 already has a hotfix out which has solved the problem, which not only caused crashes on my client, but broke dynamic spawning on aircraft carriers on my VSN servers that host the VSN F-4. None of the other VSN mods I had installed caused me problems. The following worked normally for me: VSN F-100, VSN F-104, VSN F-105, VSN F-106, VSN F-84, VSN F-80, VSN F9F, VSN Mirage III. Besides VSN mods, the following worked fine for me: A-29B, OV-10 Bronco, OH-6 Cayuse, C-130J Hercules, A-4E-C Skyhawk, MiG-25, VNAO T-45 Goshawk.

Do you have any mods installed? One mod in particular is now causing crashes when you join a server that doesn't have that mod: the VSN F-4. None of the other mods I have installed are causing a crash. But the patch changed something to do with the files being accessed by mods, which definitely broke the VSN F-4. If you have mods installed, move them to a temp folder, then try joining multiplayer. If that fixes the problem, put the mods back in one at a time to find out which one is causing the issue. If you don't have mods installed, I have no idea what is causing your problem.

I hope the EC-121 is still being developed.

It was fixed AFAIK. I can now fly the F-5E in multiplayer at full FPS enjoying the new liveries. This issue is listed as "fixed" in the F-5E forum for bugs. I don't know why they didn't spell that out in the patch announcement.

I have a small update: I am only seeing the FPS problem in multiplayer. I flew the same instant action mission as yesterday (air-to-air in Sinai) and now have FPS comparable to the F-4E. But when I spawn in a multiplayer mission, the frame rates start out insanely low, then once the textures are loaded, the frame rate is about 30 fps compared to my normal 73 fps. I haven't flow around other people in F-5s, so I can't say whether non-player F-5s affect frame rate.

Cleared my cache. No difference. My FPS are twice as good or better in the F-4E.

I just came here to see if I was the only one with this problem. Apparently not. I am getting less than half the FPS I get in the F-4E. I am guessing that something got broken when they added new effects and/or fixed the hatches opening/closing.

Which force feeback stick did you choose? Never mind. I see your other posts about Moza.

I recently observed the same thing. Same mission works when hosted locally as multiplayer, but not on a dedicated server.

The radio menu is working correctly when I host the multiplayer mission on an actual client/game installation. But, when joining the same mission hosted on a dedicated server, the radio menu is broken. Something is going on with the dedicated server.

Came here to confirm I am not alone and found... I am not alone. AWACS menu in multiplayer is still somewhat bonkers, too. But sometimes some of them show up correctly and respond to player requests.

I just realized that this is happening. I have been using EWR as AWACS GCI for public server missions for years and had no problem. But now, the AWACS menu may or may no show their correct call sign but always defaults to 124 MHz. I have not found a work around.

I have observed the same behavior.

I went back to 4K, no problem. I went back to GUI scaling = 2, problem returns.

I changed the resolution to 1080p and checked the "full screen" option. Then I set the gui scaling to 1. Now everything looks normal. I am going to experiment with the resolution/gui scaling/full screen option to see what triggers the problem.