Moonshine

You have to place the unit, set its waypoints as desired, go to wp 0 and set its speed to anything other than 0. should work in SP and MP. if you dont want the tank to be moving, still set its speed at WP 0 to like 20 or something. Have not tested that however. Maybe @Flappiecan explain in more detail i do believe that idle vehicles should give off less of an IR signature than a driving one, however, currently they pretty much match the exact color of the surrounding terrain and that does seem hard to believe. Plus on IR, exhaust should be visible, giving away its position to some extent i mean, IR is even used to find missing people in terrain. And compared to a tank in DCS, the infantryman is literally glowing

this might be due to the current lookdown penalty. this is being reworked first for the hornet. the changes there will then be transferred to the viper. known issue, read more about it here:

i hope you dont actually mean autopilot but the automatic waypoint change by this. in order for the jet to fly along the route, steering select and either altitude hold or attitude hold needs to be turned on. these are the only "autopilot" switches there are. the other is just so it automatically switches to the next waypoint upon passing the currently selected one. this in combination with the actual autopilot will make the jet follow the route. otherwise youd just be turning circles around the selected steerpoint

interesting, guess i will have to do that in the future as a workaround until its properly done.

in addition to Tobias tracks and screenshots, here are some screenshots and the track of a short test showing the IR signature of T72, T80 and T90. all of the tanks had a waypoint assigned, so the were not stationary from mission start but had to drive a short way to get to their final location.Tank_IR_signature.trk even then, i do think the IR signature to be off by a lot, given that they can barely be distinguished from the surrounding grass and road, no exhaust smoke etc. also note by the TGP position indicator, i was basically above the targets when i took the screenshots, spotting those from far away (20-30nm) is pretty much impossible without massive amounts of luck i think its self explanatory at this point.. then here is a track showing the IR signature of Map objects on PG, especially civilian cars compared to actively driving enemy vehicles: PG_Map_objects_IR_signature.trk T72 TV mode: T72 WHOT: T72 BHOT T90 TV Mode T90 WHOT T90 BHOT T80 TV T80 WHOT T80 BHOT Tank_IR_signature.trk

yeah i wish id get paid to do that not to speak of all map objects with this issue that are not selectable / placeable from the ME but rather are "built in" as map objects this comment shows it nicely, despite using arguably the pod with the clearest image there is in DCS: https://forum.dcs.world/topic/322449-fix-it-or-remove-it/?do=findComment&comment=5185516

exactly my point, and please, no "need evidence" comment, there is vast amounts of posts showing these things

As stated before, there are no hard feelings about losing TV mode for the benefit of a proper LANTIRN implementation, however at the moment a large portion of map objects on all maps (stationary civilian cars, street lamps, windows of buildings and many other things including placeable static objects in the ME) all light up like a big heat source, especially in comparison to actual running vehicles with hot engines. which to me is a concern if all we can use is IR imagery on a pod. i would appreciate if ED would bring those things in order BEFORE implementing the changes to the pod as that will significantly limit the viper, despite having „corrected“ the false lightening implementation (which i do support) if the ground stuff would show up with correct heat emissions, not many would be mad about the change of the pod as we would not lose any capabilities. however with these things in place youre not going to find a truck in a small town only using FLIR, hence really crippling this module to a point where a big part of its core role is pretty much unuseable. I hope you are aware of that

Still more info needed?

yeah not a viper issue. several maps have incorrect or not functioning ILS for years now, especially on PG. they have been reported for quite some time but you know how it is.. reference:

ILS is not on for inactive runways. the active runway is determined by wind direction as its set in the ME. if the airfield has only one ILS approach direction and the wind is not in favor of that approach, no matter the time, no matter the weather, ILS wont be active currently. probably another thing ED should consider changing.

Well TV will be fully gone, which is fine and realistic. Dont know how much thst could impact FLIR quality

if you look closely in my post above, i did give ranges at which I usually get a decent boresight for my mavs (mostly using H or K variants lately). for D and G the range might be a bit less due to poor image clarity. however, if you choose a very distinguishable object (like one house that is standing pretty much alone) it makes it easier because the mav then does not lock the stupid street lamp next to it that you cant see yet or any other nearby structure. so boresighting on an object in a city or town isnt that smart. Playing with the gain and the contrast does it for me (usually turn it down couple clicks on the rocker switch and the image does improve for me) what i dont know is the effects on image clarity of user specific graphic settings, quality of monitor people have and for the sake of it, how good your eyesight is.

