TheBigTatanka

Fromthedeep, Can you explain generally what the laser basket is? Or maybe where we can go read about it at a generalized level? Does it apply to DCS? I'm guessing this impacts why medium altitude lofts aren't great for PWII, in the way that they can work for something like a JDAM. Sent from my Pixel 3 XL using Tapatalk

Yeah, there's not a lot of documentation on this stuff. The one thing I've seen is a write up that an avionics tech did years ago on the 184, and all i remember was that stuff didn't seem super logical to me. Sent from my Pixel 3 XL using Tapatalk

Frederf -- don't inverse video highlight the Convert feature before hitting enter. Just dobber over it and hit enter. You're right, you can't re-convert something if you haven't made a change to the parameters, but I'm not sure why you would want to. I'm not seeing any issues with the MGRS conversion / input implementation -- the only thing I could think of is it would be nice if the jet knew the grid you were in and had that inputted automatically for the first 3 digits of a full MGRS coordinate -- but I have no idea if that would be accurate or not. Having to edit 5 numbers/letters before being able to put in the grid is a little annoying, but again, no idea how that works in the jet. I'll try to ask someone.

Frederf... I'll mess with it tomorrow and report back. What happens if you just dobber right again instead of hitting enter? Sent from my Pixel 3 XL using Tapatalk

But what you can't do in DCS is fly to another airport, shut the down jet with a cock-on procedure, then fire it back up with a stored heading alignment and continue. And that makes my inner nerd a little sad. Sent from my Pixel 3 XL using Tapatalk

From the deep -- that was an awesome explanation, thanks for that. Low altitude lofts are where it's at in DCS. Pretty satisfying to achieve, and definitely not something i would want to do in a single seat aircraft for real. Thanks for taking the time to write out some of the factors for delayed vs continuous lase, that was more than I wanted to get into. I'd also throw on top of that, for people's planning purposes, the benefits of dropping PWII from a dive (medium altitude attacks) to help with that terminal energy state. Sent from my Pixel 3 XL using Tapatalk

Remember that you need to be within 7-8nm to lase in DCS. A 13nm standoff goal might not be practical with paveway II. The issue of continuous lase vs delayed lase is pretty complex and scenario dependant. There's not one "correct" way to employ. Delayed vs continuous combines with static vs moving target and level vs diving delivery and self vs buddy lase in a pretty intricate matrix. If you want standoff with a paveway II, go high and fast, get into a slight dive to get faster, and then toss the bomb. Have someone on the ground with combined arms lase the bomb in for you. Unless you were tossing from very high, delayed lase is probably best. Last 10-15 seconds is probably best too, because there's a minimum time that the seeker needs to find the laser spot + corrections. Sent from my Pixel 3 XL using Tapatalk

You guys talking about slaving sensors to a datalink track act like datalink is able to generate target accurate coordinates in 4 dimensions. It's only as good (and probably not even then) as what's feeding the sensor. So if AWACS is generating the track, do you really think your FCR or TGP is going to be able to snap to a moving airborne contact? Now your wingman who is transmitting out their own data.... That's going to be better. So, The greatest utility for this tool is not offensive, but to keep SA on your wingmen when in sensor formation. It basically turns your 5nm line abreast formation into a visual formation. Sent from my Pixel 3 XL using Tapatalk

That makes sense actually. As a work around for now, I've coded the "enter" key on my keyboard to the "enter" key on the ICP. We punch in the upcomming minute and do a time-hack over the radio from the F-10 Map clock. At the hack, I hit my enter key. It works for being in VR.

My guess is that this is related to how they've implemented the max toss pull up cue, which seems to have its own host of problems. I'm so confused with that thing, and I'm sure it's issues are seeping into other modes. Sent from my Pixel 3 XL using Tapatalk

It's working for me. Might want to check key bindings. It's tied to radio 2 ptt. Sent from my Pixel 3 XL using Tapatalk

No luck refueling with the F-16 either on the KC-10. The boom moves rather erratically when I'm well below or slightly to the side, but never makes contact. If you try to fly in good position, the boom won't try to move at all. Any chance this can be looked at? Is it just a matter of changing the coordinates in the .lua? I could try and test that out pretty easily, but anything beyond that is beyond my limits. Would love to have diversity in tankers, and the model is so beautiful. Hope this gets looked at again. I think I'm the 3rd person posting on this since February.

