[Lykurgos88]

Wow, thank you very much for fast replies! I'll proceed to try those.

EDIT: The new 3.7.1 SSE2 BP build fixed things Although I find it a bit inconvenient to use 3 different exes simply when switching between mods. The new 3.7.1 BP build is good ONLY for BP2, it doesn't add widescreen scaling to BP1, so I have to keep using Yarn's BP build with that. But yeah, this is really not a huge problem. Just very confusing to new BP players.

I think yous guys should definitely upgrade your BP complete installer executable. It still includes only 3.6.17 build.

[MachManX]

Right?  These guys make actual gaming companies look like the government when it comes to fixes.  Heck, comparing our fellow members to the government is an insult to our members.  You guys are awesome

I'll post a build using the latest BP release and Yarn's patch file.  Cool?

(If I am not allowed to post the build, then go ahead and delete it off my post or reply and I'll do it myself.  Don't want to get into trouble )

[AdmiralRalwood]

I think yous guys should definitely upgrade your BP complete installer executable. It still includes only 3.6.17 build.

I think they're waiting for a few outstanding bugs to be fixed (and possibly for the finished Erebus model) before doing a new complete installer. I don't think anyone would disagree that that 3.6.17 build needs to leave circulation (it has a known corruption bug).

[Lykurgos88]

Well, I have to revise my previous statement. The newest 3.7.1 BP build doesn't seem to work 100% perfectly. I get a CTD if (and only if) I try to play two missions in a row in Act 3. I can complete the campaign now (as opposed to the Yarn's BP build), but I still have to restart the game after every mission to avoid CTD. Still, not a game-breaking issue, but there seems to be something really odd going on with the Act 3.

[niffiwan]

What sort of crash are you getting?  I think I've been seeing something similar with playing any two missions in a row (i.e. non BP missions), possibly a dock-path assertion?

[DahBlount]

The same thing happens to me but only on occasion. I can guarantee it is not limited to BP though as it happens with almost any mod (Vanilla with MVPs, JAD, etc.) I have played with the newest builds.

[Lykurgos88]

What sort of crash are you getting?  I think I've been seeing something similar with playing any two missions in a row (i.e. non BP missions), possibly a dock-path assertion?

Crash to Desktop, as in "Freespace Open has made an illegal operation and must be closed". It happens when I press Commit after playing at least one mission previously. This has happened ONLY with BP2. BP1 didn't crash at all, nor has any of my 10+ mods crashed even once. BP2 just doesn't want to co-operate with me

I'll post a new fs2open.log, if anyone wants. I'll just have to get home first

[niffiwan]

sure, a log of the crash would be good.

Also, are you using a different executable for BP2 to all the other mods that didn't have problems?

[Lykurgos88]

At the moment I use 3 different exes:

- 3.7.1 BP build for BP2
- 3.7.1 BP Yarn's build for BP1
- 3.7.1 Yarn's Adaptable HUD build for everything else (+10 mods)

Only BP2 seems to give problems. Or specifically, WIH Act 3 seems to be the most problematic. Acts 1&2 crashed very rarely.

Here is a log file.

[attachment deleted by an evil time traveler]

[Echelon9]

At the moment I use 3 different exes:

- 3.7.1 BP build for BP2
- 3.7.1 BP Yarn's build for BP1
- 3.7.1 Yarn's Adaptable HUD build for everything else (+10 mods)

Only BP2 seems to give problems. Or specifically, WIH Act 3 seems to be the most problematic. Acts 1&2 crashed very rarely.

Here is a log file.

Hrmm, there's an Assertion in that log trigger the crash that time.

Code: [Select]

ASSERTION: "dock_list == NULL" at object.cpp:157
 dock_list should have been cleared already!
Int3(): From d:\fso\scp bp\code\globalincs\windebug.cpp at line 1040


[niffiwan]

That is the issue I thought I saw recently, I believe it is a recently introduced bug, possibly from r9995.  I'll have to run some tests to confirm that.

[niffiwan]

OK, the bug that was preventing you from playing two missions in a row should be squashed.  Could you please confirm that?  Simplest way to test would be to get the compatibility pack for BP & BP2, then grab the next nightly build that includes revision r10058 (it should be ready in a few hours).

If that issue is fixed, could you check to see if the Spinning Space Stations of Doom issue is fixed as well.  If it isn't please post another log. The debug executable should get a bit further before exiting and it'll (hopefully) give us some more info about the cause of that problem.

[Lykurgos88]

Tried some missions in a row with the Simulator and then proceeded to continue the Act 3 M05. So far, crashes and spinning are gone

While I can't promise that I don't run into new problems in the long run, I must say I'm very happy to see that things get updated and fixed so quickly. Even the 3d weapons selection GUi problem was fixed in the new build. I mean, it's truly amazing to see this old game getting the care it deserves. In the future, I might even volunteer as a beta-tester, in order to contribute to the overall effort even slightly. 

Just a small question, though. What are the specific features I'm missing out when using the compatibility vps? The opening post only referred something in the render code. I'd like to know more.

[Lykurgos88]

Okay, a new problem with the Act 3 Mi05 that I didn't notice before, since at first I just tested if those stations were gonna spin. The mission is quite difficult, but now it's even more difficult, since a horrible microlag starts right when I'm starting to destroy AWACS. The mission starts with a solid 60 fps, but after some point the game almost becomes unplayable, with 0,5 second freezes every 3 seconds. FPS is jumping from 60 to 0 like crazy.

[X3N0-Life-Form]

Just a small question, though. What are the specific features I'm missing out when using the compatibility vps? The opening post only referred something in the render code. I'd like to know more.

IIRC, you are missing shadows, a bumped up number of dynamic light sources and glowpoints being capable of emitting light.

[MachManX]

So niffiwan, using the normal build with the BP2 compatibility package is the same as using a BP2 build?  If that's the case then it would make things easier for me to apply the Yarn patch to the current build.

[AdmiralRalwood]

So niffiwan, using the normal build with the BP2 compatibility package is the same as using a BP2 build?

No, you miss out on

shadows, a bumped up number of dynamic light sources and glowpoints being capable of emitting light.

[Lykurgos88]

I have effectively hijacked this thread now, but I think I know what's causing those mysterious microlags (BTW they don't occur in any other mission so far). At some point, a single Cerberus turret warps millions of kilometers away from the battlefield. I completed the mission, even though it was tough with all the lagging, and I found the last hostile target far away:



I don't know how the engine works, but I think some object that far could confuse some process.

[The E]

It's weird to see that happen, but that shouldn't cause any issues. Far away objects are just that; they do not interact with anything.

[BritishShivans]

Holy ****. Millions of kilometers away? And why would there be a Alastor warping in, anyway? It connected to anything in the mission?