AL Plugin : Deathmatch Arena Redux 1.3 30/6/08

[Dracklor]

Ok, thanks LV

[DemaeRamen]

I've noticed that this script always locks when I spot the first M3 now.


Anyone else see this?

[Mailo]

Yes, me. I sent LV a PM about this, he gave me the hint to check my codecs since this apparently causes locks, but after doing everything I could find, still no dice.
Although it not always happens upon the first M3.
My experience was that the M5 and M4 waves always work, and I have 1/3 chance to lock on the first M3, 1/3 on the first M6, and 1/3 running just fine.
(so far I have tried the wave after the M6 twice, ran once, locked up the second time.

At first I thought the freeze came with the playing of the sound sample "targeting ... falcon", but the last freeze came while trying the Extreme level, and here the sample played just fine, the freeze came roughly one second later during the spawning of the other M3s.

Also, these are the only lockups I have ever encountered in my X3, I guess if the sound was a problem, the freezes would occur also outside this script.

Too bad, this is my favorite script so far

[LV]

The codec idea didn't work

The problem here is every dm i do is fine all the way through, also i dont have everybody else saying the same problem, I know it exists but imo if my script was bugged it would be all or none if you understand me.

if you open plugin.dma.go and find set player tracking aim to $mark-> you can comment this out to stop it targeting the first new enemy class

comment out is . (full stop) comments back is , (comma)

once done, re-init script caches once

[Mailo]

I will try that, thanks a bunch.

Although ... that will make finding the next batch of ships a real pain ... I hope I'll find the line that removes scanners from my ship as well

And yes, I understand your problem, LV, debugging if noone is even sure the problem is on your end at all is nigh impossible.

Maybe patch 1.3 will help here, I hope the promised infos will come this weekend.

[Mailo]

grrr, ok, it is not the targetting command that causes the lockups.

I found the command and disabled it (the removing of scanners as well ), and rejoyced at first, because two dms went off just fine.

The last one froze again.

Brennans Triumpf, medium difficulty, 5th wave.
Thanks to triplex scanners I was able to view the spawn:
J
Khaak cluster
Falcon Vanguard (I guess, "Angreifer" in german)
Mamba Vanguard
Nova
Nova
Perseus
Perseus Vanguard
Perseus Sentinel ("Verteidiger" in german)

The last action I saw before the freeze was the breakup of the cluster.

I hope this helps.

P.S. I really really really hate enemies with mass drivers, they get me every time

[DemaeRamen]

That said the only freezes I saw before were in a wave with Khaak clusters.

When they split the game locked.

[NumNuts]

I've noticed that this script always locks when I spot the first M3 now.
Anyone else see this?

Yeah, me too! 3rd wave on medium setting = Hang and loop.
Only cheat I'm using is my ship is supercharged (NovaSentinal-MaxSpeed:536)
and Im running AL: Treasure Hunt, Escorts, Bounty Hunter & Race Responce Fleets & obviously DMA.

[LV]

I shall remove khaak clusters from the plugin, hopefully that may be the cause, patience please

99% on my tests are done pretty earlygame where i have no clusters to be scanned which does backup why i have no issue's.

[NumNuts]

if you open plugin.dma.go and find set player tracking aim to $mark-> you can comment this out to stop it targeting the first new enemy class

Is there another one down the script doing an auto set aim thing too?
set player tracking aim to $enemy ->

Is that relevant?

[DemaeRamen]

Does this mean it's ready to go now or you are going to do that at next release?

Not to be pushy or aught...

[LV]

Listen Numnuts

sorry couldn't resist
(LV wonders if he should ban himself for insulting another forum member)

yes you can but immiediatly before that line is

Code: Select all

skip if $aim != $anull

you need to comment out that also or your game will melt!

it will be ready once i get my bloody breakfast! D

[DemaeRamen]

If you're having trouble getting the food and running over it doesn't work try crouching on it or crouching and punching or....


TAXI!?

[NumNuts]

Thanks man.
I just wanted to know if it was relevant, I wouldn't know a $mark from a $enemy even if it killed me!
And I'm very lucky my game didn't melt while DMA was working!

[LV]

main download link updated to block all khaak clusters in new DM's (and still no food )

aim will still tag first new class as that did not appear to be the issue.

Code: Select all

$pname = [PLAYERSHIP] -> get pilot name

if $pname == 'DemaeRamen'
[PLAYERSHIP] -> destruct: show no explosion=[FALSE]
end

[NumNuts]

Well who know's........Same problem for me with new version.
Select "Experienced"
First two waves fine (auto target A-OK)
Third wave spawns (auto target locks), I hear "Mamba", then it melts - Freezes in loop. X3 not responding.
Who else is getting the lockup? and what do WE have in common?

[Mailo]

Yep, same here, select "experienced", got to fourth wave, hear "P", then freeze.

I will put in my triplex scanner again so that I have a chance of seeing the spawn, maybe that will give me ideas.

Although ... I just remembered I got a khaak cluster as a spawn on one of my first tries of the script, without a freeze. There it was a khaak cluster without any other M3s though.

Scripting question ... is it possible to name a ship after a number?
I tried the line
$mark = set name = $i (typed from memory, but close), but that didn't do anything.

Reason was I hoped to see if all ships of the wave spawn correctly before the freeze.

Edit: My savegame is after accepting an invitation to a deathmatch, but before actually jumping to the sector it is in ... might that have screwed up the install of the newest version of the script?

[LV]

Scripting question ... is it possible to name a ship after a number?
I tried the line
$mark = set name = $i (typed from memory, but close), but that didn't do anything.

depends what $i is, it worked for me why i did this a while ago

Edit: My savegame is after accepting an invitation to a deathmatch, but before actually jumping to the sector it is in ... might that have screwed up the install of the newest version of the script?

better to be completely fresh imo.

I have just this minute completed another full DM on Xtreme, no problems at all

[Mailo]

I finally managed to finish this one match that was giving me trouble up to the M1 wave ... and got a TL for my trouble. A TL with 1000 freight room, speed less than 100 that cannot dock anywhere

The next one also went off without a hitch, this time one step further than the M1 ... and I can only say ROFL ... I actually managed to kill about half of the wave with my Nova before succumbing to a M2 fully fitted with PSG, mass drivers and both types of flak guns in addition to the photon and plasma cannons.

But I noticed my game came pretty close to freezing during the larger spawns. How about leaving 0.5 or 1 second pauses between shipspawns?

The $i in my statement was from your code, the integer in the while-loop for ship spawning.

[NumNuts]

Hey LV, more Numnuts notes for ya!

Played with it again when I got home, this time I selected "Easy" (option 1) to see if I still got the lockup. I didn't, it ran fine, however once the M3 wave appeared I thought to check what Global scripts were running, to my surprise I saw "plugin.dma.medium", and thought that little bugger shouldnt be there...right??

Anyways, I ran the mission again but this time I deleted "plugin.dma.medium" from Global before I answered the experience level question, to which I replied "Experienced".
It was all go after that, M3's showed up, auto locked etc without a hitch.
Dont know if this helps but it seems to be the cause of my lockups, but I dont know how "plugin.dma.medium" got stuck in Global running fulltime.

@Mailo - you may want to check your Global list too, just in case.