Str][ker

I wanted to make sure that this bug was also noticed and potentially fixed with this update. I noticed that even if I don't delete the waypoints from The Way and I send them to my aircraft, the waypoints are sent twice. Here's how this happened for me. 1) Entered 8 waypoints into The Way. 2) Started the transfer process. I made a mistake and adjusted something which messed up the entry for The Way. It wound up finishing but I had to re-enter them. 3) I went back to the starting waypoint which I wanted in the Aircraft and hit Transfer Waypoints to Aircraft 4) The Way entered 16 Waypoints (only 8 were in The Way). It went through the 8 Waypoints twice (1-8 and then 1-8)

Hi! I made a video to show how to use this in VR effectively. I also showed how I use the key binds. Basically there are three for VR, one to send a waypoint to The Way (made super easy in VR with Scratch Pad), one to send the waypoints to your aircraft (this still requires popping out to the desktop even after selecting don't ask again).. hopefully this gets fixed), and one to delete the waypoints in The Way (this is also bugged but a fix is pending).

Uninstalling and then installing had no effect upon the check box to not ask again. It also had no effect upon the deleted waypoint issue.

Will do. Did you need a video which demonstrates the Deleted waypoints issue? What happens: 1) Add three waypoints to The Way 2) Transfer -> The Way enters the three waypoints to the aircraft 3) Delete Waypoints from The Way (they are no longer displayed) 4) Add 1 new waypoint to The Way 5) Transfer -> The Way enters 4 waypoints to the aircraft. The order added is: The first three then the new one. So new waypoints get appended to the old waypoint list. Note: The above is performed using the hot keys which were added for VR. I will try uninstalling and then installing to see if that helps with the Don't Ask Again issue.

Correct, the headset does not show anything. You pretty much need scratchpad to get this working in VR @Comrade Doge I had this happen as well in the F-18. I clear out old waypoints and then add new ones. The old ones get added as well. Also, that Don't Ask Again button is not working still. I updated to the hotfix as requested.

I wanted to share a video I made demonstrating your excellent program. It shows its use from a VR user's perspective. I utilized the great suggestion from @nighteyes2017 to include using scratchpad to get around the problems of figuring out where The Way is going to grab the map co-ordinates from. I'll include the link below for your reference. Please let me know if I missed anything or made errors.

@Comrade Doge Thanks for the great update! I noticed that for the transfer to DCS press, I am still being prompted to confirm even though I clicked the do not ask me again box the last time I used it. Should this not be persistent each time the app is started or are you only setting this per session? If per session, can you please set this as permanent (or at least include a variable which we can manually set in the config file?) As it is, I still need to hop out of VR to the desktop in order to transfer the waypoints to the jet in DCS which defeats the potential of this option for VR users. Thanks!

@Comrade Doge So I used The Way in conjunction with Scratch Pad in VR (thanks @nighteyes2017!) and it works perfectly.. except for one minor issue. The confirmation box on The Way still requires me to pop out of VR to click on it (unless I missed some option somewhere?). Could you please add an option to disable the confirmation? Perhaps a check box on the main The Way screen for VR users. Have it list the requirements for Precise setting etc. with a check box so it will just enter the waypoints once I tell it to? Otherwise, it's amazing! Thanks! I was finally able to spam out 8 JSOW's against an airbase on a 4YA server. It was pretty fun!

What I found really helped solidify my knowledge is.. 1) Hop onto a training server online to practice. I really like the Hoggit training server on the Caucuses map. There are all kinds of targets there and you can spawn your own targets. Some targets shoot back and some don’t (it explains this for you on the server). So when I needed to practice the JSOW’s or laser mavericks, this was a great place to try it out plus I could listen to others talking on SRS (in game communications software but is separate from DCS), watch people flying around attacking stuff and have a safe environment to practice using these weapons and sensors. 2) I found using campaigns really helped force me to learn aspects of the jet which I may have ignored. Specifically I loved the Raven One campaign. It was a lot of fun and it forced me to learn stuff I had forgotten.

Someone forked the original version and added F-15E support. You can snag it at this link... https://github.com/blueberrypi-studio/DCSTheWay/releases/tag/V2.1.3

