MTrenda

Wanted to report that in Greywolf's seperatists aggression mission there are two mision that require static object to be blown up. Two Ammo depots and a command center. The trigger to determine they are dead are "unit dead" Ammo depot and "Unit dead" command Center. i believe the unit's are under structures wharehouses.(sorry at work right now) The issue is when you begin seperatist agression these two missions report as completed. it appears as though these static units are considered dead even though the Dead check box is unchecked. removing the condition for unit dead in these missions resolves the 'completed' at the begining of the game but then you can not determine when the ammo dumps or the command center are destroyed. Can someone please verify: place an ammo dump or a command center on the map set a one time trigger for unit dead ammo dump set action to msg all "trigger is evaluated as true" set plan on map and start mission see if the trigger is evaluated as true at the start of the mission. thanks 76th Falcon TFB

Just keeping this one alive - bump it up

Just an update that ED responded and is looking at the mission in respects to it closing after exactly 5 hrs. No estimate when we will see any results since all priorities need to be adressed. FYI thanks MTrenda

the Stuck Key has been there a long time, sometime in Beta i think. to clear it just press OSB 11 (ACK) for Acknowledge. the warning comes up if you hold the osb buttons down too long. as Far as the crash i have not seen this on the forums yet. is this the first time or can you get it to do it every time. personally i change my HOF on 97 every flight and have not had it crash on me for that at all. it has crash before but not for this action. Hope this helps, happy flyin. thanks 76th Falcon

Rik, Just wanted to make sure you got the files you needed. thanks Falcon

Ok will do when I get home. Thanks Falcon

looks like they put out a fix for several crashes yesterday so i download the fixes. I was hoping the update would fix the issue but it did not. I ran the mission again last night and right about 1:34 AM PST five hours after start time (8:30 PM) the server crashed. it does not appear anyone was in the server. bummer.

I am getting the Same error with one of my missions: Seperatists Aggression Day and Day two. It seems to come up about 4:30 hrs to 5:00 hrs into the mission. No one is in the mission the last two times it crashed so it must be an AI unit. This does not happen on other Missions so i would have to say that it is an AI unit causing it. i get the same error. maybe can compare notes on the missions and narrow the budder down. i am thinking ship related. i will have to check day two to see if the ships are in there but it is the only thinkg that i can think of that get kickoff latein the mission. Maybe Greywolf, Speed, or other brilliant mission designers can help us here. I have logs and missions if needed but they are the same you are posting here. thanks 76th Falcon

ED & Team I say keep up the awesome work, and Happy Holidays. I enjoy your hard work and look forward all the new releases. Thanks 76th Falcon

Every step torward your dream is exciting and fun, keep up the vision. we are all along for the ride.

Thanks Wags always nice to hear from ya. looking forward to what you in store for us. Thanks for the hard work to you, the devs, testers and support staff. thanks

I thought this is were they take the month off and come back around the mid Janurary. Not sure but there might not be anyone home. Or maybe that was summer time, either way we can knock on the door and see if anyone answers. Knock knock

After messing around with seperatist aggression day 1 for a week now, trying every setting in the world to no avail. I was finally able to get a squad member to connect to my server. Wait for it......................... I deleted the two KC135's in the mission. Not sure what about them is the issue but right now we are going to do some flying and later i can mess with the tankers to see if both of them are an issue. I bet it is the drunkin boom operator - fire him - he is late to work again. 76th Capt. Falcon

