Hard Light Productions Forums
Community Projects => The FreeSpace Upgrade Project => Topic started by: KappaWing on October 23, 2008, 04:33:36 pm
-
Version: fs2_open_3_6_10r-20081023_r4911.exe
MediaVPs: 3.6.10
When an AI fighter is guarding a ship in an asteroid field, it destroys a threatening asteroid as it should, but, then it continues firing on into the empty space where the asteroid or asteroid fragments should be until the "object" leaves the field. Either that, or the AI just goes crazy on all asteroids and places where asteroids should be after the initial threatening asteroid is destroyed.
EDIT: Upon closer observation, it seems the AI will attack the space where the asteroid is supposed to be, had it not been destroyed, for eternity. In reality, this translates to a wing of ships shooting at a point in space that moves steadily further away from the mission area.
This is most certainly a mediaVP issue, as when I removed the mediaVPs, the mission ran fine with the AI behaving normally.
I hope this issue is resolved in the next MediaVP release, as progress on Relentless has ground to a halt due to this issue.
-
It could _possibly_ be a Mediavp mission error if it happened in a FS2 (or Port) Mission.
If it did not happen in a VP bugfixed version of a Retail mission though, or if the mission did not have AI Profile set to Retail, then it would be fairly difficult to pin point the culprit without some additional details by which to reproduce it and as a result, make sure that it get's fixed for the next release version.
If the problem is happening with your own mod missions (which are drawing on assets from the VP's, I would guess), it makes even less sense to believe it to be a VP bug without knowing what assets from the VP the mission in question is using.
And finally, is this the only build it happens in, or just the first one you noticed it in? Because it could just be a bit of buggery in the code, or that something previously broken is now fixed, but "work arounds" are now broken.
-
Y'know, I think I might've seen this in Procyon Insurgency, and maybe elsewhere.
-
If the problem is happening with your own mod missions (which are drawing on assets from the VP's, I would guess), it makes even less sense to believe it to be a VP bug without knowing what assets from the VP the mission in question is using.
Erm, I don't understand the rationale here. If I remove the VPs, the ai works fine. When I use the VPs, the ai is broken. I don't see how it could be anything other than the VPs.
Before trying this I used several nightly builds as well as the latest stable release. Still the same problem. This is not a mission-in-translation error. It was made by me, in the version of FRED that went with the build I was using.
The only AI profile I've ever had is "FS2 RETAIL", as it gives me no other options.
-
It sounds to me like they're chasing after an invisible fragment of the original roid - and the invisible roid thing has since been fixed on internal. :)
-
If you can make a very simple mission where ai demonstrates this behaviour and post it - that would probably help resolving the issue. Use only retail/mediavp ships. And if possible try to make it so that the problem is visible from the start.
-
If you can make a very simple mission where ai demonstrates this behaviour and post it - that would probably help resolving the issue. Use only retail/mediavp ships. And if possible try to make it so that the problem is visible from the start.
See attachment.
It sounds to me like they're chasing after an invisible fragment of the original roid - and the invisible roid thing has since been fixed on internal.
Cool! Lets hope the ai recognize this. I await the next mvp release to resume creating my mod. =)
[attachment deleted by Tolwyn]
-
Good catch. This would be pretty annoying to have in the final version.