Dustoff74

It looks like the throttle commands work all as toggles right now. It doesn't mater what I press, R-Ctrl Home, R-Shift Home, R-Alt Home. They all toggle between OFF and IDLE. Setting my HOTAS that way is impossible.

I don’t know if it is related, but also the day/night rocker on the AMPCD seems to work the wrong way round. Selecting day dims the display, night makes it brighter. The lost gain control makes the map pretty much useless.

Great to hear and glad I could help!

Hey guys, I didn’t read the whole thread, so this might have come up already. I started getting the Track-IR plugged/unplugged thing in the last couple of month. After disabling Device Hotplug in the control settings it never happened since. You might wanna try this.

Hi @Flappie, thanks for shedding some light on my issue. I was afraid you would say something along those lines. Right now it doesn't make any sense to upgrade the RAM since I plan to retire the whole system, as soon as I can upgrade my main PC. That is, when GPUs will be available again, one fine day, in a galaxy... well, fingers crossed! I'll increase my pagefile and hope it helps until then. Thanks for your help, I really appreciate it!

Hi @Flappie, thanks for looking into it. I attached the dcs.log and dcs.log.zip. The .zip didn't get updated with the latest crash, but at least with the crashes before. I guess it's some kind of special zip, because I'm unable to open it? dcs.log dcs.log-20210302-190354.zip

After a while , ranging from about 15min to 1 hour DCS freezes then CTD without any error message. So far only in MP on different serves, lot of player seem to make it worse. What I did so far: -Repair DCS -Check Pagefile (set to manual 16384 for 16GB of RAM) -Put the autoexec.cfg into .../config, but it doesn't seem to to anything. -the .zip log is corrupted and it didn't get created with the latest crashes. -all crash logs involve the # C0000005 ACCESS_VIOLATION but with different files: d3d11.dll, edCore.dll, DCS.exe Right now I'm running DCS on my backup rig which is a bit dated, but runs DCS fine besides the crashes. Latest crash log: # -------------- 20210303-204239 -------------- DCS/2.5.6.61527 (x86_64; Windows NT 10.0.19042) D:\Eagle Dynamics\DCS World OpenBeta\bin\edterrainGraphics41.dll # C0000005 ACCESS_VIOLATION at 2D5252A5 00:00000000 SymInit: Symbol-SearchPath: '.;D:\Eagle Dynamics\DCS World OpenBeta;D:\Eagle Dynamics\DCS World OpenBeta\bin;C:\WINDOWS;C:\WINDOWS\system32;SRV*C:\websymbols*http://msdl.microsoft.com/download/symbols;', symOptions: 530, UserName: 'Henning' OS-Version: 10.0.19042 () 0x100-0x1 0x00007F94D4529DE5 ((module-name not available)): (function-name not available) + 0x0 0x00000129AAD5BA18 ((module-name not available)): (function-name not available) + 0x0 0x00007F94D452B990 ((module-name not available)): (function-name not available) + 0x0 0x0000012C28EB9CA8 ((module-name not available)): (function-name not available) + 0x0 0x0000000000002E50 ((module-name not available)): (function-name not available) + 0x0 0xFFFFFF97A7004B3E ((module-name not available)): (function-name not available) + 0x0 0x00000120B39DEFC0 ((module-name not available)): (function-name not available) + 0x0 0x0000012C2E9D5C00 ((module-name not available)): (function-name not available) + 0x0 0x0000000000004678 ((module-name not available)): (function-name not available) + 0x0 0xFFFFFF97A7004B4F ((module-name not available)): (function-name not available) + 0x0 0xFFFFFF97A7004DD8 ((module-name not available)): (function-name not available) + 0x0 0xFFFFFF97A7004B4E ((module-name not available)): (function-name not available) + 0x0 0x0000012C2E9D5C00 ((module-name not available)): (function-name not available) + 0x0 0x00000120B39DEFC0 ((module-name not available)): (function-name not available) + 0x0 0x00007F94D452C590 ((module-name not available)): (function-name not available) + 0x0 0x00000129AAD5BA18 ((module-name not available)): (function-name not available) + 0x0 0xFFFFFF97A700EB45 ((module-name not available)): (function-name not available) + 0x0 0x00000120B39DEFC0 ((module-name not available)): (function-name not available) + 0x0

Hey favorite feline friends. Yesterday I came across a new documentary by former F-14 pilot Mark Vizcarra. I bought it instantly and really love it. I'm in no way associated with the production company, just sincerely enjoyed it and thought you might like it as well! Tomcat Tales

Someone told me,they changed something with the drag. Using the 1% rule you end up on a much too tight downwind, like 0.8NM. With a moderate 2.5g pull I pretty much nail 1.2NM offset.

I just made a USB converter for my G940 pedals. Somehow there is an attachment missing above. So if anybody else is attempting this, check your wires. 1-4 are correct but ground is on 5. I used an Arduino Pro Micro clone for 10$ and an RS-232 extension cable for 4$. Programming with MMJOY2 was an easy process.

Hi Cupra, guck mal bei Q14. Tacview Documentation Ich mußte bei mir den Eintrag in die Export.lua auch händisch machen. Danach sollten die Files automatisch in Deinem Windows Dokumenteordner im Subordner Tacview landen.

Hi Sabre, please don't get me wrong. I'm convinced that all the missions worked flawlessly and I can't imagine what a nightmare it must be to develop for such an always changing environment DCS is. I'm in no way complaining, in fact the opposite is the case. I feel DCS is lacking a lot of training opportunities. You get the airframe specific manuals and a couple of system focused training missions and then you are on your own. Your missions teach how to employ the airframe. So I would love to see you and other more training focused developers thrive! I'm pointing out stuff I see and experience to make your campaigns even better. That's what you get for throwing yourself into a feedback focused pilot community If you would prefer feedback via other channels than the forum, please just let me know.

OK, here is my feedback for mission #9: Somehow the headings don't take the wind into consideration. You fly the headings, you miss the trigger zones. Just flying the waypoints works great und no complaints from the IP. Flying the second approach the IP advised me to keep "pattern altitude" (we are not flying a pattern, but a straight in approach, so initial altitude would be more appropriate) until that 5NM lading clearance trigger. Since 2500ft equals roughly 8NM with a 3° glide path that trigger zone should be further out. After that I get a "maintain 120", which I would understand as "maintain 120 KTS". What is meant though is the heading, which doesn't make any sense, after I'm cleared for the approach. Also I got a "MAINTAIN ANGELS 7" while I was flying exactly at 7000ft. I don't know if that's just a generic call, but it's frustrating as hell. I don't know if that's you Sabre, but while the missions are great, don't expect me to ever buy this guy a beer. I really, really hate him!

Manual reversion seems to be fixed, as I could fly without any issue. But the voiceover and system failures appear to be out of sync. I get the instructions to do something within 30sec but the failure itself happens just after my actions. I would say, I just wait until it actually happens, but then the IP starts yelling at me and fails the mission

Hi Sabre! Thanks for the timely reply. UTC makes sense, since all of aviation uses Zulu for everything. So I just insert a +4:00 local time adjustment and everything is back in sync.