Jump to content

84-Simba

Members
  • Posts

    376
  • Joined

  • Last visited

Posts posted by 84-Simba

  1. Hi !
    Since the lighting in the F-16 is somewhat weird I don't know if it is working as intended or not but ...

    the wingtips red/green lights are always lit up even if you have the position switch on "off"

    The only way to turn it off is by rotating the master light knob to off or covert positions or turning the form lights knob all the way down.

    What is weird is that in either bright or dim position you can see the bulbs.

    In the off position, the bulbs are off but the lights are still there.

    The white bulb at the base of the vertical stab is working as intended ...

    It's been a while since I flown the Viper but I don't remember this working that way.

  2. 1 minute ago, QuiGon said:

    Since the relase of 2.9 this issue returned for me as well. First off, @Raptor9 if this issue occurs, the missile's don't just go for another nearby target or so, but hit the ground at a consistent offset to the target. So for example one missile will hit the ground 15m to the left of a target and the next missile launched at the same target will hit the exact same spot on the ground and the next one will do so as well and so on. That is even consistent over different targets, so when fired at a nother target the missiles will then hit the ground 15m to the left of that target. INS reset fixes that.

    Now what causes this issue is still not entirely clear to me, but I think it's desync between both crewmember clients caused either by a temporary freeze of one of the two clients or by server lag. I think this is also the reason why I get this issue with the Lima Hellfires a lot again in 2.9, as the servers are much more unstable now.

    Exactly that but I have it in SP as well ...

  3. The thing is, the missile is not missing.

    When you follow the trajectory with the F6 view you'll see that it turns toward the intended target, pass before it and do a quick move in the last second before impact.

    It tracks and shaqs something that is not there and definitely not the intended target.

    And if you lase/store a target and slave on it you'll se how much it drifts.

    I know that someone will say that they are 2 different bugs but as soon as the INU is reset (just before beginning the engagment) the missiles work properly.

    • Like 1
  4. Weird because it is a given here.

    I tried to throw 4 Limas at a Shilka, standing still, slow movment, quick movment ... the four went exactly at the very same spot, tracking something and falling short of the target.

    Note that my flights are usually more than 30 minutes.

    In fact, this is the very same behaviour as it was before and described earlier in this thread...

  5. Hi !

    Since the last hotfix the Limas are broken again ; unless you do an INU reset just before you engage, the L will track something that does not exist generally short of your intended target.

    Like the last time, store/slave a point will show a significant drift.

    The last time a slow repair of DCS seemed to have solved the problem but not this time, unfortunately.

    It really seems INU problems are impacting Limas ...

    Thank you.

    • Like 1
  6. Hey there !

    I flown the Gazelle today and noticed that she has a great option for the trim :

    fade in

    It stands right in between instant trim and center trim.

    It works like a charm actually, as it is quick enough but does not make the helo snap when pressed.

    Any possibility to have it worked on for the Apache (and other ED helicopters) ?

    Thank you very much !

    • Like 1
  7. Hey there !

    I noticed that the FARM report does not seem to work with the AI wingmen.

    When I request one it says that it is not acknowledged.

    But if I ask a PP, it works.

    Is this a bug or is there datalink limitations with AI wingmen at the moment ?

    If so, what can they do or not do at the moment ?

    Thx !

    Fly safe

  8. 3 minutes ago, [RENEGADES] T-Bone said:

    I don't think this bug has been fixed yet, at least I can't see anything in the changelog.

    There were a few words about INU but not directly the bug we are experiencing.

    I'll try again in a few days.

    Tell us if a slow repair is solving the problem.

  9. Hi !
    As of today and with the last patch it seems the problem is solved. I managed to fly the very same training mission as always and did not performed an INU reset. The Limas are now tracking correctly and the INU does not seem to drift ; the slaving to a just stored target put the TEDAC right on spot.

    Thank you very much guys !

    • Like 2
  10. On 4/7/2022 at 10:13 AM, osram said:

    WD on the write-up. @Bunny Clark😉 Couldn't bother anymore tbh after all the variations/guides we both attempted to try and explain. Hopefully with this it becomes more concise and clear. Just adding my own monitor-setup (with different names and setup to Bunny's - do not "combine" or "mix"), as a practical/visual example.
    This below is the only way you can have the PLT MFD's ACTIVE/Displayed - When you want both PLT and CPG MFD's located/defined at the same X and Y position of your screen, GUISE. 🙂

    By commenting out your
    CPG MFD-names and restarting DCS. (After following Bunny's exaplanations file/viewport modifications, obviously)

    As indicated by Bunny - Currently DCS multiseat issue. This will not enable you to hot-switch MFD's while changing seats or anything. Just to get the selection of PLT vs. CPG under your control.

    Rather surprised it's not acknowledged by ED. No feature planned etc.? Thought heard something bout F14 hot-switching planned? No? -.-

    image.png

     

     

    Hi !

    How did you separate your KU between PLT and CPG ?

  11. Hey there !
    Has anyone figured out how to export the KU and have it hotswap like the MFDs when changing seats ?

    The MFDs are working like a charm in that matter but the KU is still showing both PLT and CPG seats at the same time ...

    Thank you guys !

  12. Further testing and I can provide some datas, if useful :

    T01 entered in the TSD at startup is : 37S BA 5490 2560

    When arrived at my battle position, ACQ to T01 and as expected, it has drifted.

    The TADS slaves roughly to 5491 2562 (on the F-10 map)

    Repositionned the TADS to the intended target, designated a Lima and ACQ/slave the seeker.

    The missile was pointing at the offset.

    Launched a Lima and the missile tracked something and fell roughly at 5479 2557 (F-10 map)

    ----- Reseted both INU ------

    ACQ T01 but now the TADS slaves to roughly 5496 2558

    Realigned the TADS and designated a Lima, ACQ the seeker and the missile was again pointing at the offset point.

    Launched the missile and this one tracked and shacked its intended target (5490 2560)

    In both shots the Lima seeker was as expected pointing at the offset point, not the vehicule I just designated ; this seems logical since the Lima has an inertial guidance in LOAL for the first seconds of its flight.

    Conclusion :

    With a degraded INU the Lima is tracking something that is not there at all and after an INU reset (still off but less degraded I suppose), it tracks correctly and shack the intended target.

    Note that during all this I was having George maintening an hover at roughly 150ft.

    The only time the helicopter moved is when I reseted the second INU.

    The aircaft yawed a bit and stabilized (Thx George !!)

    Next time I'll wait for INU 1 to reset entirely before reseting INU 2 ... or land somewhere and reset both on the ground.

    For now it seems to work more like the Viper, meaning the GPS is not updating the INU at all time but only when you request an update (if I understood the Viper correctly)

    If I follow Casmo's words, it should be embed at all time.

    But I stand corrected since I never actually saw an Apache IRL ... 🙂

    • Like 4
×
×
  • Create New...