gemballa974

The plane doesn't need to see the spot (except during laser search). If the maximum range to designate is 8nm, beyond this limit the spot should disappear and the bomb go dumb. How it is modelled right now, you will not get a hit beyond 8nm. It's not working like in real life, but at least you have the same result.

Alright. I guess the actual range of laser designation is classified, and therefore changing the length of the stick might not be suitable. I can deal with the way it is modelled in DCS. Thanks for the explanation.

Hi there, I noticed a weird behavior with the AGM 65 E, I don't know if it is related to the F18 only, so I chose to post it in General Bug section. After a rifle at 8 to 10 nm with AGM 65 E and flanking the target during the lasing the maverick will drift away. If you fly straight or limit the turn, the maverick will easily stay on course to the target. Not sure if it is a bug from the maverick / the targeting pod (here the Atflir) or a difficulty for the maverick to pick the laser when the aircraft is flanking the target. PBM MAV Laser.trk

Do you have easy comm activated ? If yes, uncheck the option, you should be able to change the radio frequency.

Did you manage to solve the problem with driver complete install ?

Hi. I had the exact same problem twice. The first time I opened a ticket with ED, even if I did lot of repairs of DCS and re-installations I did not managed to get rid of the problem. I finally did a complete re-install of windows (for another problem) and from there it worked like a charm. Few weeks a ago I experienced new crashes when hit, just after an express update of the Nvidia driver with GeforceExperience. I did a reinstall from a previous driver and everything went back in line. I highly suspect that this bug is related to the GPU driver and not to Razbam. Can you try to uninstall the driver and then reinstall the driver through a complete install (not express) ?

The bug is back. 1 out of 5 DCS crashes when the M2000 is hit (most of the time the screen freezes with the missile just in front of me). It can happen during SP mission and MP mission. Does someone have the same problem ? Logs.zip

Do you follow the flight path described in the briefing ? You must follow the flight path in order to activate the needed triggers to continue the mission.

I like the Basis because the M2000C is ready to fly, you are quickly in the action. Of course, there will not have start up procedure. Envoyé de mon D5803 en utilisant Tapatalk

If you have the RP (extra fuel tank) selected in the PCA, it will prevent you to lock the target. Check that you selected the 530d or Magic before trying to lock. Envoyé de mon D5803 en utilisant Tapatalk

I'm not very good at high altitude with the M2000C versus F15C or SU27 (I'm still a beginner with the M2000C). I prefer low altitude and sneaky attack. It is slightly more complicated than FC3 aircrafts but at the end you will really enjoy to fight with this plane.

The radar uses the doppler effect, in order to reject static object (ground, ground vehicle, birds...) there is a rejection criteria based on a minimum differential velocity. When the target is below, the threshold is higher in order to reject ground clutter, that's the reason why it is easier to loose lock. When the target is higher (radar looking up), the threshold is lower because there is not ground clutter (no ground camo), the lock is harder to break. Am I right ? If it's right, does DCS and M2000C take into account such realistic behavior (it looks like complicated) ?

I can't reproduce the bug since I posted here. I guess it is related to the server. Let's keep it that way. Envoyé de mon D5803 en utilisant Tapatalk

No crash so far since I posted here. I can't reproduce the problem, maybe it's related to the server.

Hi, I encounter quite frequently a game crash at the exact time my M2000C is hit by a missile. Is it a known bug or I'm the only one ? I attach the dcs.log and the crash log. Crash: # -------------- 20170324-183124 -------------- E:\Programmes\DCS World\Mods\aircraft\M-2000C\bin\M2KC_CPT.dll # C0000005 ACCESS_VIOLATION at E602DF30 00:00000000 00000000 00000000 0000:00000000 E602DF30 001FEF80 0000:00000000 E:\Programmes\DCS World\Mods\aircraft\M-2000C\bin\M2KC_CPT.dll E602E8A3 001FF000 0000:00000000 E:\Programmes\DCS World\Mods\aircraft\M-2000C\bin\M2KC_CPT.dll E8A4A8BA 001FF050 0000:00000000 E:\Programmes\DCS World\bin\CockpitBase.dll ??4LaserGuidedWeaponState@cockpit@@QEAAAEAU01@AEBU 01@@Z()+11A E8A54E20 001FF0A0 0000:00000000 E:\Programmes\DCS World\bin\CockpitBase.dll ??1avSatelliteSystemStatus@cockpit@@QEAA@XZ()+E10 3FE51E3A 001FF0E0 0000:00000000 E:\Programmes\DCS World\bin\DCS.exe 4000E7A4 001FF110 0000:00000000 E:\Programmes\DCS World\bin\DCS.exe EB0BE710 001FF230 0000:00000000 E:\Programmes\DCS World\bin\WorldGeneral.dll ?process_@ActionDispatcher@@AEAAXUActionEntry@@W4A ctionOrigin@@I@Z()+60 EB0C403F 001FF2F0 0000:00000000 E:\Programmes\DCS World\bin\WorldGeneral.dll ?feedEventsUpTo@TimedActionBuffer@@QEAAXN@Z()+18F F627618C 001FF360 0000:00000000 E:\Programmes\DCS World\bin\World.dll F6276785 001FF3B0 0000:00000000 E:\Programmes\DCS World\bin\World.dll 40016633 001FF420 0000:00000000 E:\Programmes\DCS World\bin\DCS.exe 4001D721 001FF480 0000:00000000 E:\Programmes\DCS World\bin\DCS.exe 4000BBD4 001FF4B0 0000:00000000 E:\Programmes\DCS World\bin\DCS.exe 4000BB24 001FF4E0 0000:00000000 E:\Programmes\DCS World\bin\DCS.exe 3FCE71CF 001FFBA0 0000:00000000 E:\Programmes\DCS World\bin\DCS.exe 4011FE1D 001FFBE0 0000:00000000 E:\Programmes\DCS World\bin\DCS.exe 76FD59CD 001FFC10 0000:00000000 C:\Windows\system32\kernel32.dll BaseThreadInitThunk()+D 7710A561 001FFC60 0000:00000000 C:\Windows\SYSTEM32\ntdll.dll RtlUserThreadStart()+21 DCS-20170324-183124.zip