Mission 6 - Fields of Death Crashing

RedHotChiliDog
Field Marshal
Field Marshal
 
Posts: 2742
Joined: 14th Nov 2000
Location: Gahanna, Ohio

Postby RedHotChiliDog » Thu Feb 10, 2011 5:21 am

I had a hard time at this point in the mission at well. After my ship was crippled, I went into stealth mode and repaired as much as I could while letting my AI friends beat up on the Mirandas. I would occasionally drop out of cloak as a distraction to buy my AI allies some time and then went back under. I had actually found that the AI allies are actually quite good fighters and did most of the work for me.

So I would recommend hit and run tactics while letting your wingmen do the heavy lifting.
RedHotChiliDog

Klingons and Potato Chips are better with ridges.

brianmoler.com - Mission scripting and other strangeness

Vuikie
Warrior Recruit
Warrior Recruit
 
Posts: 70
Joined: 17th May 2002
Location: Netherlands

Postby Vuikie » Thu Feb 10, 2011 3:25 pm

Hmmm I think I remember this one.

Normaly I always go for the warp engines as sub target, but I believe I went for the impulse 1st this time, then take out their sensors. After that it's easy pickin'. Also target 1 of them then order 1 of your escorts to attack your target, then switch target and order the other on that 1 and you head for the last one. Most of the time this will keep the others off your tail and grind you up from behind while you try and cripple the one you are tailing.

This is how I did it if I can remember correctly, but mind me I did the missions 10 years ago!

gr,

Arjan.
Cry whoe, destruction, ruin and decay. And worst of it is death... and death will have it's day.

Image

Dater
Elite Warrior
Elite Warrior
 
Posts: 212
Joined: 23rd Jun 2003
Location: Germany

Postby Dater » Fri Feb 11, 2011 12:00 am

Ok thanks guys! I will try it again in an hour. Oh an I installed the fixed script anyways. Dont want it to crash when I just finished the mirandas! ;)
Although I believe it would happen much earlier from what I read...
Dater: "Yeah, Teeth. Thanks for pushing me into a black hole!"

Image

RedHotChiliDog
Field Marshal
Field Marshal
 
Posts: 2742
Joined: 14th Nov 2000
Location: Gahanna, Ohio

Postby RedHotChiliDog » Fri Feb 11, 2011 3:08 am

Hope this goes smoothly for you with the fix. If you still crash, send me your log file and I will see if there is anything else that needs tweaked.
RedHotChiliDog

Klingons and Potato Chips are better with ridges.

brianmoler.com - Mission scripting and other strangeness

CISNDestroyer
Warrior Recruit
Warrior Recruit
 
Posts: 11
Joined: 14th Apr 2009
Location: Germany

fixed script don't work...

Postby CISNDestroyer » Thu Mar 10, 2011 7:13 pm

I have tested your fixed script and i have the Crash-bug.
I played the mission linear from a-to-z.
Here is a copy of the log:

