DCS Questions

Is it possible to have controls mapped for the A10-C transfer to all the other modules? and to transfer the control profiles between alpha and beta installs?

Just getting back to DCS after many years absence (last spent significant time with it in Blackshark1), and I picked up some modules during the sale, but DCS has gotten so much more complicated to get configured since BS1… not only did I need to install 1.5 and 2.1 and have to activate all my modules independently (what a pain), but now it seems like I have to configure separate controls for each module, and in each alpha/beta version?

Hoping there’s some non-obvious shortcut so I can get up and going without so much redundant configuration (I noticed I have less patience than I did during BS1 days).

Thanks in advance, and if there’s some nice guide for noobs I’m missing, feel free to point me in the right direction and tell me to RTFM.

1 Like

As for the guides … Chuck Owl comes to mind … Chuck's Amazing DCS Guides

I’m also wondering about the control configuration stuff though …

1 Like

You can go to: C:\Users\ [username] \saved games\DCS [version]\config\input\

Then take the module(s) of your choice, copy and paste the whole map, then go back to C:\Users\ [username] \saved games\ and choose a different version (i.e. from beta to alpha) and copy paste. This way you can copy paste all your controls inbetween different versions

1 Like

Indeed, but unfortunately this does not copy the control configuration over between aircraft types. I don’t think that that is possible.

Yes it sux to have to remap every thing. Also check for assigned axis conflicts. Dcs has a habit of assigning axis to every controller that’s plugged in.

I just downloaded 1.57 and enjoying the sites and sounds on my new computer. Beauty

another noob question: I have bought modules but cant seem to add, I am being asked to buy them, as an example FC3. I have bought this module but they want me to buy.
Am I missing something or do we require to buy upgrades in plane modules
thanks

no u dont need to rebuy anything, try checking the module manager.

Thanks Sryan, checked my download manager, logged in, and downloading all modules now :slight_smile:

1 Like

Figured this might be the best place to ask:

My DCS 2.1 OpenAlpha keeps crashing in multiplayer. Just now, I tried to fly on BlueFlag with MacLean and Bogus but my DCS client kept crashing a few minutes after takeoff each time. I ran a repair after the first crash.

After the first crash, the server would not allow me in (pure client is required) but restarting the pc fixed that.

Is there anything else I can do (already tried DCS Repair) to fix this problem?
So I can play mutliplayer again?

You could try a fresh config file set, just to narrow it down. Rename the existing directory and let DCS create a fresh one, i.e. here:

X:\Users\(YourWindowsUsername)\Saved Games\DCS.openalpha

If it starts and connects ok then copy back in your Config/Input directories to save having to rebind everything again.

Other than that, what’s the most recent Logs\ .crash file say? Example: my last one lives here:

X:\Users\(YourWindowsUsername)\Saved Games\DCS.openalpha\Logs\DCS.openalpha-20170813-191544.crash

and says:

# -------------- 20170813-191544 --------------
C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_2386fda73b467ac8\nvwgf2umx.dll
# C0000005 ACCESS_VIOLATION at 437B06AC 00:00000000

(it was a Rift crashing with a Nvidia driver error)

1 Like

Thanks for the help!

My crash file:

# -------------- 20171001-115455 --------------
C:\Program Files\Eagle Dynamics\DCS World 2 OpenAlpha\bin\NGModel.dll
# C0000005 ACCESS_VIOLATION at 6ADF1CF1 00:00000000
00000000 00000000 0000:00000000 
6ADF1CF1 0071D340 0000:00000000 C:\Program Files\Eagle Dynamics\DCS World 2 OpenAlpha\bin\NGModel.dll ?resetMults@NGModelLods@model@@UEAAXXZ()+9571
715E5371 0071D380 0000:00000000 C:\Program Files\Eagle Dynamics\DCS World 2 OpenAlpha\bin\Visualizer.dll ?DrawFlatShadows@RenderParserImpl@@QEAAXXZ()+1A1
715E9A95 0071DA80 0000:00000000 C:\Program Files\Eagle Dynamics\DCS World 2 OpenAlpha\bin\Visualizer.dll ?drawDots@RenderParserImpl@@QEAAXXZ()+39F5
71610EBC 0071F200 0000:00000000 C:\Program Files\Eagle Dynamics\DCS World 2 OpenAlpha\bin\Visualizer.dll ?Render@SceneManager_Implement@@UEAAXXZ()+19CC
D76B34A6 0071F270 0000:00000000 C:\Program Files\Eagle Dynamics\DCS World 2 OpenAlpha\bin\DCS.exe
D76BDC9E 0071F2D0 0000:00000000 C:\Program Files\Eagle Dynamics\DCS World 2 OpenAlpha\bin\DCS.exe
D736307B 0071F300 0000:00000000 C:\Program Files\Eagle Dynamics\DCS World 2 OpenAlpha\bin\DCS.exe
D73648F9 0071F9B0 0000:00000000 C:\Program Files\Eagle Dynamics\DCS World 2 OpenAlpha\bin\DCS.exe
D77FCEBF 0071F9F0 0000:00000000 C:\Program Files\Eagle Dynamics\DCS World 2 OpenAlpha\bin\DCS.exe
A6FA2774 0071FA20 0000:00000000 C:\WINDOWS\System32\KERNEL32.DLL BaseThreadInitThunk()+14
A81F0D51 0071FA70 0000:00000000 C:\WINDOWS\SYSTEM32\ntdll.dll RtlUserThreadStart()+21

