Sylosis

Bumping this... I'm surprised no one has an answer! I don't mind being told I'm doing something wrong by the way!

Hi, I have always set the INS knob to NAV and now I have this weird problem that when I do, my heading bug (vertical line in the compass showing where you must fly to reach your waypoint) stays at the right of the compass (see screenshot). Problem disappears if I turn the knob to IFA. Comes back again if I switch back to NAV. All my tests were in Persian Gulf map. Is it intended or is it a bug?

Update: It appears the problem is from setting the INS knob to NAV and not IFA. I swear I have always used "NAV" and never had any issue. What did Razbam change that makes setting the knob to NAV behave like this?

Hi all, I don't know if I'm doing something wrong, possibly in the alignment procedure, but I have this weird problem where the vertical waypoint line marker at the top of the hud, in the compass, is not at all where it should be. It stays on the right, always (think the marker is called "Heading bug"?) Suppose I have a waypoint at about 080. I see it in the EHSD and I see the big waypoint circle in my hud, the line marker (at the top, where the compass is) will even have "080" written underneath it, but it'll stay at the complete right of the compass and not move, even if I do a 360. See my screenshot for example. I have tried starting already in the air with "Create Fast Mission" and everything was fine. The line marker was indeed towards waypoint 1 and there was no problem. What am I doing wrong? I'm convinced I align the airplane as I always have. Has the procedure changed? (Summary of my INS Alignment on the ground: EHSD + Data + A/C, Enter Coordinates (using kneeboard info), Enter MVAR (using kneeboard info), Enter True Heading (using F2 to find it), Turn knob to INS Align, Wait until 0.7 OK, Turn INS knob to NAV (or IFA but that shouldn't be my issue here?), push Data again on EHSD)

Oh god! Thanks so much for that!

Yes, you are correct, that is the mission and it's the 3rd "target" I'm asked to engage (rocket launchers in the woods).

I'm wondering what I'm doing incorrectly in a campaign mission where a ground unit gives me the coordinates for a target. I create a new waypoint at that location but when selecting it, first issue is that it doesn't really seem to be at the same coordinates that I entered. The coordinates in EHSD are not what I entered and also I can see in my HUD that the waypoint indicator is not on my target. Second issue is that if I push DESGN, the TPOD doesn't appear to be ground stabilized. It's kinda pointing at the ground, but it's drifting like it's not locking to the waypoint. If I use a preprogrammed waypoint, it behaves like I would expect (it locks at the waypoint and is ground stabilized). What am I doing wrong? Is it simply because I don't enter elevation? Cause my ground unit calling for support is just giving me coordinates.

Damnit I was equipped with laser guided rockets and didn't notice.... Nevermind my post... My bad

As the title says. I almost never use rockets, but I'm in a campaign where this is the given loadout. To be completely honest I strongly disagree with the campaign creator that sends you shooting a bunch of AAA with only 2 GBUs, 12 rockets and one gun pod..... But whatever.... I have my pod on my target and diving to shoot it. Not only am I not getting any cues (although I do have one if I try my gun pod), but the rockets that are fire are completely off, by a good 5-10m all to the left, even if shot from the right wing pod. What am I not getting?

oh ok good to know thx. At the moment I don't think that is the cause of my problem. I'm flying some dynamic mission with a friend on his private server and the AI Predators also use the default 1688 code, so I don't actually need to change it. I just didn't know how to Although I did try to drop GBU-12s on his targets and they completely didn't track his laser. Not sure why.

Thanks, that's what I was curious to know.

Hi everyone, I understand that the only way right now to change the bomb code is to use the kneeboard, right? If so, is there any plan to implement the code change in the MFDs and not the kneeboard? Or is the F-16 such that the bomb code has to be programmed before take-off (in real life I mean), therefore in DCS there isn't any other mean to recreate that other than the kneeboard?

Was flying mostly the F-16 lately and went back to the F-18. I never have issues with radar locks in the F-16, however I had heard about difficulties/bugs in the F-18 when trying to perform a STT Lock. That is: you have a radar contact either in RWS or TWS, and when trying to STT, you lose lock after a few seconds. I went through reddit and the forum to try and figure out if it's a bug, if it has since been fixed, or if it's working as intended. I wasn't able to find something recent that would answer that question. And, I have started some SP F-18 missions and I indeed can't keep a STT lock for more than 2 seconds. So if it's a bug, I assume it's still not fixed? And if it's working as intended, can someone kindly explain why the F-18 radar is that "temperamental" versus the F-16's? Thank you.

Thank you very much, that fixed it.

Hi, I'm flying a mission in Operation Pontus campaign (F-18 single player) and I can recreate the same bug every time. I open the kneeboard to look at the custom pages added by the campaign designer and every single time the screen turns all black. The game is still running, but everything is black, except the yellow crosshair mouse pointer. I can push ESC to have the option to Quit or Quit to Desktop. If I quit, I go back to the normal menu and everything works fine. I'm not sure if this is the right place to post about that issue, as this is not a crash per say. But I wasn't sure where else I should post. I play DCS Open Beta, it's up to date, and my GPU drivers are up to date as well. dcs.log

Please note that there are multiple recent threads pointing out to issues with the F-14. ED even replied to one noting they are aware something is wrong and are still unsure if it's really just the F-14 at fault. That being said, a lot of people seem to have DCS freeze when flying the F-14.

By "Almost", I mean that although I haven't taken precise notes as to what I was doing when it crashed, I have a high level of confidence the freezing occurs with the F-14B, but I can't tell you it's 100% of the freezes with the F-14. I am certain it's 95% or more. Recently I have only done 2 things in DCS: either single player Operation Sandstorm F-14B campaign or multiplayer on a private server, flying the mostly the F-16. I do not recall ever freezing while being on the private server with the F-16. Moreover, I can say that the situations where it froze varied. On one occasion, it froze just as I got hit by a missile. On another occasion, it was during "time acceleration". And on another occasion, it was as I was approaching the carrier to land. It never froze right at the start of a mission. It was always after quite some playing time (30 minutes or more). Note that after posting this, I saw another thread which is very recent here about people complaining they seem to freeze with the F-14. I suspect my issue is probably the same. Finally, I'm not super tech savvy so my question might sound "noob": if I had 2 or 3 freezes yesterday, are the logs from these occurrences still available? or is the file always overwritten every time I restart DCS? If they are still available I can share them.

I can confirm that while I am not playing the Liberation mission(s), I have regular freezes while trying to play the Operation Sandstorm campaign (which is a solo campaign with the F-14B). It's nearly impossible to finish any mission as the game will freeze after some time. Not saying this is certainly the F-14 being the problem... but... it does look like it. Also, since the F-14 freezes, I switched to the F-18 and had some new bug (but as annoying). Screen turned black, but the game was clearly still working "in the background". I could lower the gears, etc. and was hearing the sound. When used task manager to kill DCS, I even had the usual pop-up message within DCS "Are you sure you want to quit" or something. This F-18 thing is most likely unrelated to the issue from this thread, but I thought I'd share. It happened when I was looking at the kneeboard.

Hi, For the last 2 weeks, I noticed regular freezes that require me to kill DCS (game freezes, but I can alt+tab and kill the DCS process). Almost only happened when playing the Operation Sandstorm F-14B campaign. I'm either spending my DCS time doing that campaign, or playing online with friends on a private server, with the F-16. I haven't had any crashes/freeze when being online. Not sure what files to share in such a situation, feel free to request them (and maybe point me to where I should find them). I attached the DXDiag report in case it's relevant. I'm currently trying to repair DCS to see if it'll help. (Specs are: Windows 11-64bits (up to date), 3080Ti (up to date drivers), 32GB RAM and Ryzen 5800X.) Running the latest DCS Open Beta version. DxDiag.txt

Thanks for giving more info, I'll look into it for sure and I'm a OB user (like most people I guess?)

oh wow ok. It's been like that since a recent patch you say? That's good info and most likely what I did wrong. That being said... I'm wondering when they'll stop changing the systems. It's frustrating when you start to get the hang of a module and they keep modifying how it behaves....I can understand they want to make it closer to the real thing but man, why not have it like that in the first place

I'm not sure I understand what you mean by "going back to INS". Could you please explain?

I'll try to recreate the thing and share yes.

Well that's the thing, I didn't want to designate, as I wanted to perform quick attacks. That being said, I did "undesignate" and I was still getting the circle staying full no matter what.

I'm not a pro with the Harrier but I'm fairly certain from all the times I have played, this is the first time I face this issue. The Gun CCIP doesn't give me proper info. I'm almost hitting the ground and the piper still is showing a full circle as if I'm not close to having my rounds hit the ground. What am I doing wrong?