Jump to content

[REPORTED]Unable to make an Ural Grad to fire with the "fireatpoint" command


FONS

Recommended Posts

Hi, i am trying to make an Ural Grad to shoot at a certain point to give the battle more ambient.

 

I've read a post somewhere about a guy saying that first:

 

- give the ural the excellent skill

- give the ural the fireatpoint command under the triggered action section

- then create under "set rules of trigger" a trigger of (1 once - time more = 10 s - Ai group on)

 

As far as i understood, the grad group should be turned on 10 secs after mission start, and with the excellent skill, start firing 2 minutes before.

 

But even waiting more than 4 minutes after mission start, the ural is't even ready to fire, with his rocket bay, yet not aiming at the point.

 

I've also tried to use instead a zone trigger, to turn the ai on when a blue coalition plan enters a determined zone, but still the same.

 

Could someone help me with this?

 

 

 

EDIT: Ok, just found after a few days eating my head with this, that the fireatpoint isn't yet working after seeing some posts 3 years old with people saying that the fireatpoint is bugged, and just works for the artillery, not for MLRS launchers... gonna create another bug report to see if they finally fix this...


Edited by BIGNEWY

[sIGPIC][/sIGPIC]

 

System

CPU: i7 4790K GPU: Asus GTX 970 4Gb MOBO: Asus Z97 PRO RAM: 16Gb OS: Win10 x64

 

Link to comment
Share on other sites

Fire at point command not working for MLRS and Grad vehicles yet.

 

Have been a few days trying to make the fire at point command to work with a group of Grad Ural's without success.

 

Finally, today, i end up in a 3 year old bug report saying that the fire at point just works for artillery (SPH) and not for Grad/MLRS.

 

http://forums.eagle.ru/showthread.php?t=98110

 

So tried changing the Grad for Artillery and it worked...

 

Please, fix this soon, it's a more than 3 year old bug...

[sIGPIC][/sIGPIC]

 

System

CPU: i7 4790K GPU: Asus GTX 970 4Gb MOBO: Asus Z97 PRO RAM: 16Gb OS: Win10 x64

 

Link to comment
Share on other sites

  • ED Team

Just did a simple test with the Grad, fire at point, on excellent, started firing after 02:30 minutes.

 

This may be a question for the mission editor part of the forum, unless you feel there is a bug, in which case could you include a .miz as an example. Thanks

 

 

EDIT: No need to make a new thread we can do it here.

 

Can you include you .miz


Edited by BIGNEWY

smallCATPILOT.PNG.04bbece1b27ff1b2c193b174ec410fc0.PNG

Forum rules - DCS Crashing? Try this first - Cleanup and Repair - Discord BIGNEWY#8703 - Youtube - Patch Status

Windows 11, NVIDIA MSI RTX 3090, Intel® i9-10900K 3.70GHz, 5.30GHz Turbo, Corsair Hydro Series H150i Pro, 64GB DDR @3200, ASUS ROG Strix Z490-F Gaming, HP Reverb G2

Link to comment
Share on other sites

:doh:My bad, then i don't know what could i be doing wrong if the SPH fired and the MLRS not...

 

Sorry for not replying faster, haven't remembered this till now. I will upload the mission tomorrow morning asap. Thanks for your help.

[sIGPIC][/sIGPIC]

 

System

CPU: i7 4790K GPU: Asus GTX 970 4Gb MOBO: Asus Z97 PRO RAM: 16Gb OS: Win10 x64

 

Link to comment
Share on other sites

Just did a simple test with the Grad, fire at point, on excellent, started firing after 02:30 minutes.

 

This may be a question for the mission editor part of the forum, unless you feel there is a bug, in which case could you include a .miz as an example. Thanks

 

 

EDIT: No need to make a new thread we can do it here.

 

Can you include you .miz

 

 

Sorry for the delay. Got home an hour ago. I attached the mission. The group that has to fire is "Grad group 1", located at Kobuleti abandoned airfield. When i change said units for SPH they fire, but they won't being MLRS. I don't know if there's something else to do when the units are MLRS's...

 