Also had another crash in openbeta after that (single player), which seems to have something to do with rendering too:

# -------------- 20171001-132207 --------------
C:\Program Files\Eagle Dynamics\DCS World OpenBeta\bin\Visualizer.dll
# C0000005 ACCESS_VIOLATION at 71ADB986 00:00000000
00000000 00000000 0000:00000000 
71ADB986 012FE760 0000:00000000 C:\Program Files\Eagle Dynamics\DCS World OpenBeta\bin\Visualizer.dll ?DrawFlatShadows@RenderParserImpl@@QEAAXXZ()+C6
71ADF06B 012FE7C0 0000:00000000 C:\Program Files\Eagle Dynamics\DCS World OpenBeta\bin\Visualizer.dll ?drawDots@RenderParserImpl@@QEAAXXZ()+28DB
71ADED08 012FE7F0 0000:00000000 C:\Program Files\Eagle Dynamics\DCS World OpenBeta\bin\Visualizer.dll ?drawDots@RenderParserImpl@@QEAAXXZ()+2578
71B02CB3 012FF0E0 0000:00000000 C:\Program Files\Eagle Dynamics\DCS World OpenBeta\bin\Visualizer.dll ?Render@SceneManager_Implement@@UEAAXXZ()+1383
446FBBE6 012FF150 0000:00000000 C:\Program Files\Eagle Dynamics\DCS World OpenBeta\bin\DCS.exe
447054FE 012FF1B0 0000:00000000 C:\Program Files\Eagle Dynamics\DCS World OpenBeta\bin\DCS.exe
443B2EBD 012FF1E0 0000:00000000 C:\Program Files\Eagle Dynamics\DCS World OpenBeta\bin\DCS.exe
443B4739 012FF8B0 0000:00000000 C:\Program Files\Eagle Dynamics\DCS World OpenBeta\bin\DCS.exe
4483C13F 012FF8F0 0000:00000000 C:\Program Files\Eagle Dynamics\DCS World OpenBeta\bin\DCS.exe
A6FA2774 012FF920 0000:00000000 C:\WINDOWS\System32\KERNEL32.DLL BaseThreadInitThunk()+14
A81F0D51 012FF970 0000:00000000 C:\WINDOWS\SYSTEM32\ntdll.dll RtlUserThreadStart()+21

So perhaps graphics driver is at fault here? Or RAM?

They looks like straight DCS crashes rather than within the graphics driver. If you’ve tried with a clean user config and it’s recreatable then reporting at ED forums might be best, as @bignewy keeps a track of what’s been reported already.

If you run an overclock then might be worth undoing that just to see if it helps.

Do you have any usermods, as in I think DCS Repair will integrity check and fix files that show a difference, but you might need to manually remove anything that has been written in manually? (i.e. start with a clean CoredMods/aircraft install directory etc).

Hi guys

I am happy to take a look, if you can post your system spec and dcs log folder zipped in a post on the forum.

https://forums.eagle.ru/forumdisplay.php?f=487

a guide for posting logs can be found in my signature here
https://forums.eagle.ru/member.php?u=86982

also worth taking a look at doing a cleanup and repair for non steam users
https://www.digitalcombatsimulator.com/en/support/faq/709/

thanks

3 Likes

Thanks for the help!
Apart from Mudspike skins, I don’t think I’ve ever had any mods.
I do have a slight CPU overclock though, and haven’t tried a fresh config file yet.

Will update when I go troubleshooting again, and post in the eagle forums if this doesn’t solve it.

Today I tested with a fresh config file, except for the input folder. (and temporarily undid my overclock through Ai Suite)

Flew UH-1H on BlueFlag again, which consistently got me crashed (3 times yesterday) and no crashes.

Now to put the Mudspike skins back and I’m back in action! Weird problem though…

1 Like