MagnumHB

The fixes covered by this radio mod should definitely be included in an official release. I suggest doing whatever is the most expedient way of making that happen. Frankly, I'm barely playing 1.2.0 right now because of the stability issues, so a mod for it would be of little use compared to having these things resolved in the next official release.

I got the following error while using the rearm GUI. It appeared to occur when, after clicking on a station to select a weapon, I then clicked outside of the resulting drop-down in order to cancel it. # -------------- 20120821-031012 -------------- # C0000005 ACCESS_VIOLATION at E6E47B8F 00:00000000 00000000 00000000 0000:00000000 E6E47B8F 0028F5B0 0000:00000000 ?setSelected@MenuItemBase@gui@@QEAAX_N@Z()+F E6E47212 0028F5E0 0000:00000000 ?onSubMenuChanged_@Menu@gui@@MEAAXPEAV12@PEAVMenuItemBase@2@@Z()+42 E6E47534 0028F610 0000:00000000 ?onVisibleChanged_@Menu@gui@@MEAAX_N@Z()+34 E6E66182 0028F640 0000:00000000 ?setVisible@Widget@gui@@UEAAX_N@Z()+12 E6E26B77 0028F690 0000:00000000 ?getActiveWindow@WindowsManager@gui@@QEBAPEAVWindowBase@2@XZ()+B67 E6E1E4FC 0028F6F0 0000:00000000 ?processMessages@GUI@gui@@QEAAXXZ()+8C 401CC81C 0028F720 0000:00000000 402508E8 0028F790 0000:00000000 40251853 0028FC60 0000:00000000 40254107 0028FD10 0000:00000000 76CB652D 0028FD40 0001:0001552D C:\Windows\system32\kernel32.dll BaseThreadInitThunk()+D 773AC521 0028FD90 0001:0002B521 C:\Windows\SYSTEM32\ntdll.dll RtlUserThreadStart()+21 Faulting application name: DCS.exe, version: 1.2.0.3205, time stamp: 0x4ff3450d Faulting module name: dxgui.dll, version: 1.2.0.3205, time stamp: 0x4fe36536 Exception code: 0xc0000005 Fault offset: 0x0000000000037b8f Faulting process id: 0xc3c Faulting application start time: 0x01cd7f49bd6e4502 Faulting application path: E:\Program Files\Eagle Dynamics\DCS World\bin\DCS.exe Faulting module path: E:\Program Files\Eagle Dynamics\DCS World\bin\dxgui.dll Report Id: b94f14b3-eb3d-11e1-922a-1c6f65d54a89

Mustang, I really hope you have a collection of all these fixes you've put together so they can be put into the next release.

P-51 is still in beta as well, but I've frequently heard the sentiment that we've never really left beta in certain areas regardless of whether a given release is officially regarded as such or not.

This was a new one for me, but apparently it was an issue for people as far back as 1.1.0.8. I guess I'll turn on force feedback for now to match the recommended fix in that thread, but it would be nice to get this resolved for real. Here are the logs: # -------------- 20120814-012634 -------------- # C0000005 ACCESS_VIOLATION at E6DF7FC4 00:00000000 00000000 00000000 0000:00000000 E6DF7FC4 0028EA50 0000:00000000 ?GetKey@gCloudGenZW@@UEAAPEAUMaterialKey_t@Graphics@@XZ()+53F4 E6DF982C 0028ECB0 0000:00000000 ?GetLoadStepCount@gCloudGenZW@@UEAAHXZ()+26C E6DFA9DD 0028EEB0 0000:00000000 ?GetLoadStepCount@gCloudGenZW@@UEAAHXZ()+141D E6DFAB43 0028EF00 0000:00000000 ?GetLoadStepCount@gCloudGenZW@@UEAAHXZ()+1583 E8F64D90 0028EF40 0000:00000000 ?Update@DXRenderer@Graphics@@UEAAXXZ()+90 E77F1897 0028F0A0 0000:00000000 ?Preload@SceneManager_Implement@@UEAAXAEBVdPosition@@W4vCameraType_e@@@Z()+4E7 3F42D4E6 0028F0D0 0000:00000000 E72912FD 0028F100 0000:00000000 E72BC3E7 0028F1A0 0000:00000000 F607A5DD 0028F1E0 0000:00000000 ??1Reader@Mail@@UEAA@XZ()+26D E7299214 0028F250 0000:00000000 E72992C1 0028F2A0 0000:00000000 E729376E 0028F2D0 0000:00000000 E72BAD13 0028F300 0000:00000000 E72D0983 0028F330 0000:00000000 3F4161C5 0028F390 0000:00000000 3F42C964 0028F3C0 0000:00000000 3F42C848 0028F3F0 0000:00000000 3F4B08E8 0028F460 0000:00000000 3F4B1853 0028F930 0000:00000000 3F4B4107 0028F9E0 0000:00000000 770D652D 0028FA10 0001:0001552D C:\Windows\system32\kernel32.dll BaseThreadInitThunk()+D 7730C521 0028FA60 0001:0002B521 C:\Windows\SYSTEM32\ntdll.dll RtlUserThreadStart()+21 Faulting application name: DCS.exe, version: 1.2.0.3205, time stamp: 0x4ff3450d Faulting module name: ZweiBlau.dll, version: 1.2.0.3205, time stamp: 0x4fe36526 Exception code: 0xc0000005 Fault offset: 0x0000000000027fc4 Faulting process id: 0xfe4 Faulting application start time: 0x01cd79b4561ecf6c Faulting application path: E:\Program Files\Eagle Dynamics\DCS World\bin\DCS.exe Faulting module path: E:\Program Files\Eagle Dynamics\DCS World\bin\ZweiBlau.dll Report Id: 15963ac8-e5af-11e1-9703-1c6f65d54a89

