Machalot

I flew a strike mission on Hoggit Syria today. The target was a set of four fuel storage tanks, large black cylinders against a gray concrete background. When I arrived at the target area, the missile seekers simply would not lock onto the tanks, so I couldn't fire the missiles. I tested and was able to successfully lock onto and fire at other nearby targets, so it's not a procedural or configuration problem. The track file is 63 MB so I can't upload it to this forum. If HB reads this and wants the track, I will find a place to upload it and share the link.

Would you mind editing your post to remove the link in my comment you quoted? I am getting people who click the link in your comment and request access to my Google drive, rather than downloading the Excel file from my edited comment. Thanks!

Why do you find the need to trim just before turning on the autopilot?

You're welcome. I have edited my previous post to the remove the link, and unshared the Google Sheet, because I discovered that it reveals my real name. I have replaced it with an Excel version uploaded to my previous post.

Sea based oil platforms are invisible to radar and anti-ship missiles.

Here's an very simple spreadsheet with the formulas for conversion. No special formatting or protection, so be careful editing it. You just input whatever format you have in the relevant input box, and it produces the other two formats. Edit: I just realized the shared Google doc reveals my real name and there's no way to hide it, so I have converted it to an Excel file and uploaded it here. DMS Calculator.xlsx

You can do the conversions using native functions in Excel and, I presume, Google docs spreadsheets. I would be happy to set it up for you.

I think the key bind is LAlt+Y to switch coordinate formats on the F10 map. Not exactly what you asked for but it should help with finding and setting waypoints.

Could also be a sticky mouse button. Under certain conditions the game will not detect the release of the mouse button when you're done turning the brightness knob up. Any subsequent mouse movement will continue to move the dial even if you don't click and hold. The most common cause I've seen for this is to open the Comms menu (including if the Comms menu is opened automatically by an ATC call) while you're turning the HUD brightness dial with the mouse. If my memory is correct, this can be fixed by releasing the mouse button, then cycling the Comms menu on and off.

I agree. The anti-ship mission is really valuable on PGAW. I have only played SAW once, but I liked not getting smoked by MiG-31s and Fox 3s.

I have seen a number of new Viggen pilots on the Hoggit servers since the 2.7 patch. And the other day there were 4 Viggens on AO at the same time.

Maybe it's in the lua files somewhere?

Cool, so like a covariance analysis?

Are you working on a tool to map the results with uncertainty included?

You're referring to the last sentence, "regardless of the current waypoint", as the part that is not working as written?

I take it your use of "apparently" is sarcastic.

It's your choice how much effort to put in, but I think now is probably the best time to bring these to HB's attention while they have the Viggen as their top priority.

That is bizarre. If I understand it right they are modeling ultra-rich combustion at high altitude. Seems worthy of a bug report.

Are these documented in bug threads? I haven't heard of some of them.

You may be exceeding the friction limit on the tires. If you apply less thrust does it still under steer? I have experienced what you're showing, but at lower thrust and lower speed I am able to control the jet quite precisely with high gain NWS.

They were trying for 2.7 but it turned out to be too much. They said it will be in one of the upcoming patches.

They said they have the Viggen as top priority until it's out of Early Access sometime soon.

Sounds plausible. There are theoretically ideal area ratios for converging-diverging nozzles, but material thermal limits probably constrain the practical nozzle schedule.

You must have an axis bound to radar elevation that is slewing it to the limit. This also explains the TGP zoom issue. Check your axis bindings.

If you are choosing not to use the keyboard for immersion, that's up to you. But I also fly in VR, and I have no trouble using the right half of the keyboard by feel: arrow keys, the insert-home-pageup-delete-end-pagedown 6-pack, and the number pad. You could map throttle idle to a key combo that's easy to find by touch.