robgraham

I can look at setting up a restart timer in there. and what was the self induced crash (incase some one else is doing it) i'm presuming the save path? I'm also looking at adding a SRS instance for each server..

So like most people I was using Restart on Crash to handle any issues with DCS crashing etc but with the New DCS server options that became a little hard to do.. because of that I decided given ED haven't given us a way to really control/monitor servers from the actual server I'd make my own controller app for it. Now a few cavets, this is really basic, it only handles 3 instances at the moment (all I run on my server box) and it doesn't monitor anything other then the DCS instance (no SRS etc monitoring). It does however let you select the 3 main options, set the write folder, a time out for if it hard locks to restart the instance, and a auto restart option for if you want to have the server automatically restart on a crash. you can grab it from https://www.taskgroupwarrior.info/download/dcs-servercontrol.zip I've included the SOURCE code in the zip, you don't need it to run the file but i wanted to be transparent and well if any one wants to extend it they can I did this really really quick and dirty and it's only got the basics of exception capturing etc on it. To use simply extract the .exe and .exe.config to were-ever you want and run the servermonitor.exe if your DCS is running as ADMIN you'll need to run the servermonitor.exe as admin if you want it to be able to autorestart else UAC will go 'hey you want to open this' This is provided as is, if you use it it's at your own risk etc. And Eagle... you REALLY need to make us something like this that's NATIVE to the server please!!!...

everything is effected by this muamshai, moose, mist, even some of the ME stuff

So your biggest aim when taking a hit from any form of missile is to make it have to waste energy and/or loose lock/track, as others have mentioned the loss of lock/track is done with Chaff for Radar guided and Flare for Heat, however with out doing anything but dropping these your chances of survival are .. well low. Now before i continue here I'm going to cavet what i'm saying with 'This is if your DEFENSIVE' if you want to remain OFFENSIVE then you need to start looking at F-POLE and other means. - Radar Threat - Your primary aim against a radar threat is to confuse the seeker into locking onto something else (The Chaff ideally) or to loose you completely, failing this you want to: 1. Make it run out of energy, 2. make it drive into the ground. To achieve this the normal means is to first put the radar itself on the beam, turn so your 3 or 9 is at the threat, this starts a notch, which as other great videos will explain will depending on the type of radar used reduce your doppler shift which in turn tends to have the radar think your part of the ground clutter. Once you have started the notch typically drop 1 - 4 bundles of chaff, at the same time you want to ELBOW on the vertical plane, this is exactly what it sounds like imagin your plane is at your shoulder and you want to get to your hand, roll and pull down at 90 degree's, loose a bit of altitude then pull back level again dropping chaff when you do. the goal in this is to confuse the seeker head and also to force the missile to use energy to follow you if it has to. If the missile has not been able to be defeated before it goes active and has enough energy to meet you.. 1. keep notching and elbowing unless you don't have enough altitude in which case try and mask yourself if you can. 2. In the last few seconds remember you HAVE the paddle switch, it's better to bend the bird by over-g then it is to die, a rapid move in the vertical (and preferably the horizontal plane) at the last few moments can cause enough of an angular change in vector that the missile can not turn to compensate given its running by this stage on pure ballastic energy (hopefully). -- Heat -- Against a heat seeker you have the issue that your biggest source of heat is also your means of thrust and 9/10 your going to be in burners or something when they are launched at you.. Presuming you see the missile launch and know it's coming first.. unless it's an AIM-9X ou should have been trying to keep him out of your 6 ;) but you want to dump flares (Sequence is up to you .. i tend to do 2 then 2 about 1/2 a second apart or so) while both trying to create as much angular Aspect change as possible and if i'm in burners cutting them instantly.. The missiles aren't likely to change their target if I'm showing them 2 F404's in Afterburner vs 2 flares.. --Electro Optical--- Russian SAMS and Jets especially can carry Electro-Optical weapons.. or basically visual guided the issue here is you can't tell if they are or not so basically you have to treat them like IR, and just try and defeat them using aspect and energy.

This is weird because i'm running --server --norender on 2 servers with LOTATC with out any issues one of which has been running for 16 hours Which lotatc you running? latest Stable or the Beta RC?

