Moonshine

here are some tracks showing the "cold-at-start" option, one BTR on the tarmac, one in the grass next to it. compare those units with the static map units as they are placed per default tested the following scenarios: - Summer, 20°C daytime - Summer, 20°C nighttime - Winter, 0°C daytime - Winter, 0°C nighttime did not test spring and autumn, should not be needed though. what i observed: during winter, obviously there is snow on the ground (at least on Caucasus). this makes it easier to pick out even cold at start vehicles. during summer, at times it is near impossible to find them as they really blend in with the exact same color as the background has unless you already know where they are (like in this scenario, the waypoint is directly on it, hence easy to spot) HOWEVER: in all of those scenarios, the static units next to the BTRs i places are BY A LOT easier to find winter_cold-at-start_night_0°C.trk summer_cold-at-start_night_20°C.trk winter_cold-at-start_day_20°C.trk winter_cold-at-start_day_0°C.trk

Upon designating a target with the tgp either in area or point track, no matter how accurate you put your crosshair, bombs consistently fall short towards your ingress direction. Also check the linked post. There is enough evidence and you can assure yourself that i do in fact use the pod correctly yes they drop accurately on markpoints etc but i should not need to make a markpoint for every target i want to hit prior to releasing the jdam.

they are accurate if you drop them on a set waypoint however they are not accurate if you drop them on a point track location designated with your TGP

yeah then again there was nothing in the patchnotes about that being fixed. i hope it wont take until the end of the year. kinda makes precision bombing useless unless its laser guided... and its been a couple months broken now

Strictly datalink. it indicates a friendly targeting a as hostile identified ground unit. however there is no way the player can currently do that. I have no idea how and why those things are displayed since at this point in time, sharing ground targets via DLink isn’t implemented. Yet if you fly even just the Nevada takeoff mission of the viper, there is some A10 doing ground attack and at times white or red dashed lines from their plane to the target they are engageing is shown on the HSD. All DL information.

did the test as described by skippy (clean viper, full fuel, 2 wingtip 120, clean mig21 full fuel). does not seem to be too much of a problem (ACE AI to guarantee he cheats). the only thing in the AI behavior that was rather surprising is that after some time in the 2 circle on the deck he decides to slightly climb while maintaining the rate fight without any noticeable loss of speed. Mig-21_rate-fight.trk Tacview-20230415-091634-DCS.zip.acmi

I think he isnt talking about SAMs but more about datalink functions in sharing target information. just like you can see a flight member targeting an airborne contact (indicated via dashed line), in some cases such things are shown when a friendly is engageing a ground target. (green dashed line, small red triangle at the end of it indicating a datalink contact - no, not an aircraft symbol, a little smaller than that.)

This. Symbols stack on top of eachother and TGT step doesnt make a difference in many cases. This also occurs with RWR priority mode enabled to limit the amount of displayed emitter. Its hard to believe that this would be according to the manual

@Raptor9 Not initially (shouldnt be needed for air threats..). I started pressing the buttons to see if that could solve the issue. To no avail edit; replayed the track and took control, tried with search enabled and search disabled, does absolutely nothing so unless the Ai is that good to know exactly where i am without using radar first (and having no DL or other help) and then instantly turning on the radar AND fire in the same milisecond, then something is very wrong also in this track you can see the missile is already couple seconds on the way until my RWR detects anything at all and im not using any mods search-enable-disable.trk

@Lord Vader The bigger issue i see in the described situation is that i do not even get nails up until the AI fires the missile, only then the symbology pops up. Even if he TWS shoots me, the RWR should detect nails as his radar has to paint me in order to guide anything. And that is what i would say is clearly wrong. thanks for looking into it to be more precise about this in order to acquire a valid TWS track, the radar has to paint me first for some time, means my RWR will detect that emission as nails PRIOR to missile launch (unless he is in my RWR blindspot which he clearly isnt), no matter in what mode the missile is then finally shot. the current behavior however does not even give me nails until the missile is already on the way towards me. seems funny, it isnt a heater and needs radar guidance (either the jets radar or the missiles own seeker) in all cases. instead it goes instantly in a STT and my RWR warns me about a missile fired in STT (given the absence of "M" just the flashing 14 indicating a STT launch)

did some tests after the recent rwr update. in some occasions i observed that i get no nails, no spike but an instant launch warning, see tracks attached. the no nail no spike to instant launch warning seems to occur with late activated groups, here tested with a tomcat but also observed with mig29. more specifically late activated via trigger, not via timer. then specifically with the F-14 when it is not late activated i do get nails however if you compare the range to the track where i tested it with the viper, the viper shows up as nails much earlier. seems weird comparing the strenght of the radars of these planes. i also never get any spike by the tomcat. fair he might launch in TWS. but then why do i get an instant missile launch warning if he shoots in TWS? and if its the missile going active that early, why is it flashing "14" instead of "M" or "U"? also i only ever get one RWR indication but if the missile goes active that early i should get the tomcats ownship (14) and the missile (M) on top - so two RWR indications... something seems to be very odd. f-14_late-activate_no-nails-or-spike.trk f-16-late-activate_nails-and-spike.trk f-14_no-spike-instant-MSL-warning.trk

about 3 months ago i moved from a VKB Gunfighter MkIII Ultimate joystick to a FSSB R3 and it indeed does make a difference. more instant reaction to any stick input, much less sluggish feel, overall a better flying experience. i was always hesitant to make that step as it is quite an investment and i always thought "it cant be that bad". when i finally did it, the difference however was very noticeable right off the bat.

I know youd use them for pop up attacks primarily to get visual references in how to fly the pop up, even that is bugged, see my referenced post. As i said, there might be multiple use-cases. whether its the „correct“ way of using them like in wags video i beg to differ and wouldnt use it like that myself. However for some reason he made a video showing this exact method in which case ED might have info about this type of use and if its clearly wrong, then that video would be better removed since it causes confusion either way its not working as it should since even for a pre planned pop up attack, the OA1 triangle is not at the correct height.

also, dont waste your time on it, in the current OB its broken (again). location of OA doesnt save. @BIGNEWY can this be moved to bug-reports? goes alongside this bug, which is already reported: did it according to Wags video and this currently is not working (watch towards the end where he designates OAs with the TGP): Track: OA_does_not_save_position.trk

there are multiple use cases for OAs you can get launch and steering information to OA1 and OA2 by pressing Left MFD OSB 10 (or right, depends on which MFD you have the sensor on) on either the tgp or the FCR when in AG master mode. so yes you could designate 3 different targets like that

yeah youre right, 25 is the highest you can go for OA.

yeah i agree i hope the mission planner together with DTC will bring much needed improvements for actual mission planning

the CombatFlite tool can help you with that. however it takes some time to get used to that tool. however pretty handy to coordinate larger scale missions.

this

nice

you forgot to turn on "GND Jettison" as you were still standing on the ground.

of course its not the same. but to visualize the offset in mounting position on the jet and therefore explain the parallax it creates, it might help

declutter your HSD. or select AG radar or TGP then the selected steerpoint will have a bigger "crosshair" on it, indicating the SPI