Recluse

See this post for the new procedure: In brief, WINC LONG (or long press on the Arrow Keys for WP on the EHSD) and select TGT POINT on the ODU.

No real reason Other than wanting to keep them default for muscle memory when actually using the keyboard at other times... and not seeing the obvious - So I realized you could put MULTIPLE key commands in any given spot, so the Muscle Memory thing is no factor - It did work with the simplified key commands, but for the View Commands, I did have to insert a DELAY which kept the action button pressed down for a longer time. Went back and put that delay in for the original compound command it it worked as well.. Looking good now!

Been experimenting further. I contacted the author and he suggested adding some delays/pauses in case the keys were being processed too quickly for DCS. So far no joy on that either, but I was wondering if anyone using VAICOM/Voice Attack have any similar timing issues with complex commands like these. Got it working well for VIEWS and Radio Menus (basically Fx key commands since the menus can change). First time I have used any sort of Voice Command software, and so far it is promising except for the examples above (Cockpit Camera Views and Active Pause).

Just a question: Is there any advantage to using Markpoints vs. hitting the TOO button to create a Target Point? That is what I usually do, though I admit that I have a hard time sometimes getting the TPOD to snap back to the selected Target Point the way I think it should. Not sure Markpoints would work any differently, but you never know!

Latest Open Beta made a change. Name the Markpoints #TP0x instead of T0x and all will be well. No need for the throwaway waypoint any longer either

Just a CODA and a Mea Culpa to my ScratchPad Extensions dilemma. I could NOT get the extensions to work, but I was intrigued enough by the new keyboard by @Draken35 that I set out again to get it working. What I discovered was that AT SOME POINT I had accidentally created a Scratchpad folder in the SCRIPTS folder of the DCS Open Beta GAME hierarchy in addition to the correct folder in the SAVED GAMES hierarchy. Once I deleted that, everything was working fine and I could use the Extensions including keyboards. OPERATOR ERROR again

The Select seems to send a "1". So, if you have NOTHING selected and hit SELECT, it will jump to F1. If you use the Up and Down to get to a menu selection, when you get there and hit SELECT it will "say" "1" but will select that item. Are you getting the sound for the counting when you use your up and down keys?

Not sure. It works fine for me. All I can suggest is to check your Joystick Mappings again in the DCS MENU NAV.ini file. Question: Do you get the Sound (VR) or visual indication (non-VR) when you hit your Toggle or is that not working either? If your Toggle isn't working, check to make sure for some reason Windows doesn't think your Joystick 2 is Joystick 3 or something. If the toggle is not working, nothing else will If the Toggle is working but the other buttons are not, then potentially the thumbwheel isn't sending discrete inputs, though I would imagine you have used it this way before. Also, as I mentioned some time ago on the VR4DCS discord, make sure your Windows Sound playback source is set correctly so you can hear the voice prompts. If using the VR headset as the speakers/headphones, make sure that is what the Windows output is set to. If using another device, make sure THAT is what it is set to otherwise you will not hear the Menu Nav sounds. This tripped me up many times.

So I have read this many times, but in this article (circa 2006) https://apps.dtic.mil/sti/pdfs/ADA498288.pdf about which pod to equip USMC F/A-18D with, it does NOT mention that the LITENING is not certified for Carrier OPS. The article makes the argument for the MARINE Litening Pods even for Carrier embarked Marine Hornets. Anyone have an actual reference to the carrier rating difference between the pods? Then there is THIS.. indicating the ATFLIR is now being replaced with the LITENING, but, this is a new LITENING pod, so it still doesn't answer the question about the "old LITENING pod" https://theaviationist.com/2022/09/07/u-s-navy-super-hornet-makes-first-flight-with-litening-pod/ This is an interesting tidbit:

That is the way it is, at least in DCS. Having any AGM-65 variant ON BOARD makes the RAID/FOV switch INOP for the FLIR.

If you do it on the GROUND the Target points are Auto Assigned. If you do it in the AIR, you need to assign Target Points with the USE OSB, and select a Target point number on the UFC. It might be those points that aren't assigned yet that are giving the error, but, I don't recall ever seeing that error. Possibly because there is a mix of Assigned and un-assigned points. Not sure.

Posted on the Discord, but maybe somebody will know here. Simple (I hope) question: Is there a way to prevent SRS starting up automatically? Since I don't use it for SP or some private MP sessions, I would like to either prevent it from starting up with Windows and/or DCS and just start it manually when needed. Also seeing a lot of DCS crashes lately. Not sure it is SRS related, but would like to be able to toggle it on and off for testing purposes. What I mean is that after a boot, SRS seems to be already running as it loads up when I start DCS. I can't really see a way to turn it OFF (other than killing it in Task Manager). I would like to have to start it manually to have the option of not having it running. EdIT: Seems like just seeing the overly before it is connected does not mean it is running. I think I can just disconnect Auto-Connect and hide the overlay to prevent SRS running. EDIT: Ciribob answered on Discord: "Turn off SRS AutoLaunch in DCS SRS Settings" Lately been having a ton of crashes that SEEM to be correlated with starting to use SRS, but I am not 100% sure that is the issue. Seems to happen in VR only. I will be flying along and then all of a sudden, VR will crash (Freeze in the headset with lots of tearing). DCS also appears frozen and I need to kill in in Task Manager. Seems like more of a VR (QUEST2) issue as I don't seem to find a DCS CRASH LOG or .dmp file and the Log file doesn't seem to show anything catastophic. Just tried connection without VR and it seemed perfectly stable. Probably not an SRS issue, but I thought I would ask if anyone else had seen any weirdness with VR. When I am connected, SRS works perfectly.

