Crashdown2

Yes they do

While playing on a multiplayer server on the Syria map, frame rate drops unexpectedly. Last night I was stuck on a CPU bound thread at average fps of 22. Exited when mission was done and fired up single player mission in Syria, and MT worked as expected, producing 120 to 145 fps. As a side note, in NTTR certain areas of the airfield are CPU bound, especially the open air covers, while everything else is GPU bound. Rest of map is GPU.

Chuck's guide is currently wrong. The Hornet radar used to turn off while jamming was on, but no longer, at least in TWS. I haven't seen much degradation in missile performance with jamming on, however I'm not sure how to quantify it, or measure it in the heat of combat.

On the control page, you are no longer able to cycle through AIR, GND, and GND DLY for the GBU 38 as of last update.

I noticed that there are two trim command sets, one for the stick and one for the wheel on the left panel. I have the trim hat set on the hotas and the trim wheel is left alone on the keyboard commands, however when I used the trim hat, the wheel moves as well, even though it's not assigned to it. Is this normal? Could this be our trimming problems?

All of the answers above, snarky or otherwise are correct, however the question was more simple. It does seem strange, since there are no forward firing weapons directly behind the front gear, but you kind of have to take into account maneuvering and the possibility that a weapon could smack into the gear. I do agree that doors off gear up would not necessitate the disabling of weapons, but if the bird only knows what it's told, and what it's told is limited, it's better to be safe than sorry. I run into this problem from time to time because the buttons on the throttle I have assigned to the gear don't work all of the time, (I disabled most of the keyboard stuff due to a chat issue that caused me to screw up a bunch of other stuff once on a paired mission) so I get it. It isn't always about "flying correctly", though it's important, even in the sim, there are times when things don't go as you expect, and by the time you notice, it can be too late to correct.

Simply by flying around, and then engaging targets A/G with gun and slick bombs. Right on target. Stored heading will give you the headache of missing all the time and falling back on manual mode. I think it is the stored heading option of alignment that is bugged, not quite the INS itself. However I don't code and don't have access to it, but stands to reason that if full alignment works and stored heading doesn't....

Just got home and tested it. Doing full alignment does not show drift or INS "mismatch". Stored heading will. So if you like to go without the GPS correction, then you'll have to put in the 8min 53sec worth of waiting for alignment.

I did say rarely as well with this, but sometimes I get lucky on hot starts. Keep in mind, the long alignment worked once so far. I don't have the patience to wait that long all the time :). Anyway, I am going to try it again when I get home. Make sure it wasn't a fluke.

Oddly enough, I messed up alignment with stored heading, and waited the nearly 9 minutes for alignment, and the issue wasn't there. I've also noted that servers or missions with hot starts don't have this issue either, or rarely. Wonder if it's tied to the stored heading.

When target is designated with ATFLIR, the waypoint moves along with the ground stabilized tracking, diamond can be erratic. This is different than how it used to behave. Set waypoint, designate as target, switch to ground stabilized, pan around. Need to go back? Then check waypoint and then designate as target or go back to diamond, ATFLIR slews back to original waypoint. Now where ever you move the the ground stabilized designator, the waypoint follows, and is updated in the data page on the HSI. Track included here https://drive.google.com/file/d/1P2KM7TnJppN36sO0np3UdHgW6_K9acrV/view?usp=sharing since file is too large to upload here. F/A-18 portion is first and shows the issue.

Just tried, thanks. I must have missed that somewhere.

It's called Memory Cleaner https://www.koshyjohn.com/software/memclean/

I just realized that I had the two bombs messed up... The GBU 31 works fine the GBU 38 does not. Maybe @NineLine can change the title. I'll make a vid.

Never had to before, just made sure FLIR was the source and it would normally update live as I slewed the TGP, which is why I like the ATFLIR more. GBU 38 still works this way. I used to be able to fly to a target zone, point at a target, drop, slew, drop, slew and so on and get all targets (or within reasonable error) but not any more.

Sorry, have not seen the notification on the reply...I have had multiple crashes before and sent the crash dump to ED each time, I hope this helps. Since I got a tool to trim memory, after the trim I can run Syria within 9GB, which is amazing.

When using GBU 31 on the Hornet in TOO mode, the MSN page of the JDAM doesn't reflect coords on ATFLIR. This problem seems to be recent, as it did work before. Other GBUs work as intended, only the 500 pounders are affected. Work around seems to be to set up markpoints and use weapon designate. This process is slow when compared to just using TGP.

Just tried it, great tool. Thanks.

Just as a note, I've noticed all maps filling memory. I watched the system monitor while on Persian Gulf and memory just kept filling at a rate of 100MB/sec. Things start to stutter pretty bad, and they never used to before this last open beta release. I thought it strange since the Persian Gulf isn't very taxing on resources. Ran a repair and that didn't work either.

The second image you showed is what happens to me, however I don't have any issues with A/G mode. Since I can't see how you are aligning the HMD, all I can say is, try to keep your head centered while pushing the align button on the DDI when done with alignment. I wonder if you are turning your head to the right DDI and it somehow ruins the centering. I know it's a far off guess, but it's the only thing I have at this point.

I have the same issue from time to time, but I look away and then look back a couple of times and it straightens out. I also notice looking at something for a while it will trail and then update and be on target. I agree, this is annoying when looking for the target in the circle, but the aircraft is somewhere offset, so I can never tell exactly what I am looking at, whether it be my target, another opposing aircraft in the same general area or a friendly that is sitting outside of the circle and then the circle snaps over the aircraft. Sometimes it is too late, especially when waiting on and confirming IFF.

I have been practicing with the sparrow lately, and have been noticing in tacview that they rarely reach anywhere above mach 2, however looking around, the AIM-7 C/E/F/M-P and RIM-7 M-P have a speed of mach 4. The F and above variants have a range of 38 miles, but you rarely get the NIRD circle to display max range unless within 27 or 28 miles. MiGs with the P77 will out-range at 50miles and have a speed of mach 4, and this coincides with the tacview data. Anyone else notice this? Is this due to the loft?

I've found better luck changing the target size to small rather than leaving it medium. Not sure if that's what people are doing. Increased my track and hit rate drastically. Since I found the AIM-7 was designed to primarily shoot down bombers, I figured large was for them, medium was for something like B1 size or around there an slightly smaller, and small for fighters. A lesson I just did said to change the size to small as well. I had always left it medium and the type to 7F rather than changing it to 7M.