wasserschorle

I know, but the CAGE-only method does not require any further input from Pilot or WSO/Jester. The question is still standing.

Funny thing: I had occasions where the missile would still track even after the target broke hard to one side and was greatly out of the radar boundaries. May also be some kind of bug, but who knows.

I can't get my head around the whole CAGE-logic in connection with the AIM-7 at close range. My previous knowledge tells me that the Sparrow needs a solid lock (STT-wise) to guide and intercept, but with the CAGE function in the F4 it seems this is wrong? Manual "3.11.3. Boresight and Cage Condition" states that a Sparrow can be fired in CAGE-only (no CAA) when the piper is positioned at the target. Done that and works nearly everytime in close range with limited G's. Question is: how, why? What exactly happens when the trigger is pulled? From where does the Sparrow get its guidance, when (at least in my world) no solid guidance data is transmitted? Since the guidance somehow works better as with CAA-lock (ground, air is locked and not the target itself) why is the CAA even necessary?

The slow motion is also good visible through the SCAS indicator (green indicator) in the control input mask (Rctrl+Enter). When you trim while getting slower/faster you can see the work the bird is doing in the internals and give you a greater understanding of the limits. Now I just let the bird catch up my controls and settle itself before throwing the stick in all directions to counter unwanted behaviour. Also in normal forward flight the SCAS is strong enough to hold a straight line without much input, again let the bird settle.

Module: F-14A Map: Syria Mode: Multiplayer Log: none provided Set up a Markpoint on the F10 Map, did the whole startup and told jester to set WPT1 to the created Markpoint. DCS crashed instantly. Repeated the procedure three times, nothing changed. Crashes ended always without the DCS crash reporting tool. dcs.20210427-111249.crash dcs.20210427-111248.crash dcs.20210427-111249.dmp

Same here. Syria was unplayable for me in 2.5, crashed nearly everytime after a while in MP. Also full usage of 32GB RAM. I guess we have to wait for 3.0 ¯\_(ツ)_/¯

Alright thanks. Maybe I just need to upgrade.

I don't know if this behavior is normal, so correct me if i get this wrong: I'm using a X52 and for all kinds of TDC-slewing, therefore the AKG controls, so I bound my ministick/mouse emulator stick to it. Since this is not an actual axis rather a mouse or 0-1 key (depends on the hotas profile) the direct controls of the C-802AKG differs from the axis ones. After a direction input the cross will not center on its own, it will just stay on its position. The cross is always centering itself as long as no input is made, according to some gameplay videos. So, could we get some kind of recenter mechanic/special option for the TDC-keybinds, or is there a workaround? Thanks.

also not with a cold one.

I guess it's not in the current OB patch?

Also got CTDs. But it was always triggered by the following: -MP cold start -RB 15F loaded -Complete startup -CTD happens as soon as I entered "80003" into Takt/in and pressed LB

When could it be possible to rent a server? I mean like renting one for ArmA from the regular game server providers.

Yep, there you go, hope its intuitive for you: https://www.dropbox.com/s/nku14h46b8fc7hy/DCS%20Viggen.pr0?dl=0 Most of the buttons are customized, because they weren't set. For the trigger unsafe option you need to copy this: {down = 3300, up = 3300, value_down = 1.0, value_up = 0.0, cockpit_device_id = devices.WEAPON_SYSTEM, name = 'Trigger safety bracket (hold) temp', category = 'Weapons'}, {down = 3300, value_down = 1.0, cockpit_device_id = devices.WEAPON_SYSTEM, name = 'Trigger safety bracket ARM temp', category = 'Weapons'}, {down = 3300, value_down = 0.0, cockpit_device_id = devices.WEAPON_SYSTEM, name = 'Trigger safety bracket SAFE temp', category = 'Weapons'}, In the default.lua at DCS Folder\Mods\aircraft\AJS37\Input\keyboard Happy hunting

Got a response from LN, they're willing to implement this in the official documentation. Great news for the weekend.

So, as long I press the reference button on final aligment either in one of two possible runway directions, the system will be fine?