BuLLeT.ZA

You don't specify which keybinds you used to bring up the radio. In the F15E you need to bind primary and secondary radio buttons manually as they are not bound to begin with. I made mine the same as the hornet (RALT-\ and RSHIFT-\). You may well be doing this, but I thought I'd suggest it just in case.

Have you tried A1? I think I recall having to swop it around.

Correct. The designation only matters for release purposes, which is what CDES comes in useful for. Then again, I'm having issues with CDES and auto tracking as well.

I'd actually say that she's erring on the side of being too forgiving. The brakes seem too effective. (Not that I'm complaining). As for over-steering it, I'd agree with Nodak.

Not that I don't agree with you, but releasing to a few Youtubers is very different from releasing to the general public. There are still bugs and problems. For instance, the last build that the youtubers got was not multicrew compatible. They just recently sorted out a TGP sync issue as well. The general Youtuber content is there to generate hype, not be guides. I wouldn't rely on any other source than Notso's videos on the official RAZBAM channel prior to release. If they release something with any significant flaws you and I both know they'll get crucified, especially after all these delays. I can't wait to get my hands on it either, but such is life.

The map locations in the PDF briefings and kneeboard are pretty accurate. What I can't find an explanation for anywhere is the "Hard mode" option. I enabled it, but I have no idea what it does.

Well... We're down from "Two Weeks TM" to "Two Days". So hopefully it trends downwards a little faster than that.

That is a great idea, and will certainly add more fuel to the hype fire.

I would love to know the exact same thing.

Just to confirm: HMD alignment was indeed the issue. With the alignment completed the target designation remains where it was placed by the HMD.

That makes sense. I'll check it out, thanks!

Not quite what I'm seeing. I can keep looking at the same spot and the TGT still starts buggering off to the front. By noise, do you mean that setting a deadzone on the TDC might solve it? I had issues with the HMD alignment and haven't bothered with it since. I assume that it should start off decently aligned? I will record a track file this evening. Seems to be constant for me so replication on my side shouldn't be an issue.

Necro time. I'm still seeing the same issue, if not worse. If I use the HMD to designate a spot, then the diamond instantly starts drifting, and rapidly moves to 500+ NM distance. Flicking to FLIR immediately is the way I get around it as well, but it's not ideal.

You were right. It appears that Magnetic is the right one to use. It's not spot on, but it's close enough to identify the ship. Another day another lesson learnt. OAP is a really nice tool to use!

I've never done it before either. I had to look it up after you mentioned it, but it seems really useful! Giving it a go now.

Just wasted an hour with the same experience as you. Finished the 1v1, climbed with Prince to 28k while he's zigging and zagging all over the show. Once at 28k he orbited WP3 until he ran out of fuel and ejected. Now that you mention it, he was marked red on the radar the whole time.

Different issue, but also Mission 5. Finished the 1v1 with Prince, after which he announced the climb to 28k. During the climb he zigzagged like a madman, and once at 28k we circled WP3 until he ran out of fuel and ejected.

Flew this one yesterday. Just plotted the range and bearing from Rock on the F10 map, which was accurate enough. I found the Tabletop without issue. From what you're saying it sounds like Rock's waypoint coordinates might be incorrect. I'll test using OAP later. Bearing should be True.

I understood "Wizards" to be a pre-set Initial point. Presumably the AO has many of these points, and the JTAC can choose the most suitable one as a common point of reference for him and the aircraft. Here is some reference to the Initial Point being a clearly defined feature or electronic marker. https://www.globalsecurity.org/military/library/report/call/call_95-10_c4_fwfii.htm#:~:text=that CAS will attack.,the IP to the target.

Could the same thing be affecting AEW/AWACS? I can't talk to Magic in Mission 2, and Smoke goes AWOL after cutting East.

I'm so happy to see this post. I've literally been tearing my hair out at this. I've now flown this mission four times, one of which Smoke flew into and blew up the tanker, the other three he cuts away as planned, then promptly runs home afterwards. Radios set as briefed. Anchored at WP4. I love these detailed missions, but it's incredibly frustrating committing to a long mission when it's broken for whatever reason. Is it even worth trying the rest?

Same issue here. SP. TTI Persian Gulf. Radar is completely useless after locking a target, and simply freezes in place. Will try it out on other missions/modes.

Any chance they'll hotfix this? Or will it simply be left as is?

I meant the current state of the game where you can't prep it during preflight.

It's one of my largest pet peeves.