I use scratchpad already but I never thought of doing it this way! That's ingenious! Thanks! It is actually awesome because I don't have to lift my visor any more using this method! I can't wait to try it!

I was curious if anyone can get this to work in VR. I understand that you need to lift your headset to see the desktop but when I do, obviously the VR mirror moves around. When I get the map positioned in the mirror and get the way's designator over where I want it and tell it to set a point there, the co-ordinates never match the game. I assume I am doing something wrong here. If someone has managed to get this working with VR could you please share how you do it? Thanks!

Thank you for your explanation of the need for tracks (it was helpful). So.. funny thing. I just fired up DCS with a night landing mission on the Sinai map and the LRLS is working now. I am guessing that it was just recently fixed (last patch)? I thought this had been fixed a while ago and then noticed it not working when flying using the previous patch version. Regardless, from my perspective, this is fixed. I also gave a daytime / bad weather CASE III approach in the Persian Gulf a try and the light was visible out quite far. I never really use it for CASE I landings so I never really noticed how visible it is in full daylight. I am using: Open Beta (latest), Open-XR VR in a Varjo Aero headset using Dynamic Foveated Rendering. AMD 7950X3D, 64 GB DDR5 6GHz RAM, NVMe drive, 4090 Video card.

I honestly thought this was a known issue and then I see us being asked to provide a track file. Yikes. I should stop assuming things. I can definitely say that the LRLS is not working properly. In this video from Wags, you can start to see it at just under 20 nm. Wags then talks about it at around 14 nm. I have always been able to use this in the past until the MT release came out. Now I can not see the LRLS while flying. It's like it's not there at all. It's effectively useless. I have a video (linked below) which I recorded in Sinai of me landing at night on the 4YA server. Even at 1.5 miles you can't see the LRLS.. you can see the IFLOLS and the ramp lights only. This is in stark contrast to before the MT executable was released where I could clearly see it at night and during the day. I can provide track files if required of day and night landings. The Super carrier manual states 10 nm so I don't know if it was to be adjusted down but it was instead dialed too far back? "The Long-Range Laser Lineup System uses eye-safe, color-coded lasers to provide visual lineup information to approaching aircraft. These low intensity lasers are projected aft of the ship and are visible out to 10 miles at night." Wags' video first visibility at around 20 nm. Wags starting to talk about the LRLS (14 nm) My video starting at about 12 nm from carrier at night (MT open beta). No LRLS visible at all, even at 1-2 miles from carrier.

Why would you feel compelled to spend time negatively responding to a post in which players are trying to note impacting game change observations to help others out and to find out if there's something which needs attention from ED? I honestly don't understand people like you who feel that then have to weigh in on conversations others are having. I personally came here to see if others are having this issue too and so this conversation was helpful. As other stated, the significantly increased load times can impact people who are trying to adjust settings or are troubleshooting other issues (such as I have been doing). Take your poor attitude elsewhere please. Nobody needs to hear it here.

While using the ATFLIR, I have noticed that Mark Points do not show up while pointing where the mark point is whereas waypoints do. I was not sure if this is working as intended or if it's a bug. My inclination would be that mark points should be displayed on the FLIR page just as waypoints do.

This would truly help us expand our enjoyment of DCS! It would also help I think, efforts to build a replacement for Vaicom Pro which recently died with the 2.8 update (developer has disappeared and so it can’t be fixed). I gravitate to servers running overlord bot.

Yeah. I can't believe that I neglected that step! I had searched through older videos on Youtube and they had varying methodologies based upon the state of JDAM programing at the time. For a while, you were not to designate each target and were supposed to just select the next TOO and step to the next station. The next thing was you would have to use mark points to designate because the TOO1 and TOO2 would not store separate targets on each station. We finally got to the current configuration which I did use before but I guiess I completely spaced on setting each station correctly. Well, I'm going to make a video about this hard learned lesson Thanks for taking the time to look at what I was doing and providing feedback! You saved my sanity because I was doing this over and over and could not figure out what I was doing wrong and so I figured I should come here to ask if it was a problem. (turns out *I* was the problem.. lol)