no, LANTIRN does not have TV mode. while im not opposed to have LANTIRN modelled correctly and therefore losing the TV mode, in the current state of the FLIR where static map structures etc are significantly brighter than a running vehicle on the FLIR, TV mode is the only one that is actually useful for finding stuff. Losing that before the FLIR is properly done on ground vehicles and objects (or the SNIPER pod is available as alternative) will not do the module any favors.

Cant wait to not have TV imagery anymore, especially with how FLIR currently is. Good luck finding stuff I hope both pods will be available in the future as the block 50 viper from the air national guard did get Lightening II pods as of 1999 https://www.af.mil/About-Us/Fact-Sheets/Display/Article/104571/litening-advance-targeting/

just did some quick googling, CM designation is a CJ that got a CCIP upgrade. so it should be a thing in both versions, currently not implemented along with lots of other datalink stuff

you have got a point. interestingly and i think this is NOT modelled in DCS at its current state, is the quote about coupling the needles to get guidance to that (i assume OFLY) markpoint he set (as in, surely you cant make one with the hud and neither with the TGP or AG radar as you cant see a thing until he basically flew over the runway, so OFLY seems logical). might have to dig in some manuals i believe the function we are looking for is called "command steering" (ILS Flight Director). the use of the Horizontal and Vertical Steering Bars is not only for an ILS approach but also for example used in LADD and CCRP loft according to some manual that should not be named in the forums. so having ILS on would provide guidance using the needles for course deviation on a CCRP loft for example. while "CMD STRG" is shown on the DED, it can currently not be activated/deactivated using MSEL (0). maybe one day it will be implemented

no you cant. ILS (the system) is a beacon (well several beacons) on an airfield. the ILS has two main components - Localizer, - Glide path/ slope. The localizer gives the aircraft lateral guidance. It tells the pilot where the centre of the runway is, by signalling the pilot to move either to the left or to the right through a cockpit instrument (vertical needle) The glide slope or the glide path provides the pilot with vertical guidance. The glide slope is set such that a glide slope angle maintained by the pilot. The horizontal needle of the slope moves up, if the aircraft is too low and moves down if it is too much above the required path. the method described here in this post is a "makeshift instrument approach" (this is NOT ILS, you wont get any needles to help you) for an airfield that does not support ILS guidance. by creating different OFLY markpoints at specified altitudes you can create a makeshift approach by then flying along the set markpoints using your instruments only. the aircraft setting those markpoints in the first place will likely have to go around

Well it is broken. When you try to make a markpoint and your TGP is SOI, the option „TGP“ under the MARK page in the DED is available. Using dobber right to step through the different MARK options does switch to FCR, HUD, OFLY but the TGP option does never show up again, thats what’s currently broken. and if the TGP is not available at all, chances are you do not have one on the jet or the hardpoint isnt powered

is reported here:

not sure if this is correct or not; currently with every sensor pressing TMS aft will CZ the SPI back to the selected steerpoint (works with TGP and even HUD for example) however, for the AG radar, TMS aft does not CZ, you have to press the OSB on the MFD. is that intended like that? AG-Radar_TMS-AFT_not_CZ.trk

then you get substantial parallax effects when trying to lock a target at longer ranges..so i suggest finding something between 5-9 nm away for boresighting purpose

yes ground alignment still is possible, you need to enable ground jettison in order for it to work. also it is rather hard finding something far enough away for a reasonable boresight when on the ground, so while still possible i question how useful that is. not often that you stand somewhere with nothing in front of you for multiple miles for a decent boresight distance, hence why aligning it in the air seems more practical. i personally use some sort of house along my route to the target to get a good boresight. using TGP in snowplow mode helps you find things easier in front of you. alternatively if i cant find anything along my route i might just do it on the first target before firing the missile. or use your buddy - fly trail for some miles, does work as well

You can by using an OFLY markpoint. from there the GS can be held using the OFLY wp as a reference. also remember, the one setting the OFLY markpoint had to improvise all the way to even set that point for the others to then follow and make use of it. by setting multiple OFLY markpoints along the descent you can improvise a glideslope, so the following planes just fly from markpoint to markpoint at a given speed Edit: since creating OFLY markpoints sets them at sea level (MSL), youll have to change its elevation to the desired value manually, so they appear at the right position in your hud