[headdie]

because it was a retail bug and R is rarely used as it is.

I use it extensively.

R as in target the nearest little **** that is trying to rip my engines to shreds? I use it fairly often, usually when one of the AI manage to annoy me enough, which is fairly often....

[z64555]

He means using R to cycle through the nearest attacking targets, not to simply target nearest attacker. 

[chief1983]

Currently, it does the same thing as H, without cycling.

[headdie]

I thought H was supposed to target nearest enemy while R targets nearest ship attacking the player

[chief1983]

Yeah, except there's a bug that's been in since retail apparently, where it doesn't.

[mjn.mixael]

I never had issues with R targeting the guy shooting at me....

[chief1983]

Probably also happened to be the closest hostile to you.

[headdie]

Probably also happened to be the closest hostile to you.

depends if you hve just done a run on a warship or freighter/transport

[chief1983]

Something weird is going on with collisions. In Apocalypse, the Mentu and Deimos can be flown through by the player, and I reloaded the mission to make sure it wasn't a one-off. I tried to isolate to ship class, but the Deimos in Into the Maelstrom was quite solid. I haven't yet found the same issue in other missions. Reproducible with or without MediaVPs.

EDIT: Hmm... reproducible as far back as RC1, but not 3.6.12.

Can anyone else reproduce?

I can't reproduce this with retail assets on RC8, on OS X.  Tried the Deimos and Mentu.

[Goober5000]

I haven't tried colliding with ships, but I have also noticed that collisions seem buggy.  See this thread.

It seems to happen after I've played several missions.  I could be following a ship and blasting it full of lasers and missiles, but nothing registers, not even a shield hit.  However, exiting FSO and restarting seems to make collisions work again.

It occurs in both the 3.6.14 branch and trunk.  From its behavior, I'm guessing it's either a memory leak or a cache problem.

[z64555]

K I'm definitely getting some sort of error here and not a random fluke:

Post-RC6 builds (going to check RC7 in a bit) corrupt the mainhall animations, and sometimes leads to a CTD.

[mjn.mixael]

K I'm definitely getting some sort of error here and not a random fluke:

Post-RC6 builds (going to check RC7 in a bit) corrupt the mainhall animations, and sometimes leads to a CTD.

First: why are you reporting this without a log?

Second: I've seen no such mainhall corruption.

[Alan Bolte]

I don't think my problem is related to yours Goober. It's very reproducible. I've tried rebooting my computer and clearing the cache. I don't have another pilot file to try that's completed the campaign, but I'd be happy to try someone else's. I tried colliding with everything in the first three missions of the campaign, but so far they all collide. I'm not sure what else to do to isolate this.

It isn't that the ships are set no-collide or anything, weapons fire hits just fine, I can just fly through them. I can also fly through my wingmen in that mission.

The attached log is from RC7 because I forgot to download the debug build of RC8. I don't see anything, but perhaps someone else will.

[attachment removed and sold on the black market]

[Kobrar44]

Alan, I haven't checked RC7 or 8, but I've checked builds from 7737 to RC6, and 7737 is the last build without collision issues[which have been adressed in new collision code[which is having its own issues]]. You might want to confirm that.

[z64555]

K I'm definitely getting some sort of error here and not a random fluke:

Post-RC6 builds (going to check RC7 in a bit) corrupt the mainhall animations, and sometimes leads to a CTD.

First: why are you reporting this without a log?

Second: I've seen no such mainhall corruption.

Here's three!

Link to Mantis Ticket.

[attachment removed and sold on the black market]

[Qent]

Ships jumping in and out are visible behind the vortex for me. Is anyone else getting this? http://pastebin.com/tqqpP5Kn

[mralexs]

Hey, i'm getting the malloc error on diaspora now

Code: [Select]

Malloc Failed!

ntdll.dll! ZwWaitForSingleObject + 21 bytes
kernel32.dll! WaitForSingleObjectEx + 67 bytes
kernel32.dll! WaitForSingleObject + 18 bytes
fs2_open_Diaspora_R1.exe! <no symbol>
fs2_open_Diaspora_R1.exe! <no symbol>
OPENGL32.dll! wglSwapBuffers + 155 bytes
fs2_open_Diaspora_R1.exe! <no symbol>
fs2_open_Diaspora_R1.exe! <no symbol>
fs2_open_Diaspora_R1.exe! <no symbol>
fs2_open_Diaspora_R1.exe! <no symbol>


[chief1983]

Well, it doesn't use RC8, but we had already been looking into if this is a common issue that was in trunk and backported.  Some other Diaspora users have been reporting crashes too, but now that you've confirmed that you got a Malloc error we might be barking up the right tree after all.

[Alan Bolte]

Alan, I haven't checked RC7 or 8, but I've checked builds from 7737 to RC6, and 7737 is the last build without collision issues[which have been adressed in new collision code[which is having its own issues]]. You might want to confirm that.

Good call. I can reproduce the issue on 7761, but not on 7737.

So, best guess is, this doesn't do what we think it does:

   // Valathil - Reinitialize collision checks
   obj_remove_pairs(objp);
   obj_add_pairs(objp->instance);

[chief1983]

Slick catch there if that's the problem.  I can't make a Windows test build based on .14 at the moment, that removes those lines, but maybe someone else can.  Or Valathil might just want to take a closer look at his fix.