_SteelFalcon_

Instead of module-bound it is now in the UI Layer section and universally useable so you dont have to bind it for every plane separately

check deadzone too, maybe your ministick has some drift. i had to set a little deadzone on mine

Current OB, the MIDS filter for the FCR removes raw hits when set to NONE or TGTS. FCR Filter.trk

WCMDs count as IAMs just like the JDAM and IAM tossing is not yet implemented. So if you wanna toss CBUs, all you can really toss is 87s and 97s

should be, because the file is not in the "(...)/Cockpits/Scripts(...)" folder, which was specifically mentioned in the patch notes to be affected by the "new" IC rule "pure scripts"

cheers, glad i could help. enjoy this maginificent aircraft

dunno, especially not without the miz file or a track. thing is, after mission start, it takes about 5 minutes for the unit to actually heat up so it is visibly different than cold units. so you wont really notice if you air start right in front of the unit with the TGP already looking at it. the engine will heat up the vehicle but it does take some time, since even alarm state red units seem to start "cold" initially. but their running engine will heat up the vehicle soon enough i guess. in 2.7 i did a little test, see linked below. that's how it currently looks like. this is with the default TGP gain, contrast and level settings on a viper in WHOT.

Do you even have coordinates for the selected steerpoint? does the HSI show a red flag top left? even if you have aligned correctly (in NORM, dont forget to confirm the LAT / LONG / ELEV within the first 2 min by pressing ENT on each line in the INS page) if you dont have coords for the selected STPT, it'll show a red flag on the HSI

@NineLine can this be checked again? The early access manual states on page 162/163: „Positioning the switch inboard short (less than .5 sec) rotates between three filter options: • ALL. All symbols are displayed • FTR+. Surveillance tracks are removed • TGTS. Surveillance and PPLI tracks are removed Positioning the switch outboard short (less than .5 sec) selects NONE and removes all datalink tracks. Selecting outboard short again returns to the previously selected filter option.“ nowhere does it say that raw radar hits/bricks are removed. Only that datalink info is being removed depending on the selected filter. currently (at least on OB) it doesnt even display the raw radar bricks. But it somehow detects them anyway since you can lock non-displayed contacts on the fcr as demonstrated in my previous track with a little help using the HSD. i believe the bug currently is, that raw radar hits are not being displayed correctly when certain filters are active.

Currently if you want units to be „hot“, set their alarm state to „RED“ until that „cold at start“ bug is fixed. Then their engine is consistently running and thus heating up the vehicle. sadly tho, the statics still glow a hell of a lot more than red state units

track added. Is that really "correct as is"? note how despite the FCR not showing anything depending on the filter that i deliberately chose, i am still able to lock targets by using the FCR cursor symbology on the HSD as aguide to slew the FCR cursor over the targets (while FCR SOI). does the filter really only affect displayed symbology? why would one use a filter to "filter out" unwanted stuff, but knowing that if one is not precise enough with the cursor, it might still lock some hidden thing nearby? how do those filters work (besides the obvious change in displayed symbology)? Do they affect trackfiles at all? FCR Filter Target locking.trk

So you‘re saying that when filter is set to NONE or TGTS and i use the HSD symbology that shows my rdr cursor as a guide and move the cursor over a bandit (while FCR SOI) and TMS up, i can basically bug a target on a blank FCR page? That sounds funny

It is called comm switch IFF IN and Comm Switch IFF Out as far as i remember. Just type „iff“ in the search bar and they should pop up

it was "off" for me too, seems fine to me

Some more of this can be seen around the engine just aft of the tail fin, instead of a smooth round-ish look, it looks more like a polygon.

Because it was already reported by me and added to the report (also by me) for 2.7 not showing tail numbers. i suggest you start reading here:

So it‘s a 3d model issue, not necessarily the normal maps?

good catch, god that looks awful...

Sent you a dm

Well, by what it says on his path (mods/<aircraft>/cockpit/scripts…) matches with the patch notes…soooo…?

That was in the patch notes tho. New IC setting - "Require pure scripts" This is an optional setting that will block mods that modify files in DCSWorld/Mods/aircraft/<MOD_ID>/Cockpits/Scripts to prevent exploits. Servers that update to the new version default to set pure scripts to disabled, so server owners will need to opt in. If you are kicked for breaking IC on a pure scripts server you need to restart DCS before you can connect to any server again, regardless of that servers IC status

I see what you did there

Bort numbers show 000 no matter what is being entered. on the default livery and on custom ones with dynamic numbers enabled

nope, it's correct. you can easily find the explanation to how this works in a certain manual page 1-149 in short: wing/tail -> red and green lights on wingtips and inlet + white light at the back of the plane above the engine fuselage -> white light for tailfin illumination