Another F-16 friend said he's never had to input the system time into the jet, it's always worked from the GPS time (although the option is there if needed). Can one of the community managers ask the team why the DCS jet isn't drawing its system time from the GPS clock? Cheers

I've gone back to setting manual weather and not using any of the new cloud presets. You just get the one layer, but at least you can set it to an altitude that doesn't interfere with TGPs. I'm also hoping for some updates to be able to have more control over the weather. Sent from my Pixel 3 XL using Tapatalk

My virtual squadron is very much wanting to transition to native voice in DCS, but it's hard to give up the mic clicks and sound effects of SRS. Haven't seen much movement on updates since the feature was released. Anyone have insight? Sent from my Pixel 3 XL using Tapatalk

I asked a friend of mine who flew the F-16 on his last assignment (~4 years ago), and he said you had to set the system clock only when the GPS Battery was dead. He said you had to manually set the L16 clock everytime to initialize link... So I'm trying to figure out what that means. Sent from my Pixel 3 XL using Tapatalk

There's a new thing to configure on page 2 of the datalink. Using the 5 key (after dobbering down a few times) you can add a "T" next to the numbers of your flight members. No idea what this is for, but i don't remember seeing it before. Hopefully it means they are working on datakink. Anyone know what that T is? Sent from my Pixel 3 XL using Tapatalk

If DCS models the GPS nature of the bomb, a longer time of flight (like 40+ seconds) will improve accuracy. The bomb needs time to get the GPS signal. Not sure if DCS models this. Sent from my Pixel 3 XL using Tapatalk

Just a dummy check..... The TGP only searches for the laser in its current field of view, so if your pod isn't already looking at the area where your buddy is lasing, then LSS won't turn up anything. A good technique is to have the guy lasing send out his SPI for everyone to hook and then cursor zero to that new datalink Steerpoint. Once you have all done that, then he can turn on his laser and have you "stare 1688" or whatever (meaning, start your LSS). That should result in a pretty quick capture on the exact vehicle/target/whatever. We were doing this yesterday viper to viper on a dedicated server with good effect. I will say that recently the LSS behavior is a little odd in that i can't tell when it's done capturing. I don't want to interrupt it, but sometimes I see the target captured, but can't yet move the TGP myself. Perhaps someone who speaks for ED can make a short YouTube video of how it's supposed to look so we have something to compare it to. Sent from my Pixel 3 XL using Tapatalk

Just spent some time looking at these clock issues. On a cold and dark jet, the analogue clock keeps time with the server clock (as one would expect). However, the GPS time does not, nor does the DED system time. As Frederf mentioned, the system time we would expect to set (if it isn't linked up to the GPS clock somehow), but the fact that the GPS time isn't accurate seems rather strange. Turning the GPS time sync on and off doesn't change the GPS time either. It's going to be pretty tough to get everyone in a 4 ship synced to the right time hack as the clocks are currently modeled (especially if everyone is in VR).

I've only been drawing MOAs with lines 1-20, and then using 31-60 for navigation points. 31-60 don't ever appear on the HSD, even as dots. I hope this means that they are doing some work on the Steerpoint system. Sent from my Pixel 3 XL using Tapatalk

This is getting a little off topic from the clock sync issue (analogue or digital system to GPS time), but IRL the JDAM releases and guides based on INS for the first part of its time of flight. After a certain number of seconds, the weapon's GPS antenna pick up the satellite signal and it guides with the more accurate GPS data. In a degraded/denied GPS environment, you would plan your attack for a shorter time of fall so the bomb only used inertial guidance from the jet's systems (which can be accurately fixed via an INS update using the radar or TGP on a known structure via an offset aim point along the route). Curious to see what happens with the clock sync issue, as I've been trying to set up servers to match real world time of day, and noticed the desync between that and jet time. I wonder if turning GPS time off and on would sync it. Sent from my Pixel 3 XL using Tapatalk

Dude! Thank you for the work around. Never would have guessed that. Sent from my Pixel 3 XL using Tapatalk

Sometimes datalink to wingmen gets frozen, indicated by a solid blue wingman symbol on the HSD. Is there any reliable way to reset this and get back the wingman's position? This is happening on multiplayer, and my wingman also loses datalink tracking to me. Sent from my Pixel 3 XL using Tapatalk

That's outstanding work. I've got a few more days of work, and then I'll be home to run the performance manual charts and test as well. Will add data. Great work man. Sent from my Pixel 3 XL using Tapatalk