Jump to content

L0op8ack

3rd Party Developers
  • Posts

    576
  • Joined

  • Last visited

3 Followers

About L0op8ack

  • Birthday 09/03/2020

Personal Information

  • Flight Simulators
    DCS
  • Location
    the Forbidden City
  • Interests
    football

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Nice to know problem resolved.
  2. TDC controlled by axes or keys?
  3. C802 and almost every anti-ship missile have same problem, need ED check and fix. image of 802AKG is bind to the axis of missile, no target in the image, no target will be hit by the missile if you are attacking moving target, you will have to manually turn missile left/right a bit, to find the target by your own eyes
  4. Let's make it clear: 1. Su-30MKK is an internal project for self-challenge, to create a reusable multi-crew framework(not fully done) and multi-language support avoinics(done but need tweak), 2. FM is 90% done if not 95%. Thanks to our FM guys, TVC is considered, so FM code may be ported to MKI, 3. We had read some docs, but lacking many sub system docs(in details), we cannot reach the basic DCS FF standard ATM, yes, it's started, more like a test bed of some ideas than a real project. To DCS FF standard? we need 2 more weeks(TM)!
  5. yes, it's an emergency seeker on mode, if someone else tell you that your target is far from the position when you takeoff. you can manually turn seeker on for max 3 times I think, if more than the limits, the missile will be self destructed.
  6. fixed max simultaneously tracked targets: 10 incorrect using the same limit of SA contacts in radar page.
  7. After some digging, I found the root cause. Incorrect notch behavior is the side effect of this bug. internally fixed.
  8. in TWS/SAM scan process, radar beam will not always point to hpt/spt within one full scan frame, we need predict their position when beam is not point to them. the only problem I see is: whether we should mark trackfile as MEM or not, after we had a solid ping-echo from target. in current implement, we mark it as MEM too, because in fact it's predicted when radar beam is not point to them. the reality: MOST OF TIME in TWS/SAM SCAN, trackfiles of hpt/spi are predictions. if we mark trackfile as solid/precise while in fact it's predicted after the solid ping-echo, the difference between real target position and TD box will be very obvious, pilots may be confused and misunderstand. We'd like be honest: flash if trackfile IS predicted.
  9. trackfiles are not displayed only after one scan frame, radar page refresh many times per second. hpt/spt trackfile will be predicted anytime they are displayed to provide proper SA for pilot, instead of jumping around after scan finished. HUD TD box and trackfile in radar page may jump a bit while contact is in MEM mode, but it is caused by no-perfect prediction(no accelaration info), totally different reasons. anytime HUD TD box flashing, it means trackfile is predicted, not direct ping from contact, and the trackfile data is not so reliable for guidance, but it will not be dropped immediately, pilots need SA reference even it's degraded. in TWS/SAM mode, we have no reason to drop hpt/spt trackfile immediately if they are in notch, because radar is centered very close to hpt, we have good chance to find them out again, until 8s timeout reached. the target have to stay in notch > 8s, anytime he run out of notch and pinged by radar within 8s timeout, trackfile will be upated, timer will be reset, and trackfile will be marked as solid ping.
  10. SP is affected too. seems like SD-10 seeker is not properly activated. we are woring on this. thanks for report.
  11. if contact is not detected by radar in one scan frame, its trackfile will go into prediction mode, and trackfile max keep time timer(8.0s) will start count down. if it's detected any time in one scan frame, trackfile updated and the timer is reset, thus, TWS/DTT contacts will not disapper immediately, and stay last known/predicted position within timeout limit(8.0s). in TWS/DTT, you are tracking a trackfile, it may or may not represent the real target, depend on when it's updated.
  12. fixed internal SP have this problem too. you can test using this SP mission, for time saving. use \ F10 command to manually set AI ECM ON/OFF AI_JAM_ONOFF-test.miz
  13. RWR in JF-17 stores signal emmiters in mem for a period of time, you are notching or not, signal symbols are displayed as last known az/range, not real time postion of emitter, unless it's in STT mode(update very fast, can be considered as real time update). scan/TWS signals have an scan interval, signal info(az/range) will not magiclly update between scan intervals, it will look like there is some lag. RWR can not detect any speed info of the signal emmiters, there is no way to predict. defender's RWR signal emmiter infos are heavily depend on offender's radar mode / scan cycle, STT gives the defender best signal info, lower scan cycle time(controled by scan az and scan lines) = more precise signal info
  14. in a simple JF-17 vs JF-17 test, SD-10 is displayed as [10] by RWR. I think SD-10 is not added into the RWR database of your plane. If you are flying JF-17, the reason may be you did not load your DTC data, JF-17 RWR database is loaded from DTC, in DCS and in RL.
  15. AAR tricks in DCS, find a ref point on the tanker, stable your plane to this ref point. In DCS, the basket wont float around as it does in RL. You get in right position, you will connect. Never chase the basket, most of PIO are caused by chasing basket
×
×
  • Create New...