I would say that the official update forum would have what you are looking for: http://forums.eagle.ru/forumdisplay.php?f=105 try this link, also make sure you are on the newest version of the world 1.2.2 as there are alot of changes since the move to world from standalone. Not everything is going to be glaring changes but the changes are excellent ... Mainly the change to world allows for Many more modular 3rd party products to be integrated into the world without core code changes. Example of modules would be BS, a-10c, p51, Combined Arms and now Flaming Cliff 3 along with a dozen other aircraft being built by 3rd parties. If we had stayed with the standalone version 3rd party developing would have been a lot more difficult. This change alone make it worth the work and sweat to get here. Some other changes are numerous changes to the flight model and to instumentation, a big fix to the stability of Multi Player. Server are now on the list for the time they are alive and don't drop off. The list goes on and on but you can catch up on the official update forum, you will have to page through in order to go back in time as the change logs are listed under their deployment version and there is not one comprehensive list since 1.1.1.1 Enjoy the upgrades and the autoupdater, this is a sweet feature that really allows fixes to be deployed alot sooner. we no longer have to wait for each patch to come out is something is really broken ED can publish the update and once a day (by default) when you launch single player the system will chaeck for updates in install them if you want them. Also if you really want something and you can get enough back from the community there is a wish list for all models that you post on. If it's popular then ED might notice or a modder. thanks 76th Capt. Falcon

Fixed w/ 1.2.2 patch Greywolf's Seperatist Aggression Day One mission Crashing in 1.2 Wanted to followup. Installing the latest patch seems to have fixed the missions that where constantly crashing, the missions seem to run until the end. Thanks ED for fixing it, although I wish i had known what the issue was and did not spend two months uninstalling, removing mods, going through every unit, trying to determine if it was some thing in the missions or my configuration. A simple hey your error seem like something we are working on would have be sufficient for me to relax and put my focus on other things. Thanks, Greywolf, Speed and Grimes for responding in the inital thread. Well i am glad it is fixed and glad for all the new things coming now we can try to get the sqaud back up and runnig. hopefully there are still guys who want to fly and have not moved on. Thanks 76th Capt Falcon

yes, i got this same error also when flyin the seperatist aggression mission.

bump it up

Surprised to see no responses from the logs........or anyone try the missions to see if they get the same results. these are all free downloadable missions..... thanks Capt. Falcon

Multiple missions crash during online game play gentlemen, Last night I downloaded a mission from one of the community servers to see if the missions that i had were an issue or my system. i have run the following missions and had crashs at about 45 mins to 60 mins into the mission. seperatist aggression day one seperatist aggression day two Redsnake first day and the one last night ( i think it was border assualt) all these crashed at different stages but ruoghly at close times in length. I have tried several items to resolve the issue: reviewed the units in the mission and triggers open and saved the missions in the new version removed jtac and f15's and ships at different times turned off virus software The only mission that seems to run all the way through is the Pilot Search mission V2. Not sure if this is because of time to complete the mission or reduced number of units. i have also tried to run the missions in single player and even without playing just leaving the game run, it crashes after a long while (60 - 90 mins). I have also tried to remove the saved games area for dcs world and run a repair. last night, to make sure a failure in the install was not an issue i removed the saved games area, uninstalled dcs, removed the dcs world directory under program files, then reinstalled the dcs game, p-51,a-10c, and ca. Ran the updates for the game. Reconfigured the joystick, throttle and rudder peddles and custom key bindings by hand. I left off all modifications to rule out any non standard changes I then started the seperatist aggression mission again and let in run in multi player over night at about 12:30 am. in morning at about 6:30 i check the server and again a crash occurred. the logs are the same for this crash is the same as I have posted previously. the most interesting one is the one from the windows application events referencing mapgeneral.dll. I must conclude at this time that there is something wrong with my paticular system and not the missions as not all people apopear to be having this issue. and some of these missions have been played on other server. i also have not hear from anyone stating they are having issue with any of these missions. my system specs are: msi p86 g65d motherboard i7 3.3 ghz quad duo proc 16 gb ram Patriot nvidia 480 gtx video card windows 7 64 bit Fully poatched. Security essentials for virus protection firewall router wired to system isp with 20 to 30 mb download 1.5 mb upload this server has been running dcs just fine for the last year and half, until the last upgrade. (i can not pin it on the last upgrade because i also upgraded the Video drivers for NVidia) At this point i am not sure were to go as i am not sure what the logs are telling me. Am i turning my wheels because there is something in the code that i can not do anything about, there is a trigger or unit in the mission, keep in mind these are missions from the beta day except borderassault or some updated video driver or windows is causing the issue. it would be helpful if someone who new what the logs meant could let me know, so that i can narrow the research down to one thing or another. it has been kind of fustrating trying to fly with a group of guys knowing the mission is going to crash half way through it. Well, lets hope that something can be found to resolve this stange behavior. Really appreciate those the that have helped so far. thanks capt. Falcon (with a broken wing)

