Unofficial, Untested (by PR) BugFixes
#22
Posted 01 February 2008 - 06:21 PM
NVM, downloading file now (forgot hehe)
PS: XML work really DOES make your eyes bleed.... but I do understand it!!!
Edited by Dane Kiet, 01 February 2008 - 06:37 PM.
One choice can change a life..........
One choice can change many lives.........
What's your choice?
#23
Posted 02 February 2008 - 08:08 AM
SpaceUnitsUtilities_CT-11_Space_Tug.xml:
<CategoryMask> Transport </CategoryMask>change it to:
<CategoryMask> fighter </CategoryMask>
Your AI will no longer retreat too easily as defender whenever large Starbases are present.
The problem was that starbases were spawning up to 5 squads of 12 tugs each, and 60 tugs were causing the AI to retreat to 'save the transports'. This is smart behavior when those 60 transports are carrying 60 teams of AT-AT's. Not so smart when they are base-defense tugs.
Edited by Dalmp, 03 February 2008 - 03:43 AM.
#25
Posted 02 February 2008 - 08:35 PM
Edited by Zarkis, 03 February 2008 - 08:13 AM.
#26
Posted 03 February 2008 - 03:41 AM
Ugh yes, I'm not sure how that happened. Category mask was the right tag to edit. Thank you, I'm glad you spotted it!EDIT: Didn't work for me when I set the ship class to fighter, but when I changed the <CategoryMask> the AI would not retreat.
I'll edit my post to reflect this if you can change it in your post please Hetter. Sorry for the inconvenience.
We just have to make shure that the AI does not start to build too many of them and send them on attack missions. Should be doable. Also, we don't want them as escorts for bombers, but they would be nice as escorts for big ships. Anyway, I will include that fix into my testing runs and see what happens.
I never thought of the AI deliberately building them as fighters. I was thinking of how the AI starbase uses them in battle but decided that that shouldn't be a big deal, given that it keeps them close to the base anyway most of the time. But you're right about that. Definitely the change is far better than the AI simply retreating on every world with a starbase (even if we have to remove tugs from the build list entirely), but there's probably a better way to do this.
Hmm.. I was thinking of setting it to frigate, but I wasn't sure how it would handle being placed in a 'frigate squadron'. Can we just create a new <CategoryMask> for the tug? It seems to be significantly more work (have to tie it into other xml's and lua's - and I'm not fully sure which files effect what), but it seems to be a more ideal solution - if possible.
Edited by Dalmp, 03 February 2008 - 06:20 AM.
#28
Posted 03 February 2008 - 05:45 PM
I never thought of the AI deliberately building them as fighters. I was thinking of how the AI starbase uses them in battle but decided that that shouldn't be a big deal, given that it keeps them close to the base anyway most of the time. But you're right about that. Definitely the change is far better than the AI simply retreating on every world with a starbase (even if we have to remove tugs from the build list entirely), but there's probably a better way to do this.
Hmm.. I was thinking of setting it to frigate, but I wasn't sure how it would handle being placed in a 'frigate squadron'. Can we just create a new <CategoryMask> for the tug? It seems to be significantly more work (have to tie it into other xml's and lua's - and I'm not fully sure which files effect what), but it seems to be a more ideal solution - if possible.
Won't be a problem. The tugs can be excluded from being build in the relevant scripts. My next AI beta will include that change already.
#29
Posted 04 February 2008 - 09:37 AM
But - Bombing Run exceptions on Skiprays.
Ouch.
I tried Phoenix's suggestion - (change Skiprays from Bombers to Fighters) - Didnt work
- So I tried setting Skiprays craft type as Bombers and changing 'Is Bomber?' to 'Yes' - Didn't Work
I looked a bit harder - and deleted 'Skipray Bombing Run' from LandBombingUnits - Didn't work.
I did spot one thing, however: The 'Skipray Bombing Run' needs the skipray.alo file and I couldn't find it in the Models.
In fact I couldnt find any skipray (or Gat-12) file in the PR Mod.
Could this be the problem? (I didn't see an ATR-6 alo file in the models either)
Obviously I couldn't check this. Hope this helps.
#30
Posted 08 February 2008 - 11:05 AM
No, it makes no difference. It doesn't even seem to care if you use "yes" and "true" interchangeably .The fixes for Reef Home and Strike class worked for me but for the bombing run exception fix when you change Bomber to fighter does it matter if I use caps or not because in some files Bomber is Capitalized while fighter is not. Like in the X-wing file it's <Ship_Class>fighter</Ship_Class> while in the skipray it's <Ship_Class>Bomber</Ship_Class>. Sorry if that is a stupid question but thought that was odd.
Ah, that makes sense. I'll have to go into the retreat script and use specific unit names instead of the transport mask.'AI retreats too easily' fix:
SpaceUnitsUtilities_CT-11_Space_Tug.xml:<CategoryMask> Transport </CategoryMask>change it to:<CategoryMask> fighter </CategoryMask>
The AI was still retreating even before I added the tugs though. I've found that it's no one thing that is hurting or helping the AI, but it's the sum of a number of different factors. For example, changing the AI combat power of the projectiles helped, changing the escort status of the ships helped, but neither give it the same capability as a player would.
That's why they were transports in the first place. Quick fix.I never thought of the AI deliberately building them as fighters.
See here.Can we just create a new <CategoryMask> for the tug?
Because I'm using the one from FoC. ATR is under "Gamma-class".I did spot one thing, however: The 'Skipray Bombing Run' needs the skipray.alo file and I couldn't find it in the Models.
In fact I couldnt find any skipray (or Gat-12) file in the PR Mod.
Could this be the problem? (I didn't see an ATR-6 alo file in the models either)
I thought others said that it had taken care of the bombing run exceptions though. You're sure there isn't another cause to your exceptions?
#32
Posted 11 February 2008 - 04:19 PM
Hi, I just realised I have only done tech tree fixes, so I tried to fix the scouting bug. But, I can't find the BasicOffensiveSpaceSet.... I went to goalfunctions, but it's not there......
Yah. that got me too. Did you fix it yet. I'm stuck
You can find link to that file in the first post of this thread, just below the fix.
Bye,
VÃtek
#37 Guest_Stieven_*
Posted 23 March 2008 - 01:01 PM
really nice mod by the way, but it feels to me like a demo mod to much if play GFFA, every time i play rebel or empire i get a crash, on easy at week 26 block 2 at normal at week 12 block 1 and hard at week 5, i dont think anyone can beat the game that fast lol. basicly it gives an exception error at those days saying something about violation in the file, i geuss Lotnik has that same problem, is there a fix for this or not?
#38
Posted 27 March 2008 - 10:01 PM
Hi Phoenix,
really nice mod by the way, but it feels to me like a demo mod to much if play GFFA, every time i play rebel or empire i get a crash, on easy at week 26 block 2 at normal at week 12 block 1 and hard at week 5, i dont think anyone can beat the game that fast lol. basicly it gives an exception error at those days saying something about violation in the file, i geuss Lotnik has that same problem, is there a fix for this or not?
I get the same errors in galactic mode. I have done every fix listed here so I don't get crashes during tactical space/land mode but something is screwy in galactic mode. I would try commenting out the CSA and fix the shared Rebel/Pirate worlds but I doubt I could do it without a tutorial and others whom have tried eventually got exception errors regardless. So obviously those aren't the droids we are looking for.
It does however sound like we may never get this resolved since I have yet to see anyone find the cause, and without a cause there is no chance of a fix.
#40
Posted 14 April 2008 - 01:59 AM
Reply to this topic
1 user(s) are reading this topic
0 members, 1 guests, 0 anonymous users