uboats

from what I know, ld10 is a short range arm

which small boat?

i have only 2, so preset only for mfd1 and mfd2. and the 3rd one requires customized binding. for the 3rd one, what's the lua name in saved game/dcs/config/input/jf-17/joystick?

then gap issue will be addressed for next update

for range issue, will be addressed for next update with detection probability implemented, it cannot guarantee a constant detection at every frame when distance is around detection boundary Lock a contact in VS mode will enter STT if lock succeeds.

did you see any report for mirage and f18 on their subforum?

there could be many issues hidden in stby weapon mode, will check it later use normal weapon delivery systems at this moment

per our sme, display board of ld10 says it's a short range one (he cannot find the display board pic at this moment)

it's known and under fix

do thank you for all your effort in making those skins.

if you want to make skins, you can share them at dcs-world user file, but we will not consider to add them into cap any more at this moment.

1. su-27 skin diff from j-11a skin (many old skins used by su-27 in plaaf no longer for j-11a) 2. j-11a only in PLAAF, so besides those general fictional skins, we would not consider other fictional skins for specific countries

1. I dont quite understand: Test Procedure: Impact Azimuth -- Off vs Actual Behavior: Bomb did establish a direct flightpath to the Target, ignoring the commanded Impact Angle where's the commanded impact angle? 2. dive angle not support yet 3. popup at the end (to check) 4. after bomb release, all flight behaviors (i.e Wiggle) are fully controlled by scheme (except impact az) 5. dlz calc, there's no api provided by ED for accurate calc, so it's more of a rough calc (needs ED help)

If you want to discuss, it’s better on forum and in this thread.

Not for j11a + pl12, unfortunately.

make a simple miz yourself, and place 3 ships (small, med, large displacement), and check the echo size on radar screen.

for pre-planned, it's "absolute" coord, while for too, it can be from onboard sensor which actually gives you coord based on aircraft coord (so relative coord). if there's drift, pp can be affected, but too might not

can it be reproduced? and all detailed steps? i cannot reproduce it

ld-10 switched to new scheme per ED's suggestion. the drag seems to be larger as expected, although the fm param is identical to sd-10. will check with ED

cannot reproduce probably fixed, please re try in next OB update

the crash info shows nothing related to JF17, but more of DCS core radio/datalink routes So need ED's help to figure it out.

JF-17 Added: probability of detection for AA radar Added: unstable track of AA contact if detected range is near detection boundary Added: if no hpt/spt, AA radar shows bearing/range from TDC to current waypoint Added: clickable eject handle for eject Fixed: AA radar VS mode Fixed: hpt/spt position prediction after being notched Fixed: small bugs in RWS and SAM+NAM/ASM modes Adjusted: AA radar notch gate speed Adjusted: radar mode display Improved: TWS/RWS contact acquisition (super search before entering STT) Improved: TWS/RWS raw hit to track file

Cannot reproduce by our programmer, or wait for next update and check again. Probably some fix internally.

will check, thanks

saved game/dcs.xxx/logs/ some zip pack or log file with coredump info at the end