_SteelFalcon_

@BIGNEWY is there any news about this? It‘s been a while and despite being listed twice as fixed in OB patches (2.8.6.41066 and 2.8.3.37556) it still is bugged. The feature symbology is useless like this at the moment. tracks should be sufficient in this report

3440x1440, native resolution for perspective, this is what i spawn in with: Pressing num Enter doesn't do anything at all. For demo purposes, i saved this cockpit angle: [13] = {--default view viewAngle = 139.307022,--FOV hAngle = 0.000000, vAngle = -11.868116, x_trans = 0.078730, y_trans = 0.088201, z_trans = 0.000000, rollAngle = 0.000000, cockpit_version = 0, Now my original snapview viewangle would be this, and i used to get there by pressing num+enter [13] = {--default view viewAngle = 109.334396,--FOV hAngle = 0.000000, vAngle = -11.868116, x_trans = 0.078730, y_trans = 0.088201, z_trans = 0.000000, rollAngle = 0.000000, cockpit_version = 0,

either or, both work.

With latest OB patch, the viewAngle seems to reset everytime the game is restarted. RAlt+num0 to save the position works temporarily, but the saved view angle is gone upon restarting the game. head position isnt affected, only view angle for the default view. tested with F-16, F-15E and F/A-18 tested with disabling all mods, still happens SnapViews.lua has the saved values however the game doesnt center on the viewAngle when centering view [13] = {--default view viewAngle = 109.316222,--FOV hAngle = 0.000000, vAngle = -11.868116, x_trans = 0.078730, y_trans = 0.088201, z_trans = 0.000000, rollAngle = 0.000000, cockpit_version = 0,

Same observations here, yes

Almost feels as if the pod is staring at and fixed to a point in the sky instead of being stabilized on the ground after a certain distance, in area or point track. Not so in INR when CZ‘d staring at a Steerpoint for some reason

Does it work if you are in Nav mode and set the radar to GMT + TGP to A-G? i can‘t test atm but i‘d be curious if it works

still works fine for me

or use DTOS, designate with helmet/hud and then refine with TGP.

so it is intended that all DL info is lost once the radar detects a contact that was previously provided with DL and already marked as either friendly or hostile? seems weird

So no more nose fuze to deploy the submunitions instantly to use the weapon below 1500 ft?

sorry if off topic, but since we're talking about the same manual, please consider this part in that manual again precisely, specifically line 2 under the EO delivery with TGP part of what exactly the MBC does take control of. something something missile SLEW... And if the MBC is the only thing that can take control of the seeker, why does VIS description state that missile is slaved to the TD box? - if nothing can take command of the missile seeker in VIS prior to designation, how does the LOS magically sync with the TD box upon designation? - if nothing can take control of the missile seeker in VIS prior to designation, why is it moving on the WPN page instead of staring straight ahead? - and if it should be moving prior to designation, why is no LOS circle displayed on the HUD"

the manuals are rather clear about that and state "slewed or is tracking" They dont mention a specific "slew-mode". and since they state "slewed", i'd expect the LOS to appear when manually selecting WPN page as SOI and SLEWING the mav seeker, even prior to designating anything. Yet in DCS no LOS is showing. And since the parts on page 400/402 in the EA manual is basically word for word out of a specific manual, I'd be curious as to what you'd wanna change about that when reviewing it to be honest.

logs are usually here: Saved Games\DCS.openbeta\Logs it might only be called DCS instead of DCS.openbeta depending on if you use the beta version or not. look for dcs.log in there

remember for full alignments you must confirm LAT/LONG on the INS page within the first 2 min of starting the alignment, else it wont align properly

@BIGNEWY / @Lord Vader thanks for looking into this. i struggle with understanding the feature in the following part: Good. but then: Now my struggle with this is: when I dms down to make the wpn page SOI without prior designation, I can slew the mav. Is that now Slew mode or Slave? Because I am clearly slewing the weapon around however no LOS circle shows. I can understand the behavior if VIS mode is active, the TD box has not been moved and is sat on the FPM. Then it makes sense to be slaved and not having the missile LOS as to not cramp too many things over eachother on the FPM making it hard to see through. but moving the TD box with HUD (TDC slew) or with HMCS entered by pressing TMS Fwd Long, we are now clearly slewing the TD box. We can clearly see the maverick seeker move around on the WPN page too -> the missile seeker is therefore slewing. So if the LOS is shown when Slewing OR Tracking, it should show up, regardless of a designation has yet been made, as described by you and by manuals that mention LOS to show when slewing or tracking. edit: this generally brings me to the question of „what does it mean when it says ‚is slaved to the hud td box‘?“ does it mean the missile will try to match los with the td box at all times also while slewing? is „slaved to“ and „slewing“ in this context mutually exclusive or do they co-exist? as in: If i slew the TD box and the missile is SLAVED to that box, does the missile, which is moving around when the TD box moves due to trying to match LOS, in fact SLEW? Or is that not considered slewing?

@Lord Vader Your description does not precisely match that of manuals regarding HMCS operation for EO VIS Mav employment. -> TMS fwd LONG will move TD Box to HMCS But to the OPs Bug report: A reference can be found in a manual, that the LOS of the missile is shown when she's slewing or tracking And if the TD Box is on the HMCS, it is clearly visible on the WPN page that the missile is slewing. Yet the Mav LOS circle is missing in DCS at the moment. Same applies when I'm not using HMCS but HUD only. slewing the TD box without designating has the Mav LOS circle currently missing. AGM65D_VIS.trk

Do it in the air. Recent changes made it so that boresighting at too close ranges creates a parallax effect when looking further distances than you boresighted. I usually do about 7nm

you can save the track replay after flying if you click „save track replay“ on the debrief screen at the end of a songle player mission. Reproduce the case in flight, when done hit esc, press „quit“ and you are on the debrief screen

Yeah, if you place a waypoint down, it‘ll most likely be a „fly over point“ and default altitude of that is roughly 6500 feet afaik. As furiz said, check the altitude of the waypoint. in the ME, if you set the altitude to 0, it will automatically then correct it to grond level. in the jet however, if you just set it to 0, bombs will fall way short, so there check the elevation your tgp gives you and enter that for your STPT elevation (or read it off the f10 map in the top left corner next to the coordinates)

Nice, however if you dont‘t provide a track replay from those situations, so ED can easily open the track to reproduce this, it might not be looked at. you can save the track replay after flying if you click „save track replay“ on the debrief screen.

I think that‘s the low alt warning height. Press 2 on the icp and change the ALOW value

glad it helped

check your slew deadzone on the RDR cursor axis, maybe it doesnt properly center and thus instantly engages ACM Slew mode.