uboats

you can use L2/L3, L4/L5

from the crash log, your crash is not related to jf17, but more to nvidia it's better to report to ED and also post the full crash package also try to update to latest stable or switch to OB

because AI cannot use tpod defined by 3rd party for laser guided weapon, same for F14. it's reported to ED

same condition, but cannot reproduce.

just to confirm, you want to adjust CCD level/gain using MFCD brt/cont button?

Here’s a bug and you can only do it with auto start at this moment. It will be fixed in Nov update soon

we tried in MP, and getting hit when guiding sd10, cannot reproduce crash

neither ED nor us can reproduce it

Neither ED nor us can reproduce it

For Nov OB update: Fixed: integrated configuration panel GUI not open if there’s wind Fixed: Cockpit capture keyboard input when integrated config panel GUI is opened Fixed: LS6-100/250 accuracy issue Fixed: unguided rocket engine not ignition bug Fixed: SPI switched to WPT when WMD7 point track downgraded to area track Added: campaign mission 11 and 12. Now campaign is completed

trk uploaded to ED, ED is working on this issue

can you open a new thread and upload a trk?

Do you also use DiCE or SRS or any other tool that may work with vaicom pro?

thanks

@hornblower793 just learnt from that vaicom will modify module device_init.lua file. This in 2.8 will break the IC.

@Hiten Bongz @FlankerFan35 @Dr_Pavelheer If you have again encountered this issue, could you please upload latest trk file of those crash? ED needs trk to debug. Also if you can quickly reproduce it after joining the server, that would be greate.

ok, vaicom modifies the file, so it fails the IC. i will consider to add those lines by default

It’s reported to ED internally.

Can you upload the reported device init file?

what's been changed by vaicom pro to that file?

it's better to share trk, acmi is useless for debug

For this avionics, yes. what i know is newer ver can select rack

if you want to try it locally here are files copy to: coremods/aircraft/chinaassetpack/entries/loadout/ jsow_ls6.lua jdam_ls6.lua

should be fixed internally now

you can make a test miz, and place small/medium/large ships, and compare the echo sizes. you need to set target size properly to match the echo size