hein22

Don't pay attention to those kids. This community is the most toxic one you will ever find, much has to do with how they are treated by the developers. I find your insights quite spot on in fact.

I wish I can, aspen. Welcome to the forums.

There are dozens of things you guys see in the DCS Hornet that are not the way the real thing works. Some are due to incomplete systems modeling and will make much more sense later in early access (like tons of HOTAS commands), some others are due to ED's misinterpretation of documents that were later corrected after a user pointed it out (JDAM logic, TGP features, etc). I strongly suspect that the whole sensors + TGT logic is wrong and that ED needs to re read the available docs. There is no way any airforce would pay more than 10 dollars to have the systems logic that the DCS Hornet has, no one would have approved that.

Didn't even read the OP before tagging. Now let's hope someone sees this thread.

I didn't really catch anything of that. Can you elaborate for me please?

Exactly! Just out of curiosity: how does an INS discover latitude and why cannot it do the same with longitude? THanks.

Nice to see the investigating tag. Look forward to seeing comments from ED. Thanks.

It never improved, high ageing setting always generated trails since day 1.

By the way, I think I wasn't clear before but the issue is still present.

This is already reported. The whole LTWS MSI thing has been broken for a year now with many bugs going on. Don't get your hopes up. https://forums.eagle.ru/showthread.php?t=267824&page=2 https://forums.eagle.ru/showthread.php?t=258337 https://forums.eagle.ru/showthread.php?t=270285 https://forums.eagle.ru/showthread.php?p=4264017#post4264017

+1

INS aligns with waypoint 0, just like Santi explained in the sticky. If you move from that waypoint then the INS would not know where you are and would align incorrectly. But in DCS it is all magically done.

No, the INS aligns on its own, once IFA is selected then the GPS keeps the INS aligned. If you align with IFA then the alignment is done with GPS. But what I am describing is about GND.

So as the title says, the new INS implementation appears to be either bugged or not simulated at all. I started cold and dark and without touching the INS knob I moved the plane quite a lot to a different position. Then I did a GND alignment and it knew exactly the new coordinates of my plane and aligned perfectly. If I had put the knob in IFA then GPS alignment would have started and it would have made sense, but in GND the alignment should not have known my new position. Track attached. ins new implementation wrong.trk

Who marked this as correct as is?? Quite rude tagging without reading OP.

Maybe all of this isn't simulated yet? Implemented, yes, but not simulated I guess. I started cold and dark and without touching the INS knob I moved the plane quite a lot to a different position. Then I did a GND alignment and it knew exactly the new coordinates of my plane and aligned perfectly. So this appears to be hardcoded as of now.

huh?

This comment was overlooked, and all the issues presented here are making the simulation quite arcade IMHO, I really hope ED has the knowledge to sort this out. The main issues here are that the missile guides magically to the real target's position despite it not having any link to any source. Even worse the Age setting is acting like a trackfile memory which are two different animals, and this "memory" state is making the missile to guide to the real position instead of the position that the memory is "remembering".

Bignewy, hi. You replied to me in the thread that was closed so I can only answer here. First of all, no, I didn't try in MP. If you play the track I attached in the original thread you will see the bug. Second, how is this a user error? Thanks.

So I've been away from DCS for months now and jusst came back to see that this bug is still around! Track attached in this thread https://forums.eagle.ru/showthread.php?t=277959

So they fixed the ICLS stabilization issue but the IFLOS bug is still present.

So as of today's OB update changelog it shows fixed and it appears to be fixed in game.

I am too. Many bugs are shown as fixed for months, even years, and never get actually fixed.

You couldn't? I don't understand, the issue is there, doesn't seem to be dependent on the PC but DCS.

Please please fix this!