JLX

Being able to save data/flags and read in following missions has been a wishlist item of mine for ages. If/when you get this working, is it something you'd be willing/able to share with the community? Sent from my SM-G930W8 using Tapatalk

This sounds fantastic! I'm going to d/l and check it out later today. Thanks for the effort and sharing! Sent from my SM-G930W8 using Tapatalk

My curiosity is definitely piqued and look forward to hearing what's coming down the pipe. But... I can't help but agree with this sentiment. I'm so eager for a finished/polished Harrier! DCS is a smorgasbord of tasty delights and I definitely want to indulge in as much as possible. However that doesn't remove the importance of chewing and swallowing before putting more food in my mouth. ;-) Sent from my MediaPad using Tapatalk

You don't seem to be able to manually put the TGP into PT mode manually by pressing the OSB button. However, you can get PT mode to work automatically (sometimes). If you slew over a target (and cross your fingers) it may identify it as a point target and automatically go into PT mode. Or, it may just stay in AREA mode. For me this has been unreliable and fiddly. When it does work and latches onto a point target, it will follow it's movement as one would expect. I've used LMAV successfully to hit these moving targets. Hopefully, the AR/PT OSB button will work in future and we'll be able to force PT mode ourselves and get more reliable locks.

Hey everyone. I've been preoccupied with other things and stepped away from the utility for a while but it's not dead. I'm considering a revised version that would make it a mod (as it would require some minor changes to a DCS LUA file) instead of the standalone utility it is now. While this would help integrate it better with DCS, part of it's current appeal I believe is its simplicity and that it doesn't get broken if DCS files change/update. So, I'm still debating if increased usability is worth the "hassle" of modding a file. It may just cause more headaches each time DCS gets updated. Anyway, to answer some neglected questions: I didn't make keybinds a priorty as it's aimed at HOTAS/Joystick users. However, I believe this is the second request so I'll consider it. The challenge is that I'm using AHK to implement this and I'm bound by what it can do. While it can output to a screen overlay, it cannot (to the best of my knowledge) write to the VR buffer which is why I can't display anything there. This is why I switched to using sound cues instead. If anyone knows how to get AHK to write to the VR display, please let me know! Tnx. Yes, it should still be working just fine. It's actually not a "mod" (in that it doesn't modify any DCS files) but a standalone utility. DCS doesn't even need to be running for it to work. So, although it looks like it's part of DCS, it's actually quite separate and just runs alongside it. Point being that yes: If it ran before, it should still run just fine now DCS updates don't affect it. Is it possible that your joystick mappings may have changed? If you've added a new device or made other system changes, it might be monitoring the wrong joystick? Worth a double check.

This already exists. It's just not implemented for all modules. https://forums.eagle.ru/showthread.php?t=171207 https://forums.eagle.ru/showthread.php?t=178045

Hosted a 4-player session last night using 2.5.2. Here are a couple of crash logs for ED. dcs.log-20180529-030843.zip dcs.log-20180529-013326.zip Please post once downloaded and I'll remove them from Dropbox, tnx.

Add a SCENERY DESTRUCTION ZONE action in addition to the EXPLOSION. A SCENERY REMOVE OBJECTS ZONE can remove trees and/or objects too. A combination of those should do the trick.

Thanks David. I only got around to reading the whole 2/3 Position Switches thread now but it's a gold mine of information.

THANK YOU!! This is even handier than quick stops for the STO Stop lever Works like a charm and is exactly what I needed :-) Cheers! EDIT: I hadn't read the other thread 2/3-Position Switches but see that Vladinski has already posted much of this and more. In particular he has quite a comprehensive list of binds (a few already implemented by Razbam, others which are still missing). And another great post on how to start understanding the LUA so you can make adjustment on your own! Still appreciate your post Rlaxoxo or I wouldn't have found the info. But, in case anyone comes across this thread, be sure to read the other as well. I didn't read the entire thing until just now but it's worth taking the time to do so. Great info in there!

Thanks for this. Handy. I haven't d/l yet but the preview looks like it's in landscape. If so, perhaps you might consider a kneeboard friendly portrait version? Sent from my MediaPad using Tapatalk

Wow! Nice job. Sent from my SM-G930W8 using Tapatalk

I've found this "off" as well but haven't taken the time to document exactly what is going on. In addition to the TGP camera angle marker, I've also noticed that the TGP pipper on the HUD doesn't quite behave as I expect either when I fly past/over a designated target. I get the feeling that perhaps the bank of the aircraft might be throwing off the calculations? i.e. seems to work when you're flying straight & level but when you bank to come around, you don't see what you expect while in the turn? Once again, I haven't taken the time to properly analyse what is really going on yet so these thoughts are just a hunch. Not a very helpful post in that regard but I just wanted to add my general support at this point as I have also found myself going back to the HSI to realign for followup passes instead of using the TGP camera angle marker which seems off. P.S. It'd be nice to get the North arrow on the TGP similar to what is displayed on the A-10.

