hein22

I'm not surprised, I've seen them. But I don't agree, xd. The type of bugs that military aircraft have has nothing to do with the type we see in dcs. Two different animals. You're confusing real life software errors and hardware limitations with endless breaking bugs that if a real equipment had would never be approved for operations. EDIT: For example, the bug that makes you not see the BRA in radar page if you have an L&S active it's something you might see in a real hornet with a software bug, but the one that makes the enemy see a launch warning when you fire an amraam in TWS is something you will never see IRL, just never. If it appeared, it would not make it to an airplane's pylon. But hey, let's just leave this here, otherwise this will turn into a nasty offtopic posts removed by eagle dynamics.

Since three patches ago when ED started to play with the lighting code, sometimes randomly when I quit the game my windows desktop and everything gets too bright and washed out until I plug and unplug the hdmi cable of my monitor. This started to happen exactly after three patches ago. Has anybody seen the same?

Subscribed. I think this might have something to do with a miss interpretation of the spanish documents they based on. There is no way in this world that any nation would have approved a TGP like this and even pay for it.

You are right indeed about those steps. However I still think the bug exists in regards of the procedure that takes which is the same for jdam and jsow and different for the SLAM.

Nice to see the ampcd stopped glowing!! It was so unrealistic and made it very difficult to fly. But I see they introduced new problems in lighting in current OB, it's all over the forums.

I agree, and I don't care about features rather than the 375 bugs (Kate gave that number) that the Hornet has. Not to mention the hundredths of bugs the DCS core has had for ages.

That's what I'm reporting Swift... SLAM can't go back without unpowering. Jesus my english must be getting worse every day. I have very hard times making my self through a point.

Please ED if this is correct as is do it so the JDAM and JSOW behave like this. I think this point has been discarded without watching the track. Currently there is NO way to get back to the main page without unpowering the weapon. JDAM and JSOW do not suffer from this bug so please take a look at the track.

I think you're right. I misunderstood the context.

After undesignating a TGT the slam timer keeps going. Track attached. SLAM TOO keeps TMR when no TGT.trk

I tested this 7 times and it seems that if you fire SLAMs when IN RANGE cue appears and after a while, the accuracy is erratic. But¿ if you launch them IN RANGE but under 10nm the accuracy is 100% perfect. Track attached. accuracy range.trk

The FLT profile won't affect the In range timing so the pilot doesn't really know if it will reach its target. Track attached. slam flt profile wont calculate max range.trk

SLAM won't return to the slam page once you have gone to the slam DSPLY page, it deselects the slam and countdown starts again. Maybe it's a bug with all 3 weapons (JDAM, JSOW and SLAM) I don't know. Track attached. slam return deselects wpn.trk

SLAM won't step once launched. Track attached. slam wont step after lnch.trk

The numbers won't stop once the designation is made, Gripes. ONly after commanding ATRK or PTRK. But just by designating no, they will keep changing.

Absolutely! Like I said before, I love how the module looks and its capabilities with IFR hood, engine limitations, etc. But each person has his own priorities, for me the first one was multicrew experience.

This. I also want to know about the current implementation.

Really? I thought this desync problem was in the c101 but not in the ED's modules. Can someone confirm this statement? I was planning on getting either one of those instead.

No, I'm afraid I will be 0 helpful this time, sorry x1000. This info came mouth to mouth and the person does not wish to get involved in any of the gaming industry. But this is for atflir only, I was wrong to put this when we have the litening 2 currently. This thread is useless, sorry that was my bad.

Did you actually watch those videos? None of them covers what I'm asking here. Thanks for the reply though.

I was surprised to see no offset mention in last wags video. When will we see one? Current implementation is odd, and we don't know how it will be after tomorrow's update.

Maybe offset feature is meant to counter this constant update thing. ED??

Yeah you're right, that's what the video is showing. Unfortunately that's not how it should work. But given that ED is using spanish documents for Litening II and we haven't even seen any tutorial or explanation of how new things work, I might very well be mistaken as the only accurate info I have about this being a bug is from ATFLIR. I really think ATFLIR and Litening II are the same in terms of LOS logic, where it won't update TGT as it would drive the pilot crazy in almost every situation.

Hey guys at ED! In Wag's latest video on JDAMs, I think I saw a new bug introduced. The TOO page for the bomb showed a constant change in coordinates just by slewing the FLIR's LOS. The coordinates in TOO mode for any weapon should only change if the TGT is actually changed, not by moving TPOD LOS. I think it's safe to say that a track isn't needed as the senior producer already documented this in his video. Hope it helps the fix. Thanks.

Although this comment is quite toxic and negative, I must admit it comes from a very true feeling that more than one have felt in the past. I think sometimes we forget we are customers and we give our money to ED in exchange of a product, sometimes a very flawed one. Kate: Won't you agree in saying that fixing first at least 50% of the huge bug list you have should come first? The hornet has suffered from this since day one: 1 thing gets implemented, that thing has 50 bugs, then another thing gets implemented, that thing has 50 bugs... and so on and so on. How does it end? Here, exactly where we are now, with a fair share of customers unsatisfied.