RagnarDa

This functionality was in a previous patch but was broken. Today’s patch fixes this.

Hmm... It looks like I made it disallow bombing non BP and M-target waypoints. Apparantly I allowed it with CCIP and DYK mode but not the others... I'm removing this code now but I have to check it first so not sure it will make it into next update (if there is one the coming week). Edit: I realized this will be the opposite of what you wanted but I think this is the correct behavior. You'll have to stay in NAV until passed the pop-up point and the switch to ANF (which wouldnt be hard in the real plane as the master mode selector is just by the throttle). Edit2: It looks like it works.

Weird, the first two pictures doesn’t look like PLAN mode. It should look more like the third picture.

HUD not switching in DYK Bomb Mode I see now that you mention that you are in ANF. Do you mean that the target ring shows the pop-up point in PLAN mode? Because if so that would be a bug.

HUD not switching in DYK Bomb Mode Can you give more information? What re your weapon settings? Are you in NAV mode? What do you see and what do you expect to see? Also, screenshot would help.

I believe there is a DCS-wide issue where damage to the landing gear only is not enough for the repair to trigger. I know I at least way back had a flat tire in the Su-25 and the repair didn’t happen. It might be that the damage to your wing is also below threshold for the repair to happen.

What kind of damage did you have? I think i've seen reports of repair not working for some types of damages like broken tires or bent landing gear.

Cobra thinks your VRAM is full and this is how it manifests itself in DCS. Try lowering texture quality, maybe that helps (as in set all graphics to lowest possible).

Wow thats weird! I would try uninstalling DCS and reinstalling it after removing the folder first. Maybe check if you can update your video driver. Was it always like this with the Viggen since you bought it or did it work at some point? Do you have any mods installed?

Can you post a screenshot? Is this while you are flying or does it also happens when standing still on the ground?

Was it after hard landing/over speeding while taxiing? If so this is the simulation of damaged gears. This happens in DCS side and I don’t know of any callback in the SDK for this hence the confused indication lights.

Thanks for the report. I've fixed this issue last night and hopefully we'll see it in the next open beta patch.

Can you upload your dcs.log? Start DCS and replicate the bug, then look into %SAVEDGAMES%\DCS Openbeta (if you use openbeta)\logs for the file and upload it here.

BELL character in log output. I’ve fixed this issue now by just removing those outputs to the log. Probably some conversion issue Unicode (Cyrillic) ASCII. It’s funny I have heard those beeps but thought it was just some random electronic sound my computer made (or that I was imagining it) lol. Thanks for reporting it!

Aiming the Rb04 comes to mind. I agree though but I guess you can’t keep adding functionality indefinitely and have to draw the line somewhere.

We’ve been informed there are several critical issues (I guess unrelated to Viggen) so the hotfix had to be postponed. We did get assurances that the broken Viggen won’t get patched into stable branch though.

I checked and yes it does unfortunately

The hotfix will come Monday or Wednesday. It’s already in the closed beta.

Thanks for the report. Hotfix incoming tomorrow friday.

Please accept my apologies guys.

I believe a fix will make it into tomorrows patch. I noticed that a recent change of the code for runway heading input looked strange, in just the same way as the changes related to TAKT-input was wrong so I changed it. Have yet to test it though.

Silent updates? The tricky part about automation tools is that it sometimes has an update for the updater, which you need to acknowledge. Then the update itself is very different in how long it takes and a dedicated server would have to be down the maximum time any update would take (like 3 hours). And DCS can’t be running as long the updater is running. I guess if you’d start notepad first (to handle any stray keypress) and then press Enter after starting the updater it will either acknowledge a new updater or start updating, then waiting a few minutes for updater to finish downloading and pressing enter again will either start the update or switch to html download, then wait 3 hours and press enter again for acknowledging the update has finished (which should close the updater and allow DCS to start). Then Alt-F4 and N to close Notepad. Edit: do you need to acknowledge the switch to HTML download? If so the script needs to run for 6 hours.

There will be a hotfix tomorrow. In the meantime: 1) avoid having friendly radars in the mission 2) avoid inputting codes into TAKT

Thanks for the reports! I’ve replicated the issue, fixed it and pushed a updated binary to EDs server. I hope ED will have the time to hotfix Viggen. The issue with inputting codes into TAKT is also fixed.

And if It's not clear its not because we're lazy but for automatic test-systems and scheduling updates when I'm not working.