repsol Posted January 12, 2013 Share Posted January 12, 2013 (edited) Hello... I'm working on a mission in the editor and i have come across a big problem... For some strange reason the AI A10 choose to 'turn its attention' to a non existent target hundreds of miles away instead of attacking its asigned target (perform task-attack unit) This does not happen every time...Sometimes the AI A10 do actually attack the asigned target and everything works as intended...but the next time i test the mission the AI choose to focus on this 'non exsistant' target that is not even on the map (making it its SPI...se pictures). This is ruining the AI plans and the mission will not work :(AI targetingproblem SHORT.mizAI targetingproblem (bug report version).miz Edited January 29, 2013 by repsol Link to comment Share on other sites More sharing options...
Jona33 Posted January 12, 2013 Share Posted January 12, 2013 Delete the gray CAS task in the Waypoint options menu. Might help. Always remember. I don't have a clue what I'm doing Link to comment Share on other sites More sharing options...
repsol Posted January 12, 2013 Author Share Posted January 12, 2013 Hello Jona33 I have done that...does not help I will look at it again just to make sure those CAS tasks are gone.. Link to comment Share on other sites More sharing options...
repsol Posted January 12, 2013 Author Share Posted January 12, 2013 Hello again...No it was the CAS task in the ADVANCED WAYPOINT that i had removed... Should i put this option to...NOTHING or perhaps GROUND ATTACK ? Link to comment Share on other sites More sharing options...
repsol Posted January 12, 2013 Author Share Posted January 12, 2013 Delete the gray CAS task in the Waypoint options menu. Might help. I gave this a try... - With the NOTHING task the AI A10 did not attack at all - With GROUND ATTACK the problem remained the same as with the grayed out CAS task (the AI seeing som non-existent target, offmap) Link to comment Share on other sites More sharing options...
Speed Posted January 24, 2013 Share Posted January 24, 2013 (edited) To make others understand your potential bug and your potential problem, you must allow others to replicate it. Thus, for most problems, you must provide a short and simple example mission or track (try to get it as short and simple as possible), and provide steps on how to replicate the bug. Otherwise, don't expect much help. Testers and veteran forum members are far too busy to go chasing around bugs by attempting to replicate them based on vague forum descriptions. And yes, your description was vague, simply because you did not include any kind of track or mission. I don't know anything about the AI's waypoints, tasks, enemy units, triggers, etc. On the other hand, sure, here on the forums, (assuming you do a forum search for the bug first) it's OK to make a quick question basically asking, "hey I just noticed this, is this a known bug?", and if the answer is "no, it's not known", only THEN to take the time to properly report it with a mission/track/whatever. Edited January 24, 2013 by Speed Intelligent discourse can only begin with the honest admission of your own fallibility. Member of the Virtual Tactical Air Group: http://vtacticalairgroup.com/ Lua scripts and mods: MIssion Scripting Tools (Mist): http://forums.eagle.ru/showthread.php?t=98616 Slmod version 7.0 for DCS: World: http://forums.eagle.ru/showthread.php?t=80979 Now includes remote server administration tools for kicking, banning, loading missions, etc. Link to comment Share on other sites More sharing options...
repsol Posted January 25, 2013 Author Share Posted January 25, 2013 Hello, Speed On the other hand, sure, here on the forums, (assuming you do a forum search for the bug first) it's OK to make a quick question basically asking, "hey I just noticed this, is this a known bug?", and if the answer is "no, it's not known", only THEN to take the time to properly report it with a mission/track/whatever. This was my intention with this thread, 'bug report'. Maybe i expressed myself a bit negatively but i was quite frustrated when making this thread after spending many hours trying to fix the problem and thinking i had done so after several succesful testruns only to find the problem returning once again... That's part of the problem...The mission will work fine for a number of tests and then for no reason that i can understand the 'bug' appears and ruins the mission AI-planing. I did do a forum search...Using the keywords 'AI TARGETING' and simply 'TARGETING' but found no thread with a simular problem...I guess i could have done more searching but i don't really know what other keyword to use... The reason i only posted a few screenshots is that the problem does not occurs at the start of the mission but will require the 'tester' to fly the mission for 30+ minutes before the problem shows itself...I thought thoose screenshots might be enough to explane my problem... I will try to upload a mission were i have 'skipped ahead' to a few minutes before the 'bug' happens...and also the full mission... Regards/ Repsol... Link to comment Share on other sites More sharing options...
repsol Posted January 25, 2013 Author Share Posted January 25, 2013 (edited) Hello... I have attached a 'scaled down' version of the mission... In this short version the problem will occur within a few minutes and will not require the player to do anything other then to take up an orbit pattern and watch the TAD screen. A full description of my problem may be wiewed in the mission briefing... I also tried to upload the full mission but the file is to big to upload here (5.16 MB). Any help will be apprisiated...Thanks Edited January 29, 2013 by repsol Link to comment Share on other sites More sharing options...
Speed Posted January 29, 2013 Share Posted January 29, 2013 (edited) Hello... I have attached a 'scaled down' version of the mission... In this short version the problem will occur within a few minutes and will not require the player to do anything other then to take up an orbit pattern and watch the TAD screen. A full description of my problem may be wiewed in the mission briefing... I also tried to upload the full mission but the file is to big to upload here (5.16 MB). Any help will be apprisiated...Thanks Yes, I'm also seeing the problem- on the AI A-10's second target, he shares SPI on something off the map, and then flies around like a chicken with its head cut off. However, I don't think I should forward this mission to the devs, not in its current state- it has too much non-related stuff in it. I certainly don't want to forward it to them. Think of it this way: they are working on patches, adding new features to the game, working on DCS: Next, working on trying to support 3rd party modders, working on EDGE, etc.- so we need to make missions that illustrate bugs as simple as possible. And I'm working on Slmod, Mist, scripting engine testing, regular testing, helping people with scripts, etc. Before a bug can be fixed it must be known what is causing it. It's not uncommon for me to spend 1-4 hours just narrowing a bug down. So, I was curious if you could delete as much non-related stuff as you can- delete as many units, triggers, etc, from the mission as possible. Anything- trigger or unit- that doesn't have any relation to the actions of this AI pilot- get rid of it. You would probably know immediately off hand which components of the mission are related to this AI pilot, but I'd have to go through and figure out how the mission worked before I would. It would probably be a good idea to leave in the human A-10, as that lets you see when the AI starts referencing this weird SPI location. Edited January 29, 2013 by Speed Intelligent discourse can only begin with the honest admission of your own fallibility. Member of the Virtual Tactical Air Group: http://vtacticalairgroup.com/ Lua scripts and mods: MIssion Scripting Tools (Mist): http://forums.eagle.ru/showthread.php?t=98616 Slmod version 7.0 for DCS: World: http://forums.eagle.ru/showthread.php?t=80979 Now includes remote server administration tools for kicking, banning, loading missions, etc. Link to comment Share on other sites More sharing options...
repsol Posted January 29, 2013 Author Share Posted January 29, 2013 Hello again, Speed Thankyou for your assistance ! I have made a new short version of the mission...named (bug report version). I have edited the first post of this thread and attached both the origanal pictures and the short version of the mission as well as the new bug report version. In the bug report version i have removed the entire mission exept for the player A10, AI A10 and the first and second AI A10 targets... Hope this helps to find the problem Thanks Link to comment Share on other sites More sharing options...
Niehorst Posted April 27, 2013 Share Posted April 27, 2013 ...same problem with the A-10A Wingman... Just wanted to get back to the roots and move some mud without the targeting pod. Would be fun if my wingman would have the same intention. He only attacks air defences. But if he attacks at all, his target is a long range SAM far behind enemy lines or he heads back to "nowhere"...:cry: NZXT H400i case i9 9900k @ 4,9GHz (cooled by NZXT Kraken X62 4x140Fan - Push/Pull) Asus RoG Maximus XI Gene with 32GB G.Skill CL14 Samsung M.2 970Pro 1000GB ZOTAC RTX 2080ti Triple Fan 11GB 34" RoG Swift Curved TFT runs smooth like Beck's Gold :D HTC VIVE pro eYe (still freaking out!) Thrust Master HOTAS Warthog on MONSTERTECH table mounts 15cm Stick Extension + red spring by SAHAJ 8 (<-- love them) (TM F-18C ordered) TPR (Thrustmaster Pendular Rudder) T.Flight USAF Headset Link to comment Share on other sites More sharing options...
Recommended Posts