...
KA:0:Hooking GNW.
KA:0:IKS Hijo OK to warp out - warp ready tests succeeded!
KA:0:IKS deHup OK to warp out - warp ready tests succeeded!
KA:0:USS Ranger given plan FightPlan
KA:0:MC: Chosen plan is FlyToDistantShipPlan for agent USS Ranger
KA:0:USS Salazar given plan FightPlan
KA:0:MemoryFile::ReadFromFile pathname ships\FCA filename FCAKCCP
KA:0:Reading file ships\FCA\FCAKCCP.mem
KA:0:(4) Something wrong reading memoryfile - exiting MemoryFile::ReadFromFile with failure
KA:0:New MemoryPlanNode created for node HighSpeedPotShotsFromDistancePlan
KA:0:MC: Chosen plan is FlyToDistantShipPlan for agent USS Salazar
KA:0:IKS Ngov OK to warp out - warp ready tests succeeded!
KA:0:IKS chetopoy OK to warp out - warp ready tests succeeded!
KA:0:RESTARTing since MandateSearchForCloakedShipWhileFighting true for USS Ranger vs IKS Lon Tul frame 29383
KA:0:MC: Chosen plan is FlyToDistantShipPlan for agent USS Ranger
KA:0:RESTARTing since MandateSearchForCloakedShipWhileFighting true for USS Ranger vs IKS Lon Tul frame 29385
KA:0:MC: Chosen plan is FlyToDistantShipPlan for agent USS Ranger
KA:0:RESTARTing since MandateSearchForCloakedShipWhileFighting true for USS Ranger vs IKS Lon Tul frame 29387
KA:0:MC: Chosen plan is FlyToDistantShipPlan for agent USS Ranger
KA:0:RESTARTing since MandateSearchForCloakedShipWhileFighting true for USS Ranger vs IKS Lon Tul frame 29389
KA:0:MC: Chosen plan is FlyToDistantShipPlan for agent USS Ranger
KA:0:RESTARTing since MandateSearchForCloakedShipWhileFighting true for USS Ranger vs IKS Lon Tul frame 29391
KA:0:MC: Chosen plan is FlyToDistantShipPlan for agent USS Ranger
KA:0:RESTARTing since MandateSearchForCloakedShipWhileFighting true for USS Ranger vs IKS Lon Tul frame 29393
KA:0:MC: Chosen plan is FlyToDistantShipPlan for agent USS Ranger
KA:0:RESTARTing since MandateSearchForCloakedShipWhileFighting true for USS Ranger vs IKS Lon Tul frame 29395
KA:0:MC: Chosen plan is FlyToDistantShipPlan for agent USS Ranger
KA:0:RESTARTing since MandateSearchForCloakedShipWhileFighting true for USS Ranger vs IKS Lon Tul frame 29397
KA:0:MC: Chosen plan is FlyToDistantShipPlan for agent USS Ranger
KA:0:RESTARTing since MandateSearchForCloakedShipWhileFighting true for USS Ranger vs IKS Lon Tul frame 29399
KA:0:MC: Chosen plan is FlyToDistantShipPlan for agent USS Ranger
KA:0:RESTARTing since MandateSearchForCloakedShipWhileFighting true for USS Ranger vs IKS Lon Tul frame 29401
KA:0:MC: Chosen plan is FlyToDistantShipPlan for agent USS Ranger
KA:0:RESTARTing since MandateSearchForCloakedShipWhileFighting true for USS Ranger vs IKS Lon Tul frame 29403
KA:0:MC: Chosen plan is FlyToDistantShipPlan for agent USS Ranger
KA:0:RESTARTing since MandateSearchForCloakedShipWhileFighting true for USS Ranger vs IKS Lon Tul frame 29405
KA:0:MC: Chosen plan is FlyToDistantShipPlan for agent USS Ranger
KA:0:RESTARTing since MandateSearchForCloakedShipWhileFighting true for USS Ranger vs IKS Lon Tul frame 29407
KA:0:MC: Chosen plan is FlyToDistantShipPlan for agent USS Ranger
KA:0:RESTARTing since MandateSearchForCloakedShipWhileFighting true for USS Ranger vs IKS Lon Tul frame 29409
KA:0:MC: Chosen plan is FlyToDistantShipPlan for agent USS Ranger
KA:0:RESTARTing since MandateSearchForCloakedShipWhileFighting true for USS Ranger vs IKS Lon Tul frame 29411
KA:0:MC: Chosen plan is FlyToDistantShipPlan for agent USS Ranger
KA:0:RESTARTing since MandateSearchForCloakedShipWhileFighting true for USS Ranger vs IKS Lon Tul frame 29413
KA:0:MC: Chosen plan is FlyToDistantShipPlan for agent USS Ranger
KA:0:RESTARTing since MandateSearchForCloakedShipWhileFighting true for USS Ranger vs IKS Lon Tul frame 29415
KA:0:MC: Chosen plan is FlyToDistantShipPlan for agent USS Ranger
KA:0:RESTARTing since MandateSearchForCloakedShipWhileFighting true for USS Ranger vs IKS Lon Tul frame 29417
KA:0:MC: Chosen plan is FlyToDistantShipPlan for agent USS Ranger
KA:0:RESTARTing since MandateSearchForCloakedShipWhileFighting true for USS Ranger vs IKS Lon Tul frame 29419
KA:0:MC: Chosen plan is FlyToDistantShipPlan for agent USS Ranger
KA:0:ERROR: no plan selected below node FightPlan
KA:0:Error EPG006a: null current node found at plan node FightPlan.
HW:Deinitializing DX9 emu

If you need, i can send you a pm with the complete log.

Thanks.

RedHotChiliDog
Field Marshal
Field Marshal
 
Posts: 2742
Joined: 14th Nov 2000
Location: Gahanna, Ohio

Postby RedHotChiliDog » Fri Mar 11, 2011 3:37 am

Hmm, this is interesting. Looks like another 'variable' situation causing this to happen. Which system did you experience the crash?
RedHotChiliDog

Klingons and Potato Chips are better with ridges.