The last Open Beta has really messed up something in the scripting backend, stuff that was running perfectly fine for months is now full of this: [string "-- world events hook..."]:427: in function <[string "-- world events hook..."]:313>. 2019-03-02 14:34:45.507 ERROR DCS: Mission script error: : [string "C:\Users\root\AppData\Local\Temp\DCS.openbeta\/~mis000051C2.lua"]:978: Parameter #self missed 2019-03-02 14:34:45.507 ERROR Lua::Config: Call error world.onEvent:[string "-- world events hook..."]:427: Parameter #self missed stack traceback: [C]: ? [C]: in function 'getCategory' local function groupSpawned(event) -- dont need to add units spawned in at the start of the mission if mist is loaded in init line if event.id == world.event.S_EVENT_BIRTH and timer.getTime0() < timer.getAbsTime() then dbLog:info('unitSpawnEvent') --table.insert(tempSpawnedUnits,(event.initiator)) ------- -- New functionality below. ------- if Object.getCategory(event.initiator) == 1 and not Unit.getPlayerName(event.initiator) then -- simple player check, will need to later check to see if unit was spawned with a player in a flight the last line in this is what is erroring constantly (part of MIST) however that is a standard event call and as said this was working 100% prior to the latest open beta patch, I know that the patch notes mentioned fixing some scripting issues but in that case maybe they should have included exactly what was fixed and how it's had an affect on the scripting incase this is a case of new functions parameters being required or the like? Quick edit before I get the normal 'Well its a mist issue' no this isn't a MIST issue, this is happening on EVERY item that uses those initator calls.. even stock API items. It means that anything which relies on the events firing is not working full stop and is a major break.

the way i've been looking at doing the rotary with pull rather then push was to have it consider 'pushed' to be off so in the Ardunio if pin x is high then button = false if it's low then button = true that way you can use an existing push button with a spring action (like the real thing). Is that kinda what you did Blue?

I'm one of those who find reading aircraft manuals fun, though depending on how i'm feeling I have noticed some of them do have chapters that you get like 2 paragraphs into and then fall asleep on.. but that could also be a combination of pain meds and the writing never quite worked it out. But the main reason is I've been in Heat Blur's position I know how much effort goes into it and reading the manual and seeing how well it's been done with that knowledge makes it even more appreciative. Based on what I've read and seen on vids etc, they have done another beautiful job and she's going to be a thrill to learn properly and to try and master, I don't envy you guys who had to do it for a living, though again having made basically a P.T.T. I know how much study goes into learning everything so that it's rote muscle memory for a lot of it. On being able to read anywhere.. as I said, saddly there is always the chance I'm gonna have a trip to a hospital at any point, and manuals make a nice distraction ;) problem is they some times get really upset when you leave mobile phones on (especially if they have an ECG attached to you hehe). Too the guys who've done the PDF's thanks :D And to the person/s who wrote this manual.. awesome work well thought out and placed like some others my only suggestion would be to maybe make some linking of systems etc to make jumping between references easier etc.

actually the basket does cause some minor push back, the resistance in the jetstream plus the actual spool effects means that you have a minor amount of push, it's not like hitting a wall or anything like that but it is there in the real world not to mention some other effects that aren't modelled currently in DCS like the fact the drogue has a minor amount of 'leading' as well no where near as much as the boom but it's there.. it's still attached to the tanker and while it's flexable it becomes a lot more ridgid when it's pumping fuel under pressure. Wags and others in the ED team have already mentioned that there aware of the limits in the current system and we'll see it updated 'eventually'. Hopefully that means things like nose bubble, slip stream effects (which given we are getting some of those finally for all ac is nice), couple physics, and maybe even some physics for the drogue hitting our plane and moving around rather then going through it? What would also be nice is if the tanker talked to the pilot like he would in real life and warned about up coming turns ;)