wondering if anyone has had a chance to try the mission out on their system to see if they can play it all the way through or do they get a crash also. thanks falcon

Grimes, Sorry I did not have time to properly thank you for taking a look at this issue but I only had time to respond quickly to your reply. So, officially thanks for looking at this. I did want to post an error that I am seeing in the window event viewer under application, not sure that the DLL is the cultprit or just one that loaded at the time. Hopefully it will help to point in the right direction. Faulting application name: DCS.exe, version: 1.2.1.6288, time stamp: 0x5073db3f Faulting module name: WorldGeneral.dll, version: 1.2.1.6288, time stamp: 0x5070aefa Exception code: 0xc0000409 thanks again to Greywo1f, speed, and grimes for taking time out to look at this and provide suggestions. thanks 76th Capt. Falcon

system crashed with single player not sure when but here are the logs.TARS.log.txt dcs.log.txt

Sure i will do that now.

i got this crash file after wiping out my profile files for dcs running a repair. all the previous times there has not been a crash file so not sure it is related beut here it is: # -------------- 20121015-005217 -------------- # C0000005 ACCESS_VIOLATION at F08F3454 00:00000000 00000000 00000000 0000:00000000 F08F3454 002CEB00 0000:00000000 ??1wMessageDatalink@@UEAA@XZ()+114 F0903BD9 002CEC10 0000:00000000 ?startMessageTransmission@wNetVoiceCommunicator@@QEAAXIW4wMsg@@AEBVLuaTableElement@@N@Z()+289 401AB60D 002CEC50 0000:00000000 401F7EE2 002CED70 0000:00000000 F622A2AD 002CEDB0 0000:00000000 ??1Reader@Mail@@UEAA@XZ()+23D E90894B4 002CEE20 0000:00000000 E9089561 002CEE70 0000:00000000 E908BE38 002CF010 0000:00000000 E9097AB7 002CF070 0000:00000000 E90AC953 002CF0A0 0000:00000000 E90C2C83 002CF0D0 0000:00000000 4028C1A5 002CF130 0000:00000000 402A32B4 002CF160 0000:00000000 402A31A9 002CF1C0 0000:00000000 40328098 002CF230 0000:00000000 403294D8 002CF720 0000:00000000 4032BEBF 002CF7D0 0000:00000000 7688652D 002CF800 0001:0001552D C:\Windows\system32\kernel32.dll BaseThreadInitThunk()+D 76E2C521 002CF850 0001:0002B521 C:\Windows\SYSTEM32\ntdll.dll RtlUserThreadStart()+21

Graywo1fg, No worries, these misions are like programs "they have minds of their own at times" i am sure we will figure it out. Last night I removed the russian ships on a recommendation that triggers on ships may be having an issue. I then turned the Server on last night at about 11:30 PM and checked it at 6:15 am. At 6:15 DCS was not responding when I clicked on the icon in the taskbar. Loking at the log three users join right at 6:00 to 6:15 right as i checked the server. Not sure if the server was running before 6:15 or just hung and the logs got written when I click on the icon. My assumption was that the users joined at 6:00 and when I went to bring up dcs it locked up. Not a good test so I restarted the mission this morning to run it while I am at work and see how things go. Will let you know. Thanks for taking the time to look at it.