This is my first post here, so hope I’m listing it in the correct forum section…I’m creating several navigation missions in DCS for WW II aircraft, and want to either disable the ability to mark your position on the kneeboard map, or capture when a used does this. Because there does not appear to be a trigger to capture this event, I’m hoping that maybe a lua script or something similar can do this. Any help or suggestions appreciated.
4 Likes
Is that ability an option, in UI? Not sure…lemme look…
And in the Mission Editor:
All I can think of off the top of my head, unless you mean something else.
Oh, and a little digging I found this:
From here: DCS Trigger
Now, I’ve not had the need for such so no experience scripting it. The word “panels” might mean something else. Probably not.
3 Likes
Will check it out. Thanks!!
2 Likes
Welcome to Mudspike - we have some pretty knowledgeble DCS Mission Editor gurus lurking about…so hopefully they can get you headed in the right direction. (Get it…direction…navigation missions…direction…)
3 Likes
No joy - those do not appear to be related to the kneeboard map marking function. Still looking (thanks)
1 Like
You bet. Let me know what you find out as I may find a use for it in the near future. Thanks ahead of time.
1 Like
The ability to navigate properly is something I really miss in DCS. If you could only mark the kneeboard map with where you think you are, rather than having a GPS tell you.
I hope you succede
Agree. I’ve built 10 navigation scenarios (VFR and IFR), and currently I’m simply stating in the briefing that marking the kneeboard position is “not allowed”. I want players to use only visual references and/or dead reckoning. But is would be cool if I could capture if they use the kneeboard marking function and create a ‘failed mission’ message. I’ve searched through the DCS lua files for anything relative to this function, but have had no luck. Worse case, I’ll just have to rely on the honor system - they’d only be cheating themselves anyway…thanks
1 Like
I’m with ya on this one. The code I’m working on now, well, to get around the limitations (Mission editor & Lua) I’m finding requires X5 more work to get around things the player (IFR) can easily ‘ignore’ (dealing with radio comms) so I’m ‘punting’ to a degree. Goal is to keep it, conceptually, accurate, if not literally 100% correct; the basic steps will be there, just not the exact phraseology and mechanisms.
I’ve been having an absolute blast with the C-101EB and C-101CC doing some good old green needle VOR/TACAN navigation in anticipation getting the boys up to speed. Just the other day I did a round-robin from Creech AFB (NTTR) up to Beatty, then down to the ILS 8 at Creech. My one and only wish for the 101EB and 101CC were that it would have an autopilot to go with that great flight director and ADI (looks like the old Sperry FD/ADI that we used to fly in our early King Airs). An autopilot I guess wasn’t an option in the C-101, but it would be a nice task reliever for concentrating on the navigation aspects.
2 Likes
When you guys (real pilot types) speak of “Green Needles” you mean, essentially, anything pre-GPS right? I’m not that familiar with the term (a deduction on my part).
Yeah, I don’t know what I’m doing but I prefer the navaid-to-navaid stuff (to include non-directional bits). I know in the real world it’s harder [than GPS stuff] but in my make believe world the old way is more satisfying.
Assuming they never get rid of ground-based navaids (first heard about that 30 years ago) it’s probably a good skill to learn?
I like to look out of the cockpit and see three to five features from which I can state exactly where I am. No point being entitled to the post nominal ‘FRIN’ if I do not navigate. Real world or a sim. If IFR then that is different but as in the real world I do not fly IFR just for fun.