AbortedMan

Monitor size is not the issue. You can have a 1920x1080 24 inch monitor and a 3840×2160 24 inch monitor and they will both require different FOV to look natural. FOV and zoom is not "basically" the same...it is the same. Limiting FOV is just not feasible. If you limit it enough to get rid of simulating binoculars, but give it enough range that each resolution can still look natural, one resolution, 1920x1080 and lower, will still have zoom while 3840x2160 will not. People should find another scapegoat for being shot down/losing because blaming FOV zoom isn't cutting it.

There already are options for server owners to limit minimum and maximum FOV to the point of no zoom (and conversely no fisheye-lens-wide FOV). No servers limit FOV because it's not feasible and no one likes it. This is a video game simulating what is seen with the naked eye...monitors and modern graphics do not, can not, currently represent what a human eye can perceive. Changing FOV is a workaround for this. ...also, not everyone is running at the same resolution, so limiting FOV to a small range will ruin the experience for one side of the resolution spectrum (triple screen users cannot play at the same FOV as single screen users).

This was an issue with the Viggen when I would run the beta build and the server was using the stable build. Make sure you're on stable if you're not already.

THE BLUE FLAG THREAD HAS DECLARED: Your opinion is incorrect. THE BLUE FLAG THREAD HAS SPOKEN!

@Ciribob just...just give everyone everything so they can all stfu and we can go back to using this thread for information about the server and mission updates without having to sift through pages of this muck.

Blue Flag is up not even a full day and the usual suspects are already at it again.

Also, if you have 2 anti-vehicle (MJ2, I think) BK90s only one will launch and the other will be stuck on the rail. 2x MJ1 and 2x mixed launch just fine.

Any progress on this lately? Is a release imminent?

Seconded...but our current situation begs the questions, "why are all the other popular servers alive and well while BF is red X'd and inop? Is this ED's issue or something on the client's end?" I'm assuming BF is down because popping open the hood of BF specific script functions to find the cause of the crashes is a huuuuge time and expertise commitment, which is understandable. I think it's time to start being realistic about what the next steps are to get BF going again, and that those steps are probably not going to come in an upcoming 1.5 patch.

Does this get read/updated in real time? Can I make a flight plan in cockpit and then send this to a wingman so he has the identical cartridge during an MP mission?

Is the server actually in Israel?

As implied by Matt Wagner in the latest Q&A with Sidestrafe (linked on DCS' Facebook) trees in 1.5 currently have no LOS capability. He stated trees being a factor for LOS is only in 2.0.

This is great info, thank you. I guess this explains why I was getting NAV SYS errors on the Blue Flag server when taking off from road FARPs with no known runway heading. What I get from this is that you don't have to do anything if you see a discrepancy between your ADI heading and actual heading (as per the F10 map) and that it will correct itself upon takeoff. Please correct if wrong.

Hmm...I'm very curious about this. Which is the correct way to be sure the targeting system is accurate?

If you have that much of an issue with it then don't play. There's nothing else you can do about it at this point.

To assume that no one in an online game is cheating is ignorant. There are cheats in every single online game. Banning the use of texture mods to curb the cheaters is silly though and not the right way to handle the issue since anyone cheating is going to be using other critical advantages that have nothing to do with the color of the ground.

Same reason I bought the Viggen as well. Was very saddened to see the state of it's main attraction.

I can't stress enough how critical it is that the BK90 implementation needs to be revised in both SP and MP.

This is great! Maybe spend a few minutes on the BK90 in MP now?...eh?...ehhhhh? ;)

Don't trigger zones themselves take just as many resources as ray tracing actions?

Does it fix the issue or is it that Ciribob turned off integrity check on the server?

Any terrain texture pack adds more detail and noise to the ground and actually makes it more difficult to spot things against the ground. Which texture mod do you know of that gives an advantage when spotting a plane over a forest??

...So there aren't any Viggen fixes in this patch I'm downloading right now or there are?

It's not up to me or about what I think is beneficial. I'm just stating what I have perceived as the common consensus as a cause/solution to the spawning-in-pause problem.

I think the common belief is that the server machine having to load the models for the first time during the mission is what is causing the pause...not individual player machines having to load the models.