-
Posts
717 -
Joined
-
Last visited
-
Days Won
1
Content Type
Profiles
Forums
Events
Everything posted by Santi871
-
DCS: F/A-18C Features Roadmap for Early Access
Santi871 replied to Kate Perederko's topic in DCS: F/A-18C
Jamming AOTs do show in az/el atm. I reported the missing RWR, L16 F/F and SURV tracks before az/el was released... so I suppose you can consider it reported. -
Fixed internally
-
[FIXED INTERNALLY]RWS Bricks act like trackfiles
Santi871 replied to Beamscanner's topic in Bugs and Problems
Now it's actually fixed internally -
reported Vertical Acq scan elevation incorrect
Santi871 replied to Jak525's topic in Bugs and Problems
Reported -
investigating A-A radar does STT incorrectly in Openbeta 2.5.6.60720
Santi871 replied to Bear21's topic in Bugs and Problems
Are you talking about the LAR not appearing in STT in the radar page? If so, that's already been fixed (internally) -
investigating A-A radar does STT incorrectly in Openbeta 2.5.6.60720
Santi871 replied to Bear21's topic in Bugs and Problems
Could you try increasing the aging time setting on the top right of the data menu and seeing if that fixes your issues? The setting is currently tied to trackfiles getting deleted so it might help. 4 seconds is low. -
Looking at this made me realize there's a bug: breaking out of FTT or GMTT with sensor control switch (not undesignate) should not undesignate. So it should be possible to break radar track while the FLIR stays at the last track point.
-
reported Radar Scan Elevation locked in RWS after using TWS
Santi871 replied to RED's topic in Bugs and Problems
Reported, thanks -
reported earlier Same FLIR handoff problem for FTT
Santi871 replied to LastRifleRound's topic in Bugs and Problems
This is as designed. If the radar is in a tracking mode it will drive the designation and for another sensor to drive the designation, track needs to be exited. The same "should" happen with the FLIR in tracking modes but don't think it's modeled correctly right now. -
investigating AUTO bombing mode and GMTT
Santi871 replied to Hetzenauer999's topic in Bugs and Problems
For FLIR, a MV TGT option needs to appear while tracking and that needs to be boxed for AUTO to calculate lead. But it's not modeled. For GMTT, I need to look into it, not sure off the top of my head. -
Yes, it does.
-
Oh, I see a possible cause. It seems your startup flow might be so quick that the aircraft hasn't properly acquired GPS when you move the INS knob to IFA. IFA RDR starts for a brief second and nukes your current alignment, then GPS acquires and it goes straight into AINS with a shot alignment. You can check in HSI/DATA/AC. GPS horizontal and vertical error are 0 feet until GPS acquires and gives you actual error values. Also once GPS is acquired you'll get a NOSEC GPS option at PB2. I'll check if there's any advisories about GPS not having acquired but IIRC there are not. tldr: slow down your startup flow
-
I'll report it. For some reason it doesn't happen to me other than in your track. Doesn't even happen if I do the alignment a second time. Are you able to cause it if you start alignment after the left engine has actually started up?
-
[INVESTIGATING]Marking Target via HUD - Possible Bug
Santi871 replied to RoGaR's topic in Bugs and Problems
The behavior you described (-7.5 degrees or velocity vector, whichever is steeper) is how it should and how it does work for HUD designations. -
AzEl is an MSI display along with the attack and SA formats and as such, any MSI trackfiles - onboard, offboard or both - should be displayed. There is no question about this.
-
correct as-is first time AZ/EL selection on A/A master mode
Santi871 replied to Spectre1-1's topic in DCS: F/A-18C
Yep, I could reproduce this by exiting and entering a/a mode a second time. PS: please include a track next time (to OP) -
The current A/A mechanization ingame like RRSLV and such belong to older OFPs that predate things like MSI or az/el page entirely. The same OFP that introduced those things replaced RRSLV with L&S/BST/MSI track slaving. You can read about them in a certain wiki if you google them. By the time ATFLIR was introduced things like RRSLV were long gone.
-
Based on what I've read I wouldn't expect much of a difference apart from symbology, 3 FOV levels instead of two, auto stepping FOV when max/min zoom is reached and different and better A/A mechanization/modes (which is a function of OFP but by the time ATFLIR was introduced the old mechanization which is currently ingame was long gone). Would be surprised to see any NAVFLIR stuff considering it hasn't been used or trained with in a very long time, and if it was ever used it was for a very short period AFAIK. I'm not even confident the NAVFLIR still appears in any documentation, all that I've seen seems to completely ignore it.
-
Yeah, that's part of it. It has a prioritization scheme more complex than but similar in nature to the Tomcat's.
-
The actual aircraft does optimize the centroid and azimuth/bars setting to keep as many tracks as possible in a similar way to the Tomcat.
-
AACQ was updated and works correctly now, but it is missing bump acq (AACQ while in STT).
-
this one's been reported already
-
[CORRECT AS IS] JDAM TOO (WPDSG) weird behaviour depending on QTY
Santi871 replied to AstonMartinDBS's topic in DCS: F/A-18C
Yes, when QTY in TOO is set any change to the TGT designation will change the target in each boxed station.