brianmoler.com - Mission scripting and other strangeness

CISNDestroyer
Warrior Recruit
Warrior Recruit
 
Posts: 11
Joined: 14th Apr 2009
Location: Germany

Postby CISNDestroyer » Fri Mar 11, 2011 6:29 am

KA. crashes in Regula system, shortly after warp in.

Gordon Finlay
Elite Warrior
Elite Warrior
 
Posts: 238
Joined: 14th Nov 2000
Location: San Diego, CA, USA

Postby Gordon Finlay » Fri Mar 11, 2011 7:01 am

That's the same problem I'm having in the last mission.

KA:0:ERROR: no plan selected below node FightPlan
KA:0:Error EPG006a: null current node found at plan node FightPlan.


appears to be fatal, causes KA crash.

I'm half-tempted to just re-script k25 to make all the enemies warp to me and have one big epic battle to settle the question of ascession right there. ;)

Dater
Elite Warrior
Elite Warrior
 
Posts: 212
Joined: 23rd Jun 2003
Location: Germany

Postby Dater » Fri Mar 11, 2011 9:10 am

HAHAHA! Make it multiplayer and I am sure we will battle on your side!! ;)
For glory and honor!
Dater: "Yeah, Teeth. Thanks for pushing me into a black hole!"

Image

RedHotChiliDog
Field Marshal
Field Marshal
 
Posts: 2742
Joined: 14th Nov 2000
Location: Gahanna, Ohio

Postby RedHotChiliDog » Mon Mar 14, 2011 4:54 am

Thanks for the additional information. Will look to see what other AI commands that I may have missed in the first pass that are causing this.
RedHotChiliDog

Klingons and Potato Chips are better with ridges.

brianmoler.com - Mission scripting and other strangeness

Gordon Finlay
Elite Warrior
Elite Warrior
 
Posts: 238
Joined: 14th Nov 2000
Location: San Diego, CA, USA

Postby Gordon Finlay » Tue Mar 15, 2011 12:42 am

Seems to me it's a lack of AI commands that are causing it to explode. Or getting an order with a null parameter possibly.

Annoying, since we have no control over AI. :/

RedHotChiliDog
Field Marshal
Field Marshal
 
Posts: 2742
Joined: 14th Nov 2000
Location: Gahanna, Ohio

Postby RedHotChiliDog » Tue Mar 15, 2011 3:54 am

I am presuming this has something to do with AI orders being issued against enemies that are in other systems or have not completely come out of warp. The time delay that I used for a temporary fix appears to have only corrected some of this since there are still those who are running into the issue. I may have missed something in that system that needs to be tweaked as well due to a timing issue.
RedHotChiliDog

Klingons and Potato Chips are better with ridges.

brianmoler.com - Mission scripting and other strangeness

CISNDestroyer
Warrior Recruit
Warrior Recruit
 
Posts: 11
Joined: 14th Apr 2009
Location: Germany

Fixed Mission Script - Please test and report

Postby CISNDestroyer » Tue Mar 15, 2011 11:00 am

Hello,

I think i have found the issue for the mission 6.
here you can download the english version: http://minecraft-cisn.dyndns.org:8080/k06x_eng.rar ,

and here the german version: http://minecraft-cisn.dyndns.org:8080/k06x_ger.rar

of me fixed script.
Extract the archive in KA-dir\Scripts, if the scripts folder does not exist, greate one.

Please tell me if an issue exist.
Last edited by CISNDestroyer on Fri Oct 12, 2012 7:50 pm, edited 1 time in total.

Parias
Warrior Recruit
Warrior Recruit
 
Posts: 12
Joined: 18th Dec 2000

Postby Parias » Wed Mar 16, 2011 1:51 am

So just dump this into a newly-created /scripts folder where Klingon Academy is installed?

Just gave this a spin but still hit the symptoms; as soon as I dropped out of warp in the Regula system, I had long enough to lock onto my first target before the mission immediately crashed (I'd assume the point where the rest of the fleet starts warping in), so no luck here I'm afraid =\

CISNDestroyer
Warrior Recruit
Warrior Recruit
 
Posts: 11
Joined: 14th Apr 2009
Location: Germany

Postby CISNDestroyer » Wed Mar 16, 2011 3:08 am

[quote="Parias"]So just dump this into a newly-created /scripts folder where Klingon Academy is installed?

Just gave this a spin but still hit the symptoms]

Yes, place the File from the archive here in:
Image

I have the fixed script testet several times.
Do you follow the mission linear?
Sorry for me bad english, i come from germany.

