[Mr_Maniac]

Hello...
I start this Topic after I was smashed by the Enif Station in "The Sixth Wonder"...

Problem: The Mannheim (GTT Elysium) is docked on the Enif-Station...

In the Past that was only noticable because when it jumps out, it pulls the whole Station with it (very funny, somehow)...
But NOW... Well... I guess something shot at the Mannheim and it tried to evade/flee...
WHILE docked on the Station...
So the Whole Station spins around very fast and BAM! There goes Alpha 1... *OUCH!*

Maybe this is something to fix in the MediaVP 3.6.8 Beta?

It's funny, but if I get slammed, slashed and beaten by an ARCADIA... Well... Uhm...

Secondly... In some of the first missions, the Myrmidon is equipped with its Standard Primarys (Subach HL-7 and Prometheus R). But the Prometheus R isn't available in these missions...
That's only a little mistake but in one of these missions it brought my FS2_Open to CTD...

Maybe some people find other bugs in the missions...

[Cobra]

Home run!!

by your description, i'm imagining the arcadia as a giant bat with an elysium for a hand.

on a serious note, it's not a 3.6.8 vp problem, it's been there for a while now.

[Mr_Maniac]

Home run!!

by your description, i'm imagining the arcadia as a giant bat with an elysium for a hand.

Yes, indeed...
That's how it is... And WAM I'm splattered...

on a serious note, it's not a 3.6.8 vp problem, it's been there for a while now.

I know, but I didn't want it to get forgotten
Actually I tried to fix it myself... But this f****** Elysium just won't undock!


Oh... And inspired by this I made a few tests
One Argo - 7 Docking-Bays... Hmmm...
Dock one Argo with another and the other 6 Points... Elysiums (On both Argos)...
Then an Arcadia... Orion to the Big Ship Dockpoint and an Argo on the other... And 6 Argos on the Argo...
Next: Dock an Ulysses with an Ulysses... Looks like some sort of X-Wing...
Now dock an Ulysses with a Leviathan...
Last thing: One disabled Rakshasa...

Command the Argo on the Arcadia to attack the Rakshasa... The whole Arcadia with all the Argos and the Orion is now flyint to the Rakshasa (and attacking of course)...
Now I command one Elysium thats docked with the first Argo to attack the Rakshasa... The whole thing flys to the Rakshasa and attacks...
The double-Ulysses too..
Only the Leviathan-Ulysses Combination doesn't follow this order.. It just flys around... Doing nothing...

Okay.. When the Rakshasa is destroyed, I command the same ships to depart...
Argo-Arcadia-Orion: The Orion stays in space after the Argo-Arcadia warped out...

Argo(with 6 Elysiums)-Argo(also with 6 Elysiums): The Elysium pulls the two Argos out... But the 6 Elysiums on the second Argo stay in space...
But the Orion and the Elysiums ARE still docked with the Warped-Out Arcadia/Argo... So they're docked with nothing... But they're docked...
Confusing... A funny chaos...

Wah.. Look for yourself

EDIT:
Forgot to tell you which ships you should give orders to:
GTT Elysium 12 (For the Transport-Array)
GTT Argo (For the Arcadia-thing)
GTF Ulysses (Leviathan-Ulysses Combination)
GTF Ulysses 33 (The X-Wing Ulysses)

[attachment deleted by admin]

[starfox]

Sounds very...interesting, gotta try this out.

[Mr_Maniac]

Meep... New mission "Bug" found:
In "A flaming sword", the meson bombs don't have "special explosion"... They just explode like a normal ship (without shockwaves) and nothing happens...
No blast...

[Mr_Maniac]

Hi again...
Two little things:

First:
I think the Meson-Bombs are useing Fighter-Shockwaves... But these are not included in the MediaVPs 3.6.8 Beta...

Second:
I want to ask all other FS2_Open players (hopefully some of you read this) if they have the Problem with Enif-Station, too?
Or is it a Linux-/CVS-/Whatever-Issue?
According to Goober, this bug was already fixed in August/September 2005...

EDIT:
Okay.. I already figured it out.
It IS a Linux-Only-Bug!

[Goober5000]

EDIT:
Okay.. I already figured it out.
It IS a Linux-Only-Bug!

That seems highly improbable...

[WMCoolmon]

Are you running 64-bit Linux builds and 32-bit Windows builds?

[Mr_Maniac]

Nope
32-Bit Windows-Builds (from the Recent-Builds Forum)
32-Bit Linux-Builds (self-compiled, almost every day)

More Details:
My PC:
CPU: AMD Athlon Thunderbird 1.333 GHz
MoBO: ASUS A7V-133
GPU: GeForce 3 (Creative Labs, 64 MB DDR-RAM)
RAM: 512 MB Non-DDR RAM (Infineon, CL-2)

OS:
Gentoo Linux - Kernel 2.6.14
i686-pc-linux-gnu
gcc-3.4.5, glibc-2.3.5-r2
dev-lang/python:     2.4.2
sys-apps/sandbox:    1.2.12
sys-devel/autoconf:  2.13, 2.59-r6
sys-devel/automake:  1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r1
sys-devel/binutils:  2.16.1
sys-devel/libtool:   1.5.20
virtual/os-headers:  2.6.11-r2

OS2:
WinXP with SP2 and all patches...

[taylor]

I always remember the station doing that, but then I've been using the Linux version for a LONG time.  The icculus.org version does it to and that's just a port of retail.  I can't remember ever actually trying it under Windows since I originally played FS2 when it came out.  I fail to see how it's a Linux only bug, but it's certainly possible.  It does happen on both 32-bit and 64-bit builds so that's not the problem.  The other option is that it's really a code bug which just doesn't show up under Windows for some reason, maybe GCC triggers it where the MS compiler doesn't.

Either way I guess this will get pushed closer to the top of my debug list.

[taylor]

Yep, code bug.  It's a problem with a qsort() comparison function.  Basically two goals have the same priority, the same time (comments seem to think that can't/shouldn't happen), and since the comparison function doesn't allow for equals it ends up reverting to the previous goal.  This means that it's continuously in a dock->undock->dock->undock->dock->... loop.  If I allow to equal values in comparison then it properly undocks and proceeds to jump out, leaving the station in place.

I don't know if that fix has other issues though, another idea is to deal the similar times elsewhere, but now we know why it's happening.

And the comparison function is identical to the original source release so it hasn't changed.

[Goober5000]

Yep, code bug. It's a problem with a qsort() comparison function. Basically two goals have the same priority, the same time (comments seem to think that can't/shouldn't happen), and since the comparison function doesn't allow for equals it ends up reverting to the previous goal. This means that it's continuously in a dock->undock->dock->undock->dock->... loop. If I allow to equal values in comparison then it properly undocks and proceeds to jump out, leaving the station in place.

Wow.

Good sleuthing.

[taylor]

Haven't found anything bad yet with the comparison change.  This isn't really a docking problem but since docking and undocking is a multi-stage proceedure it is just more likely to occur there.  That means that about the only way this will be a problem is for initially docked ships with two (or more) initial goals with both having the same priority.  Guess it just needs to hit some CVS builds and then we can figure out if it has any negative impact.  I'll do that later tonight, assign the Mantis bug to myself, and then just keep a close eye on any reports of strange event behavior.

[Mr_Maniac]

Oh... While we at it

http://www.hard-light.net/forums/index.php/topic,37545.msg769606.html#msg769606

[StratComm]

That sounds like something wrong with either the weapon or ship's mass value, as the ship in question has rocketed off beyond FLOAT_MAX and is no longer "in mission".  There should never be a NAN on the display, especially not there.