I'll second the could we please have a pdf version as well.. Like Alicatt some times don't have internet access but do have tablet access (like oh during long car trips, certain part of hospital stays when they won't let you have your net turned on because of 'interference' etc). Living doc's are great but pdf's are awesome too ;). Otherwise the lay out and everything looks great.

Under certain shadow conditions / sun angels etc the shadows on clouds and other items in the RIGHT eye flicker and shimmer really bad, because it's the right eye there is no way to easily capture the effect on video either. The left eye is fine however.

It would be really nice if in VR we could have a small area at the BASE of our NVG's were we could 'peak' down at my displays etc with out having to rapidly flick the goggles up and down each time.. SME's I know state that is how they work with them in real life, they may be focus'd to infinity but they can still glance down and get a view of instruments etc if they need to. In non VR you can do this fine as you have the NVG effect in the middle of the screen only however in VR it's impossible as you have the NVG effect across both eyes.

No but adjusting some scaling, increasing the resolution of the base textures, adjusting the way the ddi's antialias, etc can all have a big impact on the resolution as well, increasing the base line performance allows a higher pixel density to be used giving us better super sampling which again can improve visual quality. So no ED don't need to make us headsets, but optimisation and better draw call use will help everyone, not only Vr users but also monitor based ones.

Yeah the air to air waypoint is def using tur, not magnetic which is wrong and bloody annoying if you have a Gci, as your bra and picture calls are messed up if they are doing them correct

part of that is meant to be programmable in a DC and loaded via MUMI to allow for Pilot Preferences so It wouldn't surprise me if we don't get them until we get MUMI and the DC stuff

This mod is AWESOME. Thank you, It's become my best friend in the HAWG and the like when I need to get co-ords down. 1 big big request.. PAGES!

This happened last night at some point on the server machine: 2019-01-22 04:18:10.619 INFO SCRIPTING: E: BASE00000(RADIO REPAIR CHECKER RADIO COUNT IS CURRENTLY: 0) 2019-01-22 04:18:10.619 INFO SCRIPTING: E: BASE00000(RADIO 1 IS ALIVE Radio count is: 1) 2019-01-22 04:18:10.619 INFO SCRIPTING: E: BASE00000(RADIO 2 IS ALIVE Radio count is: 2) 2019-01-22 04:18:10.619 INFO SCRIPTING: E: BASE00000(RADIO 3 IS ALIVE Radio count is: 3) 2019-01-22 04:18:10.619 INFO SCRIPTING: E: BASE00000(Total Radio count is: 3MAX SPAWN MULTIPLIER WILL BE: 4) 2019-01-22 04:18:24.826 INFO SCRIPTING: E: RESCUEHELO03506(RESCUEHELO Stennis_R Helo_01 |Rescue Helo Stennis_R Helo_01#001: state=Running fuel=13.9) 2019-01-22 04:18:30.596 INFO SCRIPTING: E: BASE00000(Routing Stennis to NAV3 at a speed of :25) 2019-01-22 04:18:39.852 INFO EDCORE: try to write dump information 2019-01-22 04:18:39.881 INFO EDCORE: # -------------- 20190122-041841 -------------- 2019-01-22 04:18:39.889 INFO EDCORE: D:\DCS World OpenBeta\bin\Transport.dll 2019-01-22 04:18:39.897 INFO EDCORE: # C0000005 ACCESS_VIOLATION at 0DE31367 00:00000000 2019-01-22 04:18:39.906 INFO EDCORE: SymInit: Symbol-SearchPath: '.;D:\DCS World OpenBeta;D:\DCS World OpenBeta\bin;C:\Windows;C:\Windows\system32;SRV*C:\websymbols*http://msdl.microsoft.com/download/symbols;', symOptions: 530, UserName: 'root' 2019-01-22 04:18:39.914 INFO EDCORE: OS-Version: 10.0.14393 () 0x10-0x3 2019-01-22 04:18:40.297 INFO EDCORE: 0x00007FFB0DE31367 (Transport): Vehicle_Descriptor::getEquipmentArgValue + 0x5647 2019-01-22 04:18:40.305 INFO EDCORE: 0x00007FFB0DE311BD (Transport): Vehicle_Descriptor::getEquipmentArgValue + 0x549D 2019-01-22 04:18:40.307 INFO EDCORE: 0x00007FFB0DDCBE0B (Transport): AI::groundAndNavalAiInit + 0x80FB 2019-01-22 04:18:40.307 INFO EDCORE: 0x00007FFB0DDD8889 (Transport): wcColumn::update + 0x29 2019-01-22 04:18:40.308 INFO EDCORE: 0x00007FFB0DDDD961 (Transport): wcColumn::setOption + 0xD01 2019-01-22 04:18:40.308 INFO EDCORE: 0x00007FFB19FC2720 (World): (function-name not available) + 0x0 2019-01-22 04:18:40.309 INFO EDCORE: 0x00007FFB19FC2C55 (World): (function-name not available) + 0x0 2019-01-22 04:18:40.310 INFO EDCORE: 0x00007FF7F17E26A6 (DCS): (function-name not available) + 0x0 2019-01-22 04:18:40.310 INFO EDCORE: 0x00007FF7F17F0C4E (DCS): (function-name not available) + 0x0 2019-01-22 04:18:40.311 INFO EDCORE: 0x00007FF7F17C91B0 (DCS): (function-name not available) + 0x0 2019-01-22 04:18:40.312 INFO EDCORE: 0x00007FF7F1443DD5 (DCS): (function-name not available) + 0x0 2019-01-22 04:18:40.312 INFO EDCORE: 0x00007FF7F1445C30 (DCS): (function-name not available) + 0x0 2019-01-22 04:18:40.313 INFO EDCORE: 0x00007FF7F197E05F (DCS): (function-name not available) + 0x0 2019-01-22 04:18:40.313 INFO EDCORE: 0x00007FFB32F78364 (KERNEL32): BaseThreadInitThunk + 0x14 2019-01-22 04:18:40.314 INFO EDCORE: 0x00007FFB33CCE851 (ntdll): RtlUserThreadStart + 0x21 2019-01-22 04:18:40.458 INFO EDCORE: Minidump created. 2019-01-22 04:18:40.460 INFO DCS: try to write track file 2019-01-22 04:18:40.462 INFO DCS: 'C:\Users\root\Saved Games\DCS.openbeta\Logs\dcs.20190122-041841.crash' deleted successfully 2019-01-22 04:18:40.564 INFO DCS: 'C:\Users\root\Saved Games\DCS.openbeta\Logs\dcs.20190122-041841.dmp' deleted successfully 2019-01-22 04:18:40.564 WARNING DCS: track file empty 2019-01-22 04:18:40.564 WARNING DCS: packing mission istead 2019-01-22 04:18:40.564 WARNING DCS: file 'C:\Users\root\Saved Games\DCS.openbeta\Missions\RED-IBERIA-WAR-version1-104a.miz' skipped due to large size, 12.694562 MB 2019-01-22 04:18:40.564 INFO DCS: dxdiag.exe /64bit /whql:off /t "C:\Users\root\Saved Games\DCS.openbeta\Logs\dxdiag.txt" 2019-01-22 04:18:50.743 INFO DCS: failed to open 'C:\Users\root\Saved Games\DCS.openbeta\Logs\dxdiag.txt' for reading 2019-01-22 04:18:50.743 INFO DCS: trying dxdiag.exe /64bit /whql:off /t C:\Users\root\AppData\Local\Temp\dxdiag.txt 2019-01-22 04:19:00.077 INFO DCS: 'C:\Users\root\AppData\Local\Temp\dxdiag.txt' deleted successfully === Log closed. If i'm reading that right something messed up with the naval and ground ai which is weird as it's been possibly the one thing since 2.5.4 that's been rock solid for me all that the naval group does is move between 3 zones (seems there is no go to waypoint for naval ships).

The hornet has it's own version of the HTS Slider it's called the TAS and is contained wholly in the pylon that carries the HARM itself, it can supply the same information as the 16's HTS with the same general limits with a whole 10kg increase to the pylon weight. (edit correct arconyms) On the HARM chasing the wrong Radar.. I've seen it do it when the station I shot at went silent.. the harm was like oh there is another radar over here I'll go chase... which given we only have SP mode and that is Bearing and hope the missile wants to chase the right source.. is understandable... plus the real birds will switch and swap if a radiating source goes 'dead'.

Nine, I've got an unhandled Exception 'the remote name could not be resolved: skate-zilla-graphics.000webhostsapp.com' then has the jit log looks like exactly what it says there's not any exception handling for if the app can't do a version check at yourwebsite for what ever reason.. st-in-time (JIT) debugging instead of this dialog box. ************** Exception Text ************** System.Net.WebException: The remote name could not be resolved: 'skate-zilla-graphics.000webhostapp.com' at System.Net.HttpWebRequest.GetResponse() at DCSUpdaterUtility.Form_Main.CHECKDCSVERSIONS() at DCSUpdaterUtility.Form_Main.Button_DCS_SERVER_VER_Click_1(Object sender, EventArgs e) at System.Windows.Forms.Control.OnClick(EventArgs e) at System.Windows.Forms.Button.OnClick(EventArgs e) at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent) at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks) at System.Windows.Forms.Control.WndProc(Message& m) at System.Windows.Forms.ButtonBase.WndProc(Message& m) at System.Windows.Forms.Button.WndProc(Message& m) at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m) at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m) at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam) I'd suggest on the function just adding a catch for it and a message with 'can't find server' instead ;)

So my server missions solution was 2 fold. 1. Any time a zone were a SAM should be is 'flipped' it simulates the fact that side now brings in fresh equipment (and soon that'll have a production sim behind it) 2. Any existing SAM site gets checked every 2 hrs, and if it's 'dead' gets repaired 2 hrs after that, ALL sam's get repaired every 6. 3. My SAM's will turn their radars off if they need to :P . It's not 100% accurate no but it gives people 'time' to punch a hole and exploit it if they are willing to put that effort in. Just like there are ways to counter 120's in mission there are ways to counter HARMS etc in the shape and form of things that are rewarding to players rather then 'No you can't use this shinny new toy'.

Just one question nine, we automatically upload bug reports every crash now, or at least my server does and my actual machine, which if looked at should show that with the current open beta builds there are a lot more crashes happening. Is there a way to reference those when we post here?

I wouldn't mind hearing and seeing more female voices and pilots, part of my group would like to be able to have their pilots sound more like they do, and honestly the excuses used constantly by people against are a bit of a joke. We have US, British, Russian and many others all whom have had active combat pilots either since ww2 (Russia) or at least the late 80's and 90's ... of course while we are at it... change some of the voices so we are not talking to wags all the time hehe.

mark it's not an issue with MOOSE it's an issue with DCS, the SPAWN commands haven't changed in months but there what is causing the crash... something as simple as putting a C-17 in have it late activate and running C17TEST = SPAWN:New("Test Group"):InitLimit(1,999):InitRepeatOnLanding():SpawnScheduled(5,0.75) will have DCS crash when the units deleted on landing So by the looks of it while ED may have fixed one bug they introduced another. (This was functioning fine last build) and nothing has changed in moose. So @Grimes On Engine shut down is working, on landing is crashing now. Just so your aware..

Thanks Rik.

I'm still getting crashes happening.. Oh some further info if it helps Grimes or the like.. those are all using the repeat on landing (not engine shut down) and it's happening with Heli's and Planes alike 2019-01-18 11:36:10.719 INFO Scripting: event:type=land,target=Gelendzhik,initiator=RECON 1#001-01,place=Gelendzhik,t=43014.861,placeDisplayName=Gelendzhik,initiatorMissionID=1000289, 2019-01-18 11:36:10.719 INFO EDCORE: try to write dump information 2019-01-18 11:36:10.730 INFO EDCORE: # -------------- 20190118-113611 -------------- 2019-01-18 11:36:10.742 INFO EDCORE: D:\DCS World OpenBeta\bin\WorldGeneral.dll 2019-01-18 11:36:10.750 INFO EDCORE: # C0000005 ACCESS_VIOLATION at 1B4245F4 00:00000000 2019-01-18 11:36:10.784 INFO EDCORE: SymInit: Symbol-SearchPath: '.;D:\DCS World OpenBeta;D:\DCS World OpenBeta\bin;C:\Windows;C:\Windows\system32;SRV*C:\websymbols*http://msdl.microsoft.com/download/symbols;', symOptions: 530, UserName: 'root' 2019-01-18 11:36:10.792 INFO EDCORE: OS-Version: 10.0.14393 () 0x10-0x3 2019-01-18 11:36:12.513 INFO EDCORE: 0x00007FFB1B4245F4 (WorldGeneral): Sound::Source::play_once + 0x4 2019-01-18 11:36:12.525 INFO EDCORE: 0x00007FF6085E0CB0 (DCS): (function-name not available) + 0x0 2019-01-18 11:36:12.534 INFO EDCORE: 0x00007FF6085F2DFA (DCS): (function-name not available) + 0x0 2019-01-18 11:36:12.536 INFO EDCORE: 0x00007FF6085AB30F (DCS): (function-name not available) + 0x0 2019-01-18 11:36:12.537 INFO EDCORE: 0x00007FFB290A2720 (World): (function-name not available) + 0x0 2019-01-18 11:36:12.538 INFO EDCORE: 0x00007FFB290A2C55 (World): (function-name not available) + 0x0 2019-01-18 11:36:12.539 INFO EDCORE: 0x00007FF6088626A6 (DCS): (function-name not available) + 0x0 2019-01-18 11:36:12.540 INFO EDCORE: 0x00007FF608870C4E (DCS): (function-name not available) + 0x0 2019-01-18 11:36:12.541 INFO EDCORE: 0x00007FF6088491B0 (DCS): (function-name not available) + 0x0 2019-01-18 11:36:12.542 INFO EDCORE: 0x00007FF6084C3DD5 (DCS): (function-name not available) + 0x0 2019-01-18 11:36:12.544 INFO EDCORE: 0x00007FF6084C5C30 (DCS): (function-name not available) + 0x0 2019-01-18 11:36:12.545 INFO EDCORE: 0x00007FF6089FDFEF (DCS): (function-name not available) + 0x0 2019-01-18 11:36:12.546 INFO EDCORE: 0x00007FFB32F78364 (KERNEL32): BaseThreadInitThunk + 0x14 2019-01-18 11:36:12.547 INFO EDCORE: 0x00007FFB33CCE851 (ntdll): RtlUserThreadStart + 0x21