Sandman1330

Looks that way, I don’t see how it could be related to your mission. I was able to simply use the F10 menu to make the rejoin.

Ah, may have found out how to change the Hornet format to DD MM SS.SS! Starts at 33sec. Before seeing this I thought precise only accepted DD MM.MMMM - colour me schooled.

I know what the issue is. The coordinates given to us by the JTACs in all of the missions are in DD MM SS, where the hornet's nav system only accepts DD MM.MM So if you are given 25-53-59, that's 25 degrees, 53 minutes, 59 seconds. You need to convert 59 seconds into decimal minutes. Since there are 60 seconds in a minute, it becomes 25 53.98 or something close to that (you can convert it mathematically or via a converter but I'm doing it in my head) It's a bigger problem in Mission 11, where you're hitting the hawk sites. He gives you precise coords in DD MM SS.S, but there's no way to input it into the UFC. Edit: though I think for JDAM/JSOW preplanned you can enter DD MM SS.SS... you just can’t swing your pod onto it to be sure what you are dropping on. Edit 2: I do seem to remember, at one time, you would enter coordinates as DD MM SS and it would appear, converted, in DD MM.MM on the DDI. However, they now seem to appear on the DDI as entered in DD MM.MM without conversion. I may need to do some testing...

Roger, understood that. It's Cajun's directions that lead to confusion; he tells the flight (which would include you) to go drop visually. That's the piece I feel like should be clarified.

Question about the JDAM drop. So, Cajun instructs the flight to drop "visually." IIRC, in the book, it's implied because the JDAM GPS is sour, they go in and drop in CCIP. I had to pause the mission and sit there scratching my head for a few minutes, wondering - can I even do that in DCS? Is there even a way to drop JDAM in CCIP in DCS? I think the answer is no... Thankfully, and no doubt by design to get around this, the "middle" targets were the ones I had already entered into my preplanned targets. So I just dropped in auto mode and let the JDAMs do their thing, and all worked well. I guess the question, though: Can we do CCIP drop of JDAM? If not, maybe the instructions could have been a bit clearer? (ie "flip, do a standard drop since yours are working, everyone else follow me for a visual drop...") In the same vein, in the mission briefing, it says to "check your targets with the FLIR before you drop." Is this possible with preplanned JDAM targets? Is there a way to slew the pod to the preplanned target? The only way I can think of is creating a waypoint at each target point, using waypoint designate to slew the pod and drop in TOO mode. Thoughts?

Yes! I just started mission 10, and am now facing the prospect of having no idea who to rejoin with because the IDs in SA page aren't working. Exactly why I came on the forums just now was to see if I was alone (or doing something wrong)... Apparently not.

No mods, I will check if it’s as admin, good call! Edit: Nope, didn't help. Every time I run the server I have to reset the name of the observer and change the pause settings. The name has always been an issue, the pause settings problem is new...

OK, did a fully clean install. Deleted everything, including the saved games folder (I backed up config but haven't moved it back over yet) and did a full reinstall via the updater (thanks gigabit fibre!) Unfortunately, the sound bug is still present. Tracks and logs, and a video for good measure, are included for your reference. All are using the F16 free flight instant action on the latest open beta. What a bugger! Track: https://1drv.ms/u/s!Ascm8Kmu7NR0g-4m-h5nn8GYHlIexg?e=EkNqiP Video: dcs.log

This is the quote I’ve been waiting for! I still play Op BACTRIA, going in and fixing things that go awry with various updates (the new Caucuses map took a fair bit of work). I hope you’re glad to hear that mission is still alive and well! When you start work on your new mission, I’d be happy to help with VOs or anything else you need, since I’ve gotten so much play out of the original it’s the least I can do to give back. On topic, it’s awesome that you are helping out with the Warthog II. I can’t wait for both!

Seems like a recent thing, but lately my dedicated server isn’t retaining the advanced options. Specifically, the resume options - every time I start a new mission or restart the server, I have to change the settings back to “resume with clients”, it keeps defaulting to resume manual. Any way to make it stick?

The coordinates probably just aren't precise enough. What I did was enter it into the UFC as a waypoint, use WPDSG to designate that waypoint and swing the pod to that point, then refined the aim point with the pod and dropped in TOO mode. Shack'd the center of the compound no problem!

BN, I'll have a scrape through and make sure I don't have any mods, but I don't think I do. Any I do have will be disabled in the module manager I believe. That being said, at least from my perspective, this is far from a game breaking bug. While I laud your efforts to track it down and try and fix it, it seems to be fairly rare and has minimal impact on playability. I guess what I'm saying is, again my personal opinion only, if it's proving to be a real time-sink, maybe the juice isn't worth the squeeze? I know you guys have a lot on your plates already! Either way I'll check it out this weekend. It might even be a good time for me to do a full reinstall of DCS, it's probably been 3+ years since I've done that and there may be some old mods or files from previous versions kicking around...

With my current 1080Ti, MSI Afterburner reports that all 11Gb of VRAM and nearly all 32GB of system RAM are in use while on PG or Syria maps. Though I'm just beginning to realize that, with regards to system RAM anyway, Afterburner is reporting RAM that's pre-reserved, and actual RAM in use is lower, I haven't found a way to verify if my VRAM is truly all being used or if it's simply reserved by the game. If my VRAM usage really is that high, I'm concerned about the drop from 11GB to 10GB of VRAM on the 3080. It seems like a very strange choice to go down in VRAM... It's the only thing that gives me pause about the new card!

BTD, As requested. There are 2 .trk files and 2 DCS Log files, one with loud afterburner off, and one with it on. Both use the basic F16 Caucuses free-flight mission on the latest open beta. The bug replicated both times after the first ejection (I eject, then respawn, and the bug is present). With loud afterburner turned off, it was there whether I was in mil or AB; with loud afterburner on, the sound went away on AB, but came back when going back to mil power. I hope this helps, and please let me know if you need anything else! Track loud afterburner: https://1drv.ms/u/s!Ascm8Kmu7NR0g-wd0LIsz1F6i9Ucow?e=58p1ue Track no loud afterburner: https://1drv.ms/u/s!Ascm8Kmu7NR0g-wc7R1PwQYHh1IcoA?e=Chb5Gc Loud afterburner off.log Loud Afterburner On.log

Oh really? Do you know which number MSI Afterburners performance monitor reports? The reason I ask is lately I have been seeing MSI Afterburner report all 11Gb of VRAM and all 32GB of system RAM in use while playing DCS (especially in Syria and PG, Caucuses uses less system RAM). Playing with system settings had had little to no effect. I’m curious if that RAM is actually in use or just pre-allocated as you say...

Back to the point of the thread, I think one key element has been overlooked: the lightning pod was only used by the USMC, and from what I understand, only in training (could be wrong). On deployment (and for sure on the carrier), all US Navy and USMC Hornets used the ATFLIR pod. We got the lightning first in DCS because it was already in game on other airframes and the early hornet was limited by not having a pod. ED was actually asked by the community to delay the ATFLIR and focus on the lightning as a stop gap measure. I think it’s entirely plausible that the lightning implementation is accurate, and is a little wonky because the aircraft is designed for the ATFLIR. One example from another thread (don’t ask me to find it) is that the ATFLIR does not have wide/narrow FOV, just progressive zoom. This would explain the logic behind locking FOV control to the mav. This is only one example, I am sure there are many more. In short, I think we should wait until we see how the ATFLIR integrates before we get too upset.

Ok, will try. What’s the best way to go about this? Can I replay the track to replicate the problem then send the log file immediately afterwards, or do I need to play a mission to replicate it again? What’s the best way to ensure the log file contains the error?

Oh yah, seems worse than before (could be I’ve been flying the Tomcat too much lately, spoiled by the DLC). I find the bird floats really bad over the ramp, necessitating a drop in power to maintain ball that leads to EGTL or EGIW

Thanks BN. Do you need any log files / dxdialogs / anything from us to try and nail down the specific circumstances where this is present?

Haha, I know, by the end I was flying through a sea of parachutes!

As promised, here is a much better one. It happens after the very first ejection - At the very start of the track I spawn into an F16, then eject about 5 secs later and use Ctrl+shift+tab to get a new plane. When I spawn into the new plane, the bug is there. I then proceed to do it several more times, and it happens ~10% of the times after that first one. https://1drv.ms/u/s!Ascm8Kmu7NR0g-ljcak32C7HiObSvg?e=IafW3E

Concur. Even if I decide not to get whatever AMD brings to the table, it sounds like it should be competitive enough to drive NVidia prices down, so it’s a win for everyone,

In my case it stayed in the Alt Hold position. Made it super confusing for me!

Check your dead zones on your controller. I didn’t have any issues before either, but recently I ran into the same problem as you. My Warthog stick on Virpil base was so heavy it was pulling the stick slightly forward of center. I increased my dead zones and it fixed the AP issue. Maybe they recently reduced the control input tolerance for AP engagement?

Here's probably the shortest track I can find. Near the end, there will be a string of times where I spawn in then immediately eject again, back to back a few times. This was when I was getting the rumbling, so I jumped out to take a new jet. Unfortunately it's just not consistent or repeatable enough to get a shorter track. I'll try tomorrow to purposely cause it and see if I can make it shorter. These are in the Tomcat, BTW - but the bug is the same in the Viper. https://1drv.ms/u/s!Ascm8Kmu7NR0g-k68fZMCol-Cxi4Nw?e=sTvxh7 I ran the track back myself, you're looking at about 10-15mins into the track for it to start. It did reproduce when I did the playback, at least for me...