L0op8ack

At last, my hammer found this nail. The motor speed is not properly set, the default motor moving speed is too low, laser will take centuries to repoint to target. FIXED!

What ED post on the forums, is based on very early stage of SD10 from internal version. I can understand it why they choose this version to release to the public.

will check, thanks for report.

LOAL had been in service in RL. it’s comfirmed by SMEs. but implement it in DCS need many hard work, both ED and Deka, I can not be sure it will come or not.

I think it's the +-180 degrees limit of roll channel, when you overfly the target, pod seeker need roll back fully to re-point to target. if laser on when seeker is rolling, LGBs may fly around to chase the laser. We are digging into it. thanks for report.

if you use F+B, you get only a bit less than half jamming power in each direction, it will increase the burn through range(bad). F or B use full power in one direction, so better protection, but you need manually press OSB to set it properly. Let's do a test in detail for it. :)

we know it’s typo, as the real one:)

they do move in real time, but no radar contact, no precise position. contact positions are predicted with last speed measured, without acceleration information, so the predicted positions are not 100 pecent precise, especially the target have accelarations. this implementation make continuous mid-course guidance more important, than ID-guide implementation, you can not shoot and run at a very long distance.

OFF: no power connected, not BITed, we even dont know it's broken or not STBY: it BITed, but high volt NOT applied, idle but NOT ready JAM: high volt applied and ready to go, but nothing to do yet(idle AND ready) JAMMING: send waves with patterns, depend on pilot settings press key "E", WCS tell SMS apply high volt to the POD(state change from STBY to JAM/READY).

We added some axises for HUD/UFCP/AAP knobs, but the total number of axises is limited, we have to re-arrange axis for different usage.

It's fixed.

Players are fickle in love of weapons.

Flares are dispensed too quickly, it's hard to set up a proper mission to test. In my test, IR seeker may lock wrong target if 2 or more targets are in close formation (radar locked 1#, while IR seeker lock 2# even it's slaved to radar). Since we use 16-leaf rose scan pattern if uncaged(instead of dead on radar target), and IR seeker always lock the first hot thing, biting flares is very likely.

Thermobaric damage effect is not support in DCS so far, we can model these weapons, but the effect may be incorrect.

LOS rate will be too high if very close to the target, pl5 seeker may lost track. you can verify this behavior by brutal pedal kick to the oppsite side of direction target moving. my personal suggestion: pull harder to lead target, stable the LOS rate to 0 if possible, wait tone, shoot.

in the HOTAS map, most of S2 keys are not defined in STT mode.

fixed

thanks for report.

When you are ground hot, you may change your loadouts, manually load may be the better choice.

DCS do not limit your implement too much, it's all about complexity and performance.

RCS value in lua is defined as 'front aspect'. How RCS affect radar detection, depend on how the radar(which is painting JF-17) is implemented, using a static RCS value, or build a common azimuth/RCS map, addtional RCS from pylons etc. 30% ~ 50% of front aspect RCS is generated by inlet/engine, JF-17 with DSI use the same front aspect RCS of Mig-21, seems a bit wired.

you need \ F8 call ground crew to update your DTC card, then insert your DTC card, by click DTC card slot in cockpit, and load settings in MAIN MENU -> DATA -> DTC -> ALL, ENT

Block I was delivered in a hurry, from my perspective. Officer of PAF who were in charge of Thunder project, want to see it get into service before his retirement. Most of subsystems can be upgraded without many modifications, it's a reasonable dicision.

No, please do not misunderstand me, I dont mean players, I mean inside. All public infos are treated as false and fake, even they are from the developer of real thing. We are lucky to find a report with PL12/SD10 acmi video, we tested dcs version sd10 with the same parameters of shooter and target in the video, we found dcs SD10 performance is a bit underpowered, but still within acceptable difference, 3%.

It’s the radar signals which cause rwr screams. Missile in mid-course will not trigger any rwr warning until seeker active in end game. We checked radar code, test shoot in cycles of rws-> sam -> dtt -> stt and tws -> hpt -> dtt -> stt radar signals are correctly sent in these submodes. We are waiting for feed back from tester team, see what's happening in radar when shooting at all kinds of target.