Thanks for your help, if you need anything just tell me.

Exodus_Warfare_WW2-KW_Coop_V0.8.miz

[sIGPIC][/sIGPIC]

 

System

CPU: i7 4790K GPU: Asus GTX 970 4Gb MOBO: Asus Z97 PRO RAM: 16Gb OS: Win10 x64

 

Link to comment
Share on other sites

  • ED Team

I am looking now, I see you have it on a AI task push.

 

I was doing it with advanced way point action, which may be a work around for you for now.

 

We will continue to look into this, so thanks


Edited by BIGNEWY
  • Like 1

smallCATPILOT.PNG.04bbece1b27ff1b2c193b174ec410fc0.PNG

Forum rules - DCS Crashing? Try this first - Cleanup and Repair - Discord BIGNEWY#8703 - Youtube - Patch Status

Windows 11, NVIDIA MSI RTX 3090, Intel® i9-10900K 3.70GHz, 5.30GHz Turbo, Corsair Hydro Series H150i Pro, 64GB DDR @3200, ASUS ROG Strix Z490-F Gaming, HP Reverb G2

Link to comment
Share on other sites

Fire at point works, however there is a bug. If a stationary AI is given a target and the point they are aiming at is within a spot they aren't allowed to to shoot in, then the AI is supposed to move to get a valid shot. In the case of MRLS they generally can't shoot "over" the front of their own vehicle and must shoot to either side. Using Bignewy's mission file I simply rotated the vehicles 90 degrees to get them to shoot. In the attached screenshot the Grad in the foreground isn't shooting, while the background Grad will. So the bug is AI aren't moving to get a valid shot when they should be.

  • Like 1

The right man in the wrong place makes all the difference in the world.

Current Projects:  Grayflag ServerScripting Wiki

Useful Links: Mission Scripting Tools MIST-(GitHub) MIST-(Thread)

 SLMOD, Wiki wishlist, Mission Editing Wiki!, Mission Building Forum

Link to comment
Share on other sites

fireatpoint with zero radius results in no response from the grad group. Non-zero radius puts them to work, however I have only tried 250m and 150m ... if that is the case I don't think zero should be the default radius.

 

Note; tested in 1.2.16


Edited by eyusuf
Link to comment
Share on other sites

I am looking now, I see you have it on a AI task push.

 

I was doing it with advanced way point action, which may be a work around for you for now.

 

We will continue to look into this, so thanks

 

Ah ok thanks for your time. i will have a look at it asap.

 

Fire at point works, however there is a bug. If a stationary AI is given a target and the point they are aiming at is within a spot they aren't allowed to to shoot in, then the AI is supposed to move to get a valid shot. In the case of MRLS they generally can't shoot "over" the front of their own vehicle and must shoot to either side. Using Bignewy's mission file I simply rotated the vehicles 90 degrees to get them to shoot. In the attached screenshot the Grad in the foreground isn't shooting, while the background Grad will. So the bug is AI aren't moving to get a valid shot when they should be.

 

Aah man that makes too much sense xD. The Ural's with Grad i placed were almost pointing 12 'clock to the target i was giving to him with the fireatpoint. I mean the cabin was on the way and you are right, the missile banks were turned slightly off to the right when i think the objective was more to the left, where the cabin was... And yeah, they were static, so that can be the main reason.

Thanks for the info man.

 

 

fireatpoint with zero radius results in no response from the grad group. Non-zero radius puts them to work, however I have only tried 250m and 150m ... if that is the case I don't think zero should be the default radius.

 

Note; tested in 1.2.16

 

Never tried giving it a radius, because as far as i understood in the Manual, the radius command consists in establishing a radius where the AI will shoot randomly around it. Am i wrong?

[sIGPIC][/sIGPIC]

 

System

CPU: i7 4790K GPU: Asus GTX 970 4Gb MOBO: Asus Z97 PRO RAM: 16Gb OS: Win10 x64

 

Link to comment
Share on other sites

  • 5 years later...
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...