Thanks!! Oddly enough, last night after the Open Beta Patch, we re-started Syrian Power from the beginning, and oddly enough both coalitions started off at 0! I was afraid I loaded the wrong mission, but all the FARPS and Apaches were functional, so it must have been the right one. The two or three times I loaded it in SP and the one time we did it in MP previously, it had that 22% for OPFOR start. I have NO IDEA what could have changed. I hosted instead of the usual host, but that shouldn't have affected anything. If it happens again, I will try your script additions above.

I saw the same thing last night with GBU-38. Just checked again and it is happening with Mk-82 as well. I think it is a general issue with the ACP. - Last night I was in the Air, AG mode, Master ARM ON - Just now I tried it on the ground with and without AG Mode/MA On. Same behavior in each case.

Well put!

Not sure I understand. Since the AZ/EL page does not have a distance measurement, it is hard to tell where contacts are without cross referencing with the radar. For example, I often am tracking a Radar contact (let's say they are at 40 miles and just coming into my TWS 40 mile scan) I can find that contact on my AZ/EL page but there may be (DATALINKED) contacts "below" it which on a B-scope means CLOSER, but on AZ/EL just means lower elevation. When I put the TDC over them on the AZ/El page, I can see they are FARTHER away (often outside the ATTACK RADAR range setting) and just at lower Elevation than the contact I am tracking. Since they are datalinked contacts, I never stopped to wonder (until now) why they seem to appear within my Radar Scan Volume, when my radar is only scanning out to 40 miles. I was thinking that the Scan Volume shown on AZ/EL is based on the Attk Radar range setting, but I am now thinking it reflects scan volume of MAXIMUM radar range despite what the radar is set to actually DISPLAY. Makes sense since, setting your radar display to a shorter distance doesn't mean the radar beam itself is cutting out early, just that it is only displaying contacts within the set range.

LOL... yeah.. I had that exact thought while paring down the number of MST4 ships!! I somehow remembered doing that, but maybe it was only Non-Statics.

Thanks Rudel! I was afraid of that I did go to the Objects List and show the hidden Units. DiMon added quite a lot of units so it was a daunting list for sure. Luckily the naming convention should make it easy to remove those ship objects added in MST4.

Hi, quick question. Is there an easy way to REMOVE the templates once added to a mission? I want to make a version of the mission WITHOUT the templates for a little better VR performance, though flying around the Marianas is much more enjoyable with the Templates on. I think I would maybe just leave the BASE and remove the SHIPS. I am sure I am missing something obvious.

Difference in terminology... You are correct that the Mav will boresight, in that the seeker will be boresighted in it's forward and locked position. I think what that OP was asking was a similar process needed on the F-16 where you have to do an alignment between the Mav seeker and the TPOD to assure that they will line up so targets are handed off correctly. Also called "boresighting". I don't own the DCS F-16 but I remember doing that process in the BMS F-16. Essentially you slew the Targeting pod over a target, and independently slew the MAV seeker over the same target and tell them that they are now aligned, and magic happens... Ooops... I am repeating what I said above. Funny, I had no recollection of making that earlier post...

We have been enjoying the heck out of Georgian Power/Vegas Power/Persian Power both in Single and Multiplayer!! Another question! One of our crew wants to fly the Apache. I added some Apaches to Syrian Power using the tip above for editing the LUA file to allow Helicopters. Worked perfectly!! I based the Apaches on FARPS situated within easy flying distance of the enemy bases. I set the FARPS as NON-Airbases in the LUA similar to the way Carriers and Escorts are set in the example above. The FARPS have the usual complement of AMMO, FUEL, ATC, etc.. statics AND some SAM and AAA defenses. When I START the mission, the OPFOR starts with 22% Progress and the number of targets is significantly higher than in the plain vanilla mission. I believe it is because the FARP objects are somehow being COUNTED in the totals of BLUE objects, but LUA gets the count of SURVIVING targets from those that are GENERATED, so it looks like there are fewer total targets than there really are. Just a guess on my part. I haven't actually counted them up. Probably no big deal, as the total number of generated targets remains the same, and the OPFOR probably won't get many more of them if we do our jobs, but I was wondering if there was an easy LUA edit to add the FARP objects (if indeed this is what is causing the discrepancy).

A .trk would be helpful. It works fine for me. I have used it extensively since the patch and hotfix.

This might be part of the already reported bug for servers below, but it also happens when a Player hosts a server. The HOST's score/kill stats show with the apostrophe hotkey, but all of the clients are 0.

YES it is, but Surveillance tracks have Elevation and azimuth information associated, so the AZ/EL page should represent their position as inside or outside the current radar scan volume just as you can TDC over it on the radar screen to get the Elevation and slew the scan and elevation to bring it within constraints for detection by your radar.

BUMP.. I'd be interested if there were an answer to this... Not as much of an issue any longer as today's patch made it so ONLY the pilot's Target Points are imported in a Multiplayer Session. While I never used that capability in MP, it seems like it was a good option to have. I was more concerned with Re-assigning target points from multiple sorties in my own Harrier, but I found that I can ERASE them from the CAS PAGE, DELETE them from the Map and then re-create Target Points on the Map and the ATHS will re-import the NEW points with the right numbers, So.. I think I am good on this now.