AvroLanc
-
Posts
1346 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Posts posted by AvroLanc
-
-
Anyone been able to confirm these bugs?
I’m holding off on the update in case the Apache is broken…..
-
1
-
-
1 hour ago, Snappy said:
Not how I interpret the manual. What you wrote applies if you put the inner FD knob (of the mode selector knob) to HDG. With both the mode selector knob and the inner FD knob set to VOR/ILS I would expect guidance onto the selected radial or ILS localiser course, unless of you are outside of reception range of the tuned ground station, which would be an exception.
Yep, you can get bank steering guidance on the ADI to the selected radial, but you also must use the HEADING SET knob to set the command course.
Direct quote from HB manual:“The HSI Heading Set knob is used to set a desired TACAN course for bank steering presentation on the ADI. As the bank steering is based on the heading marker position, if it is not set properly, bank steering on the ADI will not be correct to intercept the desired course”
Go try it. It works.
-
14 hours ago, IvanK said:
See attached jpg. I am on the selected VOR course but the FD is giving me a fly right indication ??
You need to set the command heading to the same radial/course (with the HEADING SET knob). The FD will only give correct commands with a suitable heading set.
-
+1 This has been mis-implemented since release.
The ARBCS modes have serious flaws that need investigating. It gets worse when you combine a LABS/ARBCS mode with WRCS/OFFSET. The warning tones and functionality are missing. Problem is....it gets VERY complicated single pilot to set up and reproduce in a track.
Bit frustrating since it was claimed all weapon delivery modes were to be working at release.
-
On 10/1/2024 at 5:38 PM, Tango3B said:
Yup. The new engine sounds are definitely a step back. While they were actually intended to create more immersion they really do not. Now, on my end at least, it sounds a bit like the famous "J-79 Dyson edition". Especially the quite immersive revving howl isn´t there anymore, which is sad. Maybe something has gone wrong with the files HB submitted to ED for the update. As it stands, the old engine sounds were way better in my opnion...
On 10/1/2024 at 8:12 PM, IronMike said:Thank you for the feedback, we will take a look.
Yep, the new sounds are definitely NOT an improvement. I miss the old 'howl' sound. The old sounds need to make a comeback. This is a huge step backwards imho.
-
Oh and by the way…the yellow emergency manual release handle does work in the trap door position….so that’s cool. And the hook is animated.
There are also 3 ‘hook lights’ that are controlled from the same position. They work.
Unfortunately the radar altimeter doesn’t yet work.
Still couldn’t close the trap door, even holding the button. I’ll try again today. (I’m thinking now that playing with the emergency release lever may have blocked the trap door from closing?)
-
2 minutes ago, Slippa said:
I’ve opened and closed it with the same button.
Yeah, not working for me. The only button is a toggle - open/close. Maybe I bugged it out of sequence somehow.
-
Anyone worked out how to CLOSE the trap door?
I’ve got it to open and found the extra view position looking out of the trap door with a sling load attached…..but can’t seem to close the trap door again, once the load is released……
-
Nope
-
58 minutes ago, Raptor9 said:
This was already reported internally; unfortunately it was discovered during final testing right before the most recent update went out and we were not able to fix it in time.
In the interest of specificity, the bug isn't really about the activated PFZ as much as the fact that the NTS (and ANTS) are being designated immediately upon initial target detection within the first scan cycle. When a scanburst is initiated, the NTS, ANTS, and the entire target ranking process should only be finished when a) the first scan cycle within the scanburst has been completed or b) the scanburst is aborted by the crewmember in any way. As a result, currently the FCR is not getting a chance to complete its first full scan cycle and getting a full look at the entire scan volume (to include all targets inside and outside the activated PFZ), its just putting the NTS on one of the first targets it sees, and the entire ranking process is thrown out of whack. The bug doesn't affect the NFZs since those areas are occluded from the FCR page entirely.
But thank you for the report, in case others find similar behavior in the short term.
Thanks for your reply. Yes, I noticed that the NTS was being assigned immediately too, and suspected that was wrong. I couldn't fully assess the bug though in my limited time available to test, it was only clear that PFZ's are not working, despite being fine in the past.
It's actually super irritating that previously working features in this module are breaking with almost every patch. Admittedly it's complicated but I thought the new 4-6 week patch cycle was supposed to be an improvement.
Anyway, thanks for your explanation Raptor.
-
1
-
-
As of the latest patch BAM PFZ's no longer affect the FCR target priority order.
If you create an active PFZ, it should be the top priority for selecting the NTS target. Instead the logic seems to ignore the PFZ completely. This USED to work perfectly...........rather like C-scope used to. This patch hasn't been kind to the AH-64.
No Fire Zone's NFZ's, continue to work correctly.
Thanks.
-
9 minutes ago, corbu1 said:
This is very sad. C-Scope is one of the coolest features .
Indeed. Hopefully this can be hotfixed soon…..
There’s no point getting new features if they get broken soon after being introduced and then having to wait at least 6-8 weeks for a fix. Where’s the closed beta team?
-
Can 100% confirm here as well. They giveth and they taketh away. Super annoying.
Only the Shot-At and the ANTS symbols appear. NTS and all TGT symbols are missing.
-
I've been using the MK-20 Rockeye values. Works well enough.
Be aware though that you need to plan a higher release height than Mk-20's. The CBU-52 has a 4s time fuze in the nose. In RL the M907 fuze could be set between 4-92 seconds in half second intervals. In DCS we're stuck with just 4s for now. Hopefully ED will implement better fuze options. But in any case, the 4s will need at least 1200ft AGL for a level release or at least 4000ft for a diving release to guarantee a good bomblet spread.
-
1
-
-
28 minutes ago, Zabuzard said:
This particular one is fixed for the next patch, thank you
Thankyou. Hopefully HSI 'TGT' light too soon. Amazing job guys.
-
1 hour ago, Zabuzard said:
The most frequent user mistake I see is people flying the wrong airspeed, as they look at the IAS and not TAS gauge.
This is undoubtedly true. But I wonder if the ED ballistics is just a little too sensitive for TAS. I’m finding in particular that high drag bombs are EXTREMELY sensitive to errors in TAS and even a 5–10 knot difference from planned throws Snakeeyes and Ballutes significantly long or short.
-
For Offset and TGT FIND you can easily hop into the WSOs seat just prior to the VIP overfly to hit Freeze and Insert buttons. Hopefully Jester will be able to do this with a special VIP waypoint action.
-
1
-
-
Can confirm that this IS an issue. Clicking on the buttons with the mouse works normally, animation present.
However, when the MPD buttons are bound to a device, no animation is displayed. Can the ED testers please reproduce this bug with the buttons assigned to a device.
-
Yes it does work. The manual description is a little misleading. The pod can’t be slaved to a an absolute LAT LONG. What you’re doing is using TGT FIND mode and the N/S and E/W offset distances to define a TGT point with reference to either visual or radar offset point.
You can use the bombing calculator to calculate those offsets and have jester input them into the WRCS. I recommend you use a VIP first because the radar is a pain to use.
When over the VIP, as WSO press FREEZE and INSERT and if all set up correct and pod is in WRCS mode the pod will slave to your pre planned target. -
During OFFSET and TGT FIND bombing modes the TGT mode indicator light on the HSI should illuminate when the WSO 'Inserts' the target with his INSERT button.
However, this light doesn't illuminate, although the offset function does indeed work. It's just confusing not having the confirmation of the TGT light.
I can provide track, but hopefully that makes sense. Thanks.
(Actually the WSO's INSERT button should illuminate as well, but it doesn't, separate issue....)
-
Good luck.
-
1
-
-
Bump. This been broken since the Dec 2023 patch. Thanks.
-
1
-
-
Hi,
At some point a bug has cropped in where the LASE TIME REMINDER/INDICATOR on the TGP MFD is removed from view when the last LGB in the current program is dropped.
This obviously prevents the AUTO LASE logic to kick in at your set ALAS time, and also if manual lasing, the MLAS reminder is absent when this happens.
In my track the first of 4 bombs is dropped in STEP and the MLAS/ALAS indication is correct. I.e it remains.
In the 2nd pass I dropped the 3 remaining weapons and the MLAS/ALAS goes away. Forcing me to manual lase at 10 seconds TIMPACT, AUTOLASE would never kicked in if I had that selected.
In the past, the MLAS/ALAS logic remained until the weapon had impacted, even if it was your last LGB.
It's a VR track, but you can still view the issue.
Thanks.
-
If any new weapons are to be added, going with the 'variety' argument, I'd go with Maverick first. As the only Forward Firing AG weapon, they'd offer some different gameplay options and they are relatively simple. Otherwise, no, I think working on GBU-15/AGM-130 and Sniper etc right now would be a massive mistake. They'd take up a huge amount of dev time and the long term foundation of the module would suffer.
New bugs after 03/29/2025 patch
in General Bugs
Posted
Guys, are these bugs exclusively MP or SP as well?
How on earth do these things not get picked up in closed beta testing?