SnorreSelmer

Thanks ApoNOOB, that fixed it! I had to manually remove the NS430 key as there was no reg-file for that one, but it was an easy job.

I already tried that, but I'll try the registry fixes, then do another round of "manual" activations.

The short version: I upgraded my i5 6600K to an i7 7700, and DCS wants me to activate the modules again because of hardware changes. This is expected, this is fine. What's NOT fine is that when I go through the activation process, I click "OK" at the end, and the activation application hangs for ~30 seconds and silently dumps to desktop with no error. When I run DCS again, it asks me (again) to activate the modules I just manually ran the activation for. Is my only option to do a clean Windows reinstall to get out of this endless loop of unhelpfulness? I'm on my last activation on several modules, so I'd like to avoid this in case I need to wait for 30 days to get to fly some modules.

I agree with this, but since the title of the thread is what it is, maybe the original poster could collect each issue in this thread into a bullet-list and mark th issues as "REPORTED" or "FIXED" as we move along. That, or have an official pinned bug-track post (locked so people don't post new issues there, but make separate ones per issue?) in a similar manner.

I can get my Mi-8 buddies to verify it if you wish, I have several.

The LSHIFT+LALT+B combo doesn't show he GPS unit in VR, only the move/resize bar.

I did something similar, flying from UGTB (Tbilisi Lochini), via DF (Mukhrani NDB), AL (ALI NDB) to UGKO (Kutaisi), and it didn't switch to the next leg when I neared Mukhrani NDB.

dxdiag attached. I flew the same mission with Entropy and Looney DxDiag.txt

Hi all. I've tried to update DCS Open Beta both via the command-line and the updater link in the start menu, but they both report my 1.5.6 install being the latest version. I even tried to run "dcs_updater update 1.5.7" without any luck. Any tips on how to solve this?

Only way I can think of is to dip the nose and hope you have enough altitude to get out. As for avoiding it, that's fairly easy: when nearing translation, make sure you never (NEVER) descend faster than 3m/s. Doing the final slowdown in ground effect is a good way to do it, then you don't need to descend much to get wheels on the ground. Sent from my Nexus 5 using Tapatalk

Sounds like a Depth of Field issue.. DoF is calculated from the the player cockpit, not camera location. Sent from my Nexus 5 using Tapatalk

Too young to ever have owned an actual Walkman? I call "working as intended" on this... Sent from my Nexus 5 using Tapatalk

I used the OGG converter in foobar2000 (best music player ever), worked fine. Sent from my Nexus 5 using Tapatalk

Sweet! Can't wait to try this.

While the autopilot channel is active, the light stays green. If you interfere, the autopilot isn't quite off, so the lights are off. Once you hit the off button, the autopilot is properly off, and the lights will reflect this. Sent from my Nexus 5 using Tapatalk

Working as intended.. In real life the autopilot is disengaged when you depress micro switches on the anti-torque pedals. Since this is not easily modeled in a sim, a compromise was made, and the result was that the disconnect is done by moving the pedals. Once the pedals are returned to the same position as they were when you engaged the autopilot heading hold channel, autopilot will resume control. Sent from my Nexus 5 using Tapatalk

When it was revealed on the Viggen live stream that a new map was in the early stages of planning or something, I was really excited. I'm hoping for a Baltic Sea area scenario as it would be perfect for a 70s/80s cold war scenario with the AJS-37, MiG-21, Mi-8 and the F-5... Sent from my Nexus 5 using Tapatalk

Bunyap covers bombs on targets of opportunity in one of the last videos in his Viggen series. Sent from my Nexus 5 using Tapatalk

Tried it the other day, didn't work. But that was before the latest update I think, maybe they added that functionality now? Sent from my Nexus 5 using Tapatalk

The QFE question asked earlier today (JTAC QFE) could definitely benefit from kneeboard interaction. Sent from my Nexus 5 using Tapatalk

Yes, if you take the difference in altitude from a known reference with QFE (like the starting airfield), then you should be able to add/subtract the number of mB needed to get the target QFE. There will be inaccuracies, but they should be manageable. This ofcourse has the prerequisite that you don't run Dynamic Weather Remember, the swedish doctrine was to use the Viggen for pre-planned attacks against Russian forces on swedish soil, so they would have detailed knowledge of terrain, and could get barometric info from nearby weather stations. The AJS 37 wasn't really designed for CAS and loitering for targets. ;) Sent from my Nexus 5 using Tapatalk

p.51: Target point marked as T3, should be M3? p.57: PPI scope mislabled as PPO

Excellent work Chuck! Sent from my Nexus 5 using Tapatalk

Ah, yes, now I see what you're saying. My bad! Sent from my Nexus 5 using Tapatalk

Cool! Sent from my Nexus 5 using Tapatalk