Zomba

The last few nights playing in GaW MP server I noticed when using JHMCS in the merge the 9X field of regard was limited to 30 degrees or so instead of the usual ~80 degrees. Anyone notice this or has something changed I wasn't aware of?

I retested on GaW, 104th and Through The Inferno. Only GaW showed 0-ingame. It indicated normal at first, but after 10 seconds the bug would show. EDIT: Just tried the 104th again and it's getting that bug too.

I'm getting the O ingame bug too. Incoming comms becomes intermittent or muted entirely as a result as well. I there any fix for this, it makes SRS unusable.

Track While Scan (TWS) basically builds a track file of every contact with all the info the system needs to support a weapon to engage that target (AIM-120 etc). In order for this info to be accurate enough to do that the radar has to sweep the target within a certain rate, like one sweep per two seconds just as an example. The radar can only sweep so fast so in order to achieve the minimum rate you either limit the azimuth and/or elevation limits of the search volume. This limits the total volume of airspace you can search, but it gives you good tracks to work with. However track info is very handy for other things beyond supporting a weapon. All sorts of information like heading, altitude, azimuth, range, speed, IFF, type, can all be stored in the track. This is what Latent Track While Scan (LTWS) can give you. You get the benefits of a track file for the contacts (Although not accurate enough for a weapon engagement) without having to limit the total radar search volume as much. LTWS is accessible in the normal Range While Search (RWS) mode.

He said as much in the stream.

I get it every now and again. At least with now I know what the trigger is for it and can try and avoid.

Very cool. It's great that the Mirage is getting some love to push it further along that final stretch.

Anyone having issue with the download failing about half way through? I'm in Australia.

I also noticed when cruising at 55,000 feet ~mach 2 today that FF didn't change appreciably across the AB range from low to high. This must be a somewhat recent change as it didn't used to do that AFAIK.

When we still had the model enlargement system it didn't scale with res and had less than ideal results across different resolutions. I remember someone in the community modded the system so it would scale correctly. It gave much better results, and according to him it was only a few extra lines of code.

Currently no, it's just a visual thing and it makes no difference to the flight model. However this may change in the future.

Just validating the issue with cat failing to initiate with cold conditions. With testing I've found the issue occurs when engine rpm fails to register 99% due to weather conditions and appears the cat trigger looks for mil power based on rpm. However when I exit the mission and bump the temp back up into the positives, save and then launch mission from ME the bug remains even though rpm reaches 99%. The only way to clear it with that mission that I've found is to reload default weather, redo the settings and then test.

Was just about to post a query about this. Noticed last night it behaved like it was pitch rate restricted.

I tried to look, but maybe I'm blind and couldn't find it, but will the new trees affect AI line of sight detection?

Against the backdrop of all the fanfare with the AV-8NA release, thanks to the Razbam team for an awesome update to the Mirage, the flight model improvements are really nice in lower speeds. I'm not sure what the real Mirage's behaviour is, but I find you have be more dynamic with the controls now, the FBW system doesn't dominate in directional authority like it used to, especially on approach and landing rollout. I personally like it like this as it makes it more interesting and fun to fly. Good job!

I wouldn't buy the Mirage at the moment, it's a bit too broken and has been for quite a while now. However it's next update is coming up that should sort most of that out hopefully.

Maybe they should explore the option of removing it from release and putting it back into beta to avoid any exposure to being accused of being misleading.

Kind of surprised no one was able to answer this question.

Just wondering about the reason why Mk.82 cannot be mounted to the center station and yet GBU-12 can in either single or AUF mount. Was it because it was just never certified due to low priority?

It's the question I was more concerned about.

As I understand it the Nimitz is a separate asset that can be purchased which will provide carrier ops for the Hornet. If I host a server whose mission includes a Nimitz, will people that have not purchased the Nimitz asset be able to join the server?

Yeah, you're right. It was an online server and I just checked with them about it and it was set to January.

Fiddling with it a bit and I found that setting the HSI to Cv NAV will give you true values, but any other (NAV,TAC) will give you incorrect readings. Maybe one is true heading and the others are magnetic? I'm not sure what the drift is in that region of the world.

After the 1.5.6 patch I'm having trouble with the alignment as it appears to align -100deg from where it should be. Say, lining up with Batumi airfield at 305deg it will read 206deg. It makes no difference what class of alignment is done. Am I doing something wrong? I've got quite a few hours in the Mirage and don't usuelly have trouble with it, but may have missed something in the update.

Is Lotatc compatible with the latest patch in 1.5? I've been having toruble with it not connecting