Zabuzard

Due to how the TAS gauge works internally, it cannot give reliable values outside of the calibrated range of 150 to 1500 knots. So that is expected behavior :)

For bombing you would use the True Airspeed Gauge to the top left. The values on the Bombing Table are all TAS not IAS :)

Cobra explained it on Reddit once. You can't use that template as-is because it cross references multiple files from private servers and has some complex setup, also with ED. There is quite some work involved into making it into a standalone paintkit that can be distributed and used by non-employees. At the moment there isn't much to say other than you will get it once it's there.

When you ask Jester to go BST you enter the normal boresight mode, as opposed to CAGE/BORESIGHT (vs CAGE/CAA which is just one button click away). Everything you said so far hints me into thinking that something causes you to enter CAGE/CAA. As then for example Jester would also say "no can do" to your aspect-requests, as you are not in one of the two boresight modes.

Sorry, no ETAs.

You can already mute and also fully disable Jester. Jester Menu > Crew Contract and then Presence to disable him fully and the Silence option for him to not talk anymore. Moving your Intercom Volume knob down works as well ofc.

Could you send a track? It really smells like you enter CAA mode for some reason. Possibly doublecheck your binds, perhaps sth is indeed pressing the button (unintended). And no, we did our change a thing. Can't talk for ED though, who are responsible for behavior of weapons once launched. Btw, I would avoid the term "nerfed" as that implies a change is being made for balancing reasons - which is never a goal for us or any developer in DCS. We pursue realism, not a balanced multiplayer experience :)

They are actually all implemented and functional. Its just that you cant interact with them currently (yet). They are all connected to the corresponding systems and if you could pull one of them the corresponding system would not have power anymore. The CB-fidelity is there, you just cant experience it yet. The problem with making them interactable is that you are going down to 1 FPS and DCS also starts to crash when you just add 200 more clickables in the cockpit. It is super unfortunate but the regular way DCS wants you to make clickables does not work for that amount of switches anymore. That said, we have a few ideas how we could work around and tackle the issue - which is also why we went the effort in coding and connecting all the CBs in the code from day one. Right now we only made the really important CBs clickable, which are the ones in the Pilot Cockpit. Cheers

Agreed. The general idea is still that it doesnt really require deep prep - in particular since in most "standard situations" the "default" drag coefficient works fine and even if you just roughly put in a planned attack and then only follow it somewhat, you will likely score a hit. But yeah, the way the manual has it worded is a bit unfortunate

Not sure where you take this from exactly in the manual. The drag coefficient is a required input for DT (and hence also for TGT FIND). The bombing tool always displays all required inputs. Since the Drag Coefficient is also influenced by release altitude and speed, you have to input that into the tool as well to obtain a proper Drag Coefficient.

It will work for anything that actually plays over your Intercom. So for example the real actual Jester voice - not the artifical sound files played in these training missions. Or also the Crew Chiefs voice.

The thing is, no one knows it ad-hoc. We can figure it out if you put a dev on, but right now we are all super busy (as usual). Your request has been heard and you will get a detailed answer from us at some point. Most likely at the same time when we want to expand this section in the manual with said details.

The last patch had no updates from us. The cutoff was around christmas time when everyone was on vacation. Our stuff will be uploaded probably in the next patch.

ah, that one plays through the mission. u can only change that volume through the sliders in dcs audio settings. but likely also affects other sounds.

No ETA.

Yes, Intercom Volume knob on the Intercom Panel. It has a bindable axis already. Further, the "Headphone" slider in DCS auduo settings is the master volume for every sound played through the helmet.

Do you have some screenshots or anything? Otherwise it is hard to judge how good your contrast actually was. So far whenever people reported similar problems it turned out to be not enough contrast, so that would be my first guess. (Note that the contrast locking is an ED topic)

I am not sure what you are trying to say. To me it sounded like "Oh look, there is the Naval variant in the video, HB must be working on it already and it will perhaps be out this or the following years". The Naval variant is very far out. What you have seen in the video is the existing Phantom with one of the existing liveries and you should not use that to draw any conclusions regarding a module that, at the current state is nothing more than a vague "maybe" for the distant future. In regards to the Phantom we are working on the DMAS version next.

Kindly check this duplicate thread which has detailed steps: /topic/366674-f-4-authorization-error/

The video did not contain a Naval Phantom nor any other Phantom news. What you have been looking at is one of the existing liveries.

Not a video but a track file. That has the advantage that we can replay it locally while attaching the debugger and inspecting all interior behavior as it plays DCS shows you a "Save Track" button in the Debriefing window at the end of your (Singleplayer) flight. You can then also check it from the Main Menus "Replay" option to see if it captured the issue and then send it to us

Correct, the video did not contain anything new for the Phantom. The Phantom will first get the DMAS upgrade. A naval variant is for the distant future and will also be an entirely separate module (please also see the FAQ in our Discord). It is very far out.

Could you send a track replicating that issue? That would help us massively in pinning down and fixing the issue, cheers.

Yes, those are standardized brevity terms. If you google "dcs brevity terms" or similar you should find a good list or also videos explaining them :) Nails means you got sth on your RWR, not locked yet (that would be a "spike"). This here seems to cover most of the terms: https://wiki.hoggitworld.com/view/Brevity_List

Kindly see this, thanks: /topic/366674-f-4-authorization-error/