guitarxe Posted July 1, 2024 Posted July 1, 2024 In the manual, on pg 245, it is described as follows: [quote]Laser Type. Pressing this pushbutton cycles between laser types: MARK (target designation laser), PTR (infrared pointer, used to visually point out targets at night), and BOTH.[/quote] However, if I push the OSB above the words "MARK", it simply boxes it and unboxes it. It does not seem to cycle between the modes "MARK", "PTR" and "BOTH". Is this something that is not implemented in the Hornet? I know that in the A-10C you can use the Lightening II to point targets with an IR laser, so I thought this was the same for the hornet.
Foka Posted July 2, 2024 Posted July 2, 2024 I guess it's not implemented. In ATFLIR pressing MARK sets Marpoint.
guitarxe Posted July 7, 2024 Author Posted July 7, 2024 Oh, not implemented yet? I thought the Hornet was out of Early Access? Anyway, since it works in A-10C, how come it doesn't in the Hornet? It's the same pod, isn't it? Just curious.
Muchocracker Posted July 8, 2024 Posted July 8, 2024 (edited) 2 hours ago, guitarxe said: Oh, not implemented yet? I thought the Hornet was out of Early Access? Anyway, since it works in A-10C, how come it doesn't in the Hornet? It's the same pod, isn't it? Just curious. They have nothing to do with eachother but use the same models. The programing that makes all of the systems/interfaces/functions happen individually for each module. Edited July 8, 2024 by Muchocracker
guitarxe Posted July 13, 2024 Author Posted July 13, 2024 Okay, but outside of DCS and the context of coding, this is the same pod, right? And since this feature exists in the implementation that they have for the A-10C, but doesn't for the Hornet, then it should be reported as a bug, right? Because the Hornet is out of Early Access now, so features like these are expected to be all implemented, this is why I'm asking about it. I guess it doesn't matter very much since you should be using ATFLIR most of the time instead, but still important I think. I read some other posts on the forum that mention that ED Team used a Spanish version of an older Lightening pod that supposedly didn't even have MSI. So if that is true, and if that pod doesn't have this feature, then I guess this would be considered correct in terms of what they modeled it against, but they should at least clarify that somewhere, at least in the manual. There are stuff in the manual that say things work one way, but then in DCS they don't work that way, and it drives me nuts. What is the source of truth?
Muchocracker Posted July 14, 2024 Posted July 14, 2024 (edited) 16 hours ago, guitarxe said: Okay, but outside of DCS and the context of coding, this is the same pod, right? The implementations, interfaces, and functions can be wildly different from aircraft to aircraft for the same pod. What it does on one does not mean it does it on the other. 16 hours ago, guitarxe said: And since this feature exists in the implementation that they have for the A-10C, but doesn't for the Hornet, then it should be reported as a bug, right? Because the Hornet is out of Early Access now, so features like these are expected to be all implemented, this is why I'm asking about it. early access does not mean every single feature is implemented. Go read the features list and it spells out many items coming after early access. That isnt even the metric for what is a bug in the first place. That is expected function and features using the proper documentation vs the actual. If there is something wrong then it needs to be cited with sources. Edited July 14, 2024 by Muchocracker
Recommended Posts