I also got this error during SP the other day, playing the second mission of Wags' updated Georgian Hammer campaign. The timing was seemingly random, with no immediately apparent cause. # -------------- 20120813-033919 -------------- # C0000005 ACCESS_VIOLATION at EC8BC0FB 00:00000000 00000000 00000000 0000:00000000 EC8BC0FB 001EEE70 0000:00000000 DebugSetMute()+8FB EC8B14EE 001EEED0 0000:00000000 Direct3DCreate9Ex()+F08E EC8E1D4F 001EEF20 0000:00000000 Direct3DCreate9()+869F EC8E1CA8 001EEFE0 0000:00000000 Direct3DCreate9()+85F8 E7768E88 001EF1B0 0000:00000000 E7768F77 001EF200 0000:00000000 E83FC372 001EF230 0000:00000000 ??0RadioButtonTheme@gui@@QEAA@PEAVRadioButton@1@@Z()+1B2 E8409B92 001EF260 0000:00000000 ?drawBkg_@Theme@skin@gui@@MEBAXXZ()+12 E8409B49 001EF290 0000:00000000 ?draw@Theme@skin@gui@@UEBAXXZ()+19 E841644D 001EF2C0 0000:00000000 ?draw_@Widget@gui@@MEBAXXZ()+1D E8416352 001EF2F0 0000:00000000 ?draw@Widget@gui@@UEBAXXZ()+32 E83D7CAC 001EF320 0000:00000000 ?drawChildren_@Container@gui@@MEBAXXZ()+2C E8416352 001EF350 0000:00000000 ?draw@Widget@gui@@UEBAXXZ()+32 E83D7CAC 001EF380 0000:00000000 ?drawChildren_@Container@gui@@MEBAXXZ()+2C E8416352 001EF3B0 0000:00000000 ?draw@Widget@gui@@UEBAXXZ()+32 E83D7CAC 001EF3E0 0000:00000000 ?drawChildren_@Container@gui@@MEBAXXZ()+2C E8416352 001EF410 0000:00000000 ?draw@Widget@gui@@UEBAXXZ()+32 E83D7CAC 001EF440 0000:00000000 ?drawChildren_@Container@gui@@MEBAXXZ()+2C E8416352 001EF470 0000:00000000 ?draw@Widget@gui@@UEBAXXZ()+32 E83D7CAC 001EF4A0 0000:00000000 ?drawChildren_@Container@gui@@MEBAXXZ()+2C E8416352 001EF4D0 0000:00000000 ?draw@Widget@gui@@UEBAXXZ()+32 E83D5E5D 001EF500 0000:00000000 ?captureMouse@WindowsManager@gui@@QEAAXPEAVWidget@2@@Z()+75D E83CE177 001EF540 0000:00000000 ?draw@GUI@gui@@QEAAXXZ()+87 EB223034 001EF750 0000:00000000 ?Render@SceneManager_Implement@@UEAAXXZ()+664 3FF5425B 001EF7E0 0000:00000000 3FF5624D 001EF840 0000:00000000 3FF6C964 001EF870 0000:00000000 3FF6C848 001EF8A0 0000:00000000 3FFF08E8 001EF910 0000:00000000 3FFF1853 001EFDE0 0000:00000000 3FFF4107 001EFE90 0000:00000000 77B2652D 001EFEC0 0001:0001552D C:\Windows\system32\kernel32.dll BaseThreadInitThunk()+D 77C5C521 001EFF10 0001:0002B521 C:\Windows\SYSTEM32\ntdll.dll RtlUserThreadStart()+21 Faulting application name: dcs.exe, version: 1.2.0.3205, time stamp: 0x4ff3450d Faulting module name: d3d9.dll, version: 6.1.7601.17514, time stamp: 0x4ce7c5a4 Exception code: 0xc0000005 Fault offset: 0x000000000001c0fb Faulting process id: 0x13a0 Faulting application start time: 0x01cd7903c32a2590 Faulting application path: E:\Program Files\Eagle Dynamics\DCS World\bin\dcs.exe Faulting module path: C:\Windows\system32\d3d9.dll Report Id: 77a7090b-e4f8-11e1-8371-1c6f65d54a89

