[Iss Mneur]

With using 2D sound only, I get a drop in music volume during action (I've noticed this so far in stock FS2 and in Ancient-Shivan War). Still have incomplete afterburner sounds in stock FS2.

With my build that I linked or with the builds in the OP?

Lastly, I don't know if it's addressed, but in all builds of .14 I checked so far, capital ships don't exactly blow up like they did in .12 (as in the ship model makes a duplicate, the two models separate upon exploding/sending shockwaves, and after about five to seconds after the explosion, I can see ship debris).

Make sure you have the correct shaders.

Thankfully, .14 doesn't crash on my laptop when it's in projector-only mode (checked with my old Dell flat panel and my HDTV)... yet. It does love to crash when I'm using my natural laptop screen....

A log of the crash....?  Please?

[NFSRacer]

You'll have to forgive me as it's been ages since I've messed about with FS2 SCP, but with this latest release, is there a downloader that I can get my hands on like what was provided for 3.6.12 and earlier?  If not, is there a link for the entire package including the wxLauncher for Windows?  Again, I've been out of touch with the community for so long, I need to update my game now, and I've not the slightest clue as to what to do any more since it seems the entire installation of the SCP has changed.

[Satellight]

Simply follow THIS GUIDE.

Manual installation FTW  !

[NFSRacer]

Yeah, that guide didn't exactly do anything different for me.  I just want the latest release for MediaVP files and the launcher and EXE release, really.  Is there anyway to update the game?

[Commander Zane]

Step six in that manual installation guide is where the latest MediaVP files are, and you're getting the latest Launcher and .exe from this very thread.

[Goober5000]

Yeah, that guide didn't exactly do anything different for me.  I just want the latest release for MediaVP files and the launcher and EXE release, really.  Is there anyway to update the game?

Something like that is being worked on, but for now, manual is your best option.

[jr2]

Is there anyway to update the game?

Something like that is being worked on, but for now, manual is your best option.

Any chance of a public alpha or beta?

[Goober5000]

Soon, but the part that actually updates isn't complete yet.

[NFSRacer]

Soon, but the part that actually updates isn't complete yet.

Okay, well, that answers another question I had.  I guess the 3.6.12 installer is still valid for now?

[Rodo]

This popped up when trying to enter the weapons selection on the very first mission of FS2 retail campaign.

Code: [Select]

Assert: model_num >= 0
File: modelread.cpp
Line: 2843

ntdll.dll! ZwWaitForSingleObject + 21 bytes
kernel32.dll! WaitForSingleObjectEx + 67 bytes
kernel32.dll! WaitForSingleObject + 18 bytes
fs2_open_3_6_14_RC7_DEBUG.exe! <no symbol>
fs2_open_3_6_14_RC7_DEBUG.exe! <no symbol>
fs2_open_3_6_14_RC7_DEBUG.exe! <no symbol>
fs2_open_3_6_14_RC7_DEBUG.exe! <no symbol>
fs2_open_3_6_14_RC7_DEBUG.exe! <no symbol>
fs2_open_3_6_14_RC7_DEBUG.exe! <no symbol>
fs2_open_3_6_14_RC7_DEBUG.exe! <no symbol>
fs2_open_3_6_14_RC7_DEBUG.exe! <no symbol>
fs2_open_3_6_14_RC7_DEBUG.exe! <no symbol>
fs2_open_3_6_14_RC7_DEBUG.exe! <no symbol>
fs2_open_3_6_14_RC7_DEBUG.exe! <no symbol>
fs2_open_3_6_14_RC7_DEBUG.exe! <no symbol>
fs2_open_3_6_14_RC7_DEBUG.exe! <no symbol>
kernel32.dll! BaseThreadInitThunk + 18 bytes
ntdll.dll! RtlInitializeExceptionChain + 99 bytes
ntdll.dll! RtlInitializeExceptionChain + 54 bytes

The game crashes and spews that.
playing with 3612mvps, will try to bypass weapon selection to see what happens. brb

edit:

ok ship selection also kills the process apparently with the same message.
mission runs just fine if I avoid those two options, noticed the doubled ets hud gauge and I get the dialogue / speech cut dry whenever firing the afterburner both already mentioned.

Have to go, I'll make some more runs in a few hours when I get back.

edit 2:

Never mind that, it's just a pilot file issue, with new pilot the problem goes away.
If anyone wants it for testing let me know.

[MachManX]

Wow, I just went through that changelog and even though I knew the devs were working on SCP, I never realized how much fixing you guys actually do per release.   For a game that was released in 1999 (I think), you guys sure are dedicated.  Moreso than freakin' paid devs for actual games (in which a lot of bugs go unfixed!).  This just gives me a new appreciation for all you do for the Freespace community and I thank you from the bottom of my gaming brain   

I think heart fits in somewhere but I don't know if it goes with gaming 

[Goober5000]

Thanks very much.

[Fr3z3r]

Lastly, I don't know if it's addressed, but in all builds of .14 I checked so far, capital ships don't exactly blow up like they did in .12 (as in the ship model makes a duplicate, the two models separate upon exploding/sending shockwaves, and after about five to seconds after the explosion, I can see ship debris).

Make sure you have the correct shaders.

This is the issue I'm having too - as described in detail in this thread. I've had it in 3.6.12 final and I was hoping it'd go away in 3.6.14, but no such luck. Using -no_glsl fixes it, but is hardly a solution.

Win7, Radeon HD6670, launcher 5.5g.

Any ideas?

[Iss Mneur]

Lastly, I don't know if it's addressed, but in all builds of .14 I checked so far, capital ships don't exactly blow up like they did in .12 (as in the ship model makes a duplicate, the two models separate upon exploding/sending shockwaves, and after about five to seconds after the explosion, I can see ship debris).

Make sure you have the correct shaders.

This is the issue I'm having too - as described in detail in this thread. I've had it in 3.6.12 final and I was hoping it'd go away in 3.6.14, but no such luck. Using -no_glsl fixes it, but is hardly a solution.

Win7, Radeon HD6670, launcher 5.5g.

Any ideas?

Please start by checking your graphics driver version. See Known Drivers to avoid.

[Fr3z3r]

Driver issue indeed, thanks very much!

[Deepstar]

This is my first 3.6.14 Release on my laptop. Because i'm playing many Community-Missions there.

I figured out, that 3.6.14 introduced a few errors and i'm surprised, that nobody noticed it before.



This is a screenshot from a mission of "Dante's Ascension", i have to scan the capital ships. No problem with 3.6.12, because the subsystems are scannable.




On every 3.6.14 RC' it's a complete different story. You can't fulfill this objective, because the subsystems are NOT scannable. I noticed this bug the first time during "Causualties of War 2", but thought, that was a fredding error there, but after i encountered the same problem here again, i look after it.

I can confirm the same bug also on my PC. Seems to be a general coding error.


Also my laptop introduced with 3.6.14 a graphical issue like this:


Every ship popped out of nowhere and fly through the subspace vortex. On the same method Ships leaving the Area. They fly through the subspace vortex and after that, they disappear completely.
Can't confirm this on my PC, so it looks like a problem with my graphic chip in my laptop. 3.6.12 do not have this problem, even if i use the current shaderfiles for 3.6.14. The same problem stays even if i disable the new 3.6.14 features named fxaa and soft particles. But maybe my graphic chip (GeForce 555M) is not fully compatible with 3.6.14?

[chief1983]

If your Nvidia drivers are up to date, you _shouldn't_ have any graphical issues specific to that card.  As far as I know.

[MatthTheGeek]

Also, until you play those missions with 3.6.12 and confirm the error didn't exist there (which nothing in your post indicates you did), you can't tell it is an error with 3.6.14. It might just be very old missions that could have broken for a multitude amount of other reasons, ranging simply from bad FREDing to recent MVP incompatibility.

[Deepstar]

If your Nvidia drivers are up to date, you _shouldn't_ have any graphical issues specific to that card.  As far as I know.

Yes, you are right. After i created a profile for 3.6.14 in the driver and select that the Game are only allowed to use the GeForce and not the integrated intel chip additionally, it worked

Also, until you play those missions with 3.6.12 and confirm the error didn't exist there (which nothing in your post indicates you did), you can't tell it is an error with 3.6.14. It might just be very old missions that could have broken for a multitude amount of other reasons, ranging simply from bad FREDing to recent MVP incompatibility.

I said, that i played the mission also in 3.6.12... look at the first screenshot and the sentence below :-).

I tested the Mission a few minutes ago even with Retail and 3.6.10 Builds (.10 without MVPs), like with 3.6.12 (i used the current MVPs and Shaders with it), there are no problems to scan the ships. With every RC-Build it is not possible (look Screenshot #2).

[Master_of_the_blade]

I was playing the scp version of Warzone(again) and i realized that neither the bombers were firing their bombs, nor the shivan warships were attacking fighters of the GTVA.