Please report, if the problem still exist i will change the script a bit more.

P:S.: Please post the last 10 lines of the d3demu.log here, thanks.

regarts Michael

RedHotChiliDog
Field Marshal
Field Marshal
 
Posts: 2742
Joined: 14th Nov 2000
Location: Gahanna, Ohio

Postby RedHotChiliDog » Wed Mar 16, 2011 3:41 am

While I have never been able to reproduce the crash myself, I tested the English version of your script to see if there were any issues. I did not run into any problems running your patched script so it seems to work well in my situation.

Thanks for helping in trying to tackle this interesting crash. With the results varying by system configuration and the lack of being able to reproduce the crash myself I definitely welcome any attempts to help fix this issue!
RedHotChiliDog

Klingons and Potato Chips are better with ridges.

brianmoler.com - Mission scripting and other strangeness

Parias
Warrior Recruit
Warrior Recruit
 
Posts: 12
Joined: 18th Dec 2000

Postby Parias » Fri Mar 18, 2011 10:15 am

CISNDestroyer wrote:I have the fixed script testet several times.
Do you follow the mission linear?

Please report, if the problem still exist i will change the script a bit more.

P:S.: Please post the last 10 lines of the d3demu.log here, thanks.

regarts Michael


Hah - just tried the mission a second time with the script, but hit the same crash at the same spot. I do indeed follow the mission in a linear manner]1.17[/url] build of KA).

However I actually just tried the mission again with RedHotChilliDog's fix from page 3 - reading another tip in the thread, I also stopped and let the rest of the strike fleet warp from Janus to Regulus. This time I averted the crash - however, after killing everything, the objective to destroy the Regula station cleared, but the objective to destroy all targets remained even though there was nothing left. I'd have blamed this on an enemy ship getting lost somewhere or something if it wasn't for this constantly appearing in the logs (now that I have debugging turned on);

Code: Select all
KA:0:There are no targets available in this system.
KA:0:There are no targets available in this system.
KA:0:There are no targets available in this system.
(Etc, etc)


I'm not sure if that's just from me pounding the "target nearest enemy" button or some AI component looping because there weren't any enemies left though. I'll give the mission another spin and see if it happens again.

Parias
Warrior Recruit
Warrior Recruit
 
Posts: 12
Joined: 18th Dec 2000

Postby Parias » Sat Mar 19, 2011 12:47 pm

Aha, worked this time - blew away everything in the Regula system and the objectives all cleared, so it was just a fluke - then of course I made the grave mistake of telling the freighter to hide in the Janus-system planetary rings. Woops, forgot about the huge rocks whipping around inside of there.

In any case, this mission seems to be working great now - thanks for the fix!

Dater
Elite Warrior
Elite Warrior
 
Posts: 212
Joined: 23rd Jun 2003
Location: Germany

Postby Dater » Sat Mar 19, 2011 1:04 pm

Good to know Parias. I tried this mission multiple times already but didn't beat it yet. Any suggestions? On which difficulty level are you playing? Last time the AI beamed security officiers onboard my ship and.. errm... well... after they destroyed my warp core, impulse and weapons I ran out of options...
Dater: "Yeah, Teeth. Thanks for pushing me into a black hole!"

Image

CISNDestroyer
Warrior Recruit
Warrior Recruit
 
Posts: 11
Joined: 14th Apr 2009
Location: Germany

Postby CISNDestroyer » Sat Mar 19, 2011 6:16 pm

Parias wrote:Hah - just tried the mission a second time with the script, but hit the same crash at the same spot. I do indeed follow the mission in a linear manner]1.17[/url] build of KA).

However I actually just tried the mission again with RedHotChilliDog's fix from page 3 - reading another tip in the thread, I also stopped and let the rest of the strike fleet warp from Janus to Regulus. This time I averted the crash - however, after killing everything, the objective to destroy the Regula station cleared, but the objective to destroy all targets remained even though there was nothing left. I'd have blamed this on an enemy ship getting lost somewhere or something if it wasn't for this constantly appearing in the logs (now that I have debugging turned on);

Code: Select all
KA:0:There are no targets available in this system.
KA:0:There are no targets available in this system.
KA:0:There are no targets available in this system.
(Etc, etc)


I'm not sure if that's just from me pounding the "target nearest enemy" button or some AI component looping because there weren't any enemies left though. I'll give the mission another spin and see if it happens again.


OK, i wil try to find a another way to prevent the crash.
(sorry for le late answer)

PreviousNext

Return to Mission Scripting

cron