Have you tried this resolution?

I haven't gotten this error since updating my C++ redistributables and following the fix outlined in this post. The redistributables are available here: x86, x64, x86 SP1, x64 SP1. I'm not sure which ones are truly necessary, but it won't hurt to install all of them.

Pressing on the toe brake should apply brakes and pressing on the pedal should yaw in the corresponding direction. My Saitek combat pedals are set up as follows: Rudder: JOY_RZ Left Wheel Brake: JOY_X (invert axis) Right Wheel Brake: JOY_Y (invert axis)

It might be worth trying Mustang's z-fighting fix here: http://forums.eagle.ru/showpost.php?p=1509264&postcount=139

I got a chance to play this last night, and we had one problem with it. Due to a combination of circumstances, we missed a tasking and were unable to complete the mission since we didn't know where to go next. It would be great if there were a way to repeat a tasking either manually (F10 radio menu) or automatically. Otherwise, great mission.

Indeed, I suspect this is not really so much a fix as a workaround for one particular case. I would not be surprised to see my connection be unstable on a different server, for example.

I was miraculously able to play a solid hour and a half or so earlier this evening without crashing or being disconnected. Changing my connection speed in-game to ADSL 1024 seemed to solve the connectivity problem, as I stated previously. It may be the case that the host and other clients were also set the same way, but I can't guarantee that. My crash problem was resolved with the fixes in this thread.

Interestingly, I changed my connection speed to ADSL 1024 last night, which I believe matched the host, and I was able to maintain a stable connection for long enough to get in the air and fire a few weapons. Unfortunately, I then got a regular freeze, followed by the master server connection crash when I tried to restart.

BRooDJeRo - These connection issues are widespread even for groups that regularly play together that have never had unstable connections and don't have to deal with immature server admins. This is a legitimate, crippling technical issue, and should not be downplayed. Multiplayer is currently unusable as far as I have seen.

Mustang - It looks like this error is still present: http://forums.eagle.ru/showthread.php?t=85114

It's possible that may even make the problem worse. If my theory is correct, any client joining after the AI is activated would be disconnected.

Perhaps the problem is some sort of AI/Client sync error.

Right now, I would be happy with stable multiplayer that doesn't crash or disconnect for no apparent reason.

I have noticed an added stall buffet effect on the A-10 in 1.2.0. Is this intentional, or an unintended side effect of some other change (to the P-51 perhaps)?

Sure looks like it to me, although I didn't notice any difference between SAS yaw on or off. The ball was all over the place either way.

The S-60 is definitely going to be a great addition to DCS. We've been in need of something between the 23mm guns and SAMs.

Nearly every combat loadout used in A-10C is asymmetrical due to the targeting pod.

Right on. Besides, who really cares about some minor cosmetic feature like this when there are real, serious bugs to be dealt with? The idea of spending time altering the physical model for something like this while critical aircraft systems are non-functional (as of 1.1.2.1) would be laughable if it weren't so depressing. Plus, if we really want to get pedantic, since we technically have aircraft from a couple years ago before the pods started coming off (as far as I know anyway), it would be correct to keep them on.

The content of missions in DCS is a matter of whatever the mission builder decides to put in. Many missions have heavy SAM presence simply as a way to increase the difficulty level.