BJ55

Unfortunately I don't have PNG's of the screenshots anymore, in my case dots are black 2x pixel squares.

Almost nothing, because DCS render objects at the correct size and at that altitude/distance with that resolution it's impossible to spot a camo vehicle. In order to see something you need an "eye resolution", wich is magnitudes bigger than the ones of current video display devices.

2560x1440 MSAA 2x: Symbols are invisible and labels are unreadable.

I took control and everything was OK, check your axis assignments and also check if AP is engaged (it is when mission starts).

@uboats From the changelog: "Baro knob will adjust the value for selected source (QNH or QFE)" , QFE works as intended, but QNH is locked at standard 29.92 (baro setting knob does nothing), can you check? Best regards.

+1

Cancellalo manualmente e poi lancia il programma di aggiornamento di DCS, se continua a darti errori nella rimozione file obsoleti allora lancia DCS_updater come amministratore.

The hundreds rotary is correct. Buone Feste e Tanti Auguri a tutti gli sviluppatori di IFE!

You are in TV mode.

Glad to help you. I use different curves because I prefer a faster vertical slewing of the reticle with this module.

My settings: Ministick is not so precise, so you need a deadzone bigger than 2.

LastMissionTrack.trk dcs.log

Check axis dead zones, check for doubled bindings, check spurious outputs from the device, check for firmware programming errors, remove mods, scripts, etc... Something is moving your TDC without user input. As you can see in the images here https://forum.dcs.world/topic/365003-map-designate-only-goes-to-tgt-and-not-stptpod-to-soi-wont-goto-stp/#findComment-5563870 I have no issues with both axis and key bindings assigned for TDC.

Opening two threads for the same problem won't help you... As intended, since you moved your INS target point away from the STP. Read carefully Chuck's guide, since the manual is incomplete and unmaintained like the module, to me it seems that you're confusing the complex A-10 procedures with the complicated AV-8 procedures.

This is realism: pilots have to deal with gremlins of all kinds.

Doing that way it works, but with that ammount of mils the delay is near to zero, like in direct mode (2° dive -> 160 mil), and at the moment DL is useless. At least now I know that it's not a "pilot error".

To me it seems that you're confusing the procedures, If I: 1- Start the TPOD, select the waypoint and verify that INS is the active sensor 2- Designate the WP 3- Enter TPOD HTS, use TDC controls to correct the target then TDC depress Everything works as espected.

Could you try the attached missions? I keep on having the same .....y results in L/DL modes. To hit the column I have to set 80-81 mils instead of 91, forgot to take note of the difference at 450kts 500ft 1nm. Don't know if ED changed something lately, but also the F1 bombing tables must be redone. F-4_ag_train_cauc_82.miz F-4_ag_train_cauc_82SE.miz

There's no need fot TDC depress, probably you missed one step (From Chuck's guide, page 432): 7.Press the Sensor Select Switch – FWD (INS) to slave the TDC (Target Designation Caret) to the Inertial Navigation System. Suggestion: forget the default training missions, read the guide and then pratice with simple custom missions.

There are reports of artifacts with 560 series, that would be my first thing to check.

Without logs and sys info is impossible for ED to understand the cause of artifacts. If you're using the latest NV drivers try with DDU->install older drivers (552.44 are OK) and check for card overheating.

Check Chuck's guide, if you're following that procedure everything must be OK. https://chucksguides.com/aircraft/dcs/av-8b/ Later I'll check if there are issues with the unmaintained instant action. No issues with the instant action, after going to idle detent make sure to move throttle 1" forward and back or it will not spool up.

Cores are not parked, that's good, but: dcs.20241106-173412.log APP (Main): Command line: "F:\DCS World\bin/DCS.exe" --restarted (restarted because of previous crash?) APP (Main): CPU cores: 16, threads: 24, System RAM: 32530 MB, Pagefile: 1293 MB ... DX11BACKEND (18280): failed to create structed buffer. Reason: E_OUTOFMEMORY dcs.20241106-173412.crash 0x000000000002535b (edCore): ed::fatal_out_of_memory + 0x3B The F-4 is resource heavy, increase pagefile to fixed 32GB or 64GB, in special options set "HB UI online access" to "offline", reduce/disable some eye-candy DCS settings, like chimneySmokeDensity motionBlur civTraffic. Also check this link: https://forum.dcs.world/topic/331896-crash-troubleshooting-guide/#comment-5272952 and be aware that latest NV drivers are causing multiple issues.

I've noticed that after the last update 9 clicks are needed in the hundreds rotary to go from 0 to 1 and the reticle moves at every click, also with more than 3 clicks+9+9 the reticle goes out of sight. As you can see from the image with 0 click+9+9 (99 mils) the reticle is lower than with 9 click+0+0 (100 mils).

I've did as you suggested: in the track replay bombs are released in the same point as in mission, but there's only one speed call, while in mission I've had four sequential speed calls. Edit: sometimes there are 4-5 speed calls, other times it's endless like OP said. (I have half refresh rate HBUI) F-4_ag_train_cauc_82SE_L_wIP9.trk