Zabuzard

(It is currently not planned)

Uuuh wtf is that, almost like a beat oof. The track doesnt replicate it for others and no one else reported something alike yet. So whatever it is, it must be something "on your end". Im not sure what though. My recommendation would be to do a full repair and kill all mods, but you said you did that already.

That wont work with the F4 but you could just delete the UI from the folder. In the F4 the entire UI is "local" and fully moddable. It is in Mods/aircraft/F4/UI/JesterWheel But it wont fix the problem, your UI inputs are not replayed and hence the aircraft is in a wrong state. If you make a coldstart with the UI using mouse or headtracking and then replay that, your aircraft will in the replay fly with engines off and no electric power. Consequently no weapons will drop, nothing works. Same in the F14. you can hide the UI but if the UI actions arent clicked then the aircraft is in the wrong state.

Smells like you did use HB UI such as the Bombing Tool, which isnt captured in the replay and has to be entered manually during replay as explained earlier in the thread, cheers.

That is because mouse actions and head movement on the UI isnt really captured during replays by DCS. That also leads to the tracks not working as expected, for example the aircraft taking off with a dead engine and not firing any weapons. You can either control the the Jester Wheel via keybinds (for example the CW/CCW/Enter binds) or recreate your actions while the replay plays by pressing ESC and then mouse clicking on the right actions.

(I cant watch the track right now, but) A few things to consider: * approach the target from slightly below, do not get into a look-down attitude * approach the target from the side to increase its RCS, avoid head-on * avoid placing the target in front of mountains or other terrain from your viewpoint * do not place the target at a distance equal to your own altitude * if done right, expect to spot fighters at 10-20nm, maybe 22nm if you are good. large targets like bombers at 30nm-40nm. * if ur flying against typical DCS players that hug the ground, forget it. u wont get them on screen with a regular search * at visual ranges make use of the pilot controlled radar modes, for example BORESIGHT, allowing you to lock targets by putting them on your pipper * expectation management, this isnt a search radar. you need to know where the enemy is (awacs etc) and then optimize your position to get the bandit on screen. even in good circumstances, against fighters you will only have time to fire maybe a single missile until you are already in range for sidewinders and guns

It happens during taxi because putting it into STANDBY will start the heatup, leading to the radar melting if you take your time on ground.

That is because you have not received this build of the F-4E yet. It is fixed internally but not available to the public yet Could you perhaps record it on a quick video or something? Potentially you are doing something wrong or it is correct behavior. Hard to guess based on that. For example, with wind even on a cold aircraft you will hear the engine blades making noise depending on which direction the aircraft is facing.

Hey everyone, good news! I got you the desired visibility args added. They will be available with the next update of the F-4: HIDE_PILOT_QF = 4500, -- used for QF drone liveries, the code should not overwrite this HIDE_WSO_QF = 4501, -- used for QF drone liveries, the code should not overwrite this

Not sure why you guys conclude "HB say its intended, they wont fix it" when I keep saying the opposite. Sorry if the messages have not been clear enough, so let me try it one more time: The current behavior is "working as expected" but that doesnt mean that it won't be improved/changed. As I keep repeating, it is on the list and it will eventually receive another pass so that the lag is gone. Please do not misinterpret that some things take longer than you want for lack of interest or willingness to change and improve something.

Odd. Yeah, probably try without mods then. They have caused severe issues in the past for no apparent reason. A screenshot of your "tiny ingame manual" and your settings page (graphics and f4 special options) would help :)

Are you using a multimonitor setup or sth like HELIOS? What resolution did you set in ur DCS settings? Maybe something very big so it works for multi-monitor? In that case you would need to fiddle with the Special Settings of the F4 HB UI. Screenshots will definitely help once you can share them :)

Ah, I assume you are a VR users? Then you are probably just running into the usual UI issue that some users have because of a DCS bug. Good news is that there is a fix for it 1. Go to your VR settings in DCS 2. Check "Use DCS System Resolution" 3. Select "Both Eyes" 4. Go to your Graphics settings in DCS 5. Select a resolution of 1920x1080 (or higher) 6. Restart DCS (mandatory) Should work now (This is also somewhere in our pinned FAQ here on the forum)

You said you bound Jester Context Action to A? That wouldn't be the right bind for bringing up the menu. The menu one is called, I believe, Jester Ui Action, not Context Action. It would also be interesting to know if other HB UIs work. Press M to bring up the ingame Manual. Or click on the right canopy spot to bring up the Grease Pencil menu. Or RCTRL+V for the virtual browser or RCTRL+L for Jester Console. Do these work? If those work then it must likely be an issue with your Jester binds. If they do not work, its likely an issue with your graphics settings. Either case, share some screenshots of the corresponding stuff and we can probably get you back on track within a few minutes :)

Hey there, this is an already reported issue, cheers. It was done on purpose to prevent silly looking abrupt and jumping animations as can be seen in those other modules you referenced. It will be revisited and improved eventually. You mentioned that you are aware of the previous posts on this topic, so I am not sure why you are creating a new one. FYI that wont speed up things, cheers.

Potentially you forgot to unlock them, i.e. moving out of the OFF into the IDLE position (by raising the fingerlifts)? Maybe you can share a track file or a quick video or also just a screenshot of the left console area? Alternatively, maybe you are looking in the WSO bind-category instead of Pilot. Or perhaps you have a double assignment somewhere else on the throttles. A check of the in-game Control Indicator could help here.

It is "just" the known issue. As explained in the threads, the exact way how the bug surfaces on your end changes with each update (for technical reasons - its called "Undefined Behavior").

He will enter NARROW mode and adjust the antenna of the radar to always point at this bandits altitude. He will also follow the bandit with the screen distance setting to keep him mostly centered. And of course also keep the cursor on them. In other words, the radar beam is pointed straight at the bandit (provided you also point the aircraft at the bandit azimuth-wise). It is the closest you get to a TWS in this aircraft.

Known issue, thanks

It is because the cause of the bug is whats called "undefined behavior". It surfaces for you in a "random" (but deterministic) way and btw changes with each DCS update.

It does work and that setting should be in your Mission Editor. Either you are looking at the wrong spot or your are on an old DCS version :)

No worries, happens. In fact, 90% of bug reports end up as some sort of user mistake. Totally normal, glad you figured it out [emoji106]

Does it work if you start hot not cold? What if you start in the air? Cpuld you potentially provide a video where you show everything you do from start to the point you are trimming? Cheers

Likely an ED topic. The tone is based on the signal strength reported through the DCS SDK. This part of the Sidewinder logic is controlled by ED. (I personally dont know enough about the weapon to comment on this being correct behavior or not)

Worth noting that the bellows measure "airspeed" at the bellows intake sitting on your tail, next to the anti-collision light. If that probe gets damaged (e.g. combat damage) or clogged (e.g. ice/frozen when flying without pitot-heat turned on), it cant do its job and the bellows will go absolutely bonkers on your stick. And since the trim-system connects to the bellows, the trimming wont do anything useful anymore at all either. And since the engineers didnt think of adding a way to disable the bellows/bobweight linkage, you will have a fun time flying back home. The procedure is to disable all assistance systems by pulling the ARI CB (left subpanel), disabling the STAB AUG system (left console aft) and pulling the CBs for AIL, STAB and TRIM (right wall). Set trim to 0 so when the system kicks back in you wont be caught by surprise. Then hard grip the stick, not let it go, and descent to hotter air to hopefully remove any bellow intake blockage. Until the problem is resolved you have to actively fight the bellows wanting to throw your stick around like crazy.