Yeah that's all making sense now! Thanks. It has been a long time since I did this and so I guess I forgot about that particular step. I really thought that I would just switch on the one page but obviously I am mistaken. This also makes sense as to why the targets missed sometimes varies.. it would be because of which TOO the particular station was sitting on. I greatly appreciate everyone's help!

Regarding number 1.. I put the aircraft into precise mode so that I could show through the FLIR that the JDAM coordinates were accurate for each target. I usually don't do this. Regarding number 2.. I understand that each station has TOO1 and TOO2 but I did miss the aspect of setting all stations to the same TOO. I've never had to do this before and have always dropped all bombs on designated targets. In the video, (and when I have done this over multiple attempts) all bombs are dropped.. the issue is that some of the bombs hit a target which it is not supposed to and misses the designated target. I'll try setting all stations to the same TOO and see if it makes a difference.. I generally have them all on the same TOO (TOO2).. I just stepped through them all in the video to show that the targets were properly assigned.

Here's the video and the mission which I used to demonstrate. JDAM Demo03.miz

I have reproduced this issue multiple times and I created a video to illustrate what I see each time. I will link the video once I get it finalized and posted via an unlisted Youtube Link. This is against static targets (in my test mission I used static ground vehicles) which will not move once there are impacts near them. Load of 8 x 500lb JDAMs 2 each per rack. All are set to TOO. All have fuse set. All are aligned. First rack - TOO1 - assign to target 1 using TDC and FLIR. Next, select TOO2, assign to target 2. Press Step to next rack. Next rack - TOO1 - assign to target 3 using TDC and FLIR. Next, select TOO2, assign to target 4. Press Step to next rack. Next rack - TOO1 - assign to target 5 using TDC and FLIR. Next, select TOO2, assign to target 6. Press Step to next rack. Next rack - TOO1 - assign to target 7 using TDC and FLIR. Next, select TOO2, assign to target 8. Press Return and the QTY button. I select all 4 weapon stations. This will drop all 4 with a single press and hold of the weapon release button for the selected TOO group. (note: it is important to only select the quantity AFTER assigning each JDAM to its target. Selecting all first will result in all weapons sharing the same target (whichever is last assigned)) I have manually stepped through each rack and both TOO1/TOO2 to verify the targets (using active pause). All are assigned properly. With TOO1 (or TOO2) selected, I press and hold the weapon release until all 4 bombs are away. I then press TOO2 (or TOO1) and press and hold the weapon release until the last 4 bombs are away. Observing the impacts, I am always hitting 5 targets and missing 3. The 3 bombs which miss their assigned target instead hit the other targets. The specific targets missed seem to vary for reasons unknown. This is 100% repeatable. I have used this method in the past to drop 8 weapons on 8 stationary targets without issue. JDAMs should each retain their respective target and not pick up a target assigned to another weapon. All JDAMS have their targets assigned in an identical manner and some work while others don't. This should not happen.

I decided to play around with dropping 8 JDAMS in a single pass. There appears to be an issue where the JDAMs are losing their targets and wind up hitting the target of another JDAM. I used to be able to hit 8 different targets with ease, now I tend to only hit 4 or 5. JDAMS aligned and all in TOO mode TOO1 - Designate target using ATFILR, Switch to TOO2, Designate next target using ATFILR, Step to next station Repeat step 2 for all stations Select Quantity and select all stations Release all for TOO1, Select TOO2, Release all I verify that each JDAM has a unique target based upon a quick check of coordinates. In the attached track file, I select separate targets however some targets are not hit while others get two hits. Am I missing something / doing something incorrectly? jdam02.trk

Thanks! This actually solved an issue which I was having related to sound output to virtual audio cables to facilitate recording different parts of the game to separate audio channels.

I found the answer here (link to other thread below). Specifically what was happening is the cockpit warning and voice sounds were being routed to my headphones and not to the desktop because I had the headphones set to my actual headphones. I didn't understand what this would do as I thought it was asking what device were my headphones. Once I modified this to also feed to my virtual audio cable, the sound is now being recorded as I wanted.