Juuba

Yes debug said J. Maybe it wont work properly on 3070. Here's an album with images with Preset J in the Hornet: (Reshade pictures - even though now it seems that DCS original shots also have the artifacts..) https://imgur.com/a/sQJXZ54

I tried the new preset J.. It didn't pass, F looks and behaves better on my RTX 3070 in 1440P. The ghosting is really bad in the cockpit MFD:s in J. Thanks for the tips tho... Preset F in DLAA remains for me, this is what the hornet looks like from the outside, trailing edges flicker: (1440P, cropped and enlarged 1,5x) but the plane itself is recognisable: (ingame screenshot via ReShade - the game's own screenshot does not show the ghosting-flickering edges) I went thru the different super-scaling options: FSR, DLSS and NIS-something or other... the FSR was the worst: it breaks the plane (from the outside) ... Also the clouds went into Lego mode:

Yeah, noticed that the old loadouts (in the Saved Games\DCS\MissionEditor\UnitPayloads) dont have the Fuzes: [7] = { ["CLSID"] = "{BRU33_2X_MK-83}", ["num"] = 3, }, Re-made a loadout and the new has "settings": [5] = { ["CLSID"] = "{BRU33_2X_MK-83}", ["num"] = 3, ["settings"] = { ["NFP_VIS_DrawArgNo_57"] = 0, ["NFP_fuze_type_nose"] = "M904E4", ["NFP_fuze_type_tail"] = "M905", ["arm_delay_ctrl_M904E4"] = 2, ["arm_delay_ctrl_M905"] = 4, ["function_delay_ctrl_M904E4"] = 0, ["function_delay_ctrl_M905"] = 0, }, Tthats a single pylon with 2x Mk-83 bombs..

Yeah, something like that we also assumed. But to not show that someone is locking you up, regardless of who it is... Well, early access is what it is.

So, we had a multiplayer co-op sortie, and on rejoin as I Boresight locked my flight members up, they didn't get any warnings on TEWS. They did have F-15 NAILS (from me) when I dropped the lock and some AI-MiG-25 NAIL:s far off to the east. no track, it's huge, but a short video here:

Noticed this today also. Only affects the R-CFT (pylon 4 I guess) and the "MK-84 * 2" as Starfire said.

Hmm, dunno what happened, cheers.

Related to mission 7 - Rock waypoint (wp2) was not in the position where the bullseye was on the map. is this as planned? As such, the ROCK bullseye calls were way off if WP2 is set as A/A point.

Happened here as well. Skippig the mission, and first time flying the M05, completed succesfully, and then I got completion on M04. Community A-4E-C, Blackhawk and T-45C installed in saved games.

Wow :D

Cursor enter.

Yeah, well RMB pulls them

Two of the right-most volume knobs cannot be turned with mouse click and dragging. Happened to me at least on multiplayer and local mission, where I'm a "client". I just re-tested on single-player (Instant Action - Ghost Farp) and there I noticed that right-clicking the knobs they're raised. But still they dont move when click-n-dragged. Left clicking the knob pushes it in. Maybe that somehow conflicts with the function. They must be turned by using the mouse wheel. VCR Volume Control Knob And the ADF Volume Control Knob:

It doesn't some much get stuck, but it looks like the cursor position value has no boundaries. The cursor icon stops at the edge of the screen, but the position value goes further. It just (for example if the center is not "centered" and it keeps on creeping ..) goes WAAAY WAY WAY FAR out of the screen and it takes forever to slew it back. Faster to swap the screens back and forth with the button. Somewhat easy to reproduce, even if your axis would be centered. Just move it further out to left for 10 seconds. Then move it back and see how long it takes. My feeling is that takes the same amount of time.

Yeah, I got the error also, DCS crashes to desktop hard on init. DCS.exe process stays behind and have to kill it. Error was: 2022-03-18 14:41:21.624 ERROR DX11BACKEND: Shader "/shaders/deferred/ToneMap.fx" failed to compile. Reason: warning X4717: Effects deprecated for D3DCompiler_47 C:\shaders\deferred\ToneMap.fx(94,14-29): error X3004: undeclared identifier 'TONEMAP_FLAG_NVD'

This could be added to the default controls. ROLL A/P has it, why doesn't the PITCH have it?

Thanks, Just took a peek at the Viper threat-tables, and they have less rows. It's missing the ones that are in the tables by default, is it on purpose? EDIT:: Also the order of items is different! You're making it hard on yourself to keep things up-to-date, man!

GREAT work on the lamp of the Finnish Hornet! Thanks! You could work with Kapsu to correct the colors and the weathering of the Finnish skin. Maybe share him the PSD-files? Since, well, it seems you approriated some of his work in this one?

Yes I tried restarting - didn't try other servers.

Installed v6 of the Smoke Mod. Connected to Blue Flag Syria. Sitting in the "lobby" I had no problems. When I selected a hornet slot, it kicked me out with a "A Pure Client Required" message or something.

I'm guessing zoomed/up-scaled text on 4K screen?

Here's a list of the Warnings and whatnots: http://vbf12.proboards.com/thread/2703/dcs-18-emergency-day But.. it seems to be lacking the P/INS and HEAT advisories..

Yeah, if you currently select NAV and IFA immediately/right after starting the GND (or any time before the CV/GND ALIGN is completed) the system isn't aligned, and (needs to start) starts the IFA from scratch. Just wait the 90 seconds.. It runs by quickly if you input a few aypoints manually and configure e.g some ground munitions. Then when the HSI says "0,5" and "OK" you switch to NAV and then IFA right after. IMHO Currently, in game, the STORED HEADING doesn't "drift" more. It just aligns the system faster, since the position and heading of the aircraft are known at start. When shutting down for repair, it might cause issues if you use when restarting after repair... I'm not sure how it is modelled. To work around the issue, connect ground power before shutting down. IFA (GPS aided) works around any (over time) drifting issues there might be.

Rapier and HAWK are in H1, HQ-7 is not in any Class currently.

Track attached: HARM-TOO-Classes.trk (game version 2.5.6.54046 ) Issues: SA-2 not included H1 HQ-7 not in either H1 or H2 EDIT: not in track, but if you shoot the HQ-7 Search radar, and the launchers must use their radars individually, they show up as "7", and it's not in any Class either.