daiqan

still happening

When flying on Germany CW I've noticed the flight path vector and vertical speed indicator are not working correctly. For example sometimes I'd clearly gain altitude while the fpv would still be pointing to the ground. Or I'd enter level flight after take off and the fpv would keep pointing up high. The vsi seems to be in sync with the fpv and incorrect as well. Through_The_Inferno_GER_v1.0.2-20250801-215041.trk

Same issue here. I have the hot mic, ptt and vox positions bound to a three way switch and it doesn't seem to register the inputs at all. The switch works fine with other bindings and I've tried using other switches which didn't work either though.

[possible solution] www.reddit.com/r/dcsworld/comments/1itd5x8/launcher_error_after_latest_update/ on reddit is was suggested to do the following: - run notepad as admin - open C:\Windows\System32\drivers\etc\hosts - deposit 185.195.197.4 api.digitalcombatsimulator.com - type "ipconfig /flushdns" in the windows command line (search cmd in windows start) This worked for me but this is merely a workaround and I opened an ed support ticket so I'll keep you updated as soon as I receive news from them. [Edit] reinstalling the game and deleting the saved games folder didn't help either. When I start the launcher it fails to log in and after some time displays "bad connection". After some more time has passed the error "Launcher error. Code:-28 Message: Error: News List loading error: Timeout was reached" pops up. When I launch the game anyway it tries to login in again and then starts in offline mod. This never happened before, my internet connection is fine and it just started after the latest update today. 2025-02-19 18:35:25.126 ERROR ASYNCNET (2744): HTTP request lnch:getUpdates failed with error 28: Timeout was reached 2025-02-19 18:35:25.158 ERROR LAUNCHER (CrBrowserMain): GUI ERROR:["hasUpdate request fault",{"name":"API Error","code":-28,"message":"Timeout was reached","method":"hasUpdate","queryOptions":{"persistent":true,"parseJSON":true,"logQueries":true,"logResult":true},"stack":"API Error: Timeout was reached\n at onFailure (https://launcher/ui/assets/index-CGuOwTVl.js:4:1547)"}] 2025-02-19 18:35:55.140 ERROR ASYNCNET (2744): HTTP request lnch_1 failed with error 28: Timeout was reached 2025-02-19 18:35:55.156 ERROR LAUNCHER (CrBrowserMain): GUI ERROR:[{"name":"API Error","code":-28,"message":"Timeout was reached","method":"httpGET","queryParams":"master:en/export/requirements/","queryOptions":{"persistent":true,"parseJSON":true,"logQueries":true,"logResult":true},"stack":"API Error: Timeout was reached\n at onFailure (https://launcher/ui/assets/index-CGuOwTVl.js:4:1547)"}] 2025-02-19 18:36:25.153 ERROR ASYNCNET (2744): HTTP request getNewsList_en1 failed with error 28: Timeout was reached 2025-02-19 18:36:25.218 WARNING ASYNCNET (Main): Ignoring duplicate request to dcs:ping while one is already in flight. 2025-02-19 18:36:25.231 ERROR LAUNCHER (CrBrowserMain): GUI ERROR:["Fail to load","News",{"code":-28,"message":"News List loading error: Timeout was reached","stack":"Error: News List loading error: Timeout was reached\n at gm.loadedDataProcessing (https://launcher/ui/assets/index-CGuOwTVl.js:18:40389)\n at https://launcher/ui/assets/index-CGuOwTVl.js:16:65998"}] 2025-02-19 18:36:25.231 ERROR LAUNCHER (CrBrowserMain): GUI ERROR:["Unhandled error",{"message":{"code":-28}}] dcs.log

This. You are exactly right. I'm so sorry for bothering you with this I've never used the lst and didn't notice that it was on. Thank you.

So I flew as cpg in mp with a human pilot powered everything up and we took off. Basically the TADS when deslaved was moving on its own in a perfect square motion. It would start moving right then down, left and up, repeat. Only when slaved it wouldn't do that. Was that an error with start-up procedure? I'm pretty sure it's not a hardware issue (changed a few settings and the little joystick thing in the cockpit which usually moves when you use the TADS or curser didn't move either). When starting up I think I did all the necessary steps like powering up the TADS and laser and stuff. However we took off pretty quick so there might have been things the pilot or I forgot about when starting up. Although I'm not aware of any steps the pilot has to make to start up the TADS. Is that a known bug or just user error? Weird thing is we took off two times right before this and the issue did not occur.