MTrenda

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.

Tried the Aggression mission Day one and the results........... I tried the mission in multiplayer and it ran for 15 mins and then crashed. this time is consistant (15mins). this is the same behavior i got in the Version of your mission that i had been running since you came out with this ( prior to your campaign release. When 1.2.1 came out and the crash started I downloaded your campaign version of Seperatist Aggression and added the Tasking sequence to the mission. this caused two things one i renamed several unit's and groups to make them easier to list in SLMOD and two i opened several units in doing this. This may have changed the units in someway, not sure. Here are the logs for the Mission you gave me and the mission that i modified to add the Tasking Sequence of Speed SLMOD. i have delayed the start of the F-15 and the Jtac to 20 day in seperate tests just to rule out these as an issue, this did not seem to have an effect. This was changed back, i did change the f-15 to an escort for texaco because they were going straight for russia and getting charbroiled by sams( this has not change the behavior as far as i can tell. Hope this information helps............... thanks 76th Capt. Falcon dcs.log.txt net-server.log.txt Separatists Aggression 1 Breakout Day 3a.miz

These are the log files of the second mission we flew looks like another two and half hours into the mission, a crash occurred. we had i think about seven guys in at this time. no one i could tell was joining at the time. thanks 76th Capt. Falcon net-server.log.txt TARS.log.txt dcs.log.txt

Here are some Logs from last night These are the logs from the first mission we flew it appears we were up for 2 hours and we had seven people in, two more were joining at the time of the crash. thanks 76th Capt. Falcon net-server.log.txt dcs.log.txt

Graywo1fg, i will put this up today and see how thing s go and let you know. thanks 76th Capt. Falcon

Speed, thanks for getting back to me, yes i am runnig the SLMOD 043 with the ADMIN funtions but i am not switching missions within server. I am shutting down Multiplayer and starting backup from a fresh start. I will take a closer look at it this weekend when i have time and see if i can't get some logs put togehter. this mission does have alot aof units but they are not spawned until the mission is called which really helps on the resources required to run it. also the connect people at the time is under six so not really looking in that direction. so more info to come.. Speed - thanks for the SLMOD it really allows the multiplayer client interact with game at their own pace. Great work.... Thanks 76th Capt. Falcon

I am at work so i do not have any log files or tracks, but i was wondering if anyone has tried running Greywolf's seperatist aggression day one mission and does it crash sometime during the play. I ran it for about an hour last night and then left it running over night and when i got up Dcs had crashed. This has happened several times so something is a miss. I am wondering if anyine else has tried running this mission and do they experence the crash or is it something to do with my installs. The older version that he had, before he mad it a campaign crashes exactly fifteen minutes into the mission, consistantly. the current one that i have been using now does not crash until later in the mission. Still trying to pin it down and will review logs this weekend, when i have some more time. If anyone is running these mission on there server and not have an issue or if there is a known issue that i have not seen yet please let me know. Greywolf - by the way awesome mission, as you now. 76th Capt. Falcon

is in the weapons section at the button right. click on unit right pane second icon over (weapons) last pull down menu on the right pane

Speed, Nice little tool set. This will be perfect for our sqaudron. Ran through a few tests and it appear to work great. the 76th will test it further when we all get on line. Awesome work man, nice job. thanks [76th]Capt. Falcon

nAyo, Not sure if this is still an issue or not but in the previous release sometime i have to movethe aircraft forward just a little (1/2 meter or so) and all of a sudden the cround crew would start responding to all the calls. this wasn't all the time but only some time when they would not answer even though i had the INTCOM on and even when the canopy was open. Maybe give it a try next time the crew does not answer, move the aircraft slightly forward and listen for the crew to respond. thanks 76th Falcon

Speed, thank you for all the ward work this weekend, i have really been missing this in the mission. awesome adds to the mod i will let you know if any issues arise. thanks [76th] Falcon

Rossi, looking forward to seeing you on team speak. Falcon

The 76th Squadron is looking for pilots to fill the following positions: Mission Builders Trainers (P-51, A-10 and Ka-50) documentation Skin creator Regular pilots weekend pilots Anyone interested in the DCS series that wants to fly for fun to the one who wants to create missions should check us out. We typically fly PST 18:00 to 24:00 for US Flyers PST 24:00 to 07:00 for the German Flyers The Server is usually called 76th Open Recruitement Teamspeak server is 206.217.140.50 Website is: http://tf-blackjack.com/content.php We started as an Arma group so you will see alot of info on that but we would like to build the DCS side. you can contact any of the 76th members for further info or just jump on the teamspeak for a quick chat with a member. thanks, see ya in the air [76th] Capt Falcon

Speed, Thanks for getting back to me. sorry i did not mention i was using your SLMODV6 with world i have been using your mod for so long I just assume the verisons and install, my bad. Even though i miss the functionality as much as the first, crisp, clear wave with the morning sun. Don't kill yourself getting it released, i know how code can be a little tricky and produce unexpected results. Really enjoy all your work it has really improved the Multi player experience and ability to run a server unmonitored. Pilots can come in any time and get the current list of targets regardless of how long the mission has been going. you also have provided some exceptonal triggers that will be invaluable to combined arms. Just wanted to say thanks for all the hard work, and taking the callenge from the ground up, awesome work. looking forward to your next version. Thanks [76th] Falcon

here are the crash file and DCS log no track file created thanks 76th Falcon

Speed, So, i am getting the nil value error also. I have to assume we are waiting for your next release or havei installed something incorrectly? thanks

negative, i got the same thing. the server maybe having an issue.

Not sure if this has been addressed so here it is: issue: When pushing the '\' for comms menu you must hold it down in order to select the submenus. to fix this edit the following files: Make a backup copy before editing. Edit using Notepoad ++ <UserProfile>\Saved Games\DCS\Config\Input\P-51D\Keyboard.lau edit line 32 From: {combos = {{key = '\\'}}, down = iCommandToggleCommandMenu, up = iCommandToggleCommandMenu, name = 'COMM Communication menu', category = 'Communications'}, to: {combos = {{key = "\\"}, }, down = iCommandToggleCommandMenu, name = "COMM Communication menu", category = "Communications"}, Remove the RED TEXT <Program files>\Eagle Dynamics\dcs world\mods\aircrafts\p-51D\Inputs\P-51D\Keyboard\default.lau edit line 55 From: {combos = {{key = '\\'}}, down = iCommandToggleCommandMenu, up = iCommandToggleCommandMenu, name = 'COMM Communication menu', category = 'Communications'}, to: {combos = {{key = "\\"}, }, down = iCommandToggleCommandMenu, name = "COMM Communication menu", category = "Communications"}, Remove the RED TEXT The default is required incase you ever delete the one in your profile. This change sets the function of the key from a Pressed state = action and Up state = action, to a Pressed state= action and Up state = no action. Now when you hit the comm key in the P-51 the menu will stay up and you can choose all the submenus without holding the comm '\' key. Thanks 76th Falcon

Thanks for testing this out and confirmng the functionality. 76th Falcon

Not sure if this has been posted yet but. under the ground crew the option number four for A-10c in world is Stow the boarding ladder. this should really be option number 5 so to fix this you need to modify the following file: <drive>:\Program Files\Eagle Dynamics\DCS World\Scripts\UI\RadioCommandDialogPanel\Config\A10c.lua file. <drive> = the drive you installed your DCS to, typically C or D. 1. make a copy of the file in case you need to revert back 2. edit the file using Notepad ++ 3. goto the last line in the file (line 331) 4. change the following line: menus['Ground Crew'].items[4] = {name = _('Stow boarding ladder'), command = specialEvent({type = 7})} 5. To this: menus['Ground Crew'].items[5] = {name = _('Stow boarding ladder'), command = specialEvent({type = 7})} this changes the stow boarding ladder menu item to F5 instead of F4. F4 will now be Request repairs and now allows you to make the call for repairs as normal. need to have the engines shut down still. i tested this on a mission i had and it worked, not sure if someone has already posted this but i did not see it. Thanks 76th Falcon

Panzatard, Thanks for replying. I have some logs of the flight we had tonight. we were flying the seperatist agression mission again tonight for about and hour and half before one client crashed and then the server crashed. it appear to the weapons dll this time. Here are some logs of two of the clients and the server logs. as far as mods the only one that i am running right now is speeds SLMod ver6, Ahe mission was created in 1.1.1.1 and I just moved it to the world. the mission could be the issue but not sure. i will try some other missions and see what happens. maybe some without slmod. thanks 76th Falcon crash logs.rar

My understanding is that this is not supported. there were some changes to the key mappings and and calls that made importing not functional. A side by side comparision and manually reset the settings is the best suggestion i heard so far. thanks 76th Falcon

Hi, I am looking to see if anyone else is having this issue. I was hosting a mission (Serpratist Aggression day one) and we were in it for about an hour, suddenly several of the client ctd but the server stayed up and running. The client tried to reconnnect and they recieved an unable to connect to server error. while they were trying to connect other users were able to connect (these clients had not been in the server during this session before). If i restart the mission then all clients can connect, until they crash. I now we want tracks and log files but I am looking to see if this is something just in the Beta and will be addresses or no one is having the issue and further information is required. It appears that the clients are ctd with the Effects.dll issue but the real issue is that the clients can't connect after crashing. it seems as if they are still in the server somehow so they can't connect anymore, but new users are able to. The clients are not listed in the plane assigned screen and there are no F2 views of the clients clying anywhere. So dev's and testers - is this already a known issue and just pat of the beta or should I log an issue to be looked at other users - have you experiences this behavior on your servers. Thanks 76th Falcon

Thanks to WAGS and his team for a job well done Wags, I have to say thank you for all the hard work that has gone into the DCS series. Every night I am flying the A-10c and just reciently the P51D, so much the wife ready to pull the curcuit breaker. i have enjoyed the falcon series from the beginning and the janes series was a blast but the time and effort you have put into the dcs has really taken the simulation to a new level. I didn't think I would enjoy flying the slow, clumsy hog until i jumped into one and ran through the training videos. When I launched my first maverick and took out my first tank, i was hooked and new I would be at my computers for way to many hours. I then starting looking at the mission editor and modifying other peoples missions. I am amazed at the flexibility that the mission editor allows. It allows so much more then the sims that proceeded it. Now you have centralized the map and modulized the aircraft the gates are open for incredible things for the future. The changes that you have made and the road map you have laid out makes me check your forum daily for 'what's next?' Will one of the cumminity modders come out with a killer addon, will a mission builder put out another outstanding mission of his own creation. I thank you for allowing you system to be flexible enough for us to participate in the creation of your products. I also thank you for having a vision and ear for this community, keep up the good work. Thanks to all the developers, testers, and staff and community for making an excellent, detailed simulators. Your sim gave me the oppurnity to meet some really good friends online and in person that i would not have had a chance to meet. Keep up the great work... Thanks [76th] Falcon

the ip address is: 67.49.89.232 sorry it only stays in the list for an hour before it vanishes. not sure the issue, so you will have to join by ip. it will then be in your history and you can attach from there. thanks Capt. Falcon