^this. +1!

I wondered the same thing. I assume it's so that IRL ground forces with better eyes on the target can designate. The only other thing I could think of was moving targets. Once you fire an D/G/H/K you have to rely on internal tracking. Having control over the guidance until impact may be more reliable in certain situations by removing the chance of losing point-lock mid-flight? But in general I agree with you. All things being equal, I'd stick to the D/G/H/K varients. Sent from my BTV-W09 using Tapatalk

As you can see, the mask for the bino view doesn't work properly on widescreen (3440x1440). Would be nice if the circle diameter scaled fill more of the vertical monitor space too.

The CH Software does work with Windows 10. That said, I have also experienced issues that others have had. In my case, the cause was that the Control Manager creates virtual devices each with their own USB IDs. In certain cases (re-installs?) too many virtual devices get created causing conflicts. The solution was to simply clear all previously created virtual devices before doing a clean reinstall of the CH Control Manger. What I believe many may not be aware of is that included within the CH software suite is a program called CMDelete.exe made for this exact purpose. If you run into this issue and do clean up, be sure to reboot before reinstalling. I have recovered from the non-responsive issue using this method and my CH gear has worked flawlessly since. If you do not need the advantages of Mapped Mode that the CH Control Manger software provides, you can skip the installation of the software altogether as others have mentioned. However, the CM software is well designed and very powerful - especially if you are (or willing to become) comfortable with custom scripting. You can add a lot of extra functionality (e.g. add short/long presses to buttons, remove axis jitter, add extra virtual controls, etc.)

Of course this is ideal but not all of us have rotaries on our throttles and thus my request. Sent from my BTV-W09 using Tapatalk

In addition to the existing hotkeys for: STO Stop UP STO Stop DOWN Can we please have a set of "Jump STO to position" hotkeys added? STO Stop to 30° STO Stop to 60° (Carrier Launch) STO Stop to 82° (Vertical) STO Stop No Limit (Open) STO Stop SetFwd OPEN-82-60-30 STO Stop SetBak 30-60-82-OPEN A press+hold to have the nozzle angle change is fine but not that accurate. Using the STO Stop can be helpful but it's a pain to set accurately too. These preset stop points would be very helpful for those that choose to use them. Thanks for the consideration.

*EDIT* I thought this was related to a similar problem I was having issuing commands to units that become unresponsive using Combined Arms. As I've done more testing this afternoon, it doesn't seem to be the same issue. So, I've deleted this comment. My problems persist but I'll post in another forum/thread that is more relevant.

I also tried putting a Harrier in a simple test mission to fly straight and level at 350 kts to practice formation flying and found it would always fly as fast a possible (~550+) regardless of speed settings.

Agreed. Having a complete and varied/flexible set of keybinds (e.g. ON/OFF and TOGGLE options) is really important. Please consider the keybinds as important as the system itself - not an afterthought. It's understandable that certain systems are incomplete while in early access. However as they are implemented, please add a complete set of keybinds at the same time if at all possible. I've been wanted to spend more time in the Harrier but it's just a little too frustrating and fiddly with the weapons in their current state and lacking a few needed/useful keybinds. I'm VERY eager to see things get completed and polished up as I'm LOVING the Harrier! It's my new favourite and even the inevitable excitement over the Hornet won't be able to take the shine off this bird :-)

Thanks Viper. Just wanted to make sure I wasn't missing something. That's a decent suggestion for a workaround. While a bit time consuming to prep, I find audio vs written messages easier to process while flying anyway. So, perhaps I'll stick to that. Cheers.

I'd like to trigger a message/mark/voiceover ONLY to a player in a JTAC/TacCmdr role. The MESSAGE TO / MARK TO / SOUND TO actions can be directed to ALL / COALITION / COUNTRY / GROUP I'm running into 2 problems: 1. Even when sending a message to ALL or COALITION, the JTAC/TacCmdr doesn't receive the on-screen message. 2. Further, I want to send it just to the tactical player (who doesn't seem to be able to receive any messages at all). So, as the JTAC/TacCmdr is not in a GROUP, how do I target them (and only them) for these actions? The idea here is that as a situation unfolds, only the tactical player would receive intel via these mechanisms. It's then his job to process the information and coordinate other players. I'm working with the vanilla mission editor at present but am not adverse to using a script. If it can be accomplished that way, some help with the script would be appreciated. Thanks!

Sounds pretty impressive. I'll have to check it out. Sent from my BTV-W09 using Tapatalk