Zabuzard

Hello, kindly do what is adviced in this thread. Thank you: /topic/366674-f-4-authorization-error/?do=findComment&comment=5576100

It sounds like you are in your Firewall settings, which is incorrect. It is not about allowing DCS.exe to use the network but about telling your Windows Defender AntiVirus to stop looking for malicious files in the DCS Installation folder. It is a different menu in its UI and allows you to whitelist/trust/exclude certain folders from its search. Once that is done, you can restore the quarantined/deleted files either through their menu or by running a DCS repair. Then it should work again. If you cant find it, I would suggest to google sth like "Windows 10, Windows Defender, exclude folder from Antivirus" (with whatever OS and AV software you are using)[emoji106]

You can find an explanation for what and why here: /topic/366674-f-4-authorization-error/?do=findComment&comment=5576065 Cheers

Hello, kindly do what is adviced in this thread. Thank you: /topic/366674-f-4-authorization-error/#entry5576100

Hello, kindly do what is adviced in this thread. Thank you: /topic/366674-f-4-authorization-error/#entry5576100

Hello, kindly do what is adviced in this thread. Thank you: /topic/366674-f-4-authorization-error/#entry5576100

The exact steps will differ depending on which exact AV software you are using (e.g. Microsofts Defender, Kaspersky, Norton, Awast, AVG,...). It boils down to telling the AV software that the file is not a virus and it should be ignored (whitelisted). For simplicity and to ensure you wont be bothered by this for other DCS files in the future anymore, you can also try to tell it to trust the entire DCS install folder instead of just this particular file. After that is done, you need to make sure the affected file is restored, since your AV quarantined (deleted) it. This can often be done somewhere in their UI, but running a DCS repair (or Steam File Integrity Check) will also get you any missing files back. Since this is not a new issue, you can find other threads somewhere on this forum with step by step guides and pictures for commonly used AV softwares. Searching with Google can likely also help a lot with it [emoji106]

FYI the "authorization" message is send by DCS because it detects that you are attempting to launch with an incomplete or modified module - since you are missing one of the Phantoms DLL files that your Antivirus software deleted/quarantined. To fix the issue, you need to tell your AV to trust the file (or for simplicity the entire DCS install folder, if you want) and then make sure the file is restored. Latter can also be achieved by running a DCS repair (or Steam File Integrity Check) :)

Unfortunately, it is the only solution to the problem unless you want to wait about 2 weeks until all AV companies updated their DBs and then you have to go through this again with each update. The problem is the AV flagging good files as malicious because they do for example file or network IO (obviously, cause its a game). We have no control over what the AV does and the only way to fix this us by the customer whitelisting the file or by the AV company whitelisting it globally. And latter is a tedious process that takes a few weeks and needs to be repeated each time the file changes (i.e. on every couple of updates). Its not a new thing, it has happened to at least 5 modules over the years and also affected the Phantom half a year ago already. It also happens to other platforms, in particular indie game devs deploying without Steam and similar.

This is an unfortunate but common ongoing issue that happens every couple of updates to any module using fancy features (code-wise), such as for example also some Razbam modules for years already. Generally, the best solution is to whitelist the DCS folder in your Antivirus software and then restore the quarantined files (DCS repair will do the trick). This will also boost performance a bit. If you search through the forum and Discords you will find it mentioned every couple of months. Sadly there is no good way for us to fix this from our side. The global AV database whitelisting processes are tedious and slow. It usually takes them until about 2 weeks after the update to accept and ship the DB updates and stop flagging it - until it happens again with the next update when the DLL changed slightly again.

Bomb Button causes a TGT INSERT signal to be send. What you are describing is correctly modelled to our knowledge and supported by the electric wiring diagrams of the WRCS and Pave Spike from their corresponding maintenence manuals. SMEs also confirmed this behavior to be correct. The logic differentiates a few cases depending on what caused the insert signal, there are certain levels. I can provide details in a few weeks after vacation.

lol what. can u double check with a fresh mission that doesn't possibly use old loadouts from pre-update. thank you

Simply because it hasnt been coded yet. Primarily his awareness for "we are in a dogfight". Its on the list :)

To move it from the pilot seat you must use the "[WSO Temporary] Antenna Hand Stick" binds, since only the WSO is able to slew it normally. It is necessary that the WSO has the TV screen selected as well, otherwise the Antenna Stick is tied to the Radar instead. Jester does this when you select TGT FIND as Delivery Mode, so this is a necessary step. Additionally the pod can only be slewed in TRACK mode, not in ACQUISITION mode. Therefore, you must press the Antenna Stick Trigger HALF (or FULL) Action.

1) currently not easily possible for technical reasons. but its somewhere on the list to change that, cheers

1) that will be solved with a virtual keyboard system in the future 2) good idea. probably also easy to realize by the community once we open up jester modding

Thanks. Jester is using a SDK method to determine whether the enemy is dead. Apparently it reports those guys as dead. Possibly sth for ED to look into, we will sort it out, cheers.

These controls are for mimicing the WSO as pilot. If you want to use the Mavericks from the front seat, you have to use the Weapon mini-stick (next to the throttle) in the front pit instead :) The controls for the Mavs are locked to the pit that activates them (also IRL), which is either the Pilot or WSO. Please refer to the manual for details, cheers: https://f4.manuals.heatblur.se/stores/air_to_ground/missiles/maverick.html#employment

Because of the loadout containing TV weapons that have a mandatory warmup-timer that is reset the moment this knob isnt in TV. So the only possibility to spawn hot and be able to use these weapons directly is vy having the knob in that position and pretending the timer has passed already internally. Its a bit unfortunate that spawning with the intent to use one weapon gives trouble if the intent was to use another weapon instead.

Mh, then I have some trouble following your description - it seems to work on our side. Could you provide details or a track or video? Cheers

The display setting in the Jester Menu is for the range to use in general search (Scan). Jester will only use it then, not during Target Focus or Lock or any other phase. Kindly see the manual for details: https://f4.manuals.heatblur.se/jester/combat/radar.html#scan In other modes, Jester adjusts the display range himself based on the target in focus, so that it is always clearly visible.

There is no clean, easy and safe way for us to create content inside DCS own savedgames folder. So what we always did for our modules is to create our own folder and then have full control over it. Possibly that can be changed if ED gives us a proper way to manage content in their folder.

Great find, and thanks for the track. Probably has to do with the exact camera position within the world with respect to the model. At some point it was carefully placed to look inside a black hull naturally, but possibly some stuff changed when we touched the positioning a few months ago to prevent collisions of the laser with the own pod model.

The AI would fall onto ED, we cant control its behavior. Player F4 vs Player F4 jamming should work though. Thanks for the track. Have you replayed it locally to see whether the track works and deplicates the issue? Server tracks often dont work. Cheers For the player controlled F4 with the jammer, have you checked whether the green XMIT lamps are on? The jammer has a warmup phase of a few minutes :)

Yes, it will be available in the upcoming DCS patch. It was originally supposed to be in the previous one already but it unfortunately missed the upload deadline by a day.