njoyyoursalad

This is a must-have mod for any Kiowa pilot! Thank you × 1000

After reading "shoot it straight down the throat" I have a mental image of the AGM-45 that is now permanently burned into my memory. But jokes aside, thanks for the guide, this is very helpful. One question though, shouldn't the chart for the Mark 49 mod 0 and mod 1 have the SA-8 checked? Both of those seekers work on it. I think those two seekers also work on SA-6 but I have not personally confirmed that.

Sending all the love, good vibes, and highest praise to you @Massun92! Your wonderful asset pack is game changer now that it's being integrated into the core game! I am so delighted to see all your AAA-quality assets available to everyone in the multiplayer environment. What a treat for all of us—and especially for us helo pilots who spend most of our time near the ground and around FARPs! The scenery at road bases, FARPs and FOBs will never be the same again! I truly hope your partnership with ED will develop further. You're both making a lot dreams come true and I'm very grateful for it.

You've shown a Pakistani variant. Refer you back to 2022 response: In-game texture is based on Pakistani variant but the aircraft being modelled is based on the one described in the Chinese manual which uses a different arrangement. Changing the texture probably wouldn't be a bad idea but other than a minor visual discrepancy I see nothing wrong here.

Yes, the green values represent min/max FOV figures. If you change 140 to something like 100 then your FOV will only expand to a maximum of 100°. It doesn't work on all aircraft though so I'm hoping that someone with a bit more knowledge will chime in with a way to cover all aircraft. As for Server.lua, you can copy that out of your ..\Eagle Dynamics\DCS World OpenBeta\Config\View\ directory, paste it into ..\Saved Games\DCS.openbeta\Config\View\ and then simply apply your edit to the copied file.

Editing Server.lua in your ..\Saved Games\DCS.openbeta\Config\View\ directory will fix at least some aircraft: function default_fighter_player(t) local res = { CameraViewAngleLimits = {20.000000,140.000000}, It doesn't work for everything, and it limits your maximum FOV, but I suspect someone probably has a more effective method to use as temporary workaround.

Oh! I'm sorry I misunderstood you. I thought you were suggesting that it was failing the IC test with a red shield. I see now that you mean the server is overriding your configuration. I also have this problem on some servers but it does not affect all servers with pure scripts enabled. As I understand it this is a consequence of mission design whereby the mission designer's view configuration is imposed on all clients. Some servers exclude their view settings and thus we don't suffer with the slow default zoom speeds on those particular servers. Btw this has been a concern on some servers for a few years so perhaps something has recently changed with a server that you frequently use. Best advice is probably to notify the server operator of this and see if they can address it.

Hmm, I don't seem to have this issue on my OB install (which is currently the same build as stable.) Just verified on multiple servers with IC active and pure scripts enabled. My View.lua is modified in a similar manner with CockpitKeyboardZoomAcceleration set to 990.0 versus your 900.0

I also noticed this right after the patch. It's happening on all MP servers running the 2.8.0.32066 patch. nullEasily replicated—simply join any MP server

Just wanted to confirm that Mistrals are indeed working again on the latest 2.7.7.14727 OB, despite the fix not being mentioned in the changelog. Feels good to have some air-to-air capability again! Many thanks

I appreciate your detailed insight and respect your enthusiastic defense of the developer, but this bug affects both the Stable & Beta builds. In such cases where both builds are affected I don't think it's unreasonable to expect some kind of acknowledgement within 10 days, even if it's just a simple statement to inform the community that Polychop are aware of the issue. There's not a lot of daily traffic on Polychop's forum so there should be plenty of visibility for this topic, and good customer relations costs nothing. That said, I'd love to add a track to the other thread but the tracks I have are far too large to share. Fortunately, this is an easy bug to reproduce—it's as simple as joining an MP server and attempting to fire some Mistrals at air targets. There's also a video on the other thread which illustrates the nature of the bug very clearly. I'll continue to check both threads in case there's anything I can add to help resolve this. Thanks in advance to all concerned.

Ding, ding! Is anyone home at @Polychop Simulations...? This thread has been up for 10 days and there's still no indication of the developer taking note of this bug. Seems like a long time to remain silent on an issue which is present in both the Open Beta & Stable builds.

I'm also seeing this bug on my end with version 2.7.6.13436 OB. There are plenty of other reports about this on these forums and elsewhere. Here's another thread started 10 days ago about this same bug:

Having the same problem here. I only play MP and this is where the bug manifests itself quite clearly. Interestingly, if I play an MP mission on Caucasus set to winter with low ambient temperature I am able to get some working locks and successful tracks with the Mistral. But on Spring, Summer, and Autumn with higher ambient temperatures it is basically impossible to get a lock. I'm really hoping for a quick fix for this. I actually started a trial on the Gazelle last week and had every intention of buying this module until I realized that the weapon I wanted to use most of all is not working properly. Initially I thought it was just the temperamental nature of the missile, but after a few days it became clear that it's not working as it should. Let's hope this is resolved sooner rather than later. I'd really like to add this module to my hangar.

Please don't ruin the last guided weapon for this module which doesn't get intercepted by literally everything—including several systems which shouldn't even be capable of tracking some of these weapons, let alone zapping them from Rmax. It's bad enough that we have antiquated systems like Hawks accurately sniping a single GB-6 from ~20 nmi even when the weapon isn't headed for a target anywhere near the SAMs. This is why so many people use the 802AKG now, because all the other guided weapons available on the JF-17 have jumbo jet-sized RCS's which are significantly larger than they should be.