PawlaczGMD

The AI is not using the full realistic flight model. I don't have much experience with the AI F-16, but some AI types blatantly outperform. AI should not be used as an indicator of what numbers you, the player, can pull off.

I don't remember this mission, but it might be the case. You can change coords format in HSI->A/C-> something in the lower right corner?. However for close targets, it is good to verify the coords with your tpod, and refine the target. It is a wrong choice to do it via PP in this mission. I would recommend entering coords into a mark point, designating it for the tpod, finding the bunker visually, designating it, and using the bomb in TOO with the tpod. This really should work for you!

Yes, targets in front of clouds are very easily spotted.

Set EFUZE to INST (or in case of bunkers, try delay). BTW you need this for most weapons, first thing when you fence in, set mechanical and/or efuzes as needed. If you're not quite hitting, make sure you're using precise coords (with decimal points) in the right format. Height of drop should not matter as long as you're in range. A range cone will show on your HSI, and IN ZONE on the HUD should be flashing. If you're not IN ZONE, instead you will see a TMR counting down to when you're in range.

Interesting. Does the DCS burble depend on factors such as wind, carrier speed, or is it random, or constant?

Same impressions. Coming from the F-14, the F-18 burble seems to be extremely strong. I barely noticed it on the F-14, but here, I experience exactly the float and pitch. I mostly catch the wire anyway, but it feels relatively overmodelled.

OK, I managed to get it eventually. I think I was missing one of the VR recenters somewhere, I had it bound to joystick, but not keyboard. Rebinding it to another key fixed it.

Probably almost as much as developing them FF. The flight model would still have to be to the same standard as FF. FC3 aircraft have flight models on par with FF modules. It would not be acceptable to have a G6 with a K4 flight model, and it would defeat the point. They would only save some work on not making clickable cockpits, but a lot of the cockpit could be copied from the existing version, so it's probably not that much work, and would not justify making it simplified. Might just as well make it FF. A better idea would be to think about releasing them as a paid variant addon to the existing base model, like if you own the K4, you can add the G6 for $10 or $15. This might make financial sense for ED if significant amount of work can be directly copied from the base model. I'm not sure if it can with their dev process.

Negative, no matter what I do, num5 always centers the view. I've tried unassigning all bindings to do with view, and also assigning them to something else, nothing works.

This, the concept doesn't make much sense for warbirds. FC3 flight models are on par with full fidelity, as they should be in DCS, it is just the cockpit instruments/functions that are simplified, and buttons not clickable. There is almost nothing to simplify with the warbirds. I'm all for more warbirds, but if they develop them FC-style, it would be pretty much the same amount of work as full fidelity, so why not just do that? Because of such reasons, I also suspect that developing low fidelity modules at the price point of FC3 is not financially viable for ED.

Yeah, I know it is not centered by a fraction of a percent. I know how to fix it, I don't want a deadzone though, as it makes flying less precise. I think it is incorrect that such a small input prevents AP from engaging. I want ED to reconsider this behavior.

lol I think we bought on the same day. faulty batch?

I wonder if this is unique to the Hornet. I don't have the F-16 or 15, but if someone here does, it would be useful to see if their AP behaves the same. I agree with your point on how it should work. I cannot imagine the real plane will refuse to engage ACL because your hand is on the stick.

I think you problem might be different. We don't get the windows chime or a disconnect event in game or software, it just stops responding. It's also happening on both throttle and stick. Given this, it might be a hardware issue with wiring, or inadequate power for you. Looks like two separate issues. I'm pretty sure ours is to do with the USB protocol/firmware. Can you update me on how it went? I have one more week to escalate, I will probably do so and ask for 50% refund and keep the items. I cannot be bothered to return it and buy a new hotas rn.

Not to be that guy, and I don't disagree with anything else you've said, but a balanced neutral merge is the absolute worst scenario for unskilled players to score easy kills. Easy kills are scored by ambush, or joining a fight as the third party, etc.

Exactly, it is not just narrow, I think it is literally zero for some AP modes. I cannot engage ACL without a deadzone no matter what I do. This cannot be realistic, it's very dangerous. The allowed deflection to engage should probably be similar to the deflection that auto disengages the AP.

Same issue as here: It is caused by not perfectly centered stick, but we think this should be looked at, as there is zero allowance for stick deflection. Doesn't seem correct/realistic.

Are you sure you don't have a deadzone? I never had it in game, but my WW stick has its own software deadzone, that you can edit in WW software. The default was non-zero, I edited it to zero. Might be a similar story for Virpil.

This mission is evil. The sam launches just as I am doing a 3rd low pass. I was off burner and flared fast, still killed. It's a scripted sam launch up the tailpipe, at zero altitude and short range. Pure RNG if you live or not after doing another task for an hour.

Yes from me, I often hear the AP warning and beep just in that way! Also can you guys check this: Engage just BALT, and trim ailerons left or right. For me with AP on, it treats the trim input kind of like roll input - it will bank, but then stop banking when I let go of the trim hat. It doesn't permanently trim in AP. Trim works just fine for me outside of AP. Very weird behavior.

That might be it, I will check. I managed to remove mapping for a general padlock view bind, and that stopped num5 recentering the view in the main menu. However, it still recenters in F-18.

I double checked, everything to do with center or num5 is unbound there, it still works as recenter

Do you mean PP? In TOO, you update it exactly as you've described. As long as you have the JDAM selected.

It works just fine as UFC button 5 in the F-18. But it also recenters the view!

I've tried to remove it everywhere in controls, but num5 still centers my view in VR. I don't want this, as I'm using the num keypad for UFC inputs. Is this hardcoded, or am I missing something? I've unbound it in UI layer, and the aircraft. Still works as